I have a broken disk, partially working. This is part of dmesg after plug-in USB removable 2,5″ disk, and list from fdisk:
[1448.206941] blk_update_request: I/O error, dev sdb, sector 6293504 fdisk -l /dev/sdb Disk /dev/sdb: 931,5 GiB, 1000170586112 bytes, 1953458176 sectors ...... Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 1953458175 1953456128 931,5G 7 HPFS/NTFS/exFAT
So I will try to rescue some data from it. I will use a gddrescue program:
apt-get install gddrescue
And now, I have mounted a big 3TB nfs storage, where I will save image of this disk:
ddrescue -r1 -v -d /dev/sdb /mnt/nfs/sdb.img /mnt/nfs/sdb.log
- -r1 means, that ddrescue will try read every block one time before giving it up on this block (reading from it)
- -v means verbose mode
- -d means, that ddrescue use direct disk access and ignore kernel’s cache
- /dev/sdb is the failing drive
- /mnt/nfs/sdb.img is the destination image, where we save any data
- /mnt/nfs/sdb.log is the log file, where is written every bad block and actual position of ddrescue. We can brake this rescue at any time and continue it later with the same command. When ddrescue finish, we can repeat this check only on bad blocks with more retries
- 22.3.2017 – it was stared. post will continue after it finished 😀 maybe it take 3 days to finish, maybe more 🙂 This operation takes a long time to finish…
Total Page Visits: 179601 - Today Page Visits: 37