In the past I would often boot up into single user mode, manually
mount a bunch of filesystems read-write and then ^D later to
continue on.

With SMF, what I thought I should do is:

ok boot -m milestone=none
(login)
# mount -o remount /
# svcadm milestone all

However this causes filesystem/usr to report an error because
it can't run fsck.  Ok, I expected the solution to that to be:

# svcadm clear filesystem/usr

That restarted filesystem/usr and in doing so, I got the fsck
error again and found myself in a loop, that I eventually got
out of with a reboot.  The /usr filesystem is part of /.

I looked at filesystem/usr with svcs -x to see if there was
anything extra it was depending on and looked in the log
file but all to no avail.

What I wanted to do was tell SMF "ignore the problem with
filesystem/usr and mark it as online" (because it already was)
so that the system could continue through to "all".

What was I doing wrong here?

btw, this was with snv_44.

Darren


Reply via email to