Set boot device path for fp@0,0 2

[gallows]

I need to set up devalias for the root and mirror disk. On other systems I could replace the sd with disk, but they were scsi devices (0,0 and (1,0). This 280R has them both on the same channel, fp@0,0. Can someone please tell me what I need to change to set up an alias for sds-root and sds-mirror disks? The device paths are:
ls -l /dev/dsk/c1t0d0s0 /dev/dsk/c1t1d0s0
lrwxrwxrwx 1 root root 70 Dec 1 21:04 /dev/dsk/c1t0d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf962121,0:a
lrwxrwxrwx 1 root root 70 Dec 1 21:04 /dev/dsk/c1t1d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf9616a7,0:a
#

Thanks,
gallows

 

[bfitzmai]

At the OK> Prompt:
nvalias root_disk /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf962121,0:a

nvalias backup_root /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf9616a7,0:a

setenv boot-device root_disk backup_root

 

[gallows]

Thanks bfitzmai!! I can't get to the ok prompt. Will this work?

eeprom "nvramrc=devalias sds-root /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf962121,0:a devalias sds-mirror /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf9616a7,0:a"

eeprom "use-nvramrc?=true"

tks,
gallows

 

[bfitzmai]

Gallows,
I don't think so... But, your approach looks pretty interesting. Nvalias is used to alias paths for specific devices like disks, cdrom, etc and stores them into nvram. The only time I have used nvramrc was to set drivers.

Here is some info I found on devalias:

You can alias a node to something like "harddisk". Or something similar. Keep in mind that the devalias command will not retain the device aliases after a system reset. Therefore, you should probably use the "nvalias" command to set the alias so it stores it to the nvramrc. This file is sourced by OpenBoot when you enter the console. The syntax is the same as the devalias command.

Reading this makes me think your approach may work. May-be Ken or daFranze could give you a better answer as to if your nvramrc approach will work.

It's going to come down to if the nvramrc script is run before the boot process looks for a boot-device.

 

[gallows]

I tried this on a v100 and it worked. I changed the dad@0,0 to disk@0,0 as shown below:

# ls -l /dev/dsk/c0t0d0s0 /dev/dsk/c0t2d0s0
lrwxrwxrwx 1 root root 38 Mar 19 21:19 /dev/dsk/c0t0d0s0 -> ../../devices/pci@1f,0/ide@d/dad@0,0:a
lrwxrwxrwx 1 root root 38 Mar 19 21:19 /dev/dsk/c0t2d0s0 -> ../../devices/pci@1f,0/ide@d/dad@2,0:a

# # eeprom "nvramrc=devalias sds-root /pci@1f,0/ide@d/disk@0,0 devalias sds-mirror /pci@1f,0/ide@d/disk@2,0"

Force nvram on boot:
# eeprom "use-nvramrc?=true"

I was able to say boot sds-mirror and it booted. Same with boot sds-root.
Now, with my original post above, BOTH devices are fp@0,0 - where as on the v100 I had dad@0,0 and 0,2. I can see how the system could differiante between 0,0 and 0,2, but not when both are 0,0. That is why I didn't even bother to try it. These are my production servers, and I don't have a clue of what I'm doing)

tks,
gallows

 

[bfitzmai]

Cool... Learned something new. Have you tried setting boot-device to the new alias and tried to automatically boot to the new device alias? At this point, I don't see why it wouldn't.

Thank-you for the star Gallows... And with your information, you should have one too.

 

[gallows]

Heck, you deserved the star. You answered my question quick and completely. Can't ask for more than that)
Yes, I can boot with the new alias.
Do you have any thoughts on how I can get this to work with the disks in my first post.. fp@0,0 ?

Where's that old German guy when you need him? )

 

[bfitzmai]

I don't see why your original paths wouldn't work. They are pointing to 2 separate targets (disks). Should work the same way as the dad drives.