D&C GLug - Home Page

[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] NTFS woes...

 

On Sun, 5 Jun 2011, Dava wrote:

Hi there, i didnt know if anyone can help. im trying to recover some data from a dying/dead NTFS usb stick for a friend. If entered into an MS machine it just gives the option to format, ive tried repairing it via chkdsk /f but it comes up with "*Cannot open volume for direct access".* I tried it on my linux machine and no mountable devices show, sudo fdisk -l shows only my current disks. I have tried sudo ntfsfix /dev/sdb and i get:

Mounting volume... Error reading bootsector: Input/output error.
Failed to startup volume: Input/output error.
FAILED
Attempting to correct errors... Error reading bootsector: Input/output error.
FAILED
Failed to startup volume: Input/output error.
Volume is corrupt. You should run chkdsk.

Obviously chkdsk yields me nothing.

The drive is showing up via lsusb as:
Bus 001 Device 004: ID 1516:8628 CompUSA 128M Pen Drive

but in photorec it comes up as:
Disk /dev/sdb - 2199 GB / 2048 GiB (RO) - SKYMEDI USB Drive

Yet it is an 8gig (HP <<not that that means much)

Dmesg:

[ 1767.787709] sd 7:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1767.787720] sd 7:0:0:0: [sdb] Sense Key : Illegal Request [current]
[ 1767.787728] sd 7:0:0:0: [sdb] Add. Sense: Invalid field in cdb
[ 1767.787737] end_request: I/O error, dev sdb, sector 0
[ 1767.787745] __ratelimit: 7 callbacks suppressed
[ 1767.787750] Buffer I/O error on device sdb, logical block 0
[ 1767.789586] sd 7:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1767.789595] sd 7:0:0:0: [sdb] Sense Key : Illegal Request [current]
[ 1767.789604] sd 7:0:0:0: [sdb] Add. Sense: Invalid field in cdb
[ 1767.789612] end_request: I/O error, dev sdb, sector 0
[ 1767.789619] Buffer I/O error on device sdb, logical block 0

Any ideas on where to go now? The data on it is pretty important, ive just preeched the importance of backing up but as always its too late for that

It's showing physical errors. I suspect it's so badly damaged that Linux can't read the size of the device. If it's that bad, then it's quite bad.


e.g. sector 0 - which is where the partition table will be.

What I'd do now -

Make sure any auto-mounting magic is turned off - if possible (although it's probably not getting in the way as it's corrupt)

Become root in a terminal and plug it in.

Run hdparm to identify it:

  hdparm -v /dev/sdb

if that works then you're in with a chance, but if it fails, I'd probably give-up at that point.

Let us know what you get.

Gordon

--
The Mailing List for the Devon & Cornwall LUG
http://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq