Wellllllllllllllllllllllllllllllllllllllllllllll, here's how it goes!
After 2 days, lots of coke (a cola), and quite a bit of hair pulling it
comes down to this:
Solaris 2.6 upgrade installs a brand spanking new sd.conf file under
/kernel/drv. So, any modifications you might have made to you own personal
sd.conf file get shot to $&!^. Alright, not completely. It's at least
considerate enough to save your old one as /kernel/drv/sd.conf:2.5.1 but
that's not exactly the point, is it! The entry we had in our sd.conf file
allowed more than one lun for a particular target. Take that out and
you've got bupkiss.
Many, many thanks go to Sean <email@example.com> for all his help. He
stuck with me for 2 days, even though this is not his job, and got me going
in all the right directions. If not for him, I would've started from
Thanks to all who replied to "Upgrading 2.5.1 to 2.6 with a raw partition"
Jeffrey B. Davis
Arthur Darren Dunham
and to "Big trouble with upgrade and raw partition":
TSI Europe Helpdesk
Rick Hernandez (sort of)
This thread was "Upgrading 2.5.1 to 2.6 with a raw partition". Now it's a
Upgrade went pretty smooth, but looooooong. Took at least 3 days to
finish. Minor changes to autolayout (/usr was a little short on space) and
things went on their merry way. Until....
We go to start up Sybase, which was on the raw partition, and we get
initializing virtual device 14
cannot find /dev/rdsk/c1t1d1s2
and proceeds to do this for all slices on the raw disk. Format doesn't
show the disk, neither does prtvtoc. Not listed in /dev/md/rdsk either.
What's the scoop? Anyone? Need help quick on this one.
Thanks to all so far. Summary following a working database.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:51 CDT