help. ATA/SCSI Serial-ATA error: "ATA: Abnormal Status"

xin · 08-23-2003, 09:59 PM

Hi
Im using the SCSI_ATA kernel options that come with the 2.4.22-pre2-ac3 kernel. And the System picks up my drive (Wahoo!

) but gives me the error
ATA: abnormal status 0xXXX on port 0xXXX
Does anyone have any idea about this?
Just on the note, my motherboard is intel 865PE based, and the southbridge is ICH5-R.
My hard disk is a 120gb S-ATA drive plugged into the first S-ATA port connected to the southbridge.

Any Help appreciated, thanks.

finegan · 08-24-2003, 01:08 PM

Did you enable the ich-5 driver under the scsi low level drivers?

Code:

< > AdvanSys SCSI support                                            „_ „_
  „_ „_< > Always IN2000 SCSI support                                       „_ „_
  „_ „_< > AM53/79C974 PCI SCSI support                                     „_ „_
  „_ „_< > AMI MegaRAID support (old driver)                                „_ „_
  „_ „_< > AMI MegaRAID support (new driver)                                „_ „_
  „_ „_[*] SATA support                                                     „_ „_
  „_ „_<*>   Intel PIIX/ICH support                                         „_ „_
  „_ „_< > BusLogic SCSI support                                            „_ „_
  „_ „_< > Compaq Fibre Channel 64-bit/66Mhz HBA support

If you did and its still flaked out, I got this one to work just fine with a 2.4.22-pre4-ac1 and its still fine with a 2.4.22-rc2-ac1

Cheers,

Finegan

xin · 08-24-2003, 11:09 PM

Yeah.
Ive enabled it all.
Ill post back later with a manual copy of dmesg.

xin · 08-26-2003, 12:07 AM

Ok
Here is the copy from dmesg with all the irrelevant stuff taken out (taken the hard way *grumble*)

Quote:

SCSI Subsystem Driver
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0xF36 bmdma 0xFC00 irq 14
ata1: dev0 ata, max UDMA/133, 23441648 sectors
ata1: dev0 configured for UDMA/133
ata2: SATA max UMDA/133 cmd 0x170 cdl 0x76 bmdma 0xFC08 irq15
ATA: Abnormal Status 0x7F on port 0x177
ATA: Abnormal Status 0x7F on port 0x177
ata2: Thread Exiting
scsi0: ata_piix
scsi1: ata_piix
Vendor: ATA Model:ST3120023AS Rev0.65
Type: Direct Access ANSI SCSI revision:05
Attached SCSI disk SDA at scsi0, channel0, id0, lun0 (120034 MB)
Partition Check:
/dev/scsi/host0/bus0/target0/lun0:<4>ATA: Abnormal Status 0.7f on Port 0x17F
ATA: Abnormal Status 0.7f on Port 0x17F
ATA1: dma Timeout
ATA: Abnormal Status 0.7f on Port 0x17F

So as far as I can see.. Somthing on a driver level is wrong. Anybody got any ideas?

finegan · 08-26-2003, 01:32 AM

Of course its the driver level, but upgrade man, upgrade. The pre2-ac3 patch was only the second time this thing appeared in the Alan Cox tree at all, this bug has probably been clobbered twice by now. Check the newer patches.

Cheers,

Finegan

xin · 08-26-2003, 11:25 PM

That copy of dmesg was from 2.4.22-rc2-ac3

finegan · 08-28-2003, 03:26 AM

Now I'm lost... you're running 2 drives to my one, but that's the only difference. I figure you could check to see if this has been reported to the LKML, check the header of the source to see who the driver maintainer is for this little experiment (I don't see it staying emulated to scsi), if its Cox himself then it will probably be fixed shortly (and he won't reply to the mail... probably).

Cheers,

Finegan

xin · 09-04-2003, 04:41 AM

Ok
Updated to 2.4.22-ac1
Got things going good, Verifies the disk (sda), verifies the partitions (1-4), looks good. _But_ It still fails to mount the root partition /dev/sda4 or 8:04 (as the kernel panic tells me)
Ive compiled in the filesystem support, Pass the right root partition status to the kernel, Changed fstab (even though it can't read it). Changed Between Lilo and grub (sticking with grub now)
What could be the cause of the problem?

finegan · 09-04-2003, 12:04 PM

What's the exact panic error? "no init found", "partition table unreadable", etc?

Usually its more helpful then just a straight panic. Does it give anything at all more specific?

Cheers,

Finegan

xin · 09-04-2003, 10:42 PM

Yeah
Kernel Panic: VFS: Unable To mount root filesystem on 8:04
And One line before that it says:
FAT: Bad (Inode, Block or somthing) size 0
Somthing pretty much to that extent.
I don't believe its anything to do with the partition table seeming that it does a succesful Partition check.

xin · 09-05-2003, 10:59 PM

I asked around places and the likes. It turns out initrd was my problem *shakes fist*
Thanks for all of your help, greatly appreciated