Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#24310 - [initscripts] system won't boot due to failed fsck

Attached to Project: Arch Linux
Opened by WhoTouchaMySpageth! (tuxfusion) - Monday, 16 May 2011, 20:19 GMT
Last edited by Tom Gundersen (tomegun) - Tuesday, 17 May 2011, 18:44 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Initscripts update leaves system unbootable, downgrade fixes it again

Additional info:

* package version(s)
initscripts 2011.05.2-1
custom kernel, no initramfs, ext4 compiled in

* config and/or log files etc.

what config should I attach ?
rc.conf: http://pastebin.com/Bt59C7VP
fstab: http://pastebin.com/NBRGDTFV
kernel config: http://pastebin.com/5GKCQXeY

Steps to reproduce:
I wonder why i can't find any reports like mine:
System boots :
-bootlogd error accours something about a console , will attach details. ( never seen before)
-klogd error accours
-then fsck.ext4 fails : "/dev/sda1 non existing device", sometimes: "/dev/sda1 allready mounted / in use can't fsck " not in these words ...
I have to alter rc.sysinit so that fsck is always passed, the the system boots, but :
mutliple errors about /dev/x already mounted
Where does this buggy boot process come from ? I've tried to up udev timeout from 30 to 60 no effect.
Everything is uptodate. What info shall i provide ?

This task depends upon

Closed by  Tom Gundersen (tomegun)
Tuesday, 17 May 2011, 18:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  This is fixed in udev-168-2.
Comment by Tom Gundersen (tomegun) - Monday, 16 May 2011, 20:56 GMT
This is an udev bug. It only occurs to custom kernel without devtmpfs support.

A patch that should hopefully fix the problem is in udev git and there is a discussion about it on the udev mailinglist. We are just waiting for a confirmation that the problem has been fixed before I'll push a new udev version.
Comment by Tom Gundersen (tomegun) - Monday, 16 May 2011, 20:57 GMT
There was just an email on the udev mailinglist: apparently the problem was not fully solved by the patch, so don't expect a fix just yet... (a good fix is to enable devtmpfs if you can).
Comment by WhoTouchaMySpageth! (tuxfusion) - Monday, 16 May 2011, 21:07 GMT
Thank you so much! I really hate to hold pack updates, especially Arch's own.
Will recompile now , this should be in the news section ? .install file ?
Comment by Tom Gundersen (tomegun) - Monday, 16 May 2011, 21:25 GMT
We just found out about the problem now, and as soon as it is solved we will push updates, so I don't think it makes sense to add it to .install.

I'm not sure what is newsworthy and what is not (I'm new), so I'll let the other devs decide whether or not to post a news item.

Loading...