7.10 live cd does not boot, the error: udevd-event[2292]: modprobe abnormal exit

I have the same problem as discussed in the thread http://ubuntuforums.org/showthread.php?t=579558

The boot process ends with this message;

[64.180479] end_request: I/O error, dev fd0, sector 0

When I disable the floppy in BIOS I get the following;

EIP: [<c01fe8ab>] strstr+0x1b/0x50 SS:ESP 0068:dfe2dcd4 udevd_event [2261] ...

Disabling the various drives give different messages but will not let me boot.

Motherboard - MSI K8M NEO-V, K8M800, Socket-754, ATX S-ATA/ATA, DDR, LAN, Sound, AGP8x, VGA
Ram - Corsair Value S. PC3200 DDR-DIMM 512MB Unbuffered, Non-parity, 64Megx64, CL2.5
CPU - AMD Sempron 3100+ 1.8GHz Socket 754 256KB
Graphics - Geforce 4 440 MX
Sound - SB Audigy
IDE hda - Seagate ST320413A
IDE hdb - Maxtor 6Y08P0
IDE hdc - NEC DVD_RW ND-3500AG
IDE hdd - Maxtor 6B200P0

starting with the boot parameter all_generic_ide lets me start the system. This is written from the live-cd.

Me and some other people have almost the same problem.

I get this:
udevd-event[2452]: run_program: '/sbin/modprobe' abnormal exit

BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu7) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

The whole thing is discussed here: http://ubuntuforums.org/showthread.php?t=585047

Also I tried the "all_generic_ide" parameter and I was able to boot into the LiveCD environment and install Ubuntu. But after the reboot the progress bar of "splash" does not move at all.
The 7.10 Beta work fine(too bad I deleted the iso).
For now I am back to Feisty until this is fixed.

If you need more info just ask me.

I have the same problem, but it seems to be a bug with recognizing seagate hard drives, if I remove it the system boots without problems.

It is a kernel bug

Does anyone know if there will be a new *.iso or are we stuck in Feisty?

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

Using this the system boots fine. One strange thing I noticed is that my fstab file now shows all of my drives as sdx instead of hdx like it used to. I don't know why. My drives are all ide not SCSI.

Hello yamar,

Thanks for the fix, it worked for me too.

I've 2 pcs with ide drives, both were running Feisty following an upgrade from Edgy. I've yet to upgrade the main pc to Gutsy, wanted to try out upgrading with the second before making the jump with the main pc. Beginning with Feisty IDE drives show up as sdx because there are advantages (???!! - see below) to using this system. During the upgrade from Edgy to Feisty, the main pc converted to the sdx format while the second remained using the hdx format. It may have something to do with age, pc2 is a Pentium 3 with one 40GB and one 20GB hard drives (both 5400 kbs speed). Upgrading pc2 to Gutsy converted the system to the sdx system.

One big disadvantage (my opinion) sdx can only read a maximum of 15 partitions, not so good when you use more because they aren't mounted. I've separated ntfs partitions for system, programs, swap, data, downloads, surfing (firefox and thunderbird profiles shared on the network between Win + Ubuntu), backup, games, fonts (shared between Win + Ubuntu) and given the main Linux mount points separate partitions - a total of 20 partitions over 2 hard drives, setup when I was running Edgy. Needless to say, it's a case of hiding some partitions from Ubuntu to ensure the important shared ones are visible.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/156428
contains a kernel fix.
But I think it would be better to check with a local table and function in ide-disk.c the disk name.
Otherwise the bug can occure again, when the table layout and meaning is changed in ide-dma.c.
Better keep it simple and local.

I have the same problem. When I have connected my Seagate ST320413A IDE I can't use LiveCD. If I disconnect this HD, the LiveCD works fine.

When I press Ctrl+Alt+F4 It appears in the last lines:

n't support DPO or FUA
[51.343431] sda: sda1 sda2 < sda5 sda 6 >
[51.377639] sd 4:0:0:0: [sda] Attached SCSI Disk
[51.381255] sd 4:0:0:0: Attached SCSI generic sg0 type 0

I Have:
SATA WDC WD80 0JD-22JNC0 HD
IDE ST320413A on IDE 1 Master
DVD recorder on IDE 2 Master

Sorry for my english.

Update: all_generic_ide works for me.

Hi All,

The Hardy Heron Alpha2 LiveCD is set to come out around Dec 20. The Alpha2 release will have a newer kernel, version 2.6.24. It would be most helpful to us if you would be willing to test this newer kernel via the LiveCD. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. I'll update this report when Alpha2 has been released. At that time, please test and report back your results. Thanks in advance!

all_generic_ide looks like it might work for me, but it breaks my RAID with the kernel saying it can't find /dev/md0

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Am i wrong, or was this bug introduced by the patch mentioned in https://bugs.launchpad.net/bugs/26119 ?
The correction described in the duplicate https://bugs.launchpad.net/bugs/156428 looks like the patch copied from kernel 2.6.23 (where it seems to work).
The priority of 26119 changed from medium to low. I would have expected, that the priority raises, if the problem gets worse, wouldn't you?

Hello Frank,
I agree, it would appear to have got worse. For me, this only appeared with Gutsy and I've been using Ubuntu from Dapper onwards with this same Seagate as a secondary hard drive.
I plan to test Hardy Alpha 2 on the second PC that now uses this Seagate drive in the New Year, hopefully this will help the next release to recognise the hard drive from the full release.

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!

This problem also happens on a x86_64 Linux, running qemu emulating a x86_64 processor:
/usr/bin/qemu-system-x86_64 -monitor stdio -boot d -m 512 -cdrom '/path/kubuntu-7.10-desktop-amd64.iso' -net nic,vlan=0 -net user,vlan=0

The emulated machine says:
BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu7) Built-in shell (ash)
 Enter 'help' for a list of built-in commands.
(initramfs)

Using the kernel parameter all_generic_ide solves in the emulated machine solves the problem.

Confirmed: the Hardy Heron Alpha2 Live CD boots fine for me

The Hardy Heron Alpha2 64bit works fine.

But I am disappointed that the kernel gutsy is still broken and I am forced to use "all_generic_ide" to make it work.

I've got a similar bug related to IDE support, but "all_generic_ide" didn't work for me. I was trying to run Ubuntu 7.10 Server under QEMU 0.9.0 installed on Ubuntu 7.10 Desktop.

Here is the dmesg log:

    ...
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    ...
    ide0: I/O resource 0x3F6-0x3F6 not free.
    ide0: ports already in use, skipping probe
    ide1: I/O resource 0x376-0x376 not free.
    ide1: ports already in use, skipping probe

The details are here http://qemu-forum.ipi.fi/viewtopic.php?f=10&t=4251.

Thank you to those who tested with the newer Hardy kernel and reported back your results. It appears this issue is resolved with the newer kernel so am marking this as Fix Released against the 'linux' source package.

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.

This was a kernel issue, which has been fixed.

Thanks,
:-Dustin