Edward Middleton posted <4365CBC8.2080502@...>, excerpted
below, on Mon, 31 Oct 2005 16:46:16 +0900:
>>Only one issue now, and that is that upon shutdown, Gentoo cannot stop
>>/dev/md5 because it is in use.
>>Is there a fix for this? Perhaps in the order of the shutdown?
> hi Chris,
> Did you work out how to fix this. I am having exactly the same
> problem. I understand why it is happening (the root partition is still
> in use), but presumably there is some way of getting around this.
Well, normally the root partition /will/ still be in use, so can't be
unmounted. However, it's then mounted read-only, instead, forcing out all
cached writes to bring the fs into a consistent state and then allowing no
more writes to it after it's mounted read-only. Thus, the system can
still shut down even with it mounted.
The thing is, that's expected for your root partition, so it's normally
included in the init scripts to mount it read-only instead of unmounting
it, and for that one, it normally doesn't cause a warning, whereas for
others, it would (and should, in the general case, anyway).
The problem here is that for some reason the system apparently isn't
recognizing that partition as root, so it's still warning when it can't be
unmounted. As mentioned, it could be an order thing, or it could be that
particular raid or lvm config isn't setup correctly in the initscripts, so
it's not recognizing them as devices containing filesystems, at all.
In a few days, I'll have mine setup and be playing around with it, so may
or may not be able to confirm the issue then, but I expect to be able to
trace it if I do have it. (Note that I'm running ~amd64 and the
1.12.0-rc's of baselayout. I don't expect I'd be reverting to stable, if
the issue's happening there.)
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
firstname.lastname@example.org mailing list