Solaris SVM: stuck in pre-maintenance mode · 9 April 2008, 21:52
I rarely have pleasant encounters with LVM/disksuite/SVM. Maybe that is because I just suck at Solaris :p. The problem this time:
- One disk of a set of mirrored root disks crashed
- I took the good disk to another system, mounted it, unencapsulated it from SVM (removed rootdev from /etc/system, re-created a slice-based /etc/vfstab).
- Fsck’d the /, /var, /usr, and /export partitions on the disk.
- Took the disk back to the original question, inserted it, from ALOM (this is a T2000) booted to single user mode.
All self-tests pass, then the system starts to boot from the disk .. it gets to the point where the Sun copyright message and kernel revision is displayed, then the following is displayed over and over in a loop:
Requesting Maintenance Mode
(see /lib/svc/share/README for more information.)
After breaking the boot process, and rebooting using boot -m debug, the following additional information is displayed:
INIT: Executing svc.startd
INIT: Restarting svc.startd
Requesting Maintenance Mode
(see /lib/svc/share/README for more information.)
Root console services are never started, svc.startd doesn’t dump core, or output messages in system logs, or output anything on STDOUT or STDERR.
Sun technicians are working with me to try to figure out what is causing svc.startd to die (boy does phone support NOT want to escalate a ticket to tier 3 .. they were suggesting I restore the system from backups rather than continue to help me figure out what is causing this (same thing is happening on two systems) .. frustrating!)
Will post more when I get a resolution to this (hopefully more than just “I restored from backups”).
— Max Schubert
Comment
Using SSL proxies with WWW::Mechanize - why doesn't my HTTPS proxy setting work? Sun Support Quote - Tier 2