Page 1 of 1
Corrupted USB drive
Posted: Thu Mar 14, 2013 10:55 am
by dbbolton
I believe I have a corrupted NTFS partition on my external USB drive (it only has one partition). When I plug it in, I get something like this:
Code: Select all
[26479.436013] Info fld=0x0
[26479.436016] sd 7:0:0:0: [sdd] Add. Sense: Logical block address out of range
[26479.436024] sd 7:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[26479.436044] end_request: I/O error, dev sdd, sector 0
[26479.437486] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[26479.437493] sd 7:0:0:0: [sdd] Sense Key : Illegal Request [current]
[26479.437500] Info fld=0x0
[26479.437503] sd 7:0:0:0: [sdd] Add. Sense: Logical block address out of range
[26479.437510] sd 7:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[26479.437524] end_request: I/O error, dev sdd, sector 0
But /dev/sdd1 isn't showing up, so I can't mount it or check it. Searching the error message led me
here, but again I can't use ntfsfix because the partition isn't showing up.
Any thoughts?
Re: Corrupted USB drive
Posted: Thu Mar 14, 2013 11:18 am
by Picani
If you have access to a Windows computer, did you try to use the NTFS tools from Windows ?
Re: Corrupted USB drive
Posted: Thu Mar 14, 2013 11:26 am
by DrHu
LBA -Logical Block Addressing
http://www.tech-faq.com/lba.html
You will certainly have to try a repair, however it may be unrecoverable, since I see it is on the fisrt sector of the device where the error occurred (sector 0 (zero))
--and a windows tool will be safer to use than Linux (since FAT nor NTFS is not a native Linux format), although they can be read and written to.
I looked at your link, but it doesn't seem to be logical block error, but usually that will be an unrecoverable error and require a re-format, even trying hard drive (ntfs) repair tools may not help
--what could fix it is a disk editor, Norton had one available or even a binary editor: you would have to learn how to use same, if you want any chance of recovering your data
Hard drive (ntfs ) repair tools, not Microsoft (3rd party ones..)
http://www.hdd-tool.com/category/hdd-repair
--there may some others you could search for, but I expect a binary editor; able to reset the bits on the disk sectors to be better able to fix it
Disk editor(s)..
http://service1.symantec.com/SUPPORT/nu ... 9872811430
http://superuser.com/questions/97006/wi ... lternative
Re: Corrupted USB drive
Posted: Thu Mar 14, 2013 4:53 pm
by dbbolton
I think I'm going to have to write this off as a huge (i.e. ~1TB of backups) loss.
The drive doesn't even show up in TestDisk. It does show up under storage under Computer Management in Windows, but it cannot be initialized (interestingly, right-clicking on it says "This device is working properly"). I also noticed that it seems to make a strange noise when powering up, although the LED seems to work normally.
If there are any other diagnostic tools that I should try before tossing this thing, please don't hesitate to suggest one.
Re: Corrupted USB drive
Posted: Thu Mar 14, 2013 5:34 pm
by DrHu
You might get a different device message using..
--what does that show, and then search the internet for those statuses: or uumount the device
Code: Select all
sudo umount /dev/sd?
lsusb
--status message: no usb found (at least for the hard drive device)
plug in drive (auto regogmition..)
lsusb
--status message
if the Linux kernel has a problem detecting the device, the the IO woun't get it either
--also the windows device manager probably isn't giving you the current status of the device: remove it from the windows file manager or the USB section
--let windows OS redetect device on a system restart, now you will see the real status of tne device that windows OS sees..
Additionally..
dmesg
--will give some other messages about the device detection action: check that when you have replugged the usb connected external hard drive.
fdisk -l
what does the system see in reagrds to that device
blkid
--another way of looking at disk devices..
------------------------------------
Don't forget the physical, should probably be step 1..
Check the physical interconnects on the external hard drive case: reseat the sata or ata cables !
You are using the correct usb connection jacks/ports, they are active and match the speed of the usb connection from your mainboard (PC)
------------------------------------
--does the error clear ?