photorec photo recovery software not seeing my mounted filesystem - trying to use photorec to recover lost...












2















What is my situation?



I am working in a Dev Ops capacity for a service that manages jpeg files online. We had an unfortunate deploy and our media files (jpegs) are completely gone. I anticipate that our loss is probably simple and may be recoverable. I think somehow that the directory that contains the sub-directories that have our jpeg files was unlinked. If this is the case, we should be able to recover them.



What I have done so far and where we are hosted -- details



I realized the loss almost right away and fortunately we did not have any users online at that moment. I stopped our service and brought down our server. I did that to prevent any more writes to the filesystem figuring that avoiding writes was essential to file recovery.



We are running Ubuntu 16.04 in DigitalOcean. I have brought the server back up using DigitalOcean's recovery mode. This permits one to mount the filesystem of the given virtual host without running the virtual host and without running the services one has on the virtual host. This should be sufficient and correct for performing any form of recovery.



I need some where to write data for recovery. To that end, I have another server in DigitalOcean in the same data center (SFO1 unfortunately). I have mounted that host's filesystem using sshfs. I should be able to write any recovery data from my virtual host's filesystem (which is in recovery mode) to this other host via sshfs.



I selected the following utility to execute my recovery: PhotoRec



That utility is actually two utilities -- PhotoRec and TestDisk.



The filesystem of the host we wish to recover is ext4. PhotoRec supports ext4. TestDisk may not support ext4. That's okay, according to the documentation if the data is still there and largely uncorrupted, then we should be able to recover it with PhotoRec.



Here is the output of when I run df -Th -- as you can see the filesystem I wish to recover is /dev/vda1 it is of type ext4 and mounted via /mnt . I installed photorec in /lib/live/mount/overlay which is the tmpfs . I have mounted another host via sshfs within the same datacenter to put any recovered data on:



root@xxxx-xxxxxx-xxxxxxxxx:~# df -Th
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs tmpfs 1.6G 6.2M 1.6G 1% /run
/dev/sr0 iso9660 251M 251M 0 100% /lib/live/mount/medium
/dev/loop0 squashfs 220M 220M 0 100% /lib/live/mount/rootfs/rescue_rootfs.squashfs
tmpfs tmpfs 7.9G 14M 7.9G 1% /lib/live/mount/overlay
overlay overlay 7.9G 78M 7.8G 1% /
tmpfs tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0
root@xxx.xxx.xxx.xxx:/ fuse.sshfs 311G 13G 298G 5% /mnt2/xxxxxx-xxxxxx-xxxxxx
/dev/vda1 ext4 311G 41G 270G 14% /mnt



When I run photorec it only sees:



>Disk /dev/sr0 - 252 MB / 250 MiB (RO) - QEMU DVD-ROM


It does not see my filesystem that I want to execute recovery on at all. That is:



/dev/vda1              ext4        311G   41G  270G  14% /mnt


I have tried this with my filesystem mounted because that seems right to me. However, we did find in some online documentation that some file recovery tools require file systems to not be mounted (which seems weird to me - how is that supposed to work). So I tried executing it unmounted but same thing: it only sees:



>Disk /dev/sr0 - 252 MB / 250 MiB (RO) - QEMU DVD-ROM


Does anyone have any suggestions regarding getting photorec to see my filesystem:



/dev/vda1              ext4        311G   41G  270G  14% /mnt


I do have some backups, but unfortunately, I have about seven days worth of unbacked up photos. We could in theory live without them and reach out to our clients and get data from them and reprocess and repost it. But it would be ideal, if I could with just a few clicks of some buttons, get back this data that is likely still un the filesystem just unreachable.



Help using photorec for this purpose wouold be ideal as would any other suggestions regarding how to recover my lost/missing files.



Thanks!










share|improve this question







New contributor




Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    Testdisk is for whole disks you oopsied. Photorec is pretty easy - and does individual files if you deleted them or such.

    – Journeyman Geek
    yesterday






  • 1





    @JourneymanGeek - thanks I appreciate it, Michael Hampton also included some additional information. Anticipate that I will provide an update in about a week -- something like, what I learned while trying to recover a business's production environment. What happened was that I had a deploy go wrong and the sub-directory of ~120 GB of JPEGs from dozens and dozens and dozens of users got destroyed. After I restore= the service, I started to investigate how to recover the files. We had backups but they were seven days old, we want to recover all of the data.

    – Peter Jirak
    yesterday






  • 1





    @JourneymanGeek - PhotoRec is working but it appears that it is helping me get back the files, but without their file names. Trying to correctly restore the files without file names is going to be difficult. Also while the JPEGs may contain useful metadata, the file meta data -- user name, group, permissions, and date/times (created, accessed, modified) are missing from the data being recovered by PhotoRec.

    – Peter Jirak
    23 hours ago











  • I vaguely recall there's a python

    – Journeyman Geek
    22 hours ago
















2















What is my situation?



I am working in a Dev Ops capacity for a service that manages jpeg files online. We had an unfortunate deploy and our media files (jpegs) are completely gone. I anticipate that our loss is probably simple and may be recoverable. I think somehow that the directory that contains the sub-directories that have our jpeg files was unlinked. If this is the case, we should be able to recover them.



What I have done so far and where we are hosted -- details



I realized the loss almost right away and fortunately we did not have any users online at that moment. I stopped our service and brought down our server. I did that to prevent any more writes to the filesystem figuring that avoiding writes was essential to file recovery.



We are running Ubuntu 16.04 in DigitalOcean. I have brought the server back up using DigitalOcean's recovery mode. This permits one to mount the filesystem of the given virtual host without running the virtual host and without running the services one has on the virtual host. This should be sufficient and correct for performing any form of recovery.



I need some where to write data for recovery. To that end, I have another server in DigitalOcean in the same data center (SFO1 unfortunately). I have mounted that host's filesystem using sshfs. I should be able to write any recovery data from my virtual host's filesystem (which is in recovery mode) to this other host via sshfs.



I selected the following utility to execute my recovery: PhotoRec



That utility is actually two utilities -- PhotoRec and TestDisk.



The filesystem of the host we wish to recover is ext4. PhotoRec supports ext4. TestDisk may not support ext4. That's okay, according to the documentation if the data is still there and largely uncorrupted, then we should be able to recover it with PhotoRec.



Here is the output of when I run df -Th -- as you can see the filesystem I wish to recover is /dev/vda1 it is of type ext4 and mounted via /mnt . I installed photorec in /lib/live/mount/overlay which is the tmpfs . I have mounted another host via sshfs within the same datacenter to put any recovered data on:



root@xxxx-xxxxxx-xxxxxxxxx:~# df -Th
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs tmpfs 1.6G 6.2M 1.6G 1% /run
/dev/sr0 iso9660 251M 251M 0 100% /lib/live/mount/medium
/dev/loop0 squashfs 220M 220M 0 100% /lib/live/mount/rootfs/rescue_rootfs.squashfs
tmpfs tmpfs 7.9G 14M 7.9G 1% /lib/live/mount/overlay
overlay overlay 7.9G 78M 7.8G 1% /
tmpfs tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0
root@xxx.xxx.xxx.xxx:/ fuse.sshfs 311G 13G 298G 5% /mnt2/xxxxxx-xxxxxx-xxxxxx
/dev/vda1 ext4 311G 41G 270G 14% /mnt



When I run photorec it only sees:



>Disk /dev/sr0 - 252 MB / 250 MiB (RO) - QEMU DVD-ROM


It does not see my filesystem that I want to execute recovery on at all. That is:



/dev/vda1              ext4        311G   41G  270G  14% /mnt


I have tried this with my filesystem mounted because that seems right to me. However, we did find in some online documentation that some file recovery tools require file systems to not be mounted (which seems weird to me - how is that supposed to work). So I tried executing it unmounted but same thing: it only sees:



>Disk /dev/sr0 - 252 MB / 250 MiB (RO) - QEMU DVD-ROM


Does anyone have any suggestions regarding getting photorec to see my filesystem:



/dev/vda1              ext4        311G   41G  270G  14% /mnt


I do have some backups, but unfortunately, I have about seven days worth of unbacked up photos. We could in theory live without them and reach out to our clients and get data from them and reprocess and repost it. But it would be ideal, if I could with just a few clicks of some buttons, get back this data that is likely still un the filesystem just unreachable.



Help using photorec for this purpose wouold be ideal as would any other suggestions regarding how to recover my lost/missing files.



Thanks!










share|improve this question







New contributor




Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    Testdisk is for whole disks you oopsied. Photorec is pretty easy - and does individual files if you deleted them or such.

    – Journeyman Geek
    yesterday






  • 1





    @JourneymanGeek - thanks I appreciate it, Michael Hampton also included some additional information. Anticipate that I will provide an update in about a week -- something like, what I learned while trying to recover a business's production environment. What happened was that I had a deploy go wrong and the sub-directory of ~120 GB of JPEGs from dozens and dozens and dozens of users got destroyed. After I restore= the service, I started to investigate how to recover the files. We had backups but they were seven days old, we want to recover all of the data.

    – Peter Jirak
    yesterday






  • 1





    @JourneymanGeek - PhotoRec is working but it appears that it is helping me get back the files, but without their file names. Trying to correctly restore the files without file names is going to be difficult. Also while the JPEGs may contain useful metadata, the file meta data -- user name, group, permissions, and date/times (created, accessed, modified) are missing from the data being recovered by PhotoRec.

    – Peter Jirak
    23 hours ago











  • I vaguely recall there's a python

    – Journeyman Geek
    22 hours ago














2












2








2








What is my situation?



I am working in a Dev Ops capacity for a service that manages jpeg files online. We had an unfortunate deploy and our media files (jpegs) are completely gone. I anticipate that our loss is probably simple and may be recoverable. I think somehow that the directory that contains the sub-directories that have our jpeg files was unlinked. If this is the case, we should be able to recover them.



What I have done so far and where we are hosted -- details



I realized the loss almost right away and fortunately we did not have any users online at that moment. I stopped our service and brought down our server. I did that to prevent any more writes to the filesystem figuring that avoiding writes was essential to file recovery.



We are running Ubuntu 16.04 in DigitalOcean. I have brought the server back up using DigitalOcean's recovery mode. This permits one to mount the filesystem of the given virtual host without running the virtual host and without running the services one has on the virtual host. This should be sufficient and correct for performing any form of recovery.



I need some where to write data for recovery. To that end, I have another server in DigitalOcean in the same data center (SFO1 unfortunately). I have mounted that host's filesystem using sshfs. I should be able to write any recovery data from my virtual host's filesystem (which is in recovery mode) to this other host via sshfs.



I selected the following utility to execute my recovery: PhotoRec



That utility is actually two utilities -- PhotoRec and TestDisk.



The filesystem of the host we wish to recover is ext4. PhotoRec supports ext4. TestDisk may not support ext4. That's okay, according to the documentation if the data is still there and largely uncorrupted, then we should be able to recover it with PhotoRec.



Here is the output of when I run df -Th -- as you can see the filesystem I wish to recover is /dev/vda1 it is of type ext4 and mounted via /mnt . I installed photorec in /lib/live/mount/overlay which is the tmpfs . I have mounted another host via sshfs within the same datacenter to put any recovered data on:



root@xxxx-xxxxxx-xxxxxxxxx:~# df -Th
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs tmpfs 1.6G 6.2M 1.6G 1% /run
/dev/sr0 iso9660 251M 251M 0 100% /lib/live/mount/medium
/dev/loop0 squashfs 220M 220M 0 100% /lib/live/mount/rootfs/rescue_rootfs.squashfs
tmpfs tmpfs 7.9G 14M 7.9G 1% /lib/live/mount/overlay
overlay overlay 7.9G 78M 7.8G 1% /
tmpfs tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0
root@xxx.xxx.xxx.xxx:/ fuse.sshfs 311G 13G 298G 5% /mnt2/xxxxxx-xxxxxx-xxxxxx
/dev/vda1 ext4 311G 41G 270G 14% /mnt



When I run photorec it only sees:



>Disk /dev/sr0 - 252 MB / 250 MiB (RO) - QEMU DVD-ROM


It does not see my filesystem that I want to execute recovery on at all. That is:



/dev/vda1              ext4        311G   41G  270G  14% /mnt


I have tried this with my filesystem mounted because that seems right to me. However, we did find in some online documentation that some file recovery tools require file systems to not be mounted (which seems weird to me - how is that supposed to work). So I tried executing it unmounted but same thing: it only sees:



>Disk /dev/sr0 - 252 MB / 250 MiB (RO) - QEMU DVD-ROM


Does anyone have any suggestions regarding getting photorec to see my filesystem:



/dev/vda1              ext4        311G   41G  270G  14% /mnt


I do have some backups, but unfortunately, I have about seven days worth of unbacked up photos. We could in theory live without them and reach out to our clients and get data from them and reprocess and repost it. But it would be ideal, if I could with just a few clicks of some buttons, get back this data that is likely still un the filesystem just unreachable.



Help using photorec for this purpose wouold be ideal as would any other suggestions regarding how to recover my lost/missing files.



Thanks!










share|improve this question







New contributor




Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












What is my situation?



I am working in a Dev Ops capacity for a service that manages jpeg files online. We had an unfortunate deploy and our media files (jpegs) are completely gone. I anticipate that our loss is probably simple and may be recoverable. I think somehow that the directory that contains the sub-directories that have our jpeg files was unlinked. If this is the case, we should be able to recover them.



What I have done so far and where we are hosted -- details



I realized the loss almost right away and fortunately we did not have any users online at that moment. I stopped our service and brought down our server. I did that to prevent any more writes to the filesystem figuring that avoiding writes was essential to file recovery.



We are running Ubuntu 16.04 in DigitalOcean. I have brought the server back up using DigitalOcean's recovery mode. This permits one to mount the filesystem of the given virtual host without running the virtual host and without running the services one has on the virtual host. This should be sufficient and correct for performing any form of recovery.



I need some where to write data for recovery. To that end, I have another server in DigitalOcean in the same data center (SFO1 unfortunately). I have mounted that host's filesystem using sshfs. I should be able to write any recovery data from my virtual host's filesystem (which is in recovery mode) to this other host via sshfs.



I selected the following utility to execute my recovery: PhotoRec



That utility is actually two utilities -- PhotoRec and TestDisk.



The filesystem of the host we wish to recover is ext4. PhotoRec supports ext4. TestDisk may not support ext4. That's okay, according to the documentation if the data is still there and largely uncorrupted, then we should be able to recover it with PhotoRec.



Here is the output of when I run df -Th -- as you can see the filesystem I wish to recover is /dev/vda1 it is of type ext4 and mounted via /mnt . I installed photorec in /lib/live/mount/overlay which is the tmpfs . I have mounted another host via sshfs within the same datacenter to put any recovered data on:



root@xxxx-xxxxxx-xxxxxxxxx:~# df -Th
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs tmpfs 1.6G 6.2M 1.6G 1% /run
/dev/sr0 iso9660 251M 251M 0 100% /lib/live/mount/medium
/dev/loop0 squashfs 220M 220M 0 100% /lib/live/mount/rootfs/rescue_rootfs.squashfs
tmpfs tmpfs 7.9G 14M 7.9G 1% /lib/live/mount/overlay
overlay overlay 7.9G 78M 7.8G 1% /
tmpfs tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0
root@xxx.xxx.xxx.xxx:/ fuse.sshfs 311G 13G 298G 5% /mnt2/xxxxxx-xxxxxx-xxxxxx
/dev/vda1 ext4 311G 41G 270G 14% /mnt



When I run photorec it only sees:



>Disk /dev/sr0 - 252 MB / 250 MiB (RO) - QEMU DVD-ROM


It does not see my filesystem that I want to execute recovery on at all. That is:



/dev/vda1              ext4        311G   41G  270G  14% /mnt


I have tried this with my filesystem mounted because that seems right to me. However, we did find in some online documentation that some file recovery tools require file systems to not be mounted (which seems weird to me - how is that supposed to work). So I tried executing it unmounted but same thing: it only sees:



>Disk /dev/sr0 - 252 MB / 250 MiB (RO) - QEMU DVD-ROM


Does anyone have any suggestions regarding getting photorec to see my filesystem:



/dev/vda1              ext4        311G   41G  270G  14% /mnt


I do have some backups, but unfortunately, I have about seven days worth of unbacked up photos. We could in theory live without them and reach out to our clients and get data from them and reprocess and repost it. But it would be ideal, if I could with just a few clicks of some buttons, get back this data that is likely still un the filesystem just unreachable.



Help using photorec for this purpose wouold be ideal as would any other suggestions regarding how to recover my lost/missing files.



Thanks!







linux ubuntu data-recovery undelete






share|improve this question







New contributor




Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked yesterday









Peter JirakPeter Jirak

111




111




New contributor




Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Peter Jirak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    Testdisk is for whole disks you oopsied. Photorec is pretty easy - and does individual files if you deleted them or such.

    – Journeyman Geek
    yesterday






  • 1





    @JourneymanGeek - thanks I appreciate it, Michael Hampton also included some additional information. Anticipate that I will provide an update in about a week -- something like, what I learned while trying to recover a business's production environment. What happened was that I had a deploy go wrong and the sub-directory of ~120 GB of JPEGs from dozens and dozens and dozens of users got destroyed. After I restore= the service, I started to investigate how to recover the files. We had backups but they were seven days old, we want to recover all of the data.

    – Peter Jirak
    yesterday






  • 1





    @JourneymanGeek - PhotoRec is working but it appears that it is helping me get back the files, but without their file names. Trying to correctly restore the files without file names is going to be difficult. Also while the JPEGs may contain useful metadata, the file meta data -- user name, group, permissions, and date/times (created, accessed, modified) are missing from the data being recovered by PhotoRec.

    – Peter Jirak
    23 hours ago











  • I vaguely recall there's a python

    – Journeyman Geek
    22 hours ago














  • 1





    Testdisk is for whole disks you oopsied. Photorec is pretty easy - and does individual files if you deleted them or such.

    – Journeyman Geek
    yesterday






  • 1





    @JourneymanGeek - thanks I appreciate it, Michael Hampton also included some additional information. Anticipate that I will provide an update in about a week -- something like, what I learned while trying to recover a business's production environment. What happened was that I had a deploy go wrong and the sub-directory of ~120 GB of JPEGs from dozens and dozens and dozens of users got destroyed. After I restore= the service, I started to investigate how to recover the files. We had backups but they were seven days old, we want to recover all of the data.

    – Peter Jirak
    yesterday






  • 1





    @JourneymanGeek - PhotoRec is working but it appears that it is helping me get back the files, but without their file names. Trying to correctly restore the files without file names is going to be difficult. Also while the JPEGs may contain useful metadata, the file meta data -- user name, group, permissions, and date/times (created, accessed, modified) are missing from the data being recovered by PhotoRec.

    – Peter Jirak
    23 hours ago











  • I vaguely recall there's a python

    – Journeyman Geek
    22 hours ago








1




1





Testdisk is for whole disks you oopsied. Photorec is pretty easy - and does individual files if you deleted them or such.

– Journeyman Geek
yesterday





Testdisk is for whole disks you oopsied. Photorec is pretty easy - and does individual files if you deleted them or such.

– Journeyman Geek
yesterday




1




1





@JourneymanGeek - thanks I appreciate it, Michael Hampton also included some additional information. Anticipate that I will provide an update in about a week -- something like, what I learned while trying to recover a business's production environment. What happened was that I had a deploy go wrong and the sub-directory of ~120 GB of JPEGs from dozens and dozens and dozens of users got destroyed. After I restore= the service, I started to investigate how to recover the files. We had backups but they were seven days old, we want to recover all of the data.

– Peter Jirak
yesterday





@JourneymanGeek - thanks I appreciate it, Michael Hampton also included some additional information. Anticipate that I will provide an update in about a week -- something like, what I learned while trying to recover a business's production environment. What happened was that I had a deploy go wrong and the sub-directory of ~120 GB of JPEGs from dozens and dozens and dozens of users got destroyed. After I restore= the service, I started to investigate how to recover the files. We had backups but they were seven days old, we want to recover all of the data.

– Peter Jirak
yesterday




1




1





@JourneymanGeek - PhotoRec is working but it appears that it is helping me get back the files, but without their file names. Trying to correctly restore the files without file names is going to be difficult. Also while the JPEGs may contain useful metadata, the file meta data -- user name, group, permissions, and date/times (created, accessed, modified) are missing from the data being recovered by PhotoRec.

– Peter Jirak
23 hours ago





@JourneymanGeek - PhotoRec is working but it appears that it is helping me get back the files, but without their file names. Trying to correctly restore the files without file names is going to be difficult. Also while the JPEGs may contain useful metadata, the file meta data -- user name, group, permissions, and date/times (created, accessed, modified) are missing from the data being recovered by PhotoRec.

– Peter Jirak
23 hours ago













I vaguely recall there's a python

– Journeyman Geek
22 hours ago





I vaguely recall there's a python

– Journeyman Geek
22 hours ago










1 Answer
1






active

oldest

votes


















5














You can tell photorec explicitly which block device to work with, e.g. photorec /dev/vda1. It must not be mounted.



Of course, before photorec, you should try using extundelete, which may undelete your files on an ext* filesystem more quickly. Again, it must not be mounted.



And of course you should be prepared to go to your backup.






share|improve this answer



















  • 1





    Hi @Michael-Hampton - Thanks for your help. We tried extundelete and we tried ext4magic. extundelete and ext4magic failed to find our missing inodes. We then tried running it with some additional options and it started to recover everything, but seemingly in random order so we were not finding our missing jpegs.

    – Peter Jirak
    23 hours ago






  • 1





    Hi @Michael-Hampton - Your answer photorec /dev/vda1 was exactly right and what we needed to proceed with photorec. Thank you! The issue we are having w respect to recovery is that photorec is doing an awesome job recoverying the jpeg file contents, bit it is not restoring the filenames nor any inode data. So we we are getting our jpeg files back, but not their filenames. Thousands of files wout names or metadata. We need to associate the recovered jpegs with their former filenames because the filenames are in the database. Any suggestions on getting the filenames back as well?

    – Peter Jirak
    23 hours ago











  • @PeterJirak photorec cannot recover filenames, only the files themselves. That's why you should be trying tools like extundelete first.

    – Michael Hampton
    21 hours ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






Peter Jirak is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f959602%2fphotorec-photo-recovery-software-not-seeing-my-mounted-filesystem-trying-to-us%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









5














You can tell photorec explicitly which block device to work with, e.g. photorec /dev/vda1. It must not be mounted.



Of course, before photorec, you should try using extundelete, which may undelete your files on an ext* filesystem more quickly. Again, it must not be mounted.



And of course you should be prepared to go to your backup.






share|improve this answer



















  • 1





    Hi @Michael-Hampton - Thanks for your help. We tried extundelete and we tried ext4magic. extundelete and ext4magic failed to find our missing inodes. We then tried running it with some additional options and it started to recover everything, but seemingly in random order so we were not finding our missing jpegs.

    – Peter Jirak
    23 hours ago






  • 1





    Hi @Michael-Hampton - Your answer photorec /dev/vda1 was exactly right and what we needed to proceed with photorec. Thank you! The issue we are having w respect to recovery is that photorec is doing an awesome job recoverying the jpeg file contents, bit it is not restoring the filenames nor any inode data. So we we are getting our jpeg files back, but not their filenames. Thousands of files wout names or metadata. We need to associate the recovered jpegs with their former filenames because the filenames are in the database. Any suggestions on getting the filenames back as well?

    – Peter Jirak
    23 hours ago











  • @PeterJirak photorec cannot recover filenames, only the files themselves. That's why you should be trying tools like extundelete first.

    – Michael Hampton
    21 hours ago
















5














You can tell photorec explicitly which block device to work with, e.g. photorec /dev/vda1. It must not be mounted.



Of course, before photorec, you should try using extundelete, which may undelete your files on an ext* filesystem more quickly. Again, it must not be mounted.



And of course you should be prepared to go to your backup.






share|improve this answer



















  • 1





    Hi @Michael-Hampton - Thanks for your help. We tried extundelete and we tried ext4magic. extundelete and ext4magic failed to find our missing inodes. We then tried running it with some additional options and it started to recover everything, but seemingly in random order so we were not finding our missing jpegs.

    – Peter Jirak
    23 hours ago






  • 1





    Hi @Michael-Hampton - Your answer photorec /dev/vda1 was exactly right and what we needed to proceed with photorec. Thank you! The issue we are having w respect to recovery is that photorec is doing an awesome job recoverying the jpeg file contents, bit it is not restoring the filenames nor any inode data. So we we are getting our jpeg files back, but not their filenames. Thousands of files wout names or metadata. We need to associate the recovered jpegs with their former filenames because the filenames are in the database. Any suggestions on getting the filenames back as well?

    – Peter Jirak
    23 hours ago











  • @PeterJirak photorec cannot recover filenames, only the files themselves. That's why you should be trying tools like extundelete first.

    – Michael Hampton
    21 hours ago














5












5








5







You can tell photorec explicitly which block device to work with, e.g. photorec /dev/vda1. It must not be mounted.



Of course, before photorec, you should try using extundelete, which may undelete your files on an ext* filesystem more quickly. Again, it must not be mounted.



And of course you should be prepared to go to your backup.






share|improve this answer













You can tell photorec explicitly which block device to work with, e.g. photorec /dev/vda1. It must not be mounted.



Of course, before photorec, you should try using extundelete, which may undelete your files on an ext* filesystem more quickly. Again, it must not be mounted.



And of course you should be prepared to go to your backup.







share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









Michael HamptonMichael Hampton

173k27316642




173k27316642








  • 1





    Hi @Michael-Hampton - Thanks for your help. We tried extundelete and we tried ext4magic. extundelete and ext4magic failed to find our missing inodes. We then tried running it with some additional options and it started to recover everything, but seemingly in random order so we were not finding our missing jpegs.

    – Peter Jirak
    23 hours ago






  • 1





    Hi @Michael-Hampton - Your answer photorec /dev/vda1 was exactly right and what we needed to proceed with photorec. Thank you! The issue we are having w respect to recovery is that photorec is doing an awesome job recoverying the jpeg file contents, bit it is not restoring the filenames nor any inode data. So we we are getting our jpeg files back, but not their filenames. Thousands of files wout names or metadata. We need to associate the recovered jpegs with their former filenames because the filenames are in the database. Any suggestions on getting the filenames back as well?

    – Peter Jirak
    23 hours ago











  • @PeterJirak photorec cannot recover filenames, only the files themselves. That's why you should be trying tools like extundelete first.

    – Michael Hampton
    21 hours ago














  • 1





    Hi @Michael-Hampton - Thanks for your help. We tried extundelete and we tried ext4magic. extundelete and ext4magic failed to find our missing inodes. We then tried running it with some additional options and it started to recover everything, but seemingly in random order so we were not finding our missing jpegs.

    – Peter Jirak
    23 hours ago






  • 1





    Hi @Michael-Hampton - Your answer photorec /dev/vda1 was exactly right and what we needed to proceed with photorec. Thank you! The issue we are having w respect to recovery is that photorec is doing an awesome job recoverying the jpeg file contents, bit it is not restoring the filenames nor any inode data. So we we are getting our jpeg files back, but not their filenames. Thousands of files wout names or metadata. We need to associate the recovered jpegs with their former filenames because the filenames are in the database. Any suggestions on getting the filenames back as well?

    – Peter Jirak
    23 hours ago











  • @PeterJirak photorec cannot recover filenames, only the files themselves. That's why you should be trying tools like extundelete first.

    – Michael Hampton
    21 hours ago








1




1





Hi @Michael-Hampton - Thanks for your help. We tried extundelete and we tried ext4magic. extundelete and ext4magic failed to find our missing inodes. We then tried running it with some additional options and it started to recover everything, but seemingly in random order so we were not finding our missing jpegs.

– Peter Jirak
23 hours ago





Hi @Michael-Hampton - Thanks for your help. We tried extundelete and we tried ext4magic. extundelete and ext4magic failed to find our missing inodes. We then tried running it with some additional options and it started to recover everything, but seemingly in random order so we were not finding our missing jpegs.

– Peter Jirak
23 hours ago




1




1





Hi @Michael-Hampton - Your answer photorec /dev/vda1 was exactly right and what we needed to proceed with photorec. Thank you! The issue we are having w respect to recovery is that photorec is doing an awesome job recoverying the jpeg file contents, bit it is not restoring the filenames nor any inode data. So we we are getting our jpeg files back, but not their filenames. Thousands of files wout names or metadata. We need to associate the recovered jpegs with their former filenames because the filenames are in the database. Any suggestions on getting the filenames back as well?

– Peter Jirak
23 hours ago





Hi @Michael-Hampton - Your answer photorec /dev/vda1 was exactly right and what we needed to proceed with photorec. Thank you! The issue we are having w respect to recovery is that photorec is doing an awesome job recoverying the jpeg file contents, bit it is not restoring the filenames nor any inode data. So we we are getting our jpeg files back, but not their filenames. Thousands of files wout names or metadata. We need to associate the recovered jpegs with their former filenames because the filenames are in the database. Any suggestions on getting the filenames back as well?

– Peter Jirak
23 hours ago













@PeterJirak photorec cannot recover filenames, only the files themselves. That's why you should be trying tools like extundelete first.

– Michael Hampton
21 hours ago





@PeterJirak photorec cannot recover filenames, only the files themselves. That's why you should be trying tools like extundelete first.

– Michael Hampton
21 hours ago










Peter Jirak is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Peter Jirak is a new contributor. Be nice, and check out our Code of Conduct.













Peter Jirak is a new contributor. Be nice, and check out our Code of Conduct.












Peter Jirak is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Server Fault!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f959602%2fphotorec-photo-recovery-software-not-seeing-my-mounted-filesystem-trying-to-us%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

數位音樂下載

格利澤436b

When can things happen in Etherscan, such as the picture below?