I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled.
It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error.
Rebooting with command: boot -r
Boot device: /pci@1e,600000/pci@0/pci@2/scsi@0/disk@0,0:a File and args: -r
SunOS Release 5.10 Version Generic_120011-14 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hardware watchdog enabled
Hostname: ss071a
QLogic Fibre Channel Driver v4.20 Instance: 0
hba0: QLogic QLA2300 Fibre Channel Host Adapter fcode version 2.00.05 01/29/03
hba0: Firmware v3.3.12 (ipx)
QLogic Fibre Channel Driver v4.20 Instance: 2
hba2: QLogic QLA2300 Fibre Channel Host Adapter fcode version 2.00.05 01/29/03
hba2: Firmware v3.3.12 (ipx)
NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk
NOTICE: VxVM vxdmp V-5-3-1700 dmpnode 280/0x0 has migrated from enclosure FAKE_ENCLR_SNO to enclosure DISKS
ERROR: svc:/system/filesystem/usr:default failed to mount / (see 'svcs -x' for details)
Mar 25 18:15:36 svc.startd[7]: svc:/system/filesystem/usr:default: Method "/lib/svc/method/fs-usr" failed with exit status 95.
Mar 25 18:15:36 svc.startd[7]: system/filesystem/usr:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
I've been told that the IBM vpath drivers were installed in anticipation of the server being moved onto the new SAN, but there was no reboot carried out.
I have manually mounted the root plexes and removed the vpath drivers from /kernel/drv/sparcv9 but the damn thing won't boot.
I thought that as well at the begining of this, but the muppet that built this system didn't build a separate /usr file system it's all under the root fs.
The /etc/vfstab file is valid (I think, but messy) as far as I can see, just to let you know I have been called out on this system - the last time I worked on it was about 10 years ago when it was on an E10K.
is the content of /usr present? and is there a /usr/local directory present? can you login in single user mode? if yes what is the output of svcs -xv and what is in the logfile for the error?
This is quite interesting, it would seem that the pkgadd for the vpath IBM drivers has an interesting side effect. It over writes the /etc/system file (note over write and not append) with;
forceload: drv/vpathdd
All the stuff that was in there before is just trashed, recover the old file from tape and edit is the answer at the moment. This just goes to show that making changes to a live system and not going for a reboot, is just asking for problems!
This isn't unlike a question I answered the other day as far as the actual boot error is concerned. I advised to recreate the filesystem device paths.
The thread is here:-
Take a backup first. Perhaps the attachment of the SAN changes the device paths. The error that you posted seems to indicate it is having a problem with root!!!