My hard disk now shows some bad sectors. ef2fsck runs during boot, because the filesytem had a damage flag set. After a while, e2fsck terminates with a message which I have to translate back from German here: "unexpected error, please run e2fsck without -p or -a switch". Then the sytem boot continues. Reproducible: Always Steps to Reproduce: 1. use a fine drill bit to damage only some sectors of your harddisk 2. boot or reboot 3. watch out what e2fsck says Actual Results: "unexpected error, please run e2fsck without -p or -a switch" (not logged anywhere). System boot then continues normally. Expected Results: System boot should stop and system should enter maintenance mode. sys-apps/openrc-0.4.3-r1 gcc-Version 4.3.2 (Gentoo 4.3.2-r2 p1.5, pie-10.1.5) The problem could be also within the fsck rc script, but for some reasons I believe that e2sck returns zero along with this error.
Please post your "emerge --info".
Created attachment 188973 [details] output of emerge --info
I've created an upstream openrc bug for this issue to get some more eyes on it: http://roy.marples.name/projects/openrc/ticket/182
(In reply to comment #0) > The problem could be also within the fsck rc script, but for some reasons I > believe that e2sck returns zero along with this error. fsck would need to return a non zero value other than 1 and 8 for the boot to be interupted
please run the the fsck manually to see what the exit value actually is also, what was the exact message displayed at boot time by the init scripts ? that'll tell us the exit status of fsck.
(In reply to comment #5) > please run the the fsck manually to see what the exit value actually is > > also, what was the exact message displayed at boot time by the init scripts ? > that'll tell us the exit status of fsck. > Spanky, please take a look at the date of this bug report. Trying to answer your question five month later without a defective harddisk at hand and different releases installed everywhere is next to an impossible task without fsck having logged this error (which it didn't because the defective disk was the root partition). I don't think it's of any interest to run fsck today manually. I even don't remember the exact message today, end even if would it would be in German language. I'm just thinking about why I thoughtfsck then had returned zero. I think I concluded this from inspecting the boot rc, which is also different today.
i said "output of the init.d script", not "output of fsck". the output of fsck will be localized, but the output of the init.d script will not. the init.d script has seen fixes with other reports which might cover this one
(In reply to comment #7) > i said "output of the init.d script", not "output of fsck". the output of fsck > will be localized, but the output of the init.d script will not. Localized or not, I do not have this output, as I already explained above. > the init.d script has seen fixes with other reports which might cover this one > You may want to list the "fixes" of these ominous "other reports" which might also cover this one?
