fsck.ext3:no such file/superblock corrupt on boot...!!

cayenne · l33t Joined: 17 Oct 2002 Posts: 945 Location: New Orleans

Hello all,

Well, this is the pits. I had my media box ready to move into the living room...just had gotten wireless working, shut it down..took it in there...fired it up and it blew up.

All hd's and such seem to be found ok...in bios and starting of Gentoo boot. But, then crashed with this:

* Checking root filesystem

fsk.ext3: no such file or directory while trying to open /dev/hda1

/dev/hda1:

The superblock could 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>

File system could not be fixed :-(

Ok...I've got my hda set up as the following:

/dev/hda1 ext3
/dev/hda2 swap
/dev/hda3 reiserfs

Kernel is gentoo-sources-2.6.8-r8

Just before I had shut down...I'd emerge sync'ed
I was following this guide for wireless:
https://forums.gentoo.org/viewtopic.php?t=122435

I'd emerged baselayout-1.11.3 and the other dependent file sysvinit (I don't recall the version...but, all were done with ACCEPT_KEYWORDS="~x86"

I shutdown normal. Unplugged everything...hooked up in living room...when I plugged in the AC on the computer..it fired up (forgot had sed in bios to restart after power failure)...and it came up with this.

That's about all the info I can think of. Oh..I had just set it to start using kdm as the gui boot X too.....I had emerged a new portage system...and etc-updated files...almost all by hand...last few appeared to not change anything I knew could break anything...and did the last 5 or 6 of them with the -5 option. I'm usually quite careful..and didn't see anything that would have borked it...

At the point it stops, it allows me to enter the root password...and I can look around the filesystem of /dev/hda

I can look all around on /dev/hda3....all directories are there...etc.

So...at this point, I'm not sure what to do...or what to look for...it was working, I shut down..moved box...plugged in...and wham...

All suggestions, explanations and links greatly appreciated!!!

cayenne
_________________
Light travels faster than sound. This is why some people appear bright until you hear them speak.........

speeddemon · Apprentice Joined: 27 Sep 2003 Posts: 162

I just had this same problem too, and I tried, but couldn't fix it. Course since its just the boot partition, its easy to copy to a different partition, and just reformat. Worked fine for me.

gerix · Posted: Sun Oct 24, 2004 11:41 pm Post subject:

same error here with ext2 boot partition and the latest baselayout. to reformat did not help me:
fsck.ext2: No such file or directory while trying to open /dev/hda1

of course, the fsck executable exists in /sbin, but even the changed /etc/init.d/checkroot

xanzi · n00b Joined: 24 Oct 2004 Posts: 3

I'm having the same problem, and some help can be found here.

cayenne · l33t Joined: 17 Oct 2002 Posts: 945 Location: New Orleans

gerix · Posted: Mon Oct 25, 2004 12:20 am Post subject:

but i'm sure the mistake is in the latest baselayout-1.11.3 - no fstab was overwritten on my system an the filesystem isn't corrupt.
it's a "fresh" install with mostly stable ebuilds, except the baselayout 'cause of the cute wireless-config scripts.
_________________
mfg
gerix

cayenne · l33t Joined: 17 Oct 2002 Posts: 945 Location: New Orleans

emorphix · Apprentice Joined: 09 Oct 2004 Posts: 189 Location: Earth

I am also having the exact same issue, I even tried different kernels had had the exact same error. I tried formatting it again and still had the same issue. all this with the baselayout 1.11.3
_________________
Ebuild Exchange
http://www.ebuildexchange.org
The Portage Tree For Gentoo Users
Created By Gentoo Users

Raoul_Duke · Posted: Mon Oct 25, 2004 7:37 am Post subject:

Same here......i was careful when etc-updating so i dont know why

_________________
www.iamthepenguin.com

emorphix · Apprentice Joined: 09 Oct 2004 Posts: 189 Location: Earth

I'm starting to wonder if this is a bug of some sort?
How can we find some more information ont his issue?
_________________
Ebuild Exchange
http://www.ebuildexchange.org
The Portage Tree For Gentoo Users
Created By Gentoo Users

Raoul_Duke · Posted: Mon Oct 25, 2004 8:03 am Post subject:

It's something to do with the change in config files....i just downgraded baselayout (and switched to the old config files) and it booted fine. I'm gonna hold out until we know more
_________________
www.iamthepenguin.com

Rafje

Same here. Baselayout-1.11.3 also made my system unbootable.

anderlin · Posted: Mon Oct 25, 2004 8:54 am Post subject:

I got the same error. Somehow devfsd had been unmerged (it might have something to do with my recent use of emerge --depclean world...).

gamackey1337 · n00b Joined: 25 Oct 2004 Posts: 3

I also encountered this same problem. I get a different error, as I use reiserfs for all my partitions.

I disabled any type of checking of the /boot partition ("0 0") in /etc/fstab so that I could at least log into the system. At that point, I can then see all of the partitions and mount them and everything is fine (though I would have to manually load everything, due to it not loading at startup).

However, at startup it says it can't find any of these partitions. This problem occurred immediately after the Baselayout update and a *very* careful etc-update.

Anyway, I'm getting some sleep...hopefully someone figures out a fix for this apparent bug, as I just spent the last two days building a new Gentoo system that *was* working fabulously well.

gamackey1337 · n00b Joined: 25 Oct 2004 Posts: 3

Unfortunately, "emerge devfsd" didn't work for me. I have also never done a depclean on this system and I know devfsd was not a package that was unmerged at any point so far. Thanks for the info, though.

I'm pretty sure the problem is with /etc/conf.d/rc, as mentioned above, because I remember that being one of the files replaced in the etc-update after the baselayout-1.11.3 update. Hope someone figures out a fix for this bug soon...

ralle · Posted: Mon Oct 25, 2004 9:32 am Post subject:

I have this problem, too.
After the promt "give root password for maintanance" I gave my root password to look what's inside /dev, and all the /dev/hdXX files are missing.
So I suppose it has something to do with devfsd and the new config files after updating to baselayout-0.11.3 (switched to 0.11 because of the wireless config thing).

ralle · Posted: Mon Oct 25, 2004 10:13 am Post subject:

OK guys I just found out a simple solution how to boot your systems again:

Get some livecd, boot from it and mount the partition that contains /etc.
cd into <mountpoint>/etc/conf.d and edit rc. Change

rmcknt · Posted: Mon Oct 25, 2004 11:22 am Post subject:

ok guys, i've got the same prob here after updating to the new version of baselayout

same error, cant check root fs, all dev/hd's and /dev/sd's are gone

so the thning i did to boot my system again was the disable root fs check at boot time

edit /etc/fstab

i changed the line
/dev/sda2 /boot ext3 noauto,noatime 1 1
to
/dev/sda2 /boot ext3 noauto,noatime 0 0

after rebooting my sys, there were still errors that things in /dev are missing, so i suggest to downgrade to an earlier version of baselayout

mike

Ecco · Posted: Mon Oct 25, 2004 1:32 pm Post subject:

Maybe someone would like to post baselayout-1.11.2.ebuild since it seems to have been wiped out of existance everywhere... Renaming the ebuild does _not_ work.

twoup · n00b Joined: 25 Oct 2004 Posts: 14 Location: Australia

The problem is definately somewhere in the /sbin/rc file.. No need to do anything drastic like rebuilds..etc...etc..

I grabbed the rc file from my livecd and it workes fine... So far I havent been able to work out exactly whats broken in the broken rc file as there is a big rewrite...

How can I post the rc script? This is my first post in the forum and im not sure how things work... Is a dump into a message ok??

Cheers
Twoup

creep09 · n00b Joined: 08 Dec 2003 Posts: 6

Until before 5 minutes I had the same problem with you guys.

The solution to my problem was, as mentioned earlier, to downgrade baselayout :evil:

. The previous version was baselayout-1.10.4.ebuild.

For those of you who don't know how to downgrade to a previous version, just search in /usr/portage/sys-apps/baselayout for your previous version and just emerge it.

rmcknt · Posted: Mon Oct 25, 2004 2:26 pm Post subject:

creep09 · n00b Joined: 08 Dec 2003 Posts: 6

Ecco · Posted: Mon Oct 25, 2004 3:20 pm Post subject:

baselayout-1.11.3 has been unmasked, despite critical bugs. Nice

For anyone who's interested, 1.11.2 can still be found in the allmighty google-cache

I just switched my laptop to udev. That was long overdue anyway. So everything workes fine again (after some fiddling to get my LVM to work)

ralle, X probably misses /dev/mouse. A simple ln -s /dev/psaux /dev/mouse should fix that.

_Kevin · Posted: Mon Oct 25, 2004 7:36 pm Post subject:

I replaced my /sbin/rc file and my system returned to normal boot with one exception - I got a message with error something like this: