Problem Booting Slackware Vn12.0

Mike

I've successfully installed Slackware Vn 12.0 on other machines but I'm
hitting problems with this installation. It's been running Vn 11.0
(Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
boot the 2.6.21.5 kernel it fails with -

UDF-fs: No VRS found
(1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
VFS: Cannot open root device "301" or unknown-block(3,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(3,1)

I've tried both the "huge" and the "huge-smp" kernels without success.
I've also tried formatting the root disk with ext2 instead of my usual
choice of jfs (although jfs has been OK on the other machines).

It seems that others have had similar problems with the 2.6 kernel with
other distributions but I couldn't find any references to other
Slackware users having this problem.

Any suggestions anyone?

--
Mike

root

Mike <spamdump@fensoft.co.uk> wrote:
> I've successfully installed Slackware Vn 12.0 on other machines but I'm
> hitting problems with this installation. It's been running Vn 11.0
> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
> boot the 2.6.21.5 kernel it fails with -
>
> UDF-fs: No VRS found
> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
> VFS: Cannot open root device "301" or unknown-block(3,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(3,1)
>

Do you get this message immediately after the first boot into
the newly installed slackware 12 or have you rebuilt the
kernel in some way?

What happens if you put in the first install disk and follow
the instructions to boot into your installed system:

huge.s root=/dev/xxxx rdinit=ro

Mike

root wrote:
> Mike <spamdump@fensoft.co.uk> wrote:
>> I've successfully installed Slackware Vn 12.0 on other machines but I'm
>> hitting problems with this installation. It's been running Vn 11.0
>> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
>> boot the 2.6.21.5 kernel it fails with -
>>
>> UDF-fs: No VRS found
>> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
>> VFS: Cannot open root device "301" or unknown-block(3,1)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(3,1)
>>
>
> Do you get this message immediately after the first boot into
> the newly installed slackware 12 or have you rebuilt the
> kernel in some way?
>
> What happens if you put in the first install disk and follow
> the instructions to boot into your installed system:
>
> huge.s root=/dev/xxxx rdinit=ro
>
I'm upgrading from Vn11.0. I have all the installation files on one of
the disks (/dev/hdc1) so, following the instructions in
"CHANGES_AND_HINTS.TXT", I first installed the 2.6 kernel and its
modules and tried to re-boot. That's when it first failed. Since then,
I've reformatted the root disk (/dev/hda1) as ext2 and tried both the
"huge" and the "huge-smp" kernels with no success.

--
Mike

Richard James

Mike wrote:

> Richard James wrote:
>> Mike wrote:
>>
>>> I've successfully installed Slackware Vn 12.0 on other machines but I'm
>>> hitting problems with this installation. It's been running Vn 11.0
>>> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
>>> boot the 2.6.21.5 kernel it fails with -
>>>
>>> UDF-fs: No VRS found
>>> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
>>> VFS: Cannot open root device "301" or unknown-block(3,1)
>>> Please append a correct "root=" boot option
>>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>>> unknown-block(3,1)

I think your problem is the 2.6 Kernel IDE chipset driver for your specific
motherboard.

I managed to replicate your problem by accident. I had a virtual machine
running Slackware 12 crash while compiling a Kernel, this trashed the vm's
file system. When rebooting that virtual machine the Kernel came up with
those same error messages. It also said it first tried the Ext4 Ext3 and
Ext2 filesystem but failed to find a valid filesystem.

However you know that your filesystem is not corrupt because it boots off of
a 2.4 series Kernel. The main thing I can think of that would make the 2.6
Kernel think your filesystem is corrupt is the chipset driver that it is
communicating to your hard drive with. If that driver is faulty then that
would explain why you get those error messages from the 2.6 Kernel and not
the 2.4 Kernel.

Do you know what your motherboard chipset is?

Richard James

Mike

Richard James wrote:

>>> Mike wrote:
>>>
>>>> I've successfully installed Slackware Vn 12.0 on other machines but I'm
>>>> hitting problems with this installation. It's been running Vn 11.0
>>>> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
>>>> boot the 2.6.21.5 kernel it fails with -
>>>>
>>>> UDF-fs: No VRS found
>>>> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
>>>> VFS: Cannot open root device "301" or unknown-block(3,1)
>>>> Please append a correct "root=" boot option
>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>>>> unknown-block(3,1)
>
> I think your problem is the 2.6 Kernel IDE chipset driver for your specific
> motherboard.
>
> I managed to replicate your problem by accident.

Well, I didn't do it intentionally. ;-)

> I had a virtual machine
> running Slackware 12 crash while compiling a Kernel, this trashed the vm's
> file system. When rebooting that virtual machine the Kernel came up with
> those same error messages. It also said it first tried the Ext4 Ext3 and
> Ext2 filesystem but failed to find a valid filesystem.
>
> However you know that your filesystem is not corrupt because it boots off of
> a 2.4 series Kernel. The main thing I can think of that would make the 2.6
> Kernel think your filesystem is corrupt is the chipset driver that it is
> communicating to your hard drive with. If that driver is faulty then that
> would explain why you get those error messages from the 2.6 Kernel and not
> the 2.4 Kernel.
>
> Do you know what your motherboard chipset is?
>
I think the M/B is an ABIT BL7 with the Intel 845 chipset but I'll need
to check that. The machine is running at the moment (with the 2.4
kernel) and I shan't be able to try again until the weekend.

When I was attempting to install the 2.6 kernel, I did manage to corrupt
the root partition (I had to restore that from a back-up) which, I
think, tends to support your idea of a faulty driver. A search on
Google, just now, with "Intel 845 chipset"+"IDE driver" has thrown up a
few references to problems with the 2.6 kernel but I haven't had time to
go through them yet.

Thanks for your input, I'll do some investigating this week.

--
Mike

Richard James

Mike wrote:

> I've successfully installed Slackware Vn 12.0 on other machines but I'm
> hitting problems with this installation. It's been running Vn 11.0
> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
> boot the 2.6.21.5 kernel it fails with -
>
> UDF-fs: No VRS found
> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
> VFS: Cannot open root device "301" or unknown-block(3,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(3,1)

UDF is the filesystem for a CD-ROM. Are you trying to boot off of a CD/DVD?
It almost seems as if you have gotten a Kernel for booting the CD/DVD
installer and installed that onto your harddrive. Another possibility is
that it is loading the installers initrd and that is causing the problems.

Check the lilo.conf that everything is working sanely. That in the section
that loads the huge kernel it doesn't include anything about an initrd.

> I've tried both the "huge" and the "huge-smp" kernels without success.
> I've also tried formatting the root disk with ext2 instead of my usual
> choice of jfs (although jfs has been OK on the other machines).
>
> It seems that others have had similar problems with the 2.6 kernel with
> other distributions but I couldn't find any references to other
> Slackware users having this problem.

I found a reference on the Net about a similar problem
http://help.lockergnome.com/linux/Un...ict478387.html

Don't know if that will help

Richard James

Mike

Richard James wrote:
> Mike wrote:
>
>> I've successfully installed Slackware Vn 12.0 on other machines but I'm
>> hitting problems with this installation. It's been running Vn 11.0
>> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
>> boot the 2.6.21.5 kernel it fails with -
>>
>> UDF-fs: No VRS found
>> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
>> VFS: Cannot open root device "301" or unknown-block(3,1)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(3,1)
>
> UDF is the filesystem for a CD-ROM. Are you trying to boot off of a CD/DVD?

No. The machine doesn't have a CD/DVD. It currently runs Slackware
Vn11.0, which was installed over a network. I'm thinking about fitting
a CD drive in it and trying to install from there but I don't hold out
much hope.

> It almost seems as if you have gotten a Kernel for booting the CD/DVD
> installer and installed that onto your harddrive. Another possibility is
> that it is loading the installers initrd and that is causing the problems.
>
I'm upgrading so I've only installed the kernel and module packages so
far. All the installation files are on one of the disks (/dev/hdc1) so
I just used pkgtool to install the new kernel as per the upgrade.txt
instructions.

> Check the lilo.conf that everything is working sanely. That in the section
> that loads the huge kernel it doesn't include anything about an initrd.
>
Checked - I can't see anything wrong there.

>> I've tried both the "huge" and the "huge-smp" kernels without success.
>> I've also tried formatting the root disk with ext2 instead of my usual
>> choice of jfs (although jfs has been OK on the other machines).
>>
>> It seems that others have had similar problems with the 2.6 kernel with
>> other distributions but I couldn't find any references to other
>> Slackware users having this problem.
>
> I found a reference on the Net about a similar problem
> http://help.lockergnome.com/linux/Un...ict478387.html
>
Yes, I've seen that and quite a few others. I've yet to find one giving
the answer though. :-( Thanks anyway.

--
Mike

Richard James

Mike wrote:

> I've successfully installed Slackware Vn 12.0 on other machines but I'm
> hitting problems with this installation. It's been running Vn 11.0
> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
> boot the 2.6.21.5 kernel it fails with -
>
> UDF-fs: No VRS found
> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
> VFS: Cannot open root device "301" or unknown-block(3,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(3,1)

UDF is the filesystem for a CD-ROM. Are you trying to boot off of a CD/DVD?
It almost seems as if you have gotten a Kernel for booting the CD/DVD
installer and installed that onto your harddrive. Another possibility is
that it is loading the installers initrd and that is causing the problems.

Check the lilo.conf that everything is working sanely. That in the section
that loads the huge kernel it doesn't include anything about an initrd.

> I've tried both the "huge" and the "huge-smp" kernels without success.
> I've also tried formatting the root disk with ext2 instead of my usual
> choice of jfs (although jfs has been OK on the other machines).
>
> It seems that others have had similar problems with the 2.6 kernel with
> other distributions but I couldn't find any references to other
> Slackware users having this problem.

I found a reference on the Net about a similar problem
http://help.lockergnome.com/linux/Un...ict478387.html

Don't know if that will help

Richard James

Richard James

Mike wrote:

> Richard James wrote:
>> Mike wrote:
>>
>>> I've successfully installed Slackware Vn 12.0 on other machines but I'm
>>> hitting problems with this installation. It's been running Vn 11.0
>>> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
>>> boot the 2.6.21.5 kernel it fails with -
>>>
>>> UDF-fs: No VRS found
>>> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
>>> VFS: Cannot open root device "301" or unknown-block(3,1)
>>> Please append a correct "root=" boot option
>>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>>> unknown-block(3,1)

I think your problem is the 2.6 Kernel IDE chipset driver for your specific
motherboard.

I managed to replicate your problem by accident. I had a virtual machine
running Slackware 12 crash while compiling a Kernel, this trashed the vm's
file system. When rebooting that virtual machine the Kernel came up with
those same error messages. It also said it first tried the Ext4 Ext3 and
Ext2 filesystem but failed to find a valid filesystem.

However you know that your filesystem is not corrupt because it boots off of
a 2.4 series Kernel. The main thing I can think of that would make the 2.6
Kernel think your filesystem is corrupt is the chipset driver that it is
communicating to your hard drive with. If that driver is faulty then that
would explain why you get those error messages from the 2.6 Kernel and not
the 2.4 Kernel.

Do you know what your motherboard chipset is?

Richard James

Mike

Richard James wrote:
> Mike wrote:
>
>> I've successfully installed Slackware Vn 12.0 on other machines but I'm
>> hitting problems with this installation. It's been running Vn 11.0
>> (Kernel Vn 2.4.33.3) and it still boots OK with that but, when I try to
>> boot the 2.6.21.5 kernel it fails with -
>>
>> UDF-fs: No VRS found
>> (1,0)cfs2_fill_super:561 ERROR: superblock probe failed!
>> VFS: Cannot open root device "301" or unknown-block(3,1)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(3,1)
>
> UDF is the filesystem for a CD-ROM. Are you trying to boot off of a CD/DVD?

No. The machine doesn't have a CD/DVD. It currently runs Slackware
Vn11.0, which was installed over a network. I'm thinking about fitting
a CD drive in it and trying to install from there but I don't hold out
much hope.

> It almost seems as if you have gotten a Kernel for booting the CD/DVD
> installer and installed that onto your harddrive. Another possibility is
> that it is loading the installers initrd and that is causing the problems.
>
I'm upgrading so I've only installed the kernel and module packages so
far. All the installation files are on one of the disks (/dev/hdc1) so
I just used pkgtool to install the new kernel as per the upgrade.txt
instructions.

> Check the lilo.conf that everything is working sanely. That in the section
> that loads the huge kernel it doesn't include anything about an initrd.
>
Checked - I can't see anything wrong there.

>> I've tried both the "huge" and the "huge-smp" kernels without success.
>> I've also tried formatting the root disk with ext2 instead of my usual
>> choice of jfs (although jfs has been OK on the other machines).
>>
>> It seems that others have had similar problems with the 2.6 kernel with
>> other distributions but I couldn't find any references to other
>> Slackware users having this problem.
>
> I found a reference on the Net about a similar problem
> http://help.lockergnome.com/linux/Un...ict478387.html
>
Yes, I've seen that and quite a few others. I've yet to find one giving
the answer though. :-( Thanks anyway.

--
Mike