Will Hayworth writes: > After which it asked for my root password to get into maintenance > mode, which I provided. One of the prompts had recommended that I > run fsck, so I did, answering yes to every prompt, hoping that it > would be smart (forgive the inherent ignorance in this). But after > rebooting in normal mode, I still get that same prompt. Failsafe > boots reasonably, but I can't do anything useful in it.
The one useful thing you should be able to do in it is run "bootadm update-archive". You get into this state when there's a mismatch between the contents of the boot archive (used by GRUB) and the actual files on the disk. Rather than allowing the system to run (and potentially fly to bits in the process), it forces you into this failsafe mode to repair the problem. You always need to do "bootadm update-archive" after updating key things, such as device drivers. If you're doing that from the failsafe, you need to mount your normal root somewhere first, and use the "-R" option on bootadm. (The failsafe boot option _should_ walk you through this process. If it doesn't, then that sounds like a newboot [GRUB] problem. File a bug.) -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
