I/O error after upgrade from karmic to lucid; LiveCD or AlternateCD not recognized hard drive properly

[ionash.]

I/O error (like in Bug #539027) appears after update, and after reboot, when system trying to boot from hard drive. Hovewer, LiveCD (beta 1, and earlier) starts almost flawless, but don't recognize my disk (in gparted or palimpsest there is no disk appear at all). Installation from alternate CD starts (build from 18.03 and earlier; disk and partitions are recognized properly), but freezing when partitioning program is trying to start.
I use Asus A8VX motherboard with latest BIOS, Athlon 64 3800+ processor, Seagate Barracuda Sata II (ST3500418AS) hard drive and 32bit system. In earlier versions (from 8.04 up to 9.10) I used grub command "boot: pci=nomsi" - without this text busybox starts only.

When I used alternate cd and try install lucid on IDE disk, everything goes very good - without grub pci=nomsi command.
When I try the same operation on Sata disks (Seagate ST3500418AS and Hitachi HTS541080G9SA00), without grub pci=nomsi command, hard drives are not recognized properly, and installator asks to choose driver - and I give up. Any changes in BIOS doesn't help.
If I add pci=nomsi, installation from alternate cd was succesfull on Hitachi HTS541080G9SA00, but on Seagate ST3500418AS (wich is used as my primary disk) ends with frozen partitioning program and cannot be completed.
Now I downgrade back to karmic (on Seagate), but I have copy of /var/log (after upgrade to lucid - IMO it's useless, because lucid never boot) - if some file from there is needed, I can post.
Apologize for my english.

[ionash. (janusz-arch)]

When I try to mount my disk (ST3500418AS, with karmic installed and working) on lucid (installed on another disk, with the same motherboard Asus A8VX), system displays this message:
"Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sdc5, missing codepage or helper program, or other error. In some cases useful info is found in syslog - try dmesg | tail or so"
dmesg | tail:
[ 68.828063] ata3: hard resetting link
[ 73.860025] ata3: softreset failed (device not ready)
[ 73.860034] ata3: reset failed, giving up
[ 73.860040] ata3.00: disabled
[ 73.860048] ata3: EH complete
[ 73.860559] sd 2:0:0:0: [sdb] Unhandled error code
[ 73.860564] sd 2:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 73.860572] sd 2:0:0:0: [sdb] CDB: Read(10): 28 00 02 71 94 39 00 00 02 00
[ 73.860589] end_request: I/O error, dev sdb, sector 40997945
[ 73.861517] EXT4-fs (sdb5): unable to read superblock

This problem occurred only with this specific combination of hardware. I try to run lucid LiveCD with this Seagate hard drive and another motherboards (two different MSI motherboards, newer than A8vx), and everything goes without errors; on my Asus - like above.
In karmic this hardware (Seagate disk and Asus motherboard) just works (with pci=nomsi grub command), so I think this is kernel bug.

[Luigi Maselli (grigio)]

me too! I'm on lucid and this is my hw:
Mobo Asus P5Q + Hard Disk Seagate + SATA mode

[Luigi Maselli (grigio)]

it could be something related to the SD15 firmware..
http://forums.seagate.com/t5/Barracuda-XT-Barracuda-and/7200-11-falling-down-ST3500320AS-SD15-and-others-no-detect-in/m-p/13553?view=by_date_ascending
http://www.youtube.com/watch?v=29FztWJVxbM

I'm going crazy

[Fabio Marconi (fabiomarconi)]

Hello
Is this problem present with the latest updated Lucid's or Maverick's packages?
Thanks in advance
Fabio

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!