Prev: SunRay with different displays
Next: The IP address previously set on the network interface is no longeravailable
From: ITguy on 22 Dec 2009 18:52
On Dec 22, 9:01 am, rocker <rocke.robert...(a)pwgsc.gc.ca> wrote:
> On Dec 21, 6:12 pm, ITguy <southa...(a)gmail.com> wrote:
>
> > > The thing is, if I install the OS via interactive jumpstart and use
> > > the SAN disk as the root disk, it reset's the boot-device to point to
> > > the SAN device. It boots happily. But if I install on the local disk
> > > and mirror the SAN disk, I'm shXt out of luck. Can't find a valid SAN
> > > device to boot off of. I find this odd.
>
> > That's odd...  You might try to update the boot device from Solaris
> > using "eeprom"?
>
> > If that doesn't work I'm out of ideas
>
> After a lot of guessing and looking at previous SAN boot paths and
> hacking I figured it out. A boot path looks like:
>
> /pci@8,700000/SUNW,qlc@2,1/fp@0,0/disk(a)w50060e8005476b01,0:a
>
> As an FYI, use the boot device path from show-disks:
>
> /pci@8,700000/SUNW,qlc@2,1
>
>  with this appended:
>
> /fp@0,0/disk@w
>
> Then this gets appended too:
>
> WWPN,0:a
>
> With the HDS LUN's appended, it looks like:
>
> 50060e8005476b11,0:a
>
> So once I hacked a boot path together, it looks like:
>
> /pci@8,700000/SUNW,qlc@2/fp@0,0/disk(a)w50060e8005476b11,0:a
>
> And this works now. I'm sure this is documented somewhere... Sheeesh.
>
> Sun, you should look at how HP's nPars and vPars boot off the san...
> Just a hint.


Is that the same path linked to the device name "/dev/dsk/cXtXdXsX"?
From: rocker on 23 Dec 2009 08:45
On Dec 22, 6:52 pm, ITguy <southa...(a)gmail.com> wrote:
> On Dec 22, 9:01 am, rocker <rocke.robert...(a)pwgsc.gc.ca> wrote:
>
>
>
>
>
> > On Dec 21, 6:12 pm, ITguy <southa...(a)gmail.com> wrote:
>
> > > > The thing is, if I install the OS via interactive jumpstart and use
> > > > the SAN disk as the root disk, it reset's the boot-device to point to
> > > > the SAN device. It boots happily. But if I install on the local disk
> > > > and mirror the SAN disk, I'm shXt out of luck. Can't find a valid SAN
> > > > device to boot off of. I find this odd.
>
> > > That's odd...  You might try to update the boot device from Solaris
> > > using "eeprom"?
>
> > > If that doesn't work I'm out of ideas
>
> > After a lot of guessing and looking at previous SAN boot paths and
> > hacking I figured it out. A boot path looks like:
>
> > /pci@8,700000/SUNW,qlc@2,1/fp@0,0/disk(a)w50060e8005476b01,0:a
>
> > As an FYI, use the boot device path from show-disks:
>
> > /pci@8,700000/SUNW,qlc@2,1
>
> >  with this appended:
>
> > /fp@0,0/disk@w
>
> > Then this gets appended too:
>
> > WWPN,0:a
>
> > With the HDS LUN's appended, it looks like:
>
> > 50060e8005476b11,0:a
>
> > So once I hacked a boot path together, it looks like:
>
> > /pci@8,700000/SUNW,qlc@2/fp@0,0/disk(a)w50060e8005476b11,0:a
>
> > And this works now. I'm sure this is documented somewhere... Sheeesh.
>
> > Sun, you should look at how HP's nPars and vPars boot off the san...
> > Just a hint.
>
> Is that the same path linked to the device name "/dev/dsk/cXtXdXsX"?- Hide quoted text -
>
> - Show quoted text -

Once the kernel boots yes it has to map to the device files as you
know. It sort of maps. But it uses sdd@ instead of disk@ in the
path.This has to be documented somewhere, it can't be that hard?

So the block device maps to the /devices/hardware path below. It's
similar to the boot string I had to use.

# ls -l
lrwxrwxrwx 1 root root 70 Dec 22
14:29c0t50060E8005476B11d0s0 -> ../../devices/pci@8,700000/SUNW,qlc@2/
fp@0,0/ssd(a)w50060e8005476b11,0:a

First  |  Prev  | 
Pages: 1 2 3 4
Prev: SunRay with different displays
Next: The IP address previously set on the network interface is no longeravailable