photorec photo recovery software not seeing my mounted filesystem - trying to use photorec to recover lost jpegs The Next CEO of Stack OverflowRecover a lost NTFS partition on the cheap?Why am I getting “write queue file: No space left on device” from postfix when there's 5GB of free space on disk?XFS: No space left on devicemount a root disk in mntAWS volume from snapshot missing dataAWS Ubuntu 14 - Can't SSH After RebootWhy does /sys/fs/ext4/vda1 exist when /dev/vda1 is ext3?Recover partition table or MBR in EXT4 backup HDOptimal LVM Setup to Keep Adding Space to Single MountpointHow to recover data - from Software RAID1 - MBR is lost on both drives

Display a text message if the shortcode is not found?

Can MTA send mail via a relay without being told so?

Measuring resistivity of dielectric liquid

If Nick Fury and Coulson already knew about aliens (Kree and Skrull) why did they wait until Thor's appearance to start making weapons?

Ubuntu shell scripting

Make solar eclipses exceedingly rare, but still have new moons

How did people program for Consoles with multiple CPUs?

Why did CATV standarize in 75 ohms and everyone else in 50?

Why the difference in type-inference over the as-pattern in two similar function definitions?

Why this way of making earth uninhabitable in Interstellar?

Unreliable Magic - Is it worth it?

Is it possible to search for a directory/file combination?

Can we say or write : "No, it'sn't"?

Should I tutor a student who I know has cheated on their homework?

What connection does MS Office have to Netscape Navigator?

What happens if you roll doubles 3 times then land on "Go to jail?"

Are there any unintended negative consequences to allowing PCs to gain multiple levels at once in a short milestone-XP game?

Would this house-rule that treats advantage as a +1 to the roll instead (and disadvantage as -1) and allows them to stack be balanced?

How to get the end in algorithm2e

I want to delete every two lines after 3rd lines in file contain very large number of lines :

Received an invoice from my ex-employer billing me for training; how to handle?

Does soap repel water?

How many extra stops do monopods offer for tele photographs?

Newlines in BSD sed vs gsed



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



The Next CEO of Stack OverflowRecover a lost NTFS partition on the cheap?Why am I getting “write queue file: No space left on device” from postfix when there's 5GB of free space on disk?XFS: No space left on devicemount a root disk in mntAWS volume from snapshot missing dataAWS Ubuntu 14 - Can't SSH After RebootWhy does /sys/fs/ext4/vda1 exist when /dev/vda1 is ext3?Recover partition table or MBR in EXT4 backup HDOptimal LVM Setup to Keep Adding Space to Single MountpointHow to recover data - from Software RAID1 - MBR is lost on both drives










3















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

















  • 1





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

    – Journeyman Geek
    Mar 23 at 13:25






  • 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
    Mar 24 at 2:03






  • 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
    Mar 24 at 2:04











  • I vaguely recall there's a python

    – Journeyman Geek
    Mar 24 at 3:38















3















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

















  • 1





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

    – Journeyman Geek
    Mar 23 at 13:25






  • 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
    Mar 24 at 2:03






  • 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
    Mar 24 at 2:04











  • I vaguely recall there's a python

    – Journeyman Geek
    Mar 24 at 3:38













3












3








3








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














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













share|improve this question











share|improve this question




share|improve this question










asked Mar 23 at 5:00









Peter JirakPeter Jirak

14924




14924







  • 1





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

    – Journeyman Geek
    Mar 23 at 13:25






  • 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
    Mar 24 at 2:03






  • 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
    Mar 24 at 2:04











  • I vaguely recall there's a python

    – Journeyman Geek
    Mar 24 at 3:38












  • 1





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

    – Journeyman Geek
    Mar 23 at 13:25






  • 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
    Mar 24 at 2:03






  • 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
    Mar 24 at 2:04











  • I vaguely recall there's a python

    – Journeyman Geek
    Mar 24 at 3:38







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
Mar 23 at 13:25





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

– Journeyman Geek
Mar 23 at 13:25




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
Mar 24 at 2:03





@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
Mar 24 at 2:03




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
Mar 24 at 2:04





@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
Mar 24 at 2:04













I vaguely recall there's a python

– Journeyman Geek
Mar 24 at 3:38





I vaguely recall there's a python

– Journeyman Geek
Mar 24 at 3:38










1 Answer
1






active

oldest

votes


















8














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
    Mar 24 at 2:36






  • 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
    Mar 24 at 2:43






  • 1





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

    – Michael Hampton
    Mar 24 at 4:26






  • 1





    @PeterJirak, don't forget to mark Michael's answer as the correct one.

    – Paul Gear
    yesterday











  • @PaulGear - Thanks for the reminder. Michael Hampton's input was very valuable and useful. I am waiting to mark one or add more information until I get through this event. I learned a lot, mostly the things one would expect someone to learn under these circumstances. So, figure in a week or two, I will add more to this post and then mark something. Obviously if you or Michael are eager to contact me and work through this recovery, well, I won't say no, but I imagine the two of you have obligations odf your own.

    – Peter Jirak
    yesterday











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
);



);













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









8














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
    Mar 24 at 2:36






  • 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
    Mar 24 at 2:43






  • 1





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

    – Michael Hampton
    Mar 24 at 4:26






  • 1





    @PeterJirak, don't forget to mark Michael's answer as the correct one.

    – Paul Gear
    yesterday











  • @PaulGear - Thanks for the reminder. Michael Hampton's input was very valuable and useful. I am waiting to mark one or add more information until I get through this event. I learned a lot, mostly the things one would expect someone to learn under these circumstances. So, figure in a week or two, I will add more to this post and then mark something. Obviously if you or Michael are eager to contact me and work through this recovery, well, I won't say no, but I imagine the two of you have obligations odf your own.

    – Peter Jirak
    yesterday















8














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
    Mar 24 at 2:36






  • 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
    Mar 24 at 2:43






  • 1





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

    – Michael Hampton
    Mar 24 at 4:26






  • 1





    @PeterJirak, don't forget to mark Michael's answer as the correct one.

    – Paul Gear
    yesterday











  • @PaulGear - Thanks for the reminder. Michael Hampton's input was very valuable and useful. I am waiting to mark one or add more information until I get through this event. I learned a lot, mostly the things one would expect someone to learn under these circumstances. So, figure in a week or two, I will add more to this post and then mark something. Obviously if you or Michael are eager to contact me and work through this recovery, well, I won't say no, but I imagine the two of you have obligations odf your own.

    – Peter Jirak
    yesterday













8












8








8







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 Mar 23 at 5:34









Michael HamptonMichael Hampton

174k27318643




174k27318643







  • 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
    Mar 24 at 2:36






  • 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
    Mar 24 at 2:43






  • 1





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

    – Michael Hampton
    Mar 24 at 4:26






  • 1





    @PeterJirak, don't forget to mark Michael's answer as the correct one.

    – Paul Gear
    yesterday











  • @PaulGear - Thanks for the reminder. Michael Hampton's input was very valuable and useful. I am waiting to mark one or add more information until I get through this event. I learned a lot, mostly the things one would expect someone to learn under these circumstances. So, figure in a week or two, I will add more to this post and then mark something. Obviously if you or Michael are eager to contact me and work through this recovery, well, I won't say no, but I imagine the two of you have obligations odf your own.

    – Peter Jirak
    yesterday












  • 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
    Mar 24 at 2:36






  • 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
    Mar 24 at 2:43






  • 1





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

    – Michael Hampton
    Mar 24 at 4:26






  • 1





    @PeterJirak, don't forget to mark Michael's answer as the correct one.

    – Paul Gear
    yesterday











  • @PaulGear - Thanks for the reminder. Michael Hampton's input was very valuable and useful. I am waiting to mark one or add more information until I get through this event. I learned a lot, mostly the things one would expect someone to learn under these circumstances. So, figure in a week or two, I will add more to this post and then mark something. Obviously if you or Michael are eager to contact me and work through this recovery, well, I won't say no, but I imagine the two of you have obligations odf your own.

    – Peter Jirak
    yesterday







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
Mar 24 at 2:36





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
Mar 24 at 2:36




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
Mar 24 at 2:43





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
Mar 24 at 2:43




1




1





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

– Michael Hampton
Mar 24 at 4:26





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

– Michael Hampton
Mar 24 at 4:26




1




1





@PeterJirak, don't forget to mark Michael's answer as the correct one.

– Paul Gear
yesterday





@PeterJirak, don't forget to mark Michael's answer as the correct one.

– Paul Gear
yesterday













@PaulGear - Thanks for the reminder. Michael Hampton's input was very valuable and useful. I am waiting to mark one or add more information until I get through this event. I learned a lot, mostly the things one would expect someone to learn under these circumstances. So, figure in a week or two, I will add more to this post and then mark something. Obviously if you or Michael are eager to contact me and work through this recovery, well, I won't say no, but I imagine the two of you have obligations odf your own.

– Peter Jirak
yesterday





@PaulGear - Thanks for the reminder. Michael Hampton's input was very valuable and useful. I am waiting to mark one or add more information until I get through this event. I learned a lot, mostly the things one would expect someone to learn under these circumstances. So, figure in a week or two, I will add more to this post and then mark something. Obviously if you or Michael are eager to contact me and work through this recovery, well, I won't say no, but I imagine the two of you have obligations odf your own.

– Peter Jirak
yesterday

















draft saved

draft discarded
















































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

Adding axes to figuresAdding axes labels to LaTeX figuresLaTeX equivalent of ConTeXt buffersRotate a node but not its content: the case of the ellipse decorationHow to define the default vertical distance between nodes?TikZ scaling graphic and adjust node position and keep font sizeNumerical conditional within tikz keys?adding axes to shapesAlign axes across subfiguresAdding figures with a certain orderLine up nested tikz enviroments or how to get rid of themAdding axes labels to LaTeX figures

Luettelo Yhdysvaltain laivaston lentotukialuksista Lähteet | Navigointivalikko

Gary (muusikko) Sisällysluettelo Historia | Rockin' High | Lähteet | Aiheesta muualla | NavigointivalikkoInfobox OKTuomas "Gary" Keskinen Ancaran kitaristiksiProjekti Rockin' High