Booting Tru64 when boot disk name changes

[Eileen McColley]

We are running 5.1B, testing on an ES40. Disks are connect to an HSG80 but eventually we will be moving the disks to a SAN to be managed by an IBM Storage virtualization manager. My original boot device is actually a drive in the array on that machine...kind of the 'local san' as opposed to booting from the local drive. When we put the disks behind the SVC and tried to boot, I received a boot error, the system came up in single user mode with what looks like a bare-bones root_device. I'm guess this happened because my boot device now has a different name and I'm getting 'unknown error in boot'. Can I still boot from my original boot device or do I have to copy / and /usr to the actual local drive and boot from there?

[Steven Schweda]

If it boots at all, the "/" file system can't
be totally defective.

Did you adjust the data in the new
"/etc/fstab" to accord with the new device
names and/or AdvFS domain names?

It might help to see the details of what was
where, and what's where now.

[Vladimir Fabecic]

Hello Eileen
Your device names changed.
Try (from single user mode)
# mountroot
Then do
# hwmgr -scan scsi
# hwmgr -show scsi
After seeing new device names you can "remap" them to "original names" with
# dsfmgr -e
example:
# dsfmgr -e dsk9 dsk0
Also check links in /etc/fdmns.
If need more, supply more informations.

[Vladimir Fabecic]

Another way is to change links in /etc/fdmns

[Shardha]

Dear Eileen,

Boot from the new device, it willl put you in single user mode. At this moment the / file system is in read only mode, to make it read/write mode, run
# mount -u /

Replace old links with new one on

/etc/fdmns/root_domain
/etc/fdmns/usr_domain
/etc/fdmns/var_domain

command is as follows (suppose you have a,g and h partitions for root,usr and var respetivily.

ln -s /dev/dsk/dsk10a
ln -s /dev/dsk/dsk10g
ln -s /dev/dsk/dsk10h

shutdown -h now
and boot the system. Hope fully it will work.