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#2902 - Grub "devfs=nomount" Bug

Attached to Project: Arch Linux
Opened by Matthew (msg43) - Saturday, 02 July 2005, 02:10 GMT
Last edited by Judd Vinet (judd) - Wednesday, 24 August 2005, 21:54 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hello.
I just reinstalled archlinux with a ftp install. I add the opition devfs=nomount on my grub menu.lst file. When I rebooted I got Warning: Unable to open initial console. This was right after the file system was detected. So I rebooted edit the line that had devfs=nomount" and I removed it so I can get into my system. Then I installed the tools to irc. I went to the archlinux channel seek for help. Xentac told me to run /sbin/migrate-udev and reboot. This solved my problem. I was able to boot into my kernel with the grub opition 'devfs=nomount' . A new comer had the same issue today. The thread is here http://bbs.archlinux.org/viewtopic.php?p=97382
If you have any question just ask I will reply.
This task depends upon

Closed by  arjan timmerman (blaasvis)
Monday, 31 October 2005, 12:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  msg43 asked to close it :)
Comment by Claudio Riva (Firetux) - Sunday, 03 July 2005, 20:30 GMT
from http://wiki2.archlinux.org/index.php/UdevHowTo


If your kernel hangs during bootup with

WARNING: Unable to open an initial console

1. grab the ArchLinux installation CD and boot using it
2. mount your root partition (example: "mount /dev/discs/disc0/part3 /mnt")
3. chroot to the newly mounted dir (example: "chroot /mnt")
4. create missing static nodes in /dev with:

cd /dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3

These nodes are required for starting Udev. You might have both/only one of them/none missing. More information on here.
Comment by Sasha (kleptophobiac) - Saturday, 09 July 2005, 20:33 GMT
I tried doing that. The console came up, but not completely. I ended up with a completely unworkable system. I use lilo.

My workaround was to do the CD install with its packages, and then upgrade. That worked flawlessly and without any fuss. I am using udev.
Comment by sepht (sepht) - Tuesday, 12 July 2005, 23:57 GMT
Is this really a critical bug? uDev is not yet standard in arch, and if you read the wiki where it tells you how to install it, it covers this issue, It's not exactly critical, nor is it really a bug I think.
Comment by Matthew (msg43) - Wednesday, 13 July 2005, 02:38 GMT
I would consider this a critical bug considering many people hate devfs and devfs is going to be discontinued soon. This would probably turn a lot of newbies off. If I was a newbie and this happened to me I would think arch is some kinda crappy distro and leave it.
This only happened when I did a ftp install if I was to do a cd install it would have been fine.
I'm not trying to make arch or anyone look/feel bad. It in a basic install so I thought I would let people know. I thought it was cirtcal maybe not.
Comment by sepht (sepht) - Wednesday, 13 July 2005, 02:45 GMT
It's not a basic install, you changed and added a custom modifier to use something that you never bothered to look into on the wiki or configure. If people start adding things onto the kernel install without even reading the documentation on it, why should it be considered a bug?

Just thought you might want to know, this happened to me yesterday when I installed arch on my primary box, and a quick look at the documentation showed me how to fix it, that doesn't fall into the bug section for me, let alone a "critical" one.
Comment by Matthew (msg43) - Wednesday, 13 July 2005, 02:47 GMT
I consider it a bug because it worked with the arch 0.7 install cd.
Comment by sepht (sepht) - Wednesday, 13 July 2005, 03:11 GMT
if they tell you how to fix it, how is it a critcal bug?

Hint: It's not
Comment by Greg Meyer (oggb4mp3) - Wednesday, 24 August 2005, 21:13 GMT
You can also fix this by removing devfs before rebooting:

When I install, I use base, then reboot using devfs, then update everything with 'pacman -Syu', add devfs=nomount to the grub, then remove devfsd with 'pacman --remove devfsd' then reboot.

Since I remove devfs, adding devfs=nomount is probably not necessary, but I have not tried it to confirm.
Comment by Judd Vinet (judd) - Wednesday, 24 August 2005, 21:54 GMT
Hi Matthew,

I have not been able to reproduce this. Did you use the CD or the disk iamges to do the FTP install?
Comment by Matthew (msg43) - Thursday, 25 August 2005, 10:15 GMT
Jude at the time of the problem I used the cd to do an ftp install, so it possible it this problem was fixed from a udev package upgrade from the time the my issue occurd. This is almost 2 months old so you can probably close this issue. If I ever come across it again I'll let you know :)

Loading...