![]() Once retrieved, I performed my tests on the recovered scripts and they worked as before. You will find earlier versions of your script too. Upon checking the recovery destination, you will find directories and files (I was interested in *.sh files) as shown below:Īfter performing a few “find and grep” commands looking for my script content, I retrieved the latest version of all my scripts. The image below is a screenshot of the recovery process. Download 'TestDisk', unzip the downloaded zip file and run the 'testdiskwin.exe' file. ![]() (For this example, we’ll use All Recovery Methods). ![]() Using the dropdown menu on the right sidebar, choose your preferred recovery method and click Search for lost data. I would run this before messing around with drive settings. Press (CMD + Space) to open Spotlight Search and type Disk Drill Select the drive you want to recover. Use lsblkto confirm the partition on which your lost files resided and execute sudo photorec (e.g. PhotoRec is a recovery program that comes as part of TestDisk and is great at recovering all types of files, not just photos. Photorec is quite straightforward to use and recovers files based on your selected file types into a selected destination. TestDisk is a powerful free data recovery software which was primarily designed to help recover lost partitions and/or make non-booting disks bootable again. ![]() After frantically looking for tools to recover my scripts, I came across TestDisk/PhotoRec and photorec saved my bacon. My heart sank because I had no backup and hadn’t yet checked in my scripts into git. After spending a few hours on developing some scripts, I hastily fat-fingered a command and removed my entire scripts directory on my RHEL 7 server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |