![]()
I got a disc image (drive3.raw) having about 20 GB - not bad for a start. Unfortunately the operation got stuck and I had to stop with “Control + C”. ddrescue as a newbie I prefer storing the raw disk image to file instead of having to overwrite an actual additional hard disk.įirst try with the most basic options: $ ddrescue -d -n /dev/sdc1 /path/to/backup/drive3.raw ddrescue.log with options: -d direct disc access, bypasses the kernel's IO cache -n get most good areas by skipping the scraping phase Avoid trying to rescue difficult parts $ sudo unmount /dev/sdb1 $ lsblk | grep sdb1 sdb1 8:17 0 1,8T 0 partĢ. Its recommended to unmount the disc before applying ddrescue. In that example, sda is my operating system and sdb an external harddrive. $ lsblk -o name,label,size,fstype,model sda 119,2G SAMSUNG SSD CM87 ├─sda1 512M vfat └─sda2 118,8G ext4 sdb 1,8T Elements 10B8 └─sdb1 Elements 1,8T ntfs Use lsblk to list all block devices attached to your system. You have to identify your corrupted device. Many paths exist to get your data back, like using the forensic data recovery tool foremost, but its a bad idea to apply a bunch of different recovery tools on the disc directly since that could worsen the disc’s state.Ĭreate a raw disk image containing as much data as possible and start from there. If you use a device or a partition as destination, any data stored there will be overwritten. Never try to repair a file system on a drive with I/O errors you will probably lose even more data. It is best that the device or partition to be rescued is not mounted at all, not even read-only. Never try to rescue a r/w mounted partition. A bad sector may be like a tiny whole first but the more you try to access the data there, that whole can get bigger and more data gets lost forever.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |