Help! Hard drive corrupted (dmesg output)

apachedude · 02-04-2006, 05:10 PM

This is not a Linux compatibility question, but I'd like to ask here because I need someone who can understand dmesg outputs.

I built an external hard drive from a Seagate 200 GB and a CompUSA enclosure. It was working fine for about two months, until a few days ago. It no longer automatically mounted on my SuSE box, and I checked with some friends with Windows installed. It would not work either.

My friend has a copy of SpinRite, so he tried to see if it could do anything. Unfortunately, it seems to me he doesn't know how to use it, because he said that SpinRite detected my hard drive, but after leaving it on overnight, it had made 0.00000% progress or something. Which probably means SpinRite has a problem with my hard drive too? I'm not too sure what SpinRite does--perhaps someone else is familiar.

In any case, I have some data on the hard drive. Some of it is important, but I have backups of those. Some isn't too important, but it's my only copy, so I'd like to get the hard drive working again, preferably with the data intact if at all possible. Can anyone help me here?

Quote:

usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
Vendor: RT220082 Model: 2A Rev: 0 0
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdb: 373944496 512-byte hdwr sectors (191460 MB)
sdb: assuming drive cache: write through
SCSI device sdb: 373944496 512-byte hdwr sectors (191460 MB)
sdb: assuming drive cache: write through
sdb:<6>SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
unable to read partition table
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi2, channel 0, id 0, lun 0, type 0
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 373944320
Buffer I/O error on device sdb, logical block 46743040
usb-storage: device scan complete
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 373944320
Buffer I/O error on device sdb, logical block 46743040
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 373944240
Buffer I/O error on device sdb, logical block 46743030
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 373944240
Buffer I/O error on device sdb, logical block 46743030
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 373944240
Buffer I/O error on device sdb, logical block 46743030
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 373944096
Buffer I/O error on device sdb, logical block 46743012
SCSI error : <2 0 0 0> return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Logical unit communication CRC error (Ultra-DMA/32)
end_request: I/O error, dev sdb, sector 373944096
Buffer I/O error on device sdb, logical block 46743012

Matir · 02-04-2006, 08:30 PM

If you have a desktop, mounting it internally will give MUCH better access and information. Most enclosures use VERY cheap IDE chipsets. Most don't support the full range of IDE commands. With it mounted internally, you avoid questions of enclosure failure and allow access to tools like testdisk and smartmontools.

apachedude · 02-05-2006, 12:06 AM

I'm on a laptop, so mounting it internally isn't an option for now. If there isn't another solution, I'll have to find a desktop sometime.

MQMan · 02-05-2006, 12:07 AM

Also mountung it in a desktop will allow you to run Seagate's diagnostic software. Which they (usually) want you to run before returning a drive under warranty.

Cheers,
Eddie