LinuxQuestions.org - Problem mounting root file system with 12.2 rc1?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Problem mounting root file system with 12.2 rc1? (https://www.linuxquestions.org/questions/slackware-14/problem-mounting-root-file-system-with-12-2-rc1-689439/)

Problem mounting root file system with 12.2 rc1?

OK, some feedback for the slackware devs out there. I was trying to test a nagios Slackbuild package that I built on 12.1 to see if it works OK on 12.2rc1 I'm using virtualbox 2.0.6 on Windows to host the Slack machine.

- I installed 12.1 from scratch. Made no kernel changes (left huge in place)
- built an iso from slack-current as of Sunday eve (12/7).
- Ran the first three steps of the upgrade

Code:

upgradepkg /root/slackware/a/glibc-solibs-*.tgz

upgradepkg /root/slackware/a/pkgtools-*.tgz



    #!/bin/sh

    for dir in a ap d f k kde l n tcl x xap y ; do

      ( cd $dir ; upgradepkg --install-new *.tgz )

    done

I reran lilo and restarted. Now when it boots I get an message similar to:
Checking root filesystem
fsck 1.41.3
e2fsck: no such file or directory trying to open /dev/hda1.
The superblock could not be read...

It will allow me to login as root to "fix" the problem.

Its an ext3 filesystem and I've mounted it under a 12.1 install cd boot and run fsck and it reports clean.
If I try to run e2fsck -b 32786 /dev/hda1 (which it suggests as a possible fix) I'm told the device is busy (which makes no sense to me since it is unmounted)

FWIW, I've run Slack 12.1 in a VBOX virtual for months without problems.

What other information can I offer to assist with this?

You should have read and followed the instructions in CHANGES_AND_HINTS.TXT .. especially the part about dealing with .new files. Now, your UDEV does not work. You can fix this using the Slackware boot CD (or any other boot CD for that matter).

Eric

Well, I had read it, but I obviously got started too early this morning! udev has always been a mistery to me so perhaps it didn't sink in well. Let me take a stab at it.

Thanks

:study:Well, now isn't that amazing! Thanks again Alien_Bob.

I wonder if it would make sense for this package to overwrite the existing file knowing that it will cause this issue. Hmmm

Sorry do not take this into account

*** Sorry wrong suggestion I haven't seen that you used Huge kernel ***

When you upgraded packages, you upgraded the kernel (in a/ directory).

So you need to update the initrd image. Please refer to http://slackware.osuosl.org/slackwar.../README.initrd