I got the above message after boot up from an upgrade from Slack 12.1 to 12.2 . Was given a choice of Cntrl D or root password to fix file system. I did the root password from my old system and got in. But that is all. Any ideas of where to start to fix this.

Right now I have only a read only 12.2 system.
Not worried about loosing anything. This Slack 12.2 drive is a clone of my working 12.1 system.

my clone drive 12.2 and regular 12.1 drives are set up:
hda1: Xubuntu
hda2: Slackware root
hda3: /home
hda4: swap

Tried a fsck -t ext3 /dev/hdc2 using my 12.1 system on the unmounted 12.2 drive. No problems found. I think the 12.2 system complained about read only file system, when I tried that.

Guessing it's a config problem , fstab maybe, but don't really know where to start.

Currently stuck at Step 4. of Patric Volkerding's UPGRADE.TXT guide.

Had good experiences with Slack 3.2 many years ago and after a long hiatus away from linux, now love Slackware 12.1 version. So we are Slack friendly here.
Thanks

Yes, I get the same message (Slack 12.1. kernel 2.6.27.10)
My impression is that it can be ignored (though it's irritating).
Maybe the boot sequence is slightly incorrect, something
like that. As you say, maybe fstab.

I think not, 'cause I've changed options in fstab (I had the same problem after upgrading) and that didn't solve the problem.

Take a look at: http://www.linuxquestions.org/questi...o-12.2-690421/

..maybe it's a rc.udev.new problem?

But does it still stop you booting? I've had this error message ever
since I installed Slack 12.1 and kernel 2.6.24.5, but it has never been
a serious problem. It's annoying, but nothing more. I don't have
rc.udev.new anyway. Next time I boot I'll note down the message
in detail, then we'll try and get to the bottom of this

Which kernel are you running?

If you run the generic smp one, what command did you use for generating your initrd.gz image file?

According to README.initrd, your command should have been:

In my case, the system would stop just after that fsck message, proposing to use ctrl-d or to try different superblock.
About initrd, I guess I didn't need one, because my kernel was huge.smp

I had this problem and it turned out that my /etc/fstab had been corrupted. I'm still not sure how it happened but booting from install dvd and restoring a working backup of fstab fixed it.

Did you change the fstab in the cloned drive to the correct partition for '/'?

I use a huge.s kernel in both 12.1 and 12.2. Kernel in 12.1 was custom compiled for 586 AMD K6+ processor, module support for USB Mass Storage support, and finally libcap support enabled.

The fstab looks identical in 12.1 and 12.2. I don't see why I should modify it. I simply swap out the two drives using the same ide cable connections.

I don't pass the kernel any initrd in 12.1 or 12.2

It is the rc.udev that is your problem. The problem occurs because udevtrigger is no longer a part of udev. If you compare rc.udev and rc.udev.new, you will see that the latter does not contain udevtrigger. In my experience with this upgrade, all you have to do is backup rc.udev, rename rc.udev.new to rc.udev, chmod 755 rc.udev, also change permissions on your backup rc.udev, so both versions dont run. Reboot and your set. Thats what I did anyways.

Hope this helps,
DragonM15

Thank you DragonM15!

rc.udev.new is the ticket, and it really worked!
There has been lots of changes on my old system since I posted this.
I'll do a fresh clone of my old hard drive and start migrating to Slackware 12.2
as time permits.

Thanks again!

Anytime, thats what we are all here for.