http://bugzilla.novell.com/show_bug.cgi?id=571528
http://bugzilla.novell.com/show_bug.cgi?id=571528#c4
T. Lingk changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|TLingk@vdsvossk.de |
--- Comment #4 from T. Lingk 2010-02-04 08:49:44 UTC ---
I currently do not remember the exact message of fsck, but it complained about
that the device to check was not present.
To avoid any misunderstandings, I would like to point out that the problem
occured with a fake raid but NOT with a software raid.
As you know, fake raids are managed by "dmraid" and software raids by "mdadm".
"dmraid" tends to map devices into /dev/mapper/, not into /dev/mdXX as mdadm
does!
In my case, fsck failed as noted above. When I entered the emergency console
and had a look into /dev/mapper, I could see that the device was there and a
MANUAL run of fsck succeeded without error. I think this is because dmraid was
already finished when I had the opportunity to look into /dev/mapper and run
fsck by myself but not yet when fsck was run by boot.localfs.
Meanwhile, I have reconfigured my system so that it is using mdadm and software
raid. This works without any problems for me. Obviously, only the
dmraid-toolchain is affected by this bug.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.