Ufs Explorer Raid Recovery Download

0 views
Skip to first unread message

Shawana Messerli

unread,
Aug 4, 2024, 5:01:40 PM8/4/24
to crouchleocenra
Ifno, is there any free and reliable RAID recovery software available? With a quick google search I found ReclaiMe Free RAID Recovery software. But I am not sure about its reputation.

The best way to recover data from a RAID is to use the software or hardware that was used to build it, and if that is not an option, a tool that understands the superblock format because in order to make sense of the data contained on the individual disks, you also need some extra parameters like the block size used.


As others said, to recover any significant amount of data from a RAID-6 array you need at least N-2 drives from the array (N being the total number of drives used in the array). From single drives you may only recover files that are smaller than the array stripe unit size (generally 64 to 256 KiB).


There is an excellent program that allows to re-assemble failed arrays even without the hardware/software setup (RAID controller, OS) that was used in the first place: UFS explorer. Notice that I have absolutely no relationship with this, but I've used the software in the past and it worked surprisingly well. Plus the free version allows you to check that it can access your data before buying a license for a complete recovery.


Ufs explorer raid recovery crack downloadUfs explorer raid recovery crack free downloadUFS Explorer Professional RecoveryUFS Explorer RAID Recovery downloadUFS Explorer Professional Recovery release notesUFS Explorer redditRAID recovery software


data recovery,file recovery,ufs explorer professional recovery,recovery,photo recovery,ufs explorer professional recovery review,usb recovery,hard drive recovery,ufs explorer professional recovery software,sd card recovery,crack,how to use ufs explorer professional recovery software,raid recovery,video recovery,data


I believe a LINUX & Drive/ Volume Expert could help with this as someone did use a similar solution to recover their RAIDed disk, but I was not using RAID, maybe JBOD/ SHR so I think there should be a way?


The question is, assuming I am able to detect the Hard Drive and assuming that hardware is still kind of functional, what way can I LOAD/ MOUNT the Drive (under Windows or Linux OS etc) on a PC/Laptop? (What tools/ software should I used to do that?)


I've not had any luck using this method, but I can see the Disk attached and Ubuntu also gives me the option to format the drive. But, so far I am trying to see some way to recover the drive data.


BTW. If you bought another DiskStation you can save all this trouble. There is a non-destructive way to install DSM on your hard disk, so afterwards you can use the new NAS as if it was the old one. Look on the Synology site.


Faced the exact same situation!Tried unsuccessfully the solution involving mdadm... that was to obscure to me.Tried UFS Professional Recovery with all disks removed from synology and plugged in a spare computer I had left. I can now browse my volume and restore files on demand.Here are a few screenshots I found on the net -explorer-professional-recovery/screenshot/994150/


For ubuntu 18. I am not an expert of lvm or mdasm but here what i have done to solve.A single hard drive SHR attached trough USB-SATA adapter. The system try to set automatically the RAID volume, but something goes wrong:


So like a few others, i've been hit with a predicament caused by user-error. In a single move, I lost the contents of one of my shares (possibly during a mv command or a sym/hard link moment). While the files lost weren't "important" enough for me to keep a backup of, they were plentiful, and reacquiring would be a far more painful task than the idea of recovery.


So, as mentioned in the other threads, you'll need Nerd Pack to download tcl and tcllib. Then what I did was I stopped my array and mounted some large external storage (truth be told, i mounted an old NAS i had with 4bays, that i had replaced with unraid). Then, after mounting my Destination drive, I basically downloaded xfs_undelete, and used the following parameters to fit my needs. I knew what I was looking for (for me, video files) and I knew a date range of when they were deleted (Jan 9th):



xfs_undelete -t 2021-01-09 -r 'video/*' -o /mnt/remotes/nas-drive/xfs_undeleted/ /dev/sdd1



Now, the crappy part is doing it via cifs to the NAS, I can only run this for 1 drive at a time (the CIFS connection becomes unstable), but i reckon i could do this with drives connected via USB or SATA.



The results though are awesome! Instead of doing a scan first of everything and waiting for the Virtual Filesystem to be created, and then doing a restore job [UFS Explorers method] this just scans inode by inode and recovers immediately. The filetype allows me to just say every file of this type, rather than waiting for the vFilesystem, so that's great, but it does mean i'm going to get a bunch of junk i don't want since i can't specify filesizes (oh well). Best off...its free, and appears to just work.


@uaktags @richardoswald thanks for sharing, I followed your tips and was able to recover a bunch of priceless family photos from a very stupid mistake. Learned a real lesson, but not the hardest way thanks to you two.


I was was moving some videos around, after which i routinely deleted the then empty folders. At 03:30AM I must have accidentaly selected the parent folder and pressed delete. I noticed immidiatly and canceled the deletion but lost 3tb in movies. BtW there was a parity check running.


I shut down my server and removed each of the 5 disks. I tried to recover the files with UFS Explorer Standard Recovery but only found empty folders. The cause may be that the movie folder is in a share which has all five disks included.


If you run it on /dev/sdx#/ then you are invalidating the parity since you are writing below the devicemapper. Also, you need to run it on a partition, such as /dev/sdc1 (first partition). Specifying /dev/sdc is for the entire drive. That is why it can't find any valid filesystems..


The /dev/md# syntax may have changed on 6.12 unraid versions for ZFS tomfoolery, so check what the right device name is. I'm still on 6.11 where it's /dev/md1 for first partition of the first drive in the array.


Just want to add another shout out for Recovery Explorer. I had inadvertently wiped out most of my media share, RE allowed me to recover about 90% of the deleted files to an external drive. The rest I was able to pull down from an old AWS Glacier backup.


Edit: SOLVED. I am using XFS encrypted which makes it impossible, I believe for xfs_undelete to even recognize it as the correct file system. Luckily, my data was first on an unassigned device which I could use undelete on. I need better backup protocols for data on the array it looks like!

3a8082e126
Reply all
Reply to author
Forward
0 new messages