View previous topic :: View next topic |
Author |
Message |
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Wed Mar 19, 2008 10:38 pm Post subject: Error when checking root filesystem on reboot [SOLVED] |
|
|
Hi,
When I reboot my computer after completing the Gentoo install, when it gets to "Checking root filesystem", I'm given the error "fsck.ext3: No such file or directory while trying to open /dev/sda4". /dev/sda4 is my root partition. It then says "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>". When I try running e2fsck with the alternate superblock, I get the exact same error. Does anyone know how I can fix this?
Thanks in advance for the help!!
Last edited by srunni on Wed Mar 26, 2008 9:11 pm; edited 1 time in total |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9695 Location: almost Mile High in the USA
|
Posted: Thu Mar 20, 2008 1:02 am Post subject: |
|
|
Is there any entries in /dev? (-> is udev emerged and running?)
Is /dev/hda4 there but not /dev/sda4? (-> kernel compilation problem, use libata drivers instead of legacy?) _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Thu Mar 20, 2008 2:20 am Post subject: |
|
|
There are no sda* files in /dev, if that's what you mean. The only files in that directory are 'console', 'fd', 'null', 'pts', 'shm', 'stderr', 'stdin', 'stdout', 'tty', and 'tty1'. I don't think it would be /dev/hda4, since this is a new laptop and it uses a SATA drive. As for the drivers to compile into the kernel, I included “Intel PIIX/ICH SATA Support” and “AHCI SATA Support”, as suggested on http://home.earthlink.net/~george164/dv9500t/dv9500t.html (I have a dv9700t, which is the new version of the dv9500t, which that compatibility status page is for).
Also, I forgot to mention that I used the March 17th i686 stage3 archive from funtoo.org, not the official Gentoo stage. |
|
Back to top |
|
|
jburns Veteran
Joined: 18 Jan 2007 Posts: 1214 Location: Massachusetts USA
|
Posted: Thu Mar 20, 2008 6:39 pm Post subject: |
|
|
If Code: | Device Drivers --->
< > ATA/ATAPI/MFM/RLL support ---> | is selected your drives may change from /dev/sdxx to /dev/hdxx. |
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Thu Mar 20, 2008 6:59 pm Post subject: |
|
|
I pretty sure that is not selected, so I don't think that's the issue. I'll check anyway.
EDIT: Yeah, it's not selected, so that's not the problem. |
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Thu Mar 20, 2008 9:48 pm Post subject: |
|
|
Another strange thing is that when I run /dev/sda* is showing up as mounted to / , even though it's not showing up as a file under /dev . |
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Sat Mar 22, 2008 5:36 pm Post subject: |
|
|
Can anyone help me out?!! I still can't figure out what's wrong. |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21767
|
Posted: Sat Mar 22, 2008 8:53 pm Post subject: |
|
|
What is the output of cat /proc/partitions ; cat /proc/mounts ; for drive in /dev/[hs]d[a-d] ; do echo ${drive}; echo; sfdisk -l ${drive}; echo; done? This will show us what the kernel knows about your partitions, what filesystems you have mounted, and what sfdisk can determine about the first few drives in the system. |
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Sat Mar 22, 2008 10:08 pm Post subject: |
|
|
cat /proc/partitions :
Code: | major minor #blocks name
8 0 244198584 sda
8 1 81920000 sda1
8 2 34573 sda2
8 3 1004062 sda3
8 4 161236372 sda4 |
cat /proc/mounts :
Code: | rootfs / rootfs rw 0 0
/dev/root / ext3 ro,data=ordered 0 0
proc /proc proc rw,nosuid,nodev,noexec 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw,nosuid 0 0
devpts /dev/pts devpts rw,nosuid,noexec 0 0 |
for drive in /dev/[hs]d[a-d] ; do echo ${drive}; echo; sfdisk -l ${drive}; echo; done :
Code: | /dev/[hs]d[a-d]
/dev/[hs]d[a-d]: No such file or directory
sfdisk: cannot open /dev/[hs]d[a-d] for reading |
|
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Sun Mar 23, 2008 8:05 pm Post subject: |
|
|
I tried reinstalling again, this time with only a / partition, no separate /boot , and I'm still getting same error, still on the / partition. Anyone know what's going on?? |
|
Back to top |
|
|
crater2150 n00b
Joined: 04 Mar 2008 Posts: 22
|
Posted: Wed Mar 26, 2008 12:11 am Post subject: |
|
|
I had exactly the same problem. I noticed, that udev gave me an error a few lines above the fsck error, saying something about sockets. the problem was a missing option in kernel config:
Networking -> Networking Options -> Unix Domain Sockets
had to be compiled in the kernel. Doing this solved the problem for me.
I hope this helps you |
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Wed Mar 26, 2008 3:09 am Post subject: |
|
|
Thank you so much! That was it. I would have never guessed a network driver would have been necessary to fix this problem. |
|
Back to top |
|
|
newtonian Guru
Joined: 19 Jan 2005 Posts: 465 Location: Hokkaido Japan
|
Posted: Sun Apr 13, 2008 10:05 am Post subject: thanks for the fix |
|
|
This is not set by default in kernel 2.6.24-gentoo-r4 and is not documented in the gentoo handbook.
Thanks for the fix. |
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Sun Apr 13, 2008 4:36 pm Post subject: |
|
|
Nothing recent is documented in the Gentoo Handbook lol, it hasn't been updated in like 2 years. |
|
Back to top |
|
|
newtonian Guru
Joined: 19 Jan 2005 Posts: 465 Location: Hokkaido Japan
|
Posted: Sun Apr 13, 2008 7:50 pm Post subject: x86, amd64 handbook |
|
|
srunni wrote: | Nothing recent is documented in the Gentoo Handbook lol, it hasn't been updated in like 2 years. |
That could be so, but other than the kernel issue, I haven't experienced any other problems with the x86 or amd64 handbooks within the last year. Today, I got a dual XEON Quad compiled and running by command line install via the amd64 handbook in less than 90min. The issue in this post was the only snag I hit.
Cheers, |
|
Back to top |
|
|
srunni Guru
Joined: 26 Dec 2007 Posts: 365
|
Posted: Sun Apr 13, 2008 9:18 pm Post subject: |
|
|
Sounds like that's a server, where things haven't changed much...on PCs, particularly laptops, there are a lot of issues which aren't documented well. The main problem is with drivers for various hardware...everything else works amazingly well, though some other things are also out-of-date. These things can be fixed, but it's sometimes hard to find the info on how to fix it. I've had a lot of problems installing Gentoo on my laptop. I'm guessing the devs are more interested in servers than in PCs...same as the kernel devs |
|
Back to top |
|
|
|