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#18325 - Failing to boot.

Attached to Project: Arch Linux
Opened by Westley Martinez (anikom15) - Saturday, 13 February 2010, 23:46 GMT
Last edited by Thomas Bächler (brain0) - Monday, 15 February 2010, 18:28 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
System fails to boot due to failing to properly mount filesystems. Harddrives are not detected.

Additional info:
It's not improper syntax or anything like that. GRUB is fine and linux seems to find the root filesytem. Partitions can be mounted and fscked fine in LiveCD.

Forum topic discussing this problem:
http://bbs.archlinux.org/viewtopic.php?id=90891
This task depends upon

This task blocks these from closing
 FS#18332 - [mkinitcpio] line 9: /sbin/udevadm: not found 
Closed by  Thomas Bächler (brain0)
Monday, 15 February 2010, 18:28 GMT
Reason for closing:  Not a bug
Additional comments about closing:  PEBKAC
Comment by Jan de Groot (JGC) - Sunday, 14 February 2010, 00:18 GMT
Please give proper information. The link you give to the forum seems to be continued from another thread, but so far you don't provide any useful information. What version of mkinitcpio do you use, what kernel, what errors do you get, etc. Without that information we can't help you.
Comment by Westley Martinez (anikom15) - Sunday, 14 February 2010, 01:15 GMT
Ok, mkinitcpio and kernel are most recent. The post isn't continued from another thread, and you obviously didn't read it. Everything boots fine until the fsck, where fsck complains about being unable to find /dev/by-uuid/<uuid of root partition>. When I log into the recovery shell, there are no harddisk devices in /dev. As I said before, it's NOT a problem with mkinitcpio.conf or menu.lst or rc.conf or fstab. I would post error messages, but there are none other than the fsck failure.
Comment by Thomas Bächler (brain0) - Sunday, 14 February 2010, 11:27 GMT
A forum thread is not a bug report. If you report a bug, you must provide all information inside the bug report and summarize your findings in a readable way. The forum thread is merely for additional reference.

Anyway, I have no clues for further investigation. Your hard drives are detected just fine, as witnessed by root being mounted. Thus, the only thing that can go wrong is device creation by udev. This happened a few times when a broken udev rule file was lying around from old udev versions (in these cases it was /etc/udev/rules.d/udev.rules, which should not exist at all).

Loading...