kernel 2.6.22-14 not recognising 2nd hard drive

[Kaptain Chaos]

I upgraded Feisty to Gutsy but found Gutsy reboot hung with the message:

udevd-event[2118]: run_program : '/sbin/modprobe' abnormal exit
Busybox v1.1.3 (Debian 1:1.1.3-5 ubuntu7) Built-in shell (ash)
(initramfs)

On typing return or exit Gutsy continues to boot BUT my 2nd hard drive, containing my Linux swap partition, isn't recognised (the drive also contains two network shared ntfs partitions). Rebooting into the 2.6.20-16 kernel (left over from the Feisty installation) loaded the 2nd drive with my Linux swap file but there were problems with X 'forgetting' the configuration file and dropping back to either a 640x480 or 800x600 safe mode resolution on reboot.

As this pc is a second machine I thought I'd experiment by wiping out the Ubuntu upgrade, trying a fresh install instead to see if that produced better results. Gutsy hung during the boot-up process with the same udevd-event report stopping at the initramfs prompt and the 2nd hard drive wasn't seen by the live CD either. Typing return or exit got the boot to continue. I still couldn't get the 2nd hard drive recognised from within the fresh Gutsy install either. There were a few problems getting the restricted driver working and my splash screen was the wrong resolution.

I re-installed Feisty, left it as a vanilla install (no n-Vidia restricted driver, sharing or any extra packages) and updated the system. All running smoothly. Rebooted and ran a system upgrade to Gutsy again - same problem, hanging at the udevd-event but this time the code was [2124] and no 2nd hard drive with Linux swap! Looking at other posts I tried booting into the 2.6.22-14 kernel and ran 'sudo update-initramfs -u' but the problem persisted.

Deciding to check /etc/fstab and /dev I think I may have discovered where the problem lies but am unsure how to fix it. Both fstab and /dev list my hard drives and partitions as hdax or hdbx NOT the now more common sdax or sdbx, There are no references to sd's in /dev although I believe initramfs is looking for drives with the 'sd' prefix in /dev (I only have hd's), despite how they are configured in fstab or /dev.

Can anyone help me please?

[Mario Young (mayeco)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux-source-2.6.22.

[Kaptain Chaos (kaptain-chaos)]

Hello Mario,
Thank you for the message.

I received this email after subscribing to a similar bug report - Bug #154591 in linux-source-2.6.22 (Ubuntu)

yamar:
I was able to boot using 'all_generic_ide' in my Grub menu.lst file. This is what I have:

root (hd0,0)
kernel /vmlinuz-2.6.22-14-386 root=UUID=... ro quiet splash all_generic_ide
initrd /initrd.img-2.6.22-14-386

I followed his suggestion and can confirm this works; both hard drives boot and usplash doesn't hang at the udevd-event prompt. It seems we both have systems that were still using the hdx rather than the newer sdx driver.

[Kaptain Chaos (kaptain-chaos)]

Hello again,

Following the success of the previous post I decided to re-install Gutsy from the live cd and submit the 4 log files without the fix to the grub menu.lst in the hope it may isolate the problem.

As an aside, I was only able to successfully boot the live cd by appending the options with the all_generic_ide fix - both hard drives were successfully loaded.

If there is anything else needed please let me know, I'm happy to help.

[Kaptain Chaos (kaptain-chaos)]

As above with lspci-vvnn.log

[Kaptain Chaos (kaptain-chaos)]

As above with uname-a.log

[Kaptain Chaos (kaptain-chaos)]

As above with version.log

[Kaptain Chaos (kaptain-chaos)]

Hello again,

Here are the dmesg and lspci logs with my grub menu.lst appended with all_generic_ide

[Kaptain Chaos (kaptain-chaos)]

As above withgrub menu.lst
(lspci-vvnn.log is now an empty file)

[Leann Ogasawara (leannogasawara)]

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

[Kaptain Chaos (kaptain-chaos)]

Hello Leann,
Thank you for the helpful update, sorry it has taken so long to reply.

I'm grateful for the opportunity to help make Ubuntu better and test the
new kernel however, due to time constraints and after developing a
different fault, our second PC (that had the kernel problems) is
permanently switched off and waiting for my attention. I hope to get it
up and running again in the new year and will gladly test the new kernel
(sooner if time allows).

Once again, sorry for the delay in replying.

Kind regards,

Ken (aka Kaptain Chaos)

Leann Ogasawara wrote:
> The Hardy Heron kernel was recently uploaded for testing. We'd really
> appreciate it if you could try testing with this newer kernel and verify
> if this issue still exists. Unfortunately, the Hardy Heron Alpha1
> LiveCD was released with the older 2.6.22 kernel. You'll have to
> manually install the newer Hardy Heron kernel in order to test. This
> should not be the case for Alpha2. However, here are the instructions
> to install (if you choose to do so):
>
> 1) edit the file /etc/apt/sources.list and add the following line:
>
> deb http://archive.ubuntu.com/ubuntu hardy main restricted
>
> 2) sudo apt-get update
> 3) sudo apt-get install linux-image-2.6.24-1-generic
> 4) reboot and select the new kernel from the grub menu
>
> After you've tested, please feel free to revert back - ie boot into the
> old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove
> the line from /etc/apt/sources.list . Please update this report with
> your results. Thanks in advance!
>
> ** Also affects: linux (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
> Status: New => Incomplete
>
>

[Leann Ogasawara (leannogasawara)]

No problem Ken. Just to let you know, Hardy Heron Alpha2 should be out around Dec 20. At that point you should be able to test the new kernel via the LiveCD. That should make testing easier than having to manually install the kernel. I'll try to update this report when Alpha2 is ready. Thanks!

[Leann Ogasawara (leannogasawara)]

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

[Leann Ogasawara (leannogasawara)]

This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks.

[Leann Ogasawara (leannogasawara)]

This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release, http://www.ubuntu.com/testing. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.