| View previous topic :: View next topic |
| Author |
Message |
farmab n00b

Joined: 07 Jan 2008 Posts: 19
|
Posted: Mon Jan 07, 2008 2:54 am Post subject: [SOLVED]Can't boot fresh gentoo install |
|
|
I've run a stage3 install from the minimal CD and followed the handbook to the letter (this also isn't my first time with Gentoo--I had a working install a few months ago but had to wipe the drive to put on a windows image--so I know it shouldn't be a hardware incompatibility problem) but when I boot I'm getting an error when it checks /...
| Code: |
...
Mounting devpts at /dev/pts ... [ ok ]
Checking root filesystem ...
fsck.ext3: No such file or directory while trying to open /dev/sda5 /dev/sda:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Filesystem couldn't be fixed :( [!!]
Give the root password for maintenance
(or type Control-D to continue):
|
Running e2fsck doesn't seem on other blocks doesn't seem to do anything and, furthermore, /dev/sda5 is non-existent (or any other /dev/sda* for that matter). The filesystem is mounted RO but none of the other file systems are mounted. My /etc/fstab is as follows
| Code: |
/dev/sda2 /boot ext2 defaults,noatime 1 2
/dev/sda5 / ext3 noatime 0 1
/dev/sda6 /usr ext3 noatime 0 2
/dev/sda7 /home ext3 noatime 0 2
/dev/sda8 /var ext3 noatime 0 2
/dev/cdrom /mnt/cdrom ext3 noauto,ro 0 0
|
(/dev/sda1 is a Vista Ultimate install)
I'm pretty sure none of the filesystems are actually corrupted as I've loaded up the installation env and run fsck on /dev/sda* and they're all clean, but I'm at a loss as to why it is none of my partitions are showing up in /dev, yet it's still mounting my root partition...could it possibly be some sort of problem with GRUB? I've attached the grub.conf in any case.
| Code: |
default 0
timeout 30
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
title=Gentoo Linux 2.6.23-r3
root (hd0,1)
kernel /boot/kernel-2.6.23-gentoo-r3 root=/dev/hda5
title=Gentoo Linux 2.6.23-r3 (rescue)
root (hd0,1)
kernel /boot/kernel-2.6.23-gentoo-r3 root=/dev/hda5 init=/bin/bb
title=Vista
rootnoverify (hd0,0)
makeactive
chainloader +1
|
I'm rather tired at this point, so if I forgot anything I can provide whatever other info might be needed. Thanks in advance to anyone who can shed some light on the subject.
Last edited by farmab on Tue Jan 08, 2008 6:57 pm; edited 1 time in total |
|
| Back to top |
|
 |
yabbadabbadont Advocate


Joined: 14 Mar 2003 Posts: 4790 Location: 2 exits past crazy
|
Posted: Mon Jan 07, 2008 2:59 am Post subject: |
|
|
| I would guess that you have forgotten to include support for ext2 and ext3 when you built your kernel. Chroot into your system from the install cd and make sure you have both selected to be included directly in the kernel and not as modules. Then rebuild and install the kernel again. |
|
| Back to top |
|
 |
farmab n00b

Joined: 07 Jan 2008 Posts: 19
|
Posted: Mon Jan 07, 2008 11:27 am Post subject: |
|
|
Thought of that already. I originally built in ext2 and ext3 support, but when this started happening I rebuilt the kernel with everything ext2/3 related and I'm still having the same issue. I didn't think to include this last night, but the original problem I had was an error about being unable to mount the root from an NFS, which I think was caused by my SATA drivers being modules (confused me for the longest time...had the intel sata driver built in, but didn't notice the SATA (prod) and PATA (experimental), which houses the intel stat driver, set as a module :/), which I fixed by including it in the kernel...could it be that I missed a necessary SATA driver? It's an intel ich6, so I added the intel sata support and the ahci sata driver as well.
Anyway, here's an lspci dump if it helps at all (it's a ~3yo IBM Thinkpad T43p) and the full names of the SATA drivers I have built into the kernel
| Code: |
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge(rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 2801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc m24GL [Mobility FireGL V3200] (rev 80)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 11)
0b:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d)
0b:02.0 Network controller: Intel Corporation PRO/Wireless 2915ABG Network Connection (rev 05)
|
| Code: |
<*> Serial ATA (prod) and Parallel ATA (experimental) drivers -->
<*> AHCI SATA support
<*> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
|
...I would assume that the Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support should cover what I need, but I'm not entirely sure, and there aren't any other Intel SATA drivers there (the only other intel stuff on the list would be Intel PATA MPIIX support and Intel PATA old PIIX support) |
|
| Back to top |
|
 |
farmab n00b

Joined: 07 Jan 2008 Posts: 19
|
Posted: Mon Jan 07, 2008 11:48 am Post subject: |
|
|
| Also tried building in Generic ATA Support to no avail. |
|
| Back to top |
|
 |
schachti Advocate


Joined: 28 Jul 2003 Posts: 3765 Location: Gifhorn, Germany
|
Posted: Mon Jan 07, 2008 2:50 pm Post subject: Re: Can't boot fresh gentoo install |
|
|
| farmab wrote: |
| Code: |
/dev/sda5 / ext3 noatime 0 1
|
| Code: |
kernel /boot/kernel-2.6.23-gentoo-r3 root=/dev/hda5
|
|
If you use /dev/sda5 in /etc/fstab, shouldn't it be the same with the grub options? Or did I get something terribly wrong? _________________ Never argue with an idiot. He brings you down to his level, then beats you with experience.
How-To: Daten verschlüsselt auf DVD speichern. |
|
| Back to top |
|
 |
jmbsvicetto Moderator


Joined: 27 Apr 2005 Posts: 4725 Location: Angra do Heroísmo (PT)
|
Posted: Mon Jan 07, 2008 3:37 pm Post subject: |
|
|
Hi.
| farmab wrote: | ... the original problem I had was an error about being unable to mount the root from an NFS, which I think was caused by my SATA drivers being modules (confused me for the longest time...had the intel sata driver built in, but didn't notice the SATA (prod) and PATA (experimental), which houses the intel stat driver, set as a module :/), which I fixed by including it in the kernel...could it be that I missed a necessary SATA driver? It's an intel ich6, so I added the intel sata support and the ahci sata driver as well.
| Code: |
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
|
|
You were likely using a < 2.6.22(3?) kernel before and got bitten now that you use a 2.6.23 kernel. The 2.6.23 kernel includes a feature that will rename disks attached to a few common sata controllers as /dev/hdX instead of /dev/sdX. You need to disable the CONFIG_IDE entirely to get your disks to be seen as /dev/sdX again. _________________ Jorge.
Your twisted, but hopefully friendly daemon.
AMD64 / x86 / Sparc Gentoo
Help answer || emwrap.sh
|
|
| Back to top |
|
 |
NathanZachary Moderator


Joined: 30 Jan 2007 Posts: 2281 Location: /home/zach
|
Posted: Mon Jan 07, 2008 10:46 pm Post subject: |
|
|
| jmbsvicetto wrote: | Hi.
You were likely using a < 2.6.22(3?) kernel before and got bitten now that you use a 2.6.23 kernel. The 2.6.23 kernel includes a feature that will rename disks attached to a few common sata controllers as /dev/hdX instead of /dev/sdX. You need to disable the CONFIG_IDE entirely to get your disks to be seen as /dev/sdX again. |
Just out of curiosity, is there a list of the SATA controllers that undergo this change with the 2.6.23 kernel? Was there a reason for this change? _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
| Back to top |
|
 |
farmab n00b

Joined: 07 Jan 2008 Posts: 19
|
Posted: Mon Jan 07, 2008 10:56 pm Post subject: |
|
|
| jmbsvicetto wrote: | Hi.
| farmab wrote: | ... the original problem I had was an error about being unable to mount the root from an NFS, which I think was caused by my SATA drivers being modules (confused me for the longest time...had the intel sata driver built in, but didn't notice the SATA (prod) and PATA (experimental), which houses the intel stat driver, set as a module :/), which I fixed by including it in the kernel...could it be that I missed a necessary SATA driver? It's an intel ich6, so I added the intel sata support and the ahci sata driver as well.
| Code: |
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
|
|
You were likely using a < 2.6.22(3?) kernel before and got bitten now that you use a 2.6.23 kernel. The 2.6.23 kernel includes a feature that will rename disks attached to a few common sata controllers as /dev/hdX instead of /dev/sdX. You need to disable the CONFIG_IDE entirely to get your disks to be seen as /dev/sdX again. |
Well, that's a pain in the ass. Changing by fstab to /dev/hd* instead of /sd* fixed my problems. Yeah, I think I was using a 2.6.19 kernel..where is this CONFIG_IDE that I need to disable? |
|
| Back to top |
|
 |
cyrillic Watchman


Joined: 19 Feb 2003 Posts: 7301 Location: Groton, Massachusetts USA
|
Posted: Mon Jan 07, 2008 11:19 pm Post subject: |
|
|
| jmbsvicetto wrote: | | The 2.6.23 kernel includes a feature that will rename disks attached to a few common sata controllers as /dev/hdX instead of /dev/sdX. |
I don't think anything is getting renamed. It is simply a case of the older IDE driver loading before the newer libata driver has a chance to attach to the device.
In general, it is a bad idea to have the kernel configured with more than 1 driver trying to support the same piece of hardware. |
|
| Back to top |
|
 |
farmab n00b

Joined: 07 Jan 2008 Posts: 19
|
Posted: Mon Jan 07, 2008 11:37 pm Post subject: |
|
|
| Actually, it is getting renamed. For some reason my partitions have been renamed as /dev/hda*...strange, but whatever. It's working for now with fstab set up referencing them as /dev/hda* instead of /dev/sda*, so I'll screw around little by little with it and work out the kinks as I go. |
|
| Back to top |
|
 |
jmbsvicetto Moderator


Joined: 27 Apr 2005 Posts: 4725 Location: Angra do Heroísmo (PT)
|
Posted: Tue Jan 08, 2008 12:00 am Post subject: |
|
|
Hi.
| cyrillic wrote: | | jmbsvicetto wrote: | | The 2.6.23 kernel includes a feature that will rename disks attached to a few common sata controllers as /dev/hdX instead of /dev/sdX. |
I don't think anything is getting renamed. It is simply a case of the older IDE driver loading before the newer libata driver has a chance to attach to the device.
In general, it is a bad idea to have the kernel configured with more than 1 driver trying to support the same piece of hardware. |
You are right in that the IDE device gets to control the SATA controller before the sata driver is loaded, but as I understand it the increased support of devices by the generic IDE driver is what makes it bond to at least the Intel, AMD and nVidia sata controllers, unlike what happened before the 2.6.22 or 2.6.23 kernel.
I started noticing this from some comments here about the renaming, which at the time I didn't understood, and then it hit me on my AMD64. _________________ Jorge.
Your twisted, but hopefully friendly daemon.
AMD64 / x86 / Sparc Gentoo
Help answer || emwrap.sh
|
|
| Back to top |
|
 |
Rede n00b


Joined: 03 Jun 2007 Posts: 67
|
Posted: Tue Jan 08, 2008 12:43 am Post subject: |
|
|
Hey I am having the same problem as above ^^
Can someone please let me know how to use the livecd to go back and change my fstab? |
|
| Back to top |
|
 |
NathanZachary Moderator


Joined: 30 Jan 2007 Posts: 2281 Location: /home/zach
|
Posted: Tue Jan 08, 2008 12:49 am Post subject: |
|
|
What you basically need to do it chroot back into your environment, and you do that by booting the minimal installation disc and doing the following:
| Code: |
mount -t FSTYPE /dev/ROOT /mnt/gentoo
mount -t FSTYPE /dev/BOOT /mnt/gentoo/boot
swapon /dev/SWAP
mount -t proc /proc /mnt/gentoo/proc
mount -o bind /dev /mnt/gentoo/dev
chroot /mnt/gentoo /bin/bash
env-update && source /etc/profile
export PS1="(chroot) $PS1"
|
You replace the items in CAPS with your actual information. Therefore, FSTYPE would be either ext2, ext3, et cetera based on your system, and BOOT & ROOT would be /dev/whatever_partition. If you need further assistance, please just ask.  _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
| Back to top |
|
 |
Rede n00b


Joined: 03 Jun 2007 Posts: 67
|
Posted: Tue Jan 08, 2008 1:05 am Post subject: |
|
|
Ok that worked
Thank you.
I have a few other things I would like help with, can I just post them here? |
|
| Back to top |
|
 |
NathanZachary Moderator


Joined: 30 Jan 2007 Posts: 2281 Location: /home/zach
|
Posted: Tue Jan 08, 2008 1:11 am Post subject: |
|
|
I'd be more than happy to help you with the problems (if I can), but you might want to start your own thread about them, as that will keep the boards a little more tidy.  _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
| Back to top |
|
 |
Rede n00b


Joined: 03 Jun 2007 Posts: 67
|
|
| Back to top |
|
 |
farmab n00b

Joined: 07 Jan 2008 Posts: 19
|
Posted: Tue Jan 08, 2008 3:42 pm Post subject: |
|
|
| So I've been pulling away bits of IDE support in the kernel and trying to get this to recognize my drives as /dev/sda* instead of /dev/hda*, but nothing is working. Does anyone have any insight on how it is I'm supposed to get my drives back to being /dev/sda*? |
|
| Back to top |
|
 |
cyrillic Watchman


Joined: 19 Feb 2003 Posts: 7301 Location: Groton, Massachusetts USA
|
Posted: Tue Jan 08, 2008 4:30 pm Post subject: |
|
|
| farmab wrote: | | So I've been pulling away bits of IDE support in the kernel ... |
The best way is to remove all IDE support, and use only the newer libata drivers instead.
Your kernel .config should look like this.
| Code: | # CONFIG_IDE is not set
CONFIG_ATA=y |
|
|
| Back to top |
|
 |
farmab n00b

Joined: 07 Jan 2008 Posts: 19
|
Posted: Tue Jan 08, 2008 6:06 pm Post subject: |
|
|
| cyrillic wrote: | | farmab wrote: | | So I've been pulling away bits of IDE support in the kernel ... |
The best way is to remove all IDE support, and use only the newer libata drivers instead.
Your kernel .config should look like this.
| Code: | # CONFIG_IDE is not set
CONFIG_ATA=y |
|
K, I've done that, but now I'm back to square one. I can't boot again, even after modifying my fstab. The only thing I modified about the kernel was to comment out CONFIG_IDE...All my SATA drivers are still intact, etc. but when I boot I'm getting:
| Code: |
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Insert root floppy and press ENTER
|
This is the original message I got when I accidentally had my SATA drivers set as modules--however, all my SATA drivers are now compiled into the kernel.
...so, any ideas? |
|
| Back to top |
|
 |
NathanZachary Moderator


Joined: 30 Jan 2007 Posts: 2281 Location: /home/zach
|
Posted: Tue Jan 08, 2008 6:13 pm Post subject: |
|
|
Get to your kernel editor:
| Code: |
cd /usr/src/linux
make menuconfig
|
Go to this section:
File systems --> Network file systems -->
Remove support for NFS File System Support, and NFS Server Support
Recompile the kernel, copy it over to your boot directory, and reboot. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
| Back to top |
|
 |
farmab n00b

Joined: 07 Jan 2008 Posts: 19
|
Posted: Tue Jan 08, 2008 6:28 pm Post subject: |
|
|
Found the problem. I modified my fstab, but in the process I forgot to change my grub.conf
Thanks all for the help. |
|
| Back to top |
|
 |
NathanZachary Moderator


Joined: 30 Jan 2007 Posts: 2281 Location: /home/zach
|
Posted: Tue Jan 08, 2008 6:42 pm Post subject: |
|
|
No problem; glad you found the solution. If you could kindly put [SOLVED] in the thread title, it would be appreciated. Also, if you need further help, please just ask. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
| Back to top |
|
 |
|