No /dev/sd?? files

[Pita]

Was able to get /dev/sdb6 into lilo to boot into that partiion under VL.

/dev/sdb6 has to be in /dev. In fstab /dev/hdd6 remains and can thus be mounted. In lilo.conf setting is root=/dev/sdb6.

Just thought this might be useful for others having such an initial problem with that new device naming.

[Triarius Fidelis]

Well that's certainly idiosyncratic. How'd you track down the answer?

[Pita]

Well that's certainly idiosyncratic. How'd you track down the answer?

Meaning what ?

[Triarius Fidelis]

In LILO, you have to use /dev/sdb6.

But to mount the drive, you have to use /dev/hdb6.

That's strange.

[Pita]

In LILO, you have to use /dev/sdb6.

But to mount the drive, you have to use /dev/hdb6.

That's strange.

Strange, yes. Who can ever fathom Linux?

To run lilo the different partions one wants to boot into have to be mounted. I can't mount /dev/sdb6. It spits back: /dev/sdb6 is not a valid block device.

If in lilo.conf I will put root = /dev/hdd6 as it is in fstab instead of /dev/sdb6 I end with kernel panic when trying to boot into that prticular partition.

Beats me too. However, it works the way I have it set now.

[Kocil]

In LILO, you have to use /dev/sdb6.

But to mount the drive, you have to use /dev/hdb6.

That's strange.

I got the same strange thing in my notebook with SATA harddisk, and IDE layer in BIOS.
Kernel 2.4.x and kernel older than 2.6.18 report it as /dev/hda,
but kernel 2.6.19 - 2.6.21 report it as /dev/sda.
So you will have problem if you have 2 OS with those conflicting kernels.

Since I upgraded the kernel to 2.6.22, the harddisk is known as /dev/hda, consistently.