FS#17603 - [initscripts] On boot after improper shutdown, no automatic device check any more

Attached to Project: Arch Linux
Opened by scippio (scippio) - Friday, 25 December 2009, 12:23 GMT
Last edited by Tom Gundersen (tomegun) - Monday, 28 March 2011, 12:32 GMT
Task Type Bug Report
Category Initscripts
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
On boot after improper shutdown, no automatic device check any more

Additional info:
citation:
"Several times I have to shut down with the hardware because of the f**king intel driver freezing the X server. Until a few days ago, at boot time the / device was automatically checked, but now I just get "enter root password for maintenance" and I have to rum fsck by hand (and sometimes fsck does it in no time without any interaction from me), and reboot again.

Why isn't the device check automatically forced any more? Can I fix that?

Thank you very much in advance."

Steps to reproduce:
improper reboot...
This task depends upon

Closed by  Tom Gundersen (tomegun)
Monday, 28 March 2011, 12:32 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See my last comment.
Comment by Jan de Groot (JGC) - Friday, 25 December 2009, 14:08 GMT
At bootup an automatic recovery is done, but when this recovery needs manual interaction, it drops you to a single user shell, requesting your root password.
Comment by scippio (scippio) - Friday, 25 December 2009, 14:47 GMT
yes... that's nice, but why is manual interactions needed now? I need it as it was before.... all automatic without interaction. I do not want to go to each server individually to solve something... My server is 30km from me!
Comment by scippio (scippio) - Tuesday, 29 December 2009, 02:10 GMT
I transcribed rc.sysinit. I know it's system/drivers specific, but it's better than the old rc.sysinit. Now it stops just at the very serious mistakes.
   rc.sysinit (13 KiB)
Comment by Roman Kyrylych (Romashka) - Tuesday, 10 August 2010, 10:12 GMT
Can you provide a patch for the current initscripts that does what you want, so we can take a look what change do you propose exactly?
Comment by Thomas Bächler (brain0) - Tuesday, 10 August 2010, 18:04 GMT
I have heard of this (or a similar) problem before and it makes no sense to me. fsck explicitly reports that user interaction is necessary, but when it is run again, it just proceeds without error. One or more of the following errors must occur for initscripts to go into the recovery shell:
- File system errors left uncorrected (4)
- Operational error (8)
- Usage or syntax error (16)
- Shared library error (128)
If any of those errors occurs combined with 'System should be rebooted' (2), the system is automatically rebooted. As far as I can see it (if we believe the fsck manpage), we are acting correctly in each case. I admit the code could be less confusing though.

Without knowledge of the exact return code from fsck, there is no way to find out what the problem might be.
Comment by Tom Gundersen (tomegun) - Monday, 28 March 2011, 12:32 GMT
@scippio: I'm closing. As far as I can tell we are doing as intended by upstream. If you disagree, please request a reopen and point out which error codes you think we are not treating as intended (an up-to-date patch would also be helpful to understand your concern).

If you think fsck is returning the wrong error codes, then please report this upstream (as we will not add workarounds to second-guess what they decide).

Loading...