[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Kernel upgrade trouble: Device /sys/block/hda/dev seems to be down



Hi,

I've recently upgraded the linux-image-2.6-686 package to 2.6.14-5[1]. The
installation went as normal when new kernel images are installed, but the
ensuing reboot didn't work out as expected.

Immediately after the first IDE disk was detected, output like this was
generated on the console:

/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 1 seconds for /sys/block/hda/dev to show up
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 2 seconds for /sys/block/hda/dev to show up
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 4 seconds for /sys/block/hda/dev to show up
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 8 seconds for /sys/block/hda/dev to show up
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 16 seconds for /sys/block/hda/dev to show up

/bin/cat: /sys/block/hdaa/dev: No such file or directory

Device /sys/block/hda/dev seems to be down.
Debugging opportunity, type ^D to continue.

And I was dropped to a shell. Exiting this just restarted the cycle mentioned
above with the next disk partition. Bypassing all the partitions finally
results in a kernel panic.

I suspect the problem might be related to the fact that mkinitrd.yaird[0] was
apparently used to generate the ramdisk for the new kernel image, but I am not
at all sure about this.

I am currently booted on an older backup kernel image, kept around for just
this purpose.

Any input is welcomed.

[0] ii  yaird					0.0.12-1	yet Another mkInitRD
[1] ii  linux-image-2.6-686		2.6.14-5	Linux kernel 2.6 image on PPro/Celeron/PII/P


-- 
Søren O.                                           ,''`.
                                                  : :' :
GPG key id: 0x1EB2DE66                            `. `'
GPG signed mail preferred.                          `-



Reply to: