FS#9640 - udev-118-2 missing /etc/udev_start
Attached to Project:
Arch Linux
Opened by Zeqadious (Zeqadious) - Thursday, 21 February 2008, 15:20 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 16 March 2008, 20:09 GMT
Opened by Zeqadious (Zeqadious) - Thursday, 21 February 2008, 15:20 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 16 March 2008, 20:09 GMT
|
Details
Description:
The new udev-118-2 in testing is missing /etc/udev_start causing the system to be unable to find and mount the / or any other fs at boot. I copied the udev_start from udev-116-3 and it works perfect again. Additional info: * package version(s) 118-2 * config and/or log files etc. /etc/udev_start Steps to reproduce: pacman -Syu (this morning 2/27/08 10:00:00 EST (-5GMT) |
This task depends upon
1) when a large info message popups (with "or press Ctrl-D to continue" at the end)
enter root password
2) remount the root filesystem with the command mentioned in that info message above
3) pacman.static -U /var/cache/pacman/pkg/udev-116-3-i686.pkg.tar.gz
or pacman.static -Sy initscripts to get the latest initscripts version which works with udev-118
I did pacman -Syu and it installed udev. It did not install testing/initscripts so I didn't know their was a new one. I had splashy installed at the time of pacman -Syu so it may* have kept initscripts from being pulled and installed, I'm not sure, because pacman -Qi udev shows that udev is not dependent on udev. Splashy has initscripts-splashy which conflicted with testing/initscripts so I removed that to get the new testing/initscripts installed.
When the new testing/initscripts is installed everything works good again I can confirm.
Roman Kyrylych, my system never gets to that point. "Loading udev uevents" fails (naturally), causing a failure of everything else: filesystems aren't mounted, and services don't start. When it starts to load HAL, it sits there for ages not doing anything.
I have updated my initscripts and udev from testing but this hasn't fixed my problem.
When I boot now, during the process of loading modules and starting services, my screen resolution changes (which I guess is part of the new initscript), and is helpful beacuse it allows me to see more of the problem I'm having...
Anyway, after "Loading udev uevents", I get a message printed saying something about "Bad superblock on /dev/sda3, last edit time in the future. FIXED.", but immediately thereafter, none of my filesystems are mounted properly, and the system hangs on "Starting Hardware Abstraction Layer"
Any ideas?
I have already booted into the Arch installation environment and run an fsck on all my filesystems, they checkout OK.
How long does "Loading UDev events" take. If it actually does something, then udev is working properly and you do NOT have the bug reported in this bug report. In that case, you have a different bug.
I changed my fstab last night and forgot I had done so this morning. If you could please delete all my errant postings in this bug report, it'd be appreciated. :-)
Otherwise, I thought the instructions were clear. I followed them easily and was able to set my persistent network device names. The only problems I had were because I was running splashy. Removing splashy and using the new initscripts fixed everything. Will initscripts-splash also be updated at the same time that initscripts moves to core?
My bootup is faster now; it doesn't pause at Running Hook [udev] any more, and it hardly pauses at waiting for devices to settle. UDev uevents took 15388 ms at last boot.
Thanks for a great job!
commenting this rule. commenting(#) results in a faster boot (3.5sec) but disables module blacklisting (again)