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?

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux 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:linksresourcesdeviantartspreadbsd

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.