Re: [Dump-users] Resuming a verify after transient hardware failure

[Szabolcs S. <sz...@nt...>]

Kenneth Porter <shiva <at> sewingwitch.com> writes:

> I'm backing up to an external USB NTFS drive, using compression. The 
> resulting backup is about 150 gigabytes (after compression). After the 
> backup I do a verify with "restore -C". For the last two full backups, I 
> get a read error at sector 268435455 which turns out to be 0xFFFFFFF. I'm 
> guessing this might be an issue either in the ntfs-3g FUSE filesystem or 
> the underlying USB2 subsystem.

It's a very typical hardware/kernel driver problem with certain disk 
drives. There is absolutely nothing ntfs-3g could do about it because 
the error is at a lower, hardware level. There are more info at 
http://ntfs-3g.org/support.html#ioerror

Regrads,   Szaka

--
NTFS-3G: http://ntfs-3g.org

> I'm able to read the sector fine with dd:
> 
> dd if=/dev/sdb of=/tmp/my.sector bs=512 count=10 skip=268435453
> 
> Sep  5 15:41:37 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current:
sense key: Not Ready
> Sep  5 15:41:37 segw2 ntfs-3g[22860]: ntfs_attr_pread: ntfs_pread failed:
Input/output error
> Sep  5 15:41:37 segw2 kernel:     Add. Sense: Logical unit not ready, cause
not reportable
> Sep  5 15:41:37 segw2 kernel:
> Sep  5 15:41:37 segw2 kernel: end_request: I/O error, dev sdb, sector 268435455
> Sep  5 15:41:37 segw2 ntfs-3g[22860]: ntfs_attr_pread error reading
'/Shelob/0/root/dump' at offset 132989304832: 4096 <> -1: Input/
> Sep  5 15:41:37 segw2 kernel: Buffer I/O error on device sdb1, logical block
33554424