EATA driver/module does not load

[airblade]

I'm installing Ubuntu 7.04 server on a old server i have.
Under the installation Ubuntu does not detect my disk so i have to choose the EATA driver/module. It finds my disk and continues to install.
After rebooting, and passing grub, the system fails to find my disk.
This is the output:
Starting up ...
Loading, please wait...
               Check root = bootarg cat /proc/cmdline
               or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/disk/by-uuid/ (disk uuid) does not exist. Dropping to a shell!

cat /proc/cmdline shows:
root=UUID=(disk uuid) ro quiet splash

cat /proc/modules lists these modules:
ide_cd, cdrom, floppy, tulip, uhci_hcd, usbcore, piix, generic, fbcon, tileblit, font, bitblit, softcursor, vesafb, capability and commoncap.

uname -a shows:
Linux (none) 2.6.20-15-server #2 SMP Thu Jun 7 20:26:23 UTC 2007 i686 unknown

Of course, loading the EATA module manually in BusyBox works. And i can access my disks.
cat /proc/modules now lists these extra modules:
sg, st, sd_mod, eata and scsi_mod.

I have tried upgrading with apt, witch installs the latest kernel: 2.6.20-16-server.
I have also tried to including the modules: sg, st, sd_mod and scsi_mod in /etc/modules.

Here are some hardware specifications:
Intel SE440BX Motherboard
Intel Pentium II 350MHz, 512KB cache
767MB SDRAM
SCSI controller: DPT PM2144UW
Hard drive: IBM Ultrastar

If more info is needed, request it.

[Jeff Balderson (jbalders)]

I had the exact same problem yesterday. Ultimately, I found that the following workaround got my system to reboot correctly:

1) load the eata module from the busybox shell and wait 10s
2) exit from the shell and log in once the system has loaded
3) echo eata >> /etc/initramfs-tools/modules
4) echo eata >> /etc/modules
5) update-initramfs -k all -u

My system:

Asus P2B (P II 450)
DPT PM3334UW RAID card
ATAPI CDROM

[airblade (petterah)]

>> Jeff Balderson

Your workaround solved it :-)
BTW, this also occurs in Ubuntu 7.10

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[airblade (petterah)]

dmesg > dmesg.log

[airblade (petterah)]

sudo lspci -vvnn > lspci-vvnn.log

[airblade (petterah)]

uname -a

[airblade (petterah)]

cat /proc/version_signature > version.log

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducable with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Brian Murray (brian-murray)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.