View previous topic :: View next topic |
Author |
Message |
phillosophy Tux's lil' helper
Joined: 23 May 2005 Posts: 94
|
Posted: Sat May 28, 2005 4:40 am Post subject: Is this a GRUB or Fstab problem? [solved] |
|
|
The grub screen comes up and when i select the title, it runs through what appears to be the root system and boots but then at the end of the loading, I get the following error screen when i boot:
- starting devfsd...
\sbin\rc: line 271 : /sbin/devfsd : no such file or directory ... [!!!]
- remount root filesystem to readonly [ok]
- checking root filesystem ...
failed to open the device '/dev/hda3' - no such file or directory [!!!]
* file system couldn't be fixed ....
here is my fdisk -l :
Code: | Device Boot Start End Blocks Id System
/dev/hda1 * 1 5 40131 83 Linux
/dev/hda2 6 68 506047+ 82 Linux swap / Solaris
/dev/hda3 69 5005 39656452+ 83 Linux
|
here is my grub.conf file:
Code: | default 0
#how many seconds to wait before the default listing is booted
timeout 30
title=Gentoo Linux 2.4.28-r9 (original)
#partition where the kernel image (or operating system) is located
root(hd0,0)
kernel /kernel-2.4.28-gentoo-r9 root=/dev/hda3
|
here is my /etc/fstab
Code: |
# <fs> <mountpoint> <type> <opts> $
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1 /boot ext2 noauto,noatime $
/dev/hda3 / reiserfs noatime $
/dev/hda2 none swap sw $
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro $
#/dev/fd0 /mnt/floppy auto noauto $
# NOTE: The next line is critical for boot!
none /proc proc defaults $
|
any help would be appreciated. Thanks
Last edited by phillosophy on Sat May 28, 2005 5:29 am; edited 1 time in total |
|
Back to top |
|
|
overkll Veteran
Joined: 21 Sep 2004 Posts: 1249 Location: Austin, Texas
|
Posted: Sat May 28, 2005 5:00 am Post subject: |
|
|
I thinks it's a devfs problem.
Quote: | - starting devfsd...
\sbin\rc: line 271 : /sbin/devfsd : no such file or directory ... [!!!] |
The file "/sbin/devsd" is supplied by the package sys-fs/devfsd.
AFAIK, devfsd should be installed by default with a 2.4 kernel. You may want to check to see if it is and if its not emerge it. |
|
Back to top |
|
|
phillosophy Tux's lil' helper
Joined: 23 May 2005 Posts: 94
|
Posted: Sat May 28, 2005 5:29 am Post subject: [solved] |
|
|
cool. that fixed the problem. thanx! |
|
Back to top |
|
|
overkll Veteran
Joined: 21 Sep 2004 Posts: 1249 Location: Austin, Texas
|
Posted: Sat May 28, 2005 5:32 am Post subject: |
|
|
You're welcome. You should add [solved] to the subject of this post. It's easier for others to find stuff that way.
Have fun! |
|
Back to top |
|
|
vlooe n00b
Joined: 04 Jun 2005 Posts: 35 Location: Germany
|
Posted: Sat Jun 04, 2005 6:00 pm Post subject: |
|
|
Hello
I had the same problem on a similar system.
emerge devfsd solved the problem.
But why must i emerge devfsd?
2 weeks ago i had installed a gentoo without problem on the same machine.
Only the configuration of the kernel is different.
Vlooe |
|
Back to top |
|
|
overkll Veteran
Joined: 21 Sep 2004 Posts: 1249 Location: Austin, Texas
|
Posted: Sat Jun 04, 2005 6:03 pm Post subject: |
|
|
vlooe,
What kernel version are you using? |
|
Back to top |
|
|
vlooe n00b
Joined: 04 Jun 2005 Posts: 35 Location: Germany
|
Posted: Sat Jun 04, 2005 6:31 pm Post subject: |
|
|
I use the 2.6.11-gentoo-r9 |
|
Back to top |
|
|
overkll Veteran
Joined: 21 Sep 2004 Posts: 1249 Location: Austin, Texas
|
Posted: Sat Jun 04, 2005 7:31 pm Post subject: |
|
|
Quote: | I had the same problem on a similar system.
emerge devfsd solved the problem.
But why must i emerge devfsd?
2 weeks ago i had installed a gentoo without problem on the same machine.
Only the configuration of the kernel is different. |
Did you install 2005.0? Did you use genkernel to build your new kernel? If this is the case, did you follow the instructions about adding udev to the end of the genkernel command? I believe that if you omitted the "udev" from the genkernel command, you just built your kernel with devfs support as oppossed to udev support (which the original system was).
Then, when you rebooted, your new devfs kernel is looking for some progs it needs to start up your computer. Since your box was udev originally, you didn't have the devfsd package installed. Installing devfsd enabled your new devfs kernel to find what it needed and start and boot up.
I'm I making any sense? |
|
Back to top |
|
|
vlooe n00b
Joined: 04 Jun 2005 Posts: 35 Location: Germany
|
Posted: Sat Jun 04, 2005 7:53 pm Post subject: |
|
|
Hmm i have configured my kernel with make menuconfig
But it could be that i have activated something that is not needed.
Knows anybody the name of the unneeded module?
Vlooe
EDIT:
I think i found the unneded module
File systems --->
Pseudo Filesystems --->
[*] /dev file system support (OBSOLETE)
[*] Automatically mount at boot
The German handbook at
7.c. Standard: Manuelle Konfiguration
-----cut
Code Listing 8: Selektieren notwendiger Dateisysteme
-----cut
(Mit einem 2.6.x Kernel)
File systems --->
Pseudo Filesystems --->
[*] /proc file system support
[*] /dev file system support (OBSOLETE)
[*] Automatically mount at boot
[*] /dev/pts file system for Unix98 PTYs
[*] Virtual memory file system support (former shm fs)
-----cut
The same part in the english handbook
7.c. Default: Manual Configuration
-----cut
Code Listing 8: Selecting necessary file systems
-----cut
(With a 2.6.x kernel)
File systems --->
Pseudo Filesystems --->
[*] /proc file system support
[ ] /dev file system support (OBSOLETE)
[*] Virtual memory file system support (former shm fs)
-----cut
Last edited by vlooe on Sat Jun 04, 2005 8:25 pm; edited 1 time in total |
|
Back to top |
|
|
overkll Veteran
Joined: 21 Sep 2004 Posts: 1249 Location: Austin, Texas
|
Posted: Sat Jun 04, 2005 8:23 pm Post subject: |
|
|
OK, check to make sure that you have "/dev file system support" unselected in "File systems -> Pseudo filesystems:
Code: | File systems --> Pseudo filesystems
[*] /proc file system support
[*] /proc/kcore support
[ ] /dev file system support (OBSOLETE)
[ ] /dev/pts Extended Attributes
[*] Virtual memory file system support (former shm fs)
[ ] tmpfs Extended Attributes
[ ] HugeTLB file system support |
|
|
Back to top |
|
|
vlooe n00b
Joined: 04 Jun 2005 Posts: 35 Location: Germany
|
Posted: Sat Jun 04, 2005 8:28 pm Post subject: |
|
|
Thanks for your help.
where should i post the fault in the german handbook?
In the german forum or somewhere else?
Vlooe |
|
Back to top |
|
|
Yogi-CH Guru
Joined: 19 Apr 2004 Posts: 372 Location: Somewhere in Texas, last I remember...
|
Posted: Sat Jun 04, 2005 8:34 pm Post subject: |
|
|
vlooe wrote: | Hmm i have configured my kernel with make menuconfig
But it could be that i have activated something that is not needed.
Knows anybody the name of the unneeded module?
Vlooe |
There seems to be a small problem w/the 2005.0 handbook. In the Configuring the Kernel chapter one can use genkernel --udev all and get a kernel built. Since I need PCMCIA & a couple other goodies I executed genkernel --menuconfig --udev all and checked something out:
Using genkernel --udev all one gets a kernel with the following options...
Code: | File systems --->
Pseudo Filesystems --->
<*> /proc file system support
<* > /dev file system support (OBSOLETE)
<*> Virtual memory file system support (former shm fs) |
...whereas when one is instructed as to how to roll their own kernel the handbook example shows the following...
Code: | File systems --->
Pseudo Filesystems --->
<*> /proc file system support
< > /dev file system support (OBSOLETE)
<*> Virtual memory file system support (former shm fs) |
...and, clearly, both cannot be correct.
<RANT>
I used the example in the handbook and ended up with the problem described in the original post. I don't give a hoot whether they say devfs is obsolete, deprecated, hosed, or whatever. It works. Clearly, there is a major problem w/udev. I give you all the posts concerning it as proof, as well as the fact that I made three atttempts to get it working within 2004.3, using the udev howto on G's site, and ended up posting [ABANDONED] on the threads concerning it.
I will continue to use devfs until such time as udev is fixed, even if it means not upgrading the kernel --or anything else, for that matter.
</RANT> _________________ ...Yogi |
|
Back to top |
|
|
overkll Veteran
Joined: 21 Sep 2004 Posts: 1249 Location: Austin, Texas
|
Posted: Sat Jun 04, 2005 8:41 pm Post subject: |
|
|
First, double check WHICH handbook. As far as I know, there are more than one. I think there is a general handbook for each arch (x86, sparc, amd64,....) and there is also "2005.0" handbook.
If you find something you believe to be in error, you'd post a bug report at https://bugs.gentoo.org under documentation or handbook or such. Search the bugs database and make sure it isn't already reported. If it's is you can add your comments to the existing bug report. |
|
Back to top |
|
|
overkll Veteran
Joined: 21 Sep 2004 Posts: 1249 Location: Austin, Texas
|
Posted: Sat Jun 04, 2005 8:58 pm Post subject: |
|
|
Yogi-CH wrote: |
There seems to be a small problem w/the 2005.0 handbook. In the Configuring the Kernel chapter one can use genkernel --udev all and get a kernel built. Since I need PCMCIA & a couple other goodies I executed genkernel --menuconfig --udev all and checked something out:
Using genkernel --udev all one gets a kernel with the following options...
Code: | File systems --->
Pseudo Filesystems --->
<*> /proc file system support
<* > /dev file system support (OBSOLETE)
<*> Virtual memory file system support (former shm fs) |
...whereas when one is instructed as to how to roll their own kernel the handbook example shows the following...
Code: | File systems --->
Pseudo Filesystems --->
<*> /proc file system support
< > /dev file system support (OBSOLETE)
<*> Virtual memory file system support (former shm fs) |
...and, clearly, both cannot be correct. |
Frustrating, isn't it? However, it is possible to have devfs support in the kernel, and choose between either devfs or udev. I don't think it's in the handbook though (I haven't used it in a while). It's in the user docs section under "System Administration Documentation"
Took this quote from Gentoo udev guide
This:
Quote: | You can leave the /dev file system support (OBSOLETE) active if you wish but you have to make sure that "Automatically mount at boot" is disabled:
Code Listing 2.5: Don't automatically mount devfsd
File systems --->
Pseudo Filesystems --->
[*] /dev file system support (OBSOLETE)
[ ] Automatically mount at boot
|
And this:
Quote: | If you have included devfs support in your kernel, you can deactivate it in the bootloader configuration: add gentoo=nodevfs as a kernel parameter. If you want to use devfs and deactivate udev, add gentoo=noudev as kernel parameter. |
|
|
Back to top |
|
|
Yogi-CH Guru
Joined: 19 Apr 2004 Posts: 372 Location: Somewhere in Texas, last I remember...
|
Posted: Sun Jun 05, 2005 4:01 am Post subject: |
|
|
overkll wrote: | First, double check WHICH handbook. As far as I know, there are more than one. I think there is a general handbook for each arch (x86, sparc, amd64,....) and there is also "2005.0" handbook.
If you find something you believe to be in error, you'd post a bug report at https://bugs.gentoo.org under documentation or handbook or such. Search the bugs database and make sure it isn't already reported. If it's is you can add your comments to the existing bug report. |
You are correct. I did specify the 2005.0 handbook for the example, I believe.
I plan on looking into the documentation bugs and see if it is listed. If not, I shall certainly add it. _________________ ...Yogi |
|
Back to top |
|
|
Yogi-CH Guru
Joined: 19 Apr 2004 Posts: 372 Location: Somewhere in Texas, last I remember...
|
Posted: Sun Jun 05, 2005 4:07 am Post subject: |
|
|
overkll wrote: | Frustrating, isn't it? However, it is possible to have devfs support in the kernel, and choose between either devfs or udev. I don't think it's in the handbook though (I haven't used it in a while). It's in the user docs section under "System Administration Documentation"
Took this quote from Gentoo udev guide
This:
Quote: | You can leave the /dev file system support (OBSOLETE) active if you wish but you have to make sure that "Automatically mount at boot" is disabled:
Code Listing 2.5: Don't automatically mount devfsd
File systems --->
Pseudo Filesystems --->
[*] /dev file system support (OBSOLETE)
[ ] Automatically mount at boot
|
And this:
Quote: | If you have included devfs support in your kernel, you can deactivate it in the bootloader configuration: add gentoo=nodevfs as a kernel parameter. If you want to use devfs and deactivate udev, add gentoo=noudev as kernel parameter. |
|
Frustrating is a word and one-half. I believe that this should be broached in the installation docs since one apparently cannot expect the newly installed system to boot, otherwise.
As for the kernel parameters, I have attempted all of this some weeks ago and found that various things broke at differing times: sound, booting, korganizer, etc. It's the weird behaviour that distresses me the most when I had a working system prior to udev. That is why I say fix it & properly document it and I'll use it.
Sometimes I think I need udev anger management. _________________ ...Yogi |
|
Back to top |
|
|
jmbsvicetto Moderator
Joined: 27 Apr 2005 Posts: 4734 Location: Angra do Heroísmo (PT)
|
Posted: Sun Jun 05, 2005 4:25 am Post subject: |
|
|
Yogi-CH,
I've seen a lot of posts on udev and a lot of problems with using it. All I can say is that I've been using it for months and IT DOES WORK.
You should read again the Gentoo-udev HOW-TO and look at the /etc/conf.d/rc entries. |
|
Back to top |
|
|
Yogi-CH Guru
Joined: 19 Apr 2004 Posts: 372 Location: Somewhere in Texas, last I remember...
|
Posted: Sun Jun 05, 2005 1:12 pm Post subject: |
|
|
jmbsvicetto wrote: | Yogi-CH,
I've seen a lot of posts on udev and a lot of problems with using it. All I can say is that I've been using it for months and IT DOES WORK.
You should read again the Gentoo-udev HOW-TO and look at the /etc/conf.d/rc entries. |
Been there & done that many times. Still no workie. It's devfs till I die, I guess. I did a text search on two things: devfs & udev; devfs came back w/zero hits. I wonder why!?? That's because it just works, I guess. Deprecated?? I don't think so. In any case, both my HP & Gateway boxes strenuously object to udev ...as do I. I wish I understood the concept. I just don't seem to be able to get a handle on it. _________________ ...Yogi |
|
Back to top |
|
|
jmbsvicetto Moderator
Joined: 27 Apr 2005 Posts: 4734 Location: Angra do Heroísmo (PT)
|
Posted: Sun Jun 05, 2005 2:11 pm Post subject: |
|
|
Yogi-CH,
the concept is actually pretty simple. With devfs your /dev dir is full of dev nodes for all types of imaginable hardware. With udev, your kernel only creates the entries that are needed for your specific hardware. Furthermore, udev is built from the start to be used with hotplugging and coldplugging.
To learn more on this subject, you'll either have to read on it, the *nix way , or you'll have to ask people about it - the lazy way , just kidding. |
|
Back to top |
|
|
Yogi-CH Guru
Joined: 19 Apr 2004 Posts: 372 Location: Somewhere in Texas, last I remember...
|
Posted: Sun Jun 05, 2005 4:58 pm Post subject: |
|
|
jmbsvicetto wrote: | Yogi-CH,
the concept is actually pretty simple. With devfs your /dev dir is full of dev nodes for all types of imaginable hardware. With udev, your kernel only creates the entries that are needed for your specific hardware. Furthermore, udev is built from the start to be used with hotplugging and coldplugging.
To learn more on this subject, you'll either have to read on it, the *nix way , or you'll have to ask people about it - the lazy way , just kidding. |
Thanks for that explanation. Guess I'm just having a major Senior Moment when it comes to udev. I've read & reread the docs on switching to udev, tried it numerous times and, as I earlier pointed out, had numerous things breaking on me. Oh well... thanks, again. _________________ ...Yogi |
|
Back to top |
|
|
|