On Tue, Nov 15, 2005 at 08:06:06PM -0500, Dennis Clarke wrote: > On 11/15/05, Jonathan Adams <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 15, 2005 at 04:49:31PM -0500, Dennis Clarke wrote: > > > On 11/15/05, Sean Wilcox <[EMAIL PROTECTED]> wrote: > > > > This is because the filesystem is mounted read/write, and there > > > > is no way for fsck to 100% guarentee that the fs is sane after it > > > > has been run, especially with the -Y option, on a fs that is mounted > > > > read/write due to possible modification that might have tripped up > > > > fsck's ability to track things correctly. > > > > > > > > The Statement that the FILE SYSTEM IS BAD is probably a little too harsh > > > > but the FS INCONSISTENT statement could be true. > > > > > > Well, the ability to boot so single user mode and then run fsck on the > > > current root slice seems to be something that I have done for a long > > > long time. I think I may have to consider that one must now boot from > > > some other media in order to be assured of fs sanity. > > > > You can always boot with '-m milestone=none', and run fsck from that > > environment; the root filesystem will be mounted read-only. > > Hold on .. do you mean from the ok prompt ? > > ok boot -m milestone=none > > as opposed to > > ok boot -sv > > hmmm fascinating ... let me try that right now.
Yes; it's a completely minimal boot, with nothing but init(1M), svc.startd(1M), svc.configd(1M), and sulogin(1M) running. When you are ready to bring the system up, you can do: # svcadm milestone all and exit the shell (or keep the shell, and watch the system come up by running svcs(1) over and over again). The console login prompt won't appear until you exit your shell. Cheers, - jonathan -- Jonathan Adams, Solaris Kernel Development _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
