On Fri, May 04, 2007 at 02:18:37PM +1200, Simon wrote:
> We have a Albatron KX600S motherboard with a single IDE 40GB drive
> (with debian etch installed) and 2 x 200GB SATA (was going to software
> RAID 1 these). But we cant see /dev/sda or /dev/sdb and get the below
> in the dmesg. Any thoughts/tips/pointers on how to get these working?
>
> sda: Current: sense key: Aborted Command
> Additional sense: No additional sense information
> end_request: I/O error, dev sda, sector 390721792
> ata1: EH complete
> ata1.00: speed down requested but no transfer mode left
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata1.00: tag 0 cmd 0x29 Emask 0x1 stat 0x51 err 0x4 (device error)
> ata1: EH complete
Some hardware isn't working as it should (device error). It's either a
hardware fault:
1. drive
2. cable
3. controller
4. MB
or 5. a driver fault
To troubleshoot:
1. Can you test the drive in another box?
2. Do you have a spare cable?
3. Do you have a known-good SATA drive?
4. 3 and 4 are basically the same if the controller is integrated
to the MB. Test the same as 1.
5. What is the first mention in dmesg about SATA or ATA?
# dmesg | grep ata |less
This will occur much before your sda: Current... line, before
sda is even assigned.
On mine (Asus M2N-SLI Deluxe with nv chipset) its:
libata version 2.00 loaded
sata_nv 0000:00:05.0: version 2.00
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xE000 irq 58
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xE008 irq 58
scsi0 : sata_nv
[goes on to find the drives with no errors reported.
And dmesg | grep scsi | less
scsi0 : sata_nv
scsi[0-5] the same
the last two entries show that it all worked:
sd 0:0:0:0: Attached scsi disk sda
sd 1:0:0:0: Attached scsi disk sdb
Good luck,
Doug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
