Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

RAID 0: One hard drive is not detected

July 13th, 2012, 8:01

Some background information: I have a RAID 0 setup with two 500 GB Seagate Barracude 7200.12 (ST3500410AS) disks. I left my system running while on vacation so I could SSH into it, but once I returned one of the two disks was 'DAMAGED' as reported by the JMicron RAID controller on my Gigabyte GA-965P-DS3 motherboard.

I imaged the non-damaged disk using ddrescue and this went just fine.

I want to image the damaged disk, but the disk isn't detected (it doesn't show up in /proc/partitions). Is there any way to detect the disk, how should I proceed?

Re: RAID 0: One hard drive is not detected

July 13th, 2012, 8:50

Need to provide more details about the drive's behavior in terms of activity, such as spins? stops spinning? Any abnormal sounds?

If not sure, listen to the good drive's operation and then compare the damaged one to the good one.

Based on this, the members could assist you more.

Re: RAID 0: One hard drive is not detected

July 13th, 2012, 10:13

Aah yes. I forgot to mention that. Both drives sound exactly the same. So the damaged drive spins up and there is no clicking or other suspicious sounds.

Re: RAID 0: One hard drive is not detected

July 13th, 2012, 12:09

Ok, then check the search function using keywords such as "Seagate, firmware, translator", etc.

Best thing to do is to check with a professional, but if you want to pursue DIY, then make sure you have a solid plan moving forward. One careless mistake and and it could be game over.

Re: RAID 0: One hard drive is not detected

July 14th, 2012, 9:00

Thanks for the tip. Some quick searching didn't give me much of a clue on how to proceed. So II'll probably consult a DR company. I added the following 'dmesg' output, maybe someone knows how to interpret it. I think the line [ 1.265351] ata7.00: both IDENTIFYs aborted, assuming NODEV shows where the disk is not being detected.

Code:
[    0.801354] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
[    1.040018] ata1: SATA link down (SStatus 0 SControl 300)
[    1.228024] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.228047] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.244011] Refined TSC clocksource calibration: 2399.999 MHz.
[    1.244016] Switching to clocksource tsc
[    1.254943] ata8.00: ATA-8: ST3500410AS, CC31, max UDMA/133
[    1.254947] ata8.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    1.265351] ata7.00: both IDENTIFYs aborted, assuming NODEV
[    1.294382] ata8.00: configured for UDMA/133
[    1.360013] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.361618] ata2.00: ATAPI: Optiarc DVD RW AD-7240S, 1.03, max UDMA/100
[    1.363535] ata2.00: configured for UDMA/100
[    1.366271] scsi 1:0:0:0: CD-ROM            Optiarc  DVD RW AD-7240S  1.03 PQ: 0 ANSI: 5
[    1.368412] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.368414] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.368526] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    1.368594] sr 1:0:0:0: Attached scsi generic sg0 type 5
[    1.384012] usb 7-1: new full-speed USB device number 2 using uhci_hcd
[    1.688012] ata5: SATA link down (SStatus 0 SControl 300)
[    2.008012] ata6: SATA link down (SStatus 0 SControl 300)
[    2.008112] scsi 7:0:0:0: Direct-Access     ATA      ST3500410AS      CC31 PQ: 0 ANSI: 5
[    2.008225] sd 7:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[    2.008269] sd 7:0:0:0: Attached scsi generic sg1 type 0
[    2.008317] sd 7:0:0:0: [sda] Write Protect is off
[    2.008320] sd 7:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.008350] sd 7:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.025313]  sda: unknown partition table
[    2.025498] sd 7:0:0:0: [sda] Attached SCSI disk
[    2.025519] Freeing unused kernel memory: 712k freed

Re: RAID 0: One hard drive is not detected

July 16th, 2012, 3:06

If your drive is not ID'ed by the system, then there is nothing you can do, really.
It could be VERY simple for this drive, or it could be VERY complicated.

If you want to consult a DR pro, then these are recommended:

dobrevjetser who is in Belgium
mr_spokk who is in Gothenburg
or pcimage who is in Petersborough, UK.

They should be able to deal this for you.

Good luck.
Post a reply