I just compiled a new kernel for my MSI Wind, the 2.6.26.2 kernel, and I compiled it with jfs support so I wouldn't need an initrd, but at boot it gives me an error, it tells me to give the root password for maintenance or press ctrl+d for setup. I've tried running jfs_fsck, both as root at bootup and by loading the slackware cd, same error. Eventually, and I'm not sure when it started doing this, it just automatically continues with boot, as if there were no errors, and then after awhile it will start giving reboot messages, and shut down before I ever get to udev or the log-in.

So, any ideas? I remember some jfs errors when I was compiling my kernel, but it took 1.5 hours for my kernel to compile on my laptop, I really don't want to go through that again. If the jfs should be the problem, is there any way I can compile those individually?
I can boot into slackware using the boot cd or one of the old kernels, so I'm not totally blocked out.

Have you tried any other filesystems? Is there a particular reason you want to use JFS?

I saw a thread on here that said JFS was pretty good, so I started using it. It's a bit faster than ext3, I believe. But I am not going to reformat my install just to fix this. There has to be another way.

Hi,

When you used the Slackware install cd/dvd to boot. What was done next to attempt the repair of the filesystem? What errors?

There were no errors,
Thanks for your help, I found out that the error was in my fstab. The install process read all my drives as hda, but when I booted slackware read them has sda, thus the fstab that the install setup looked at was wrong. I changed the entries and it all worked out.

Hi,

Glad to hear your up!

You could have passed the 'noprobe = hdn' (where n= a,b,c,d) option to the kernel.

It sounds like you used the new ATA kernel driver, rather than the older one that the default Slackware kernels use. The new driver addresses both SATA and PATA devices as /dev/sdX. The same thing actually happened to me when I built a new kernel for my EEE 701.

Yeah, I started doing that, everything is resolved so far.

Is this the case for dvd also? In my system (slackware 12.1) my sata hd always show up as /dev/sdx.

But my sata dvd has shown up as /dev/hdc or /dev/sr0 depending on kernel settings.

I've never seen dvd show up as /dev/sdx. I did recently have problems burning a dvd and so I'm curious if it showing as /dev/sdx might improve performance.