Restore deleted shared folder from synology nas

[Mogwai]

Hi there

I deleted the only shared folder on my synology nas with 6 disks in raid5 (ext4 format) and i try to recover it with r-studio for a while now but get nowhere so far.

The disks are now installed in a pc running Win10. I think the problem is that the raid configuration is wrong, although i already tried the auto-detect feature. I am running reclaime free raid recovery for the second time now, as the first time it froze after 5%. I will post some screenshots when the tool has finished or crashed again...

Would there be another way to find out the raid configuration manually? I saw a manual for ntfs disks once so maybe there is also one for ext4?

Best regards

Andreas

Edit: now i got the info from the tool and i'll give it another try with the recovery...

[Alt]

Did R-Studio find any mdadm/LVM objects?

[Mogwai]

Not sure, have to check this evening.

R-Studio just finished several days of scanning this morning but no results. Guess some settings were still wrong. What i was missing after i sorted the disks in the right order were these settings, have not seen them:

IMG-20210222-WA0001.jpg

Before they showed up automatically but this time they didn't. Maybe because i have no clue of the tool anyway Guess it's right that if the block size is wrong no files can be found?

Will get back later.

Andreas

[Mogwai]

Hi again
R-Studio found some mdadm objects. I will post some screens to show you and also of the configuration so far:

Screenshot 2021-03-07 123631.jpg

This is the order of disks:

Screenshot 2021-03-07 123721.jpg

Guess after the other tool the order should be correct:

The array type is RAID5.
The array consists of 6 disks.

The disks are ordered as follows:
#00: Disk 3 - ST16000NE000-2RW103, Serial number 22F0TD, \\.\PhysicalDrive3
#01: Disk 2 - ST16000NE000-2RW103, Serial number 22ENR8, \\.\PhysicalDrive2
#02: Disk 5 - ST16000NE000-2RW103, Serial number 22EN9C, \\.\PhysicalDrive5
#03: Disk 4 - ST16000NE000-2RW103, Serial number 22F216, \\.\PhysicalDrive4
#04: Disk 0 - ST16000NE000-2RW103, Serial number 22F1LL, \\.\PhysicalDrive0
#05: Disk 1 - ST16000NE000-2RW103, Serial number 22FB7Q, \\.\PhysicalDrive1

Block size is 64.0 KB , same as 128 sectors.
The data starts at sector (LBA) 0 (this is often called "offset" or "start offset").

Block map is as follows:

1 2 3 4 5 P
7 8 9 10 P 6
13 14 15 P 11 12
19 20 P 16 17 18
25 P 21 22 23 24
P 26 27 28 29 30

What i'm missing is the configuration where i can enter the block size and eventually the block map as shown in my previous post. Do i have to create a region for that? I'm afraid i could mess up the disks although i would have clones just in case...

Back with an update:

I started over again, guess i chose the wrong command before (create virtual volume set instead of create virtual block raid & autodetect), now i have also the menu again with the block table and i also found the partition:

Screenshot 2021-03-07 144643.jpg

If i understood the manual right, it should already be possible to show the files on the partition without a scan. But when i try this i only get thousands of *.bin files... Do i have to perform a scan anyway?

[Alt]

I need to know what R-Studio shows when you don't create any RAIDs. Because R-Studio should automatically assemble mdadm RAIDs created by the NAS itself.

[Mogwai]

I think these detected volumes at the bottom came automatically, cause they can't be removed. Cannot verify at the moment as another scan is running... But they look pretty small.

Screenshot 2021-03-09 172500.jpg

[Alt]

Is there anything below virt-mdadm-Synology8:2 in this panel?
Is there any valid files on this volume (virt-mdadm-Synology8:2)?

[Mogwai]

No, that's the last entry and there are no useful files...

[Mogwai]

I did a scan with reclaime in the meantime (took only a little more than 12 days...) but with no big success. Found some files, but each with random filenames, so not very useful and there were no larger files than 4GB which is very strange as there are bigger files for sure.

So time to get back to r-studio: when i look at the bottom at volume "virt-mdadm-Synology8:2 which shows a wrong size (11.87GB), i see in the "components" register that each disk has a size of 465.76GB, which is much too small. I wonder why that is so.

On the other hand the size of the disks at the top is indicated correctly (14.55TB, which i guess is the net size of 16TB).

Is it possible that r-studio cannot handle this size of disks?

Andreas

[Mogwai]

Since the manual raid configuration didn't work i let the tool find the configuration automatically, but after 1 day it's at 3%... guess it stopped in between cause it was not responding when i just checked. Now it seems to go on again.

What bothers me are these messages in the log:

Screenshot 2021-03-25 193546.jpg

I don't know why it quotes Virtual Block Raid 3, there's only a Virtual Block Raid 1 at the moment... And what does that text mean?? Doesn't sound too good to me...

Andreas