When can recovered files be seen?

3TB · Post by **3TB** » Wed Aug 19, 2020 11:14 pm

Thanks for making this software possible! That map file is golden!

You can see below from data/screenshot below there is quite a bit of recovery to get processed.

I am curious as to when I can actually see some of the recovered files...if any? Not the number of days, that's already obvious...its already been running for 7 to 10 days and likely a few weeks to go.

FYI:
1. The failed drive has a separate power source.
2. There is a 6-inch fan blowing right into the drive for cooling.
3. Running ddrescue via Ubuntu on a windows device. I tried doing the "TRY" Ubuntu and running on thumb drive. But each time I tried to get Ubuntu fully updated with updates, the install would fail. I found there was something wrong with the thumb drive. Each time there was a restart everything had to be reinstalled. I made some room on the windows device and did a FULL install of Ubuntu 20.04. After this the install/updates did not crash.

rescued: 256303 MB, tried: 1048 kB, bad-sector: 0 B, bad areas: 0
Current status
ipos: 269498 MB, non-trimmed: 1048 kB, current rate: 2340 B/s
opos: 269498 MB, non-scraped: 0 B, average rate: 87188 B/s
non-tried: 2731 GB, bad-sector: 0 B, error rate: 0 B/s
rescued: 269497 MB, bad areas: 0, run time: 1d 18h 1m
pct rescued: 8.98%, read errors: 0, remaining time: 1675d 5h
time since last successful read: 0s
Copying non-tried blocks... Pass 1 (forwards)

Post by **hamishmb** » Wed Aug 26, 2020 8:43 am

Hello,

Good to see the recovery is making headway. Yeah, a full install is generally the best option, and I'm glad to hear about the fan - they always help.

As for when you can see the recovered files, it kind of depends on what data it has managed to read. The start of the drive is the most important when it comes to (easily) reading the files. It also depends on whether the data it has managed to read corresponds to the files you want.

However, as long as you're using a map file, you can stop the recovery and use the "mount" option at any time, and if it doesn't work you can just resume the recovery again for a while. Bear in mind that if mounting does work and you can see the files, it doesn't necessarily mean that the files are intact - its probably best to wait until the recover is finished unless you only need a small amount of data and will know if it's intact or not.

Hope this helps,
Hamish

3TB · Post by **3TB** » Mon Sep 21, 2020 11:44 pm

Hi,
Having trouble getting the recovered file mounted and the ability to see files.

ddrescue has been running for a few weeks now. Averaging only 2-4GB of recovery per day. Now it seems its not reading the drive any longer. The "current rate" went to "0 B/s" for about a day. The drive still powers on with out any loud clicking noises.
After see the recovery go to zero, I aborted and chose to try and mount the file. It gave an error saying file recovery corrupt, at least something similar to that. Then I tried recovery another time to try to get back to the point where I could Mount again.

So I have a recovered file of about 400GB to work with.

I STARTED THE RECOVERY WITH THIS (*.img and *.log on the external recovery drive)

Code: Select all

sudo ddrescue -d -r 3 /dev/sdd '/media/ubuntu/Seagate-3.63TB/hdimg/drive.img' '/media/ubuntu/Seagate-3.63TB/hdimg/drive.log'

I learned the recovery was going to overwrite everything on the destination drive so I moved the "drive.log" file over to Documents on the Ubuntu box.

I also figured out how to and installed DDRESCUE-GUI (was using only terminal prior to this).

Code: Select all

DDRESCUE-GUI SETTINGS:
checked...Use Direct Access
checked...Overwrite output file/disk
"Set to best recovery"

AFTER RECOVERY WAS ABORTED I TOOK OPTION TO MOUNT:

Code: Select all

"Please select partition you wish to mount", I selected below:
Partion sdb2, Filesystem ntfs, Size: 3.7T
"Your recovered data is now mounted at:"
/tmp/ddrescue-gui/destination

I then Open File Viewer. I can then click open the external drive to "Seagate-3.63TB/hdimg/" but in the "hdimg" folder I can not see the "drive.img" file.

I don't understand how to mount and see the files.

Code: Select all

[email protected]:/media/black/Seagate-3.63TB/hdimg$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0    55M  1 loop /snap/core18/1705
loop1    7:1    0  55.3M  1 loop /snap/core18/1885
loop2    7:2    0 255.6M  1 loop /snap/gnome-3-34-1804/36
loop3    7:3    0  62.1M  1 loop /snap/gtk-common-themes/1506
loop4    7:4    0 240.8M  1 loop /snap/gnome-3-34-1804/24
loop5    7:5    0  49.8M  1 loop /snap/snap-store/433
loop6    7:6    0  29.9M  1 loop /snap/snapd/8790
loop7    7:7    0  49.8M  1 loop /snap/snap-store/467
loop8    7:8    0  30.3M  1 loop /snap/snapd/9279
sda      8:0    0 238.5G  0 disk 
├─sda1   8:1    0     2G  0 part 
├─sda2   8:2    0   521M  0 part /boot/efi
├─sda3   8:3    0   128M  0 part 
├─sda4   8:4    0 177.3G  0 part 
├─sda5   8:5    0   1.9G  0 part /boot
└─sda6   8:6    0    28G  0 part /
sdb      8:16   0   3.7T  0 disk 
├─sdb1   8:17   0   128M  0 part 
└─sdb2   8:18   0   3.7T  0 part /media/black/Seagate-3.63TB
sr0     11:0    1  1024M  0 rom  
[email protected]:/media/black/Seagate-3.63TB/hdimg$ ll
total 285549012
drwxrwxrwx 1 black black          4096 Sep 20 14:40 ./
drwxrwxrwx 1 black black         16384 Sep 20 14:40 ../
-rwxrwxrwx 1 black black 3000592957440 Aug 26 15:59 drive.img*
[email protected]:/media/black/Seagate-3.63TB/hdimg$

Post by **hamishmb** » Mon Sep 28, 2020 11:26 am

Hello.

When you clicked "Open File Viewer" you should at that point be seeing the recovered files.

I'm not sure what you mean when you say you can't see the "drive.img" file - it's there in the terminal output you sent.

Hope this helps,
Hamish

3TB · Post by **3TB** » Wed Sep 30, 2020 10:54 pm

Ddrescue-Gui can see the file "drive.img" when it needs to write to it (rescue initiated from map file). Ddrescue-Gui can not see the "drive.img" to mount it.

The drive.img file is sitting on the external Seagate drive in "hdimg" folder. When I try to mount it from Ddrescue-Gui does not see the "drive.img" file when I navigate over to the "hdimg" folder.

Open Ddrescue-Gui, then Edit/Mount Disk, it opens to Select Device/File..., shows folder Black(user), then navigate below to external Seagate, select it then see "hdimg" folder, open the folder and is empty, "drive.img" is not seen. No errors.

Far as i know, the entire external drive partition has been used to write the drive.img file.

What else can I use to mount the drive.img file?

Post by **hamishmb** » Thu Oct 08, 2020 10:15 am

Are you still running on Ubuntu?

Perhaps you could take and upload a screenshot of the "Select Device/File" dialog for me so I can see more clearly what's going on? I suspect you're looking in your home folder /home/black instead of /media/black, and that might be why you aren't finding it.

3TB · Post by **3TB** » Thu Oct 08, 2020 10:10 pm

Adding screenshots........each is named with the step taken

1.open Seagate with Files app
2.open hdimg folder with Files app shows the drive.img file
3.Edit Mount Disk opent to this-Dell
4. tap on external Seagate drive opens to hdimg folder
5. open hdimg folder to this-empty

3TB · Post by **3TB** » Thu Oct 08, 2020 10:58 pm

attachment 4 and 5

Post by **hamishmb** » Sun Oct 11, 2020 12:00 pm

I suspect the problem is that you need to change the file type selector to "All Files/Disks (*)" (probably in the lower right hand dropdown when the file dialog is open, but can depend on your platform).