suddenly no /dev/hda3 after update?

alastairII · n00b Joined: 02 Jul 2004 Posts: 67 Location: Berkeley, CA

I did part of an emerge -uD world yesterday after a month, which stopped because it emerged a new kernel and I hadn't configured the new version yet. But I didn't care, because I had a bigger problem, which was that after I connected everything back up (after being in storage) sound didn't work. So I thought I might reboot, because that occasionally fixes things by restarting all the various services I don't know about. However, when I rebooted, there seemed to be no such file or directory /dev/hda3, my / partition. So it said:

unclecharlie · Posted: Tue Jan 17, 2006 4:17 pm Post subject: boot to the live cd...

alistair,

I'm assuming that /dev/hda3 is your fs root. If so, any problems with /dev/hda3 will need to be fixed without it mounted. To do so, boot to the gentoo live cd or a rescue cd, i.e.- http://sysresccd.org, then run your filesystem check with nothing mounted.

Charlie ;-)

alastairII · n00b Joined: 02 Jul 2004 Posts: 67 Location: Berkeley, CA

Booted into knoppix, and:

lump · n00b Joined: 16 Jun 2003 Posts: 12

I'm seeing a similar problem.

I ran my updates this morning, and after an attempt at reboot I see a similar error:

fsck.ext2: No such file or directory while trying to open /dev/hda2

/etc/fstab is fine, it was not changed with the update and still shows /dev/hda2 on /boot, etc.

But, are no hd* under /dev.

The odd thing is that it gets partly booted, and mount shows /dev/hda4 on /, even though there is no /dev/hda.

BlackEdder · Posted: Tue Jan 17, 2006 7:49 pm Post subject:

What does emerge info show?

alastairII · n00b Joined: 02 Jul 2004 Posts: 67 Location: Berkeley, CA

This is from chrooted knoppix, so probably some of it is a bit wrong (e.g. the kernel version), but here:

landi · n00b Joined: 17 Jan 2006 Posts: 5

Hi!

Seems that we have a problem in portage, i updated my gentoo a few hours ago and after rebooting it hangs with the error:
failed to open the device '/dev/hdc3': No such file or directory

the funny thing is that the HD is already mounted, so i can look into the /dev directory and there is nearly everything missing (no hd.., sd.. ).
When i boot with knoppix the whole things are there again.

landi · n00b Joined: 17 Jan 2006 Posts: 5

Hi again!

Since i can't sleep with the knowledge of having a not working gentoo i searched for the reason of the problem and think i found it. I first started with the Gentoo Live CD and chrooted my gentoo-version (like in the installation tutorial). Afterwards i searched in the emerge.log file for all sys-... packages, that were updated at the last update. After a few ineffective trys of downgrading packages i downgraded the packages:

sys-apps/baselayout
and
sys-process/psmisc

I think psmisc shouldn't be involved in this problem, so it should be enough to downgrade sys-apps/baselayout (in my case from version 1.11.14 to 1.11.13-r1).

And don't forget to run etc-update.

greetings,
Landi

alastairII · n00b Joined: 02 Jul 2004 Posts: 67 Location: Berkeley, CA

Thanks! That worked. This is probably a stupid question, but how do I tell Portage not to upgrade that again?

glober · Posted: Wed Jan 18, 2006 5:38 am Post subject:

Just for the record I would like to say that I also had a problem where the root drive failed a fsck check after doing emerge -uD world and the problem as has been mentioned was baselayout being upgraded. Version 1.11.14 is problematic, so downgrading to 1.11.13-r1 fixed the problem.

BTW, I have gentoo set for stable, so I am suprised that this happened. My question at at this point is, how do I know the problem is fixed without hosing my system again, do I wait for the version after 1.11.14 to become stable, or is 1.11.14 going to be fixed?

landi · n00b Joined: 17 Jan 2006 Posts: 5

To avoid updating baselayout again to version 1.11.14 you can create an entry into your package.mask file (which lies in /etc/portage, if not you can create one).
A simple line with
=sys-apps/baselayout-1.11.14
should be enough for ignoring it at the next update.

hanj · Veteran Joined: 19 Aug 2003 Posts: 1500

Hello All

Is this fixed with latest udev update (sys-fs/udev-079)?

Notes from changelog..

kellwood · Posted: Wed Jan 18, 2006 10:26 pm Post subject:

Hi All,

In my case, it is no /dev/sd*. How do I downgrade baselayout when I can't boot properly?

Thanks
Kevin

glober · Posted: Thu Jan 19, 2006 12:53 am Post subject:

kellwood · Posted: Thu Jan 19, 2006 1:08 am Post subject:

Thanks,

I should have thought of that.

Kevin

glober · Posted: Thu Jan 19, 2006 2:00 am Post subject:

Just a warning to everybody, baselayout version 1.11.14-r1 is also problematic. Upon doing emerge -uD world, this version comes up as the new stable version, doesn't look so stable to me. This is getting tedious. Can somebody look into this please.

devsk · Posted: Fri Jan 20, 2006 10:35 pm Post subject:

I am hitting this problem too. Can someone please post what the status of this thing is? what works?

EDIT: ok, downgrading the baselayout works.

ianw · n00b Joined: 05 Oct 2005 Posts: 9

Same problem here with /dev/sda1. I'm also getting a system.map not found warning beforehand - is this likely to be related in some way?

Edit: Yep again downgrading baselayout to 1.11.13-r1 worked wonders. I presume the only way to do this is as I did through the files in /usr/portage? Apologies for the stupid question but I'm still fairly new to this all... and somehow things don't generally go wrong!

gfaccin · Tux's lil' helper Joined: 20 Aug 2004 Posts: 120

Hello there, I had the same problem here. In the end I managed to fix it by changing fstab instead of downgrading the ebuild. My thread is here; perhaps it might be useful to you:

https://forums.gentoo.org/viewtopic-t-424087-start-0.html

alastairII · n00b Joined: 02 Jul 2004 Posts: 67 Location: Berkeley, CA

I guess my question is that is baselayout-1.11.14-r2 fixed, or am I going to have to change my fstab like gfaccin did? Perhaps one of the gentoo devs knows if it's going to be fixed?

gfaccin · Tux's lil' helper Joined: 20 Aug 2004 Posts: 120

alastairli:

Right now I'm running emerge sync && emerge world here, to test the new ebuild. I'll be using my original pre-crash fstab in the test. I'll be posting results soon.

gfaccin · Tux's lil' helper Joined: 20 Aug 2004 Posts: 120

Ok... I'm now running the latest version of baselayout (1.11.14-r2). I tried my original fstab and the error is still happening. The good news is that the fstab fix is still working with this version, so, until an ebuild fix arrives, I'll be using the modified fstab.

mwojc · Posted: Sat Jan 21, 2006 9:52 pm Post subject:

Hi guys!
I think, you should recompile your kernel with the options:

alastairII · n00b Joined: 02 Jul 2004 Posts: 67 Location: Berkeley, CA

Uh... in 2.6.14-r5, there doesn't appear to be any mention of /dev file system support in Pseudo Filesystems...

chance2105 · emerge --oneshot =sys-apps/baselayout-1.11.13-r1

I was bitten by this baselayout issue. Unfortunately for me, I couldn't just boot from the LiveCD and chroot into my install - the linux-headers version was greater than the kernel on my LiveCD version, so chroot wouldn't run ("kernel too old"), and on my arch (sparc64) there isn't a LiveCD that has a recent enough kernel for chroot to work.

Not only could I not chroot, but my filesystem is spread out over several partitions -- simply using the LiveCD to mark FSTAB to not check the root partition on boot wasn't going to work to boot the system and downgrade baselayout.

I was beginning to think I was going to have to reinstall, but here's how I fixed it in the end (culling from these posts, you guys are great for ideas):

PREFACE: USE AT YOUR OWN RISK .. although I think it's all relatively harmless ... read to the end of this post before trying my method.

Step 1 - Modify /etc/fstab
Boot the LiveCD and mount the system's root filesystem. Modify FSTAB to read 0 on the "pass" parameter of the root filesystem. Reboot, and let machine boot into your install.

Step 2: Login for "maintenance" during boot
The init scripts are going to bail out when the remainder of the partitions can't be mounted, so enter the root password.

Step 3: Manually create /dev/ nodes for your partitions.
In my case, MAKEDEV wouldn't / couldn't create /dev/sda* nodes for my SCSI disk. (And thank [deity] these commands were available.) So I resorted to using mknod.

This link got me started: http://www.faqs.org/docs/linux_admin/x797.html

Following that link, I downloaded the kernel sources onto another computer (my /usr/ is on a seperate partition on my broken gentoo install.. lucky me) and sourced linux/Documentation/devices.txt for the device major / minor numbers for the SCSI disk (in my case, the major number was 8, the minor was the number of my partition, eg sda1 = 1, sda4 = 4).

So the command finally ended up: