Is this a T1000/2000 by chance?
If so, you might be running into a bug in the vxroot script. It's easy to
check -- on line 138 is the variable $bus_drivers quoted or not? If it's NOT
quoted, then you might have this bug affecting you. The fix it is as simple as
putting quotes around it like
Thanks Mike for your quick response. Yes, the systems are T2000s.
I checked the /etc/vx/bin/vxroot script, and it already has the quotes
around the $bus_drivers.
Sample Output:
vxroot:bus_drivers=`modinfo | grep PCI Bus nexus driver \
vxroot: if [ $? -eq 0 -a -n $bus_drivers ] ;
vxroot:
Hi All --
Here you go
usilsunvirtual06# raidctl -l
Controller: 0
Disk: 0.0.0
Disk: 0.1.0
usilsunvirtual06#
Thanks Brian for responding to my post.
=] -Original Message-
=] From: [EMAIL PROTECTED]
=] [mailto:[EMAIL PROTECTED] On
=] Behalf Of Brian Wilson
Darn, that would have the easy fix. I haven't seen a problem like this on our
T2000's.
When you say on the second reboot the system couldn't just come up what
exactly does it do at that point?
If you boot the system to CD or network and inspect the drives, how much of the
encapsulation is
Hi Asim,
Ever since sun started making/supporting hardware raid in T2000's, we
have stopped encapsulating our root disks on these hosts.
The last time I did encapsulate a root disk, it is on what I would call
a Gen 1 T2000. That is, the SATA controller is a card. This worked
well, and was with
