[Feisty] Serial Ata drive not recognize in 2.6.20

Bug #83313 reported by Gaëtan Petit
16
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Medium
Ben Collins

Bug Description

Binary package hint: linux-source-2.6.20

I tried to dist-upgrade from edgy and it couldn't boot because /dev/sda4 is unknown

I tried herd3 and my Serial ATA disk isn't recognize anymore!

I think this is pretty critical.

I'm using a shuttle xpc, with a serial ata controller on mother board.

If i could help to fix this please tell me

Revision history for this message
Kyle McMartin (kyle) wrote :

Shit, my crystal ball isn't working... I guess you'll have to actually TELL US what serial ata controller it is. Please provide dmesg, lspci -vvn, lspci -vv from a working edgy install, and if possible, a dmesg from the feisty boot.

Changed in linux-source-2.6.20:
status: Unconfirmed → Needs Info
Revision history for this message
Gaëtan Petit (gaetanp) wrote :

let's see if your cristaball work better this time ;)

I made the lspci under the dapper live-cd

Revision history for this message
Ben Collins (ben-collins) wrote :

It should be using the ata_piix driver. Can you send us lsmod output from feisty aswell?

If you don't see ata_piix loaded, can you run:

sudo modprobe ata_piix

And see if that shows the drive.

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

Sorry but the ata_piix module is already launched

see the attached lsmod

Revision history for this message
LEVIS Cyril (atlas95) wrote :

for me serial ata work but it is very very slow !
my hitachi 7k100 turn around 900mb /2s with feisty and only 1500mb /2s (test with hdparm -tT) for edgy.
I think a 7200rpm hdd must have best result :s

(sorry for my english)

Revision history for this message
CeReAl KiLLeR DU 77 (regis-chezdudu77) wrote :

Hello,

kernel 2.6.20-6 of the herd3 also pauses me problem. The kernel this blocks with the boot. While modifying my bios I arrive at booter above, but my two sata are recognized in hde and hdg instead of sda and sdb. While still mofidiant the bios, I arrive has to have my two sata in sda and sdb, on the other hand not of reader/writer dvd. The other version of ubuntu never posed problem to me. My motherboard is a asus p4p800e-deluxe.

Revision history for this message
Richard Samson (richard) wrote :

Hi,

I get same problem, my sata drives are not recognized on latest 2.6.20-8-*
I need to change "native mode" to "legacy mode" in sata controler options in bios.

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

No change in Herd4
Changing mode in my bios isn't working ...
Any kernel update planned?

well, tell me if there's anything more that i can do.

At least someone could confirmed this bug.

Revision history for this message
Laurent GUERBY (laurent-guerby) wrote :

Similar reports:

https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/84964

Here are various logs from a system where 2.6.20-6 works but 2.6.20-8 does not boot enough to mount disks.

Revision history for this message
Rockzor (audunbf) wrote :

Same problems. the early 2.6.19 feisty kernel works fine, but none of the 2.6.20 kernels boot.

Revision history for this message
FiNeX (finex) wrote :

(sorry for the crosspost)

I've tried both herd3 and herd4: the system doesn't correctly recognise my SATA HD. This is the controller:
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)

I've this errors on dmesg (and on the others logfiles)

Feb 19 10:08:59 ubuntu kernel: [ 2403.853220] hdg: DMA interrupt recovery
Feb 19 10:08:59 ubuntu kernel: [ 2403.853226] hdg: lost interrupt
Feb 19 10:09:19 ubuntu kernel: [ 2423.828414] hdg: dma_timer_expiry: dma status == 0x24

From /dev/ i see hdg, hgd1,..., hdg7 (the partition of my SATA HD) but them are not accessible. If I try to mount or fdisk the shell freze and on the log file I've:

Feb 19 10:08:59 ubuntu kernel: [ 2403.853220] hdg: DMA interrupt recovery
Feb 19 10:08:59 ubuntu kernel: [ 2403.853226] hdg: lost interrupt
Feb 19 10:09:19 ubuntu kernel: [ 2423.828414] hdg: dma_timer_expiry: dma status == 0x24

Changed in linux-source-2.6.20:
status: Needs Info → Confirmed
Revision history for this message
Gaëtan Petit (gaetanp) wrote :

i tried with the latest kernel

still buggy ...

Revision history for this message
sparky (crithanuel) wrote :

feisty update from edgy. amd64. athlon64 x2 nforce asus motherboard. the default edgy kernel 2.6.17 recognizes my sata hard drives fine. however none of the feisty default kernels recognize the sata drives. The feisty amd 64 altnerate cd does not recognize the drives either.

Revision history for this message
Laurent GUERBY (laurent-guerby) wrote :

The new 2.6.20-9 does not boot on my machine.

Still using 2.6.20-6

Revision history for this message
hove99 (hove99) wrote :

Same problem here

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

I found out that the problem is very concentrated on shuttle mother board

see this topic : http://www.ubuntuforums.org/showthread.php?t=374782

We are 3 Shuttle users with 3 different models and maybe different drives.
Maybe the on board controller isn't recognized properly ...

Revision history for this message
Richard Samson (richard) wrote :

Hi,

I get the same bug on a msi and asus motherboards with intel i865 chipset.

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

hopefully this bug seems to be fixed in latest kernel 2.6.20.2

see the kernel.org bugzilla report : http://bugzilla.kernel.org/show_bug.cgi?id=7996

Revision history for this message
Matteo F.B. (conte) wrote :

can anyone confirm that this bug is fixed in the very latest kernel (2.6.20-10.17) ?

Revision history for this message
Laurent GUERBY (laurent-guerby) wrote :

Matteo F.B., the problem is still there with 2.6.20-10.17

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

yes i can confirm that latest kernel doesn't fix this problem
irq_poll wasn't guilty

I'm a bit anxious about this ...

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

still buggy with latest kernel ...

Revision history for this message
Pascal Bovet (bugreporter) wrote :

Seems as I have the same problem with the herd 5 of feisty fawn (running from cd)..

Got the same errors as FiNeX but I got it to boot with the 'irqpoll' boot option..

root@ubuntu:~# uname -a
Linux ubuntu 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

Strange that I get a Bug message about a soft lockup (hde is my SATA harddisk)
[ 6.717856] hde1 hde2 hde3 hde4 < hde5 >
[ 6.795585] ieee1394: Host added: ID:BUS[0-00:1023] GUID[00e01800003c695d]
[ 9.848805] kjournald starting. Commit interval 5 seconds
[ 9.848827] EXT3-fs: mounted filesystem with ordered data mode.
[ 9.998884] kjournald starting. Commit interval 5 seconds
[ 9.998900] EXT3-fs: mounted filesystem with ordered data mode.
[ 12.379976] kjournald starting. Commit interval 5 seconds
[ 12.379988] EXT3-fs: mounted filesystem with ordered data mode.
[ 12.502617] kjournald starting. Commit interval 5 seconds
[ 12.502631] EXT3-fs: mounted filesystem with ordered data mode.
[ 22.089910] BUG: soft lockup detected on CPU#0!

But finally I got the system to boot and I also could mount my SATA harddisk..

If you need any further information, let me know..

Changed in linux-source-2.6.20:
assignee: nobody → ben-collins
importance: Undecided → Medium
status: Confirmed → Fix Released
Revision history for this message
Gaëtan Petit (gaetanp) wrote :

i made the update via chroot

and the latest kernel return a kernel panic :

"Unable to mount / fs on unknown bloc (0,0)"

I'm dowloading the beta to test it right now

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

ok i had to reinstall from the beta
and now it's good

i noticed several regressions (rt61 still broken, screen resolution) i'll report them later ...

Revision history for this message
Matteo F.B. (conte) wrote :

ok I confirm that in beta the bug is resolved.

It can be closed now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.