|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
Hard drive error on boot 'READ_DMA timed out'
When booting FreeBSD 7.0 I get the following messages for my mates spare SATA drive:
ad7: FAILURE - READ_DMA48 timed out LBA=18446744073709551614 ad7: FAILURE - READ_DMA timed out LBA=18446744073709551599 ... The if I do a fdisk /dev/ad7 it shows me that it's a FreeBSD drive when in fact this is in Linux ext3 format. It shows up in sysinstall -> Configure -> Fdisk as Size 0, End is -1, Name is '-', PType of 12 and Desc of 'unused'. This drive was in a caddy and I have a feeling that someone plugged in the wrong power inlet whilst it was in the caddy. Is there a way to mount this drive and recover some of the data? It is only coming up with /dev/ad7 in the devices and I cannot mount this. When I try the command: mount -t ext2fs /dev/ad7 /mnt This gives me mount: /dev/ad7 : Input/output error Should I waste anymore time on this drive? It seems to be giving up/timing out in the kernel, is there a way to override this behavior and tell the kernel to keep trying and skip bad blocks? |
|
||||
Which motherboard/chipset you have?
__________________
religions, worst damnation of mankind "If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus Torvalds Linux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”. vermaden's: links resources deviantart spreadbsd |
|
|||
I've got an ASUS P5N-EM HDMI with an nvidia i630 chipset. This works with my main hard drive which is a Samsung 80GB SATA drive and I've tested other SATA drives on there which work fine. The chipset can handle SATA 1 and SATA 2.
The suspect hard drive is a: Seagate 7200.11 1TB SATA drive. The drive does spin up and keeps spinning when the OS is fully booted. Sometimes though it makes some bad noises. If I could somehow increase the timeout maybe it would skip those bad parts of the drive. |
|
|||
I tried ddrescue & testdisk and here are the errors:
# ddrescue /dev/ad7 testdump sdb.log Press Ctrl-C to interrupt Initial status (read from logfile) rescued: 0 B, errsize: 0 B, errors: 0 Current status rescued: 0 B, errsize: 0 B, current rate: 0 B/s ipos: 0 B, errors: 0, average rate: 0 B/s opos: 0 B # testdisk /log /dev/ad7 TestDisk 6.9, Data Recovery Utility, February 2008 Christophe GRENIER <grenier@cgsecurity.org> http://www.cgsecurity.org Unable to open file or device /dev/ad7 |
|
|||
Try with dd(1) instead, if with this one single byte can not be rescued forget about it.
|
|
|||
I've also noticed further up the log I have these errors
ad7: FAILURE - SETFEATURES SET TRANSFER MODE status=51<READY,DSC,ERROR> error=4<ABORTED> ad7: FAILURE - SETFEATURES ENABLE RCACHE status=51<READY,DSC,ERROR> error=4<ABORED> richardpl: I tried the dd command as follows # dd if=/dev/ad7 of=ad7.dd which gave me nothing: 0+0 records in 0+0 records out 0 bytes transferred in 0.000040 secs (0 bytes/sec) I don't have any partition information, so the only device I have in the /dev dir for ad7 is /dev/ad7. |
|
||||
I think things are more serious. Looks more like controller failure to me. If you need the data, it is going to be a PCB swap at least.
__________________
The only dumb question is a question not asked. The only dumb answer is an answer not given. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
AMD64 - Hard Drive Partitioning | Turquoise88 | General software and network | 8 | 11th September 2009 05:58 AM |
Did I fry my hard drive? | JMJ_coder | General Hardware | 7 | 23rd December 2008 10:38 PM |
CF as a *BSD hard drive? | JMJ_coder | General Hardware | 26 | 31st July 2008 05:13 PM |
FreeBSD 7.0 hard drive problems. | Errinok | FreeBSD Installation and Upgrading | 8 | 13th June 2008 03:24 PM |
Encrypting hard drive? | ViperChief | FreeBSD Installation and Upgrading | 5 | 31st May 2008 03:42 PM |