View previous topic :: View next topic |
Author |
Message |
Ast0r Guru
![Guru Guru](/images/ranks/rank_rect_3.gif)
Joined: 11 Apr 2006 Posts: 404 Location: Dallas, Tx - USA
|
Posted: Wed Jun 07, 2006 6:20 pm Post subject: SATA drive refuses to work, please help! [solved] |
|
|
I recently pulled a Seagate 300GB SATA-300 hard disk out of a 3ware RAID-5 array (on a 9550SX card). The drive showed a degraded status and the controller refused to rebuild the array with a disk that was "configured". Wanting to confirm whether or not the drive was ok, I ran an extensive SMART test on it and having received an "ok" status, I proceeded to I pull the drive out and clear the partitions with Seagate's setup tool. I wanted to confirm that the drive is functional before I put it in back in my production server. The drive is only 3 months old and it is still under warranty from Seagate but I don't want to RMA it if I don't have to. So ...
I compiled the proper SATA support into my kernel and booted Gentoo, but ... Code: | localhost ~ # fdisk /dev/sda
Unable to open /dev/sda
|
Checking dmesg reveals Code: | libata version 1.20 loaded.
ata_piix 0000:00:1f.2: version 1.05
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE802 bmdma 0xDC00 irq 16
ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 16
ATA: abnormal status 0x7F on port 0xEC07
scsi0 : ata_piix
ata2: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023 88:207f
ata2: dev 0 ATA-7, max UDMA/133, 586072368 sectors: LBA48
ata2: dev 0 configured for UDMA/133
scsi1 : ata_piix
Vendor: ATA Model: ST3300831AS Rev: 3.03
Type: Direct-Access ANSI SCSI revision: 05 |
I am confused as to exactly what "abnormal status 0x7F on port 0xEC07" means in this context. It obviously sees that a drive is connected (that is the correct model #) but is it telling me that the drive is not functioning properly or that something is wrong with my system configuration or is that not even relevant at all?
I tried booting Windows and I am able to access the drive without issue (I copied about 3 or 4 GB of data to it to make sure) so I'm at a loss as to what is wrong. If the drive is failing that is fine, but I don't want to ship it to Seagate and then have them call me in a week to tell me I'm an idiot and they're shipping the same drive back.
Does anyone have any ideas?
Last edited by Ast0r on Thu Jun 08, 2006 3:01 pm; edited 1 time in total |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
widan Veteran
![Veteran Veteran](/images/ranks/rank_rect_5_vet.gif)
![](images/avatars/142533236243680bda6f27b.jpg)
Joined: 07 Jun 2005 Posts: 1512 Location: Paris, France
|
Posted: Thu Jun 08, 2006 8:25 am Post subject: Re: SATA drive refuses to work, please help! |
|
|
Ast0r wrote: | I compiled the proper SATA support into my kernel and booted Gentoo, but ... Code: | localhost ~ # fdisk /dev/sda
Unable to open /dev/sda
|
|
Check you have the sd_mod module loaded (or that you have "SCSI disk support" enabled in your kernel). That module is responsible for creating the device nodes for SCSI disks.
Ast0r wrote: | Checking dmesg reveals Code: | libata version 1.20 loaded.
ata_piix 0000:00:1f.2: version 1.05
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE802 bmdma 0xDC00 irq 16
ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 16
ATA: abnormal status 0x7F on port 0xEC07
scsi0 : ata_piix
ata2: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023 88:207f
ata2: dev 0 ATA-7, max UDMA/133, 586072368 sectors: LBA48
ata2: dev 0 configured for UDMA/133
scsi1 : ata_piix
Vendor: ATA Model: ST3300831AS Rev: 3.03
Type: Direct-Access ANSI SCSI revision: 05 |
I am confused as to exactly what "abnormal status 0x7F on port 0xEC07" means in this context. |
In this case, "port 0xEC07" is probably related to the "cmd 0xEC00" register block, so with ata1. But your disk seems to be connected to ata2. Probably the driver complains because it can't find a device on ata1, but it's not related to your disk. Your drive is probably fine. |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
Ast0r Guru
![Guru Guru](/images/ranks/rank_rect_3.gif)
Joined: 11 Apr 2006 Posts: 404 Location: Dallas, Tx - USA
|
Posted: Thu Jun 08, 2006 3:01 pm Post subject: |
|
|
Jesus on ice-skates. I had forgotten to compile SCSI Disk Support into the kernel! Compiling that in fixed my problem.
I have confirmed that the drive functions fine and I can put it in my production server. Thank you! |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|