| View previous topic :: View next topic |
| Author |
Message |
CDRuzin
n00b
Joined: 22 Jan 2004
Posts: 35
Location: AR-USA
|
 Posted: Tue Jan 27, 2004 9:00 am Post subject: root filesystem error on startup |
 |
|
Ever since I updated portage and ran etc-update, my system has been buggy as hell. I've been steadily working my way through the errors, but have come upon one I can't figure out.
When I reboot, I get this error: | Quote: | * Checking root filesystem...
fsck.ext3: No such file or directory while trying to open /dev/hda4
/dev/hda4:
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  |
Then it asks me for root password for maintenance.
I've checked my /etc/fstab, and it looks correct.
| Quote: | /dev/hda4 / ext3 noatime 0 0
/dev/hda3 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro,users 0 0
proc /proc proc defaults 0 0 |
What is the problem here and why is it trying to read root as ext2? |
|
| Back to top |
|
 |
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Tue Jan 27, 2004 9:33 am Post subject: Re: root filesystem error on startup |
|
|
Hmm, I'm not sure, but I can at least give you an answer to
| CDRuzin wrote: | | why is it trying to read root as ext2? |
It doesn't realy matter. ext3 is just ext2 with something extra (a journal).
So you can just read/write an ext3 partition using ext2. However, if your kernel is aware of ext3 (which it should), it should indeed detect it as ext3.
Maybe the ext3 driver isn't build into the kernel? or isn't in the initrd? |
|
| Back to top |
|
|
CDRuzin
n00b
Joined: 22 Jan 2004
Posts: 35
Location: AR-USA
|
| Posted: Tue Jan 27, 2004 6:25 pm Post subject: |
|
|
I knew ext2 and ext3 were similar to each other, but I thought the kernel could tell them apart? And it was working like a charm before portage went all gimpy on me. I updated portage and ran etc-update, which changed some conf files I told it to leave alone. That screwed up portage BIG time. I had to use the portage_rescue tarball to save it. However, now I have this new problem.
I know the kernel has support for ext3 since it worked fine before the portage crap-out.
I don't have an initrd anywhere in etc. I also noticed my etc-update.conf file is blank. And my devfsd.conf file is empty. There's also nothing inside of my devfs.d directory. Could this be my problem? |
|
| Back to top |
|
|
CDRuzin
n00b
Joined: 22 Jan 2004
Posts: 35
Location: AR-USA
|
| Posted: Wed Jan 28, 2004 3:46 am Post subject: |
|
|
I figured out what the problem was and fixed it. My devfsd.conf was empty. Man, portage chopped up a bunch of my conf files. So I booted from the LiveCD, mounted the hard drive, went under /usr/portage/sys-fs/devfsd/files and copied the devfsd.conf in there over the old one. Now everything works like a charm... again.  |
|
| Back to top |
|
|
|
Installing Gentoo
