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!
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!
FS#18390 - udev bug?
Attached to Project:
Arch Linux
Opened by Desislav (Insane-Boy) - Thursday, 18 February 2010, 18:31 GMT
Last edited by Thomas Bächler (brain0) - Friday, 19 February 2010, 12:14 GMT
Opened by Desislav (Insane-Boy) - Thursday, 18 February 2010, 18:31 GMT
Last edited by Thomas Bächler (brain0) - Friday, 19 February 2010, 12:14 GMT
|
DetailsA couple of days ago I updated my system.I haven't updated for quite a while, to be honest.When I updated I couldn't boot.The error was - http://pastebin.com/m7e3da403 .Then I read there was some problem with the current udev and a kernel version lower than 2.6.27.So I updated my kernel to 2.6.32 as well.However, this didn't solved the problem.Then I read through the forum and saw a couple of similar problems.After editing the fstab like this : http://pastebin.com/m48381f91 I did manage to boot successfully.Actually the only thing I did was to remove the 0 '1' tag from the root partition.Another problem appeared - can't access none of my partitions.Whenever i type fdisk -l I get this output http://pastebin.com/m60b8e93b .It's strange because it doesn't detect even my root partition and i have /dev/sd* or /dev/hd* devices in the /dev.Finally I came across information which helped me solve me problem a little.Everytime I boot i have to enter the following commands : undevadm test /block/hda , udevadm test /block/hda1,2,3,etc otherwise I'm unable to use them.I read everything I found on google, however , I only understood it was something of a bug related to udev and nothing more.
|
This task depends upon
Closed by Thomas Bächler (brain0)
Friday, 19 February 2010, 12:14 GMT
Reason for closing: Not a bug
Additional comments about closing: PEBKA...wait for it...wait for it....C
Friday, 19 February 2010, 12:14 GMT
Reason for closing: Not a bug
Additional comments about closing: PEBKA...wait for it...wait for it....C
for x in /lib/udev/rules.d/* /etc/udev/rules.d/*; do pacman -Qo $x;done > /dev/null