SEO

I was upgrading my slack 12 to 12.1 ( using this script
ftp.slackware.com/pub/slackware/slackware-12.1/UPGRADE.TXT ), and
whena boot my computer I received the following erro:
--------------------------------------------------------------------------------------------------------------------------
VFS: Cannot open root device "806"or unknown-block(8,6)
Please append a correct "root=" boot option; here are the
available partitions:
0300 312571224 hda driver: ide-scsi
0301 20482843 hda1
0302 1 hda2
0305 20482843 hda5
0306 4996183 hda6
0307 4000153 hda7
0308 2000061 hda8
0309 2000061 hda9
030a 128905528 hda10
030b 129700746 hda11
1600 4194302 hdc driver: ide-cdrom

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(8,6)
--------------------------------------------------------------------------------------------------------------------------

In fact I understood the problem, I need to append a correct root, but
I did this change on lilo.conf and the problem persists.

And I realized something strange, I don`t have a IDE Hard Disk, is a
SATA.
So, why the available partitions are hda instead of sda? Do I need to
change some kernel configuration? How can I do it?

Thanks.

Hallo, Osiro,

Du meintest am 11.05.08:

> Cannot open root device "806"or unknown-block(8,6)

The system looks for sda6.

> Please append
> a correct "root=" boot option; here are the available partitions:
> 0300 312571224 hda driver: ide-scsi

That's a strange driver for an IDE drive.

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".

Osiro <vinicius.osiro@gmail.com> typed on 2008-05-11:
> I was upgrading my slack 12 to 12.1 ( using this script
> ftp.slackware.com/pub/slackware/slackware-12.1/UPGRADE.TXT ), and
> whena boot my computer I received the following erro:
> --------------------------------------------------------------------------------------------------------------------------
> VFS: Cannot open root device "806"or unknown-block(8,6)
> Please append a correct "root=" boot option; here are the
> available partitions:
> 0300 312571224 hda driver: ide-scsi
> 0301 20482843 hda1
> 0302 1 hda2
> 0305 20482843 hda5
> 0306 4996183 hda6
> 0307 4000153 hda7
> 0308 2000061 hda8
> 0309 2000061 hda9
> 030a 128905528 hda10
> 030b 129700746 hda11
> 1600 4194302 hdc driver: ide-cdrom
>
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
> block(8,6)
> --------------------------------------------------------------------------------------------------------------------------
>
> And I realized something strange, I don`t have a IDE Hard Disk, is a
> SATA.
> So, why the available partitions are hda instead of sda? Do I need to
> change some kernel configuration? How can I do it?

I've seen this before, it seems the ide-disk driver is picking up your
sata drive. Reconfiguring your system to use it like this is not really
an option, as it's impossible to enable DMA.

The easiest way is to add hda=noprobe & hda=none to your kernel
parameters, then ide-disk will skip it and the correct driver will be
able to pick up your drive as sda.

Regards,
--
Bartosz Oudekerk
I think a better name for PAM might be SCAM, for Swiss Cheese Authentication
Modules, and have never felt that the small amount of convenience it provides
is worth the great loss of system security. -- Patrick Volkerding

Bartosz Oudekerk wrote:
> The easiest way is to add hda=noprobe & hda=none to your kernel
> parameters, then ide-disk will skip it and the correct driver will be
> able to pick up your drive as sda.

Afaik this has to be "ide0=noprobe hda=none". Or maybe ide1.

Martin

On 11 maio, 12:52, Bartosz Oudekerk <bartosz@see_my_GnuPG-key.com>
wrote:
> Osiro <vinicius.os...@gmail.com> typed on 2008-05-11:
>
>
>
> > I was upgrading my slack 12 to 12.1 ( using this script
> > ftp.slackware.com/pub/slackware/slackware-12.1/UPGRADE.TXT ), and
> > whena boot my computer I received the following erro:
> > --------------------------------------------------------------------------------------------------------------------------
> > VFS: Cannot open root device "806"or unknown-block(8,6)
> > Please append a correct "root=" boot option; here are the
> > available partitions:
> > 0300 312571224 hda driver: ide-scsi
> > 0301 20482843 hda1
> > 0302 1 hda2
> > 0305 20482843 hda5
> > 0306 4996183 hda6
> > 0307 4000153 hda7
> > 0308 2000061 hda8
> > 0309 2000061 hda9
> > 030a 128905528 hda10
> > 030b 129700746 hda11
> > 1600 4194302 hdc driver: ide-cdrom
>
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
> > block(8,6)
> > --------------------------------------------------------------------------------------------------------------------------
>
> > And I realized something strange, I don`t have a IDE Hard Disk, is a
> > SATA.
> > So, why the available partitions are hda instead of sda? Do I need to
> > change some kernel configuration? How can I do it?
>
> I've seen this before, it seems the ide-disk driver is picking up your
> sata drive. Reconfiguring your system to use it like this is not really
> an option, as it's impossible to enable DMA.
>
> The easiest way is to add hda=noprobe & hda=none to your kernel
> parameters, then ide-disk will skip it and the correct driver will be
> able to pick up your drive as sda.
>
> Regards,
> --
> Bartosz Oudekerk
> I think a better name for PAM might be SCAM, for Swiss Cheese Authentication
> Modules, and have never felt that the small amount of convenience it provides
> is worth the great loss of system security. -- Patrick Volkerding

Some linux forums said to reconfigure kernel with support to SATA
drivers, do you think this is one way to solve it?
I'm analyzing my kernel configuration now, but I don't have idea how I
can do it?

Martin Schmitz <usenet@rmz.ath.cx> typed on 2008-05-11:
> Bartosz Oudekerk wrote:
>> The easiest way is to add hda=noprobe & hda=none to your kernel
>> parameters, then ide-disk will skip it and the correct driver will be
>> able to pick up your drive as sda.
>
> Afaik this has to be "ide0=noprobe hda=none". Or maybe ide1.

Well, hda=noprobe works for me. But my guess would be that using ide0
would work just as well, assuming you don't have a hdb device that does
need to be recognised by the driver.

Regards,
--
Bartosz Oudekerk
I think a better name for PAM might be SCAM, for Swiss Cheese Authentication
Modules, and have never felt that the small amount of convenience it provides
is worth the great loss of system security. -- Patrick Volkerding

Osiro <vinicius.osiro@gmail.com> typed on 2008-05-11:
> On 11 maio, 12:52, Bartosz Oudekerk <bartosz@see_my_GnuPG-key.com>
> wrote:
>> Osiro <vinicius.os...@gmail.com> typed on 2008-05-11:
>>
>> > And I realized something strange, I don`t have a IDE Hard Disk, is a
>> > SATA.
>> > So, why the available partitions are hda instead of sda? Do I need to
>> > change some kernel configuration? How can I do it?
>>
>> I've seen this before, it seems the ide-disk driver is picking up your
>> sata drive. Reconfiguring your system to use it like this is not really
>> an option, as it's impossible to enable DMA.
>>
>> The easiest way is to add hda=noprobe & hda=none to your kernel
>> parameters, then ide-disk will skip it and the correct driver will be
>> able to pick up your drive as sda.
>>
> Some linux forums said to reconfigure kernel with support to SATA
> drivers, do you think this is one way to solve it?
> I'm analyzing my kernel configuration now, but I don't have idea how I
> can do it?

If you're using one of Pats pre-compiled kernels, SATA support is in
there, the problem is another driver picking it up first. The kernel
parameters I specified earlier, tell the driver to leave the drive
alone so the correct driver can then pick it up.

To fix it in the kernel, you'd have to compile a kernel without
ide-disk, or ide-disk as a module which you could load after booting.

Note: I don't know if ATAPI devices (like your cdrom) use the driver. I
don't think so, but it's not really an issue if you compile it as a
module, I don't recall ever needing my cdrom drive till after booting.

Note2: I'm pretty sure it's ide-disk, but I haven't tested this by
removing ide-disk from my kernel(yet), like I describe above.

Note3: Please don't quote my .signature when replying.

Regards,
--
Bartosz Oudekerk
I think a better name for PAM might be SCAM, for Swiss Cheese Authentication
Modules, and have never felt that the small amount of convenience it provides
is worth the great loss of system security. -- Patrick Volkerding