RAID5 EXT4 4 Disk Recovery
Posted: 09 Feb 2017, 10:29
My Synology NAS RAID5 x04 disk EXT4, had x02 disk dropped out of the array. After troubleshooting, I found that 2 of the synology hdd slots were faulty.
I followed the guide initially but did not manage to assemble the array. Error message is logged below.
https://www.synology.com/en-us/knowledg ... using_a_PC
After some assistance from Synology Support, we were able to build the array. But we were not able to mount nor see the filesystem of the array.
The support is unable to continue, as they are not comfortable with Ubuntu platform, compared to installing in synology nas platform.
Then after i tried to see what information i can extract more.
Ubuntu is able to auto assemble the array /dev/md2 but does not seem to be able to mount the volume.
But I am not sure why there is no superblock information.
Furthermore the chunk size has changed to 512k instead.
I have also run testdisk to see if any partition can be recovered. But looks like a lot of errors. Not sure if it is due to wrong order of array or something else?
Not sure what to do now, i have also tried using windows software Reclaime
But funny thing is that the disk order shown here is different from what the original information i saw from the first recovery effort.
Order from Synology Support Logs (Disk 2,0,1,3)
Order from Reclaime Log (Disk 0,1,2,3)
Hence now, I need advise and help on how I should proceed on further.
I followed the guide initially but did not manage to assemble the array. Error message is logged below.
https://www.synology.com/en-us/knowledg ... using_a_PC
Code: Select all
root@ubuntu:~# mdadm -Asf && vgchange -ay
mdadm: /dev/md/2 assembled from 2 drives - not enough to start the array.
root@ubuntu:~# mdadm --examine /dev/sd*3
/dev/sda3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b8899307:d41db469:d2da917c:5943634c
Name : DiskStation:2
Creation Time : Sat Aug 2 16:54:55 2014
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5851088833 (2790.02 GiB 2995.76 GB)
Array Size : 8776632768 (8370.05 GiB 8987.27 GB)
Used Dev Size : 5851088512 (2790.02 GiB 2995.76 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=321 sectors
State : clean
Device UUID : 7cf404e5:3078928a:e14811c9:4bc24508
Update Time : Sat Jan 28 03:33:36 2017
Checksum : a3c71a8c - correct
Events : 67
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 1
Array State : .A.. ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b8899307:d41db469:d2da917c:5943634c
Name : DiskStation:2
Creation Time : Sat Aug 2 16:54:55 2014
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5851088833 (2790.02 GiB 2995.76 GB)
Array Size : 8776632768 (8370.05 GiB 8987.27 GB)
Used Dev Size : 5851088512 (2790.02 GiB 2995.76 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=321 sectors
State : clean
Device UUID : 989e8320:0da2d57f:34b382dd:6c026501
Update Time : Sat Jan 28 03:29:01 2017
Checksum : e21597e7 - correct
Events : 63
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 2
Array State : ..A. ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdc3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b8899307:d41db469:d2da917c:5943634c
Name : DiskStation:2
Creation Time : Sat Aug 2 16:54:55 2014
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5851088833 (2790.02 GiB 2995.76 GB)
Array Size : 8776632768 (8370.05 GiB 8987.27 GB)
Used Dev Size : 5851088512 (2790.02 GiB 2995.76 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=321 sectors
State : clean
Device UUID : 1f55310d:d707240b:2e18c5c7:98535992
Update Time : Sat Jan 28 03:00:58 2017
Checksum : d54b63ca - correct
Events : 67
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 0
Array State : AA.. ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdd3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b8899307:d41db469:d2da917c:5943634c
Name : DiskStation:2
Creation Time : Sat Aug 2 16:54:55 2014
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5851088833 (2790.02 GiB 2995.76 GB)
Array Size : 8776632768 (8370.05 GiB 8987.27 GB)
Used Dev Size : 5851088512 (2790.02 GiB 2995.76 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=321 sectors
State : clean
Device UUID : fad32fc1:73cc6310:c075ef4f:71fab83a
Update Time : Sat Jan 28 02:36:18 2017
Checksum : bf15a5e5 - correct
Events : 65
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 3
Array State : A..A ('A' == active, '.' == missing, 'R' == replacing)
root@ubuntu:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 2.7T 0 disk
├─sda1 8:1 0 2.4G 0 part
├─sda2 8:2 0 2G 0 part [SWAP]
└─sda3 8:3 0 2.7T 0 part
sdb 8:16 0 2.7T 0 disk
├─sdb1 8:17 0 2.4G 0 part
├─sdb2 8:18 0 2G 0 part [SWAP]
└─sdb3 8:19 0 2.7T 0 part
sdc 8:32 0 2.7T 0 disk
├─sdc1 8:33 0 2.4G 0 part
├─sdc2 8:34 0 2G 0 part [SWAP]
└─sdc3 8:35 0 2.7T 0 part
sdd 8:48 0 2.7T 0 disk
├─sdd1 8:49 0 2.4G 0 part
├─sdd2 8:50 0 2G 0 part [SWAP]
└─sdd3 8:51 0 2.7T 0 part
sde 8:64 1 14.3G 0 disk
└─sde1 8:65 1 14.3G 0 part /cdrom
loop0 7:0 0 1.4G 1 loop /rofs
Code: Select all
root@ubuntu:~# mdadm -C /dev/md2 -l5 -n4 -e1.2 -u b8899307:d41db469:d2da917c:5943634c --assume-clean /dev/sdf3 /dev/sdd3 /dev/sdb3 /dev/sda3
mdadm: /dev/sdf3 appears to be part of a raid array:
level=raid5 devices=4 ctime=Fri Feb 3 15:47:33 2017
mdadm: /dev/sdd3 appears to be part of a raid array:
level=raid5 devices=4 ctime=Fri Feb 3 15:47:33 2017
mdadm: /dev/sdb3 appears to be part of a raid array:
level=raid5 devices=4 ctime=Fri Feb 3 15:47:33 2017
mdadm: /dev/sda3 appears to be part of a raid array:
level=raid5 devices=4 ctime=Fri Feb 3 15:47:33 2017
Continue creating array? yes
mdadm: array /dev/md2 started.
root@ubuntu:~# vgchange -ay
root@ubuntu:~# mdadm -S /dev/md2
mdadm: stopped /dev/md2
Then after i tried to see what information i can extract more.
Ubuntu is able to auto assemble the array /dev/md2 but does not seem to be able to mount the volume.
But I am not sure why there is no superblock information.
Furthermore the chunk size has changed to 512k instead.
Code: Select all
root@NAS:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md2 : active raid5 sda3[2] sdb3[1] sdc3[3] sdd3[0]
8776241664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/22 pages [0KB], 65536KB chunk
unused devices: <none>
root@NAS:~# mdadm -E /dev/md2
mdadm: No md superblock detected on /dev/md2.
root@NAS:~# mdadm --detail /dev/md2
/dev/md2:
Version : 1.2
Creation Time : Fri Feb 3 17:50:44 2017
Raid Level : raid5
Array Size : 8776241664 (8369.68 GiB 8986.87 GB)
Used Dev Size : 2925413888 (2789.89 GiB 2995.62 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Feb 3 17:50:44 2017
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : ubuntu:2
UUID : b8899307:d41db469:d2da917c:5943634c
Events : 0
Number Major Minor RaidDevice State
0 8 51 0 active sync /dev/sdd3
1 8 19 1 active sync /dev/sdb3
2 8 3 2 active sync /dev/sda3
3 8 35 3 active sync /dev/sdc3
root@NAS:~# mdadm -E /dev/sd*3
/dev/sda3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b8899307:d41db469:d2da917c:5943634c
Name : ubuntu:2
Creation Time : Fri Feb 3 17:50:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850828737 (2789.89 GiB 2995.62 GB)
Array Size : 8776241664 (8369.68 GiB 8986.87 GB)
Used Dev Size : 5850827776 (2789.89 GiB 2995.62 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=961 sectors
State : clean
Device UUID : c99621f4:e29a38c6:579966bc:e32b5fe3
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Feb 3 17:50:44 2017
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 48e9a91c - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b8899307:d41db469:d2da917c:5943634c
Name : ubuntu:2
Creation Time : Fri Feb 3 17:50:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850828737 (2789.89 GiB 2995.62 GB)
Array Size : 8776241664 (8369.68 GiB 8986.87 GB)
Used Dev Size : 5850827776 (2789.89 GiB 2995.62 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=961 sectors
State : clean
Device UUID : 67de2afa:4132b674:b01121d9:a4a2f65e
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Feb 3 17:50:44 2017
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 95c27731 - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 1
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdc3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b8899307:d41db469:d2da917c:5943634c
Name : ubuntu:2
Creation Time : Fri Feb 3 17:50:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850828737 (2789.89 GiB 2995.62 GB)
Array Size : 8776241664 (8369.68 GiB 8986.87 GB)
Used Dev Size : 5850827776 (2789.89 GiB 2995.62 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=961 sectors
State : clean
Device UUID : 82523814:d76384ec:3f86b3b1:7c024714
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Feb 3 17:50:44 2017
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : b580f14a - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 3
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdd3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b8899307:d41db469:d2da917c:5943634c
Name : ubuntu:2
Creation Time : Fri Feb 3 17:50:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850828737 (2789.89 GiB 2995.62 GB)
Array Size : 8776241664 (8369.68 GiB 8986.87 GB)
Used Dev Size : 5850827776 (2789.89 GiB 2995.62 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=961 sectors
State : clean
Device UUID : 6da1893d:e5a63446:41cac1cd:db84d155
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Feb 3 17:50:44 2017
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 961b49a1 - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
I have also run testdisk to see if any partition can be recovered. But looks like a lot of errors. Not sure if it is due to wrong order of array or something else?
Code: Select all
Wed Feb 8 19:04:15 2017
Command line: TestDisk
TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Linux, kernel 4.4.0-62-generic (#83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017) x86_64
Compiler: GCC 4.4
Compilation date: 2015-04-18T13:05:16
ext2fs lib: 1.42.8, ntfs lib: libntfs-3g, reiserfs lib: 0.3.1-rc8, ewf lib: 20120504, curses lib: ncurses 5.7
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size 5860533168 sectors
/dev/sda: user_max 5860533168 sectors
/dev/sda: native_max 5860533168 sectors
/dev/sdb: LBA, HPA, LBA48, DCO support
/dev/sdb: size 5860533168 sectors
/dev/sdb: user_max 5860533168 sectors
/dev/sdb: native_max 5860533168 sectors
/dev/sdc: LBA, HPA, LBA48, DCO support
/dev/sdc: size 5860533168 sectors
/dev/sdc: user_max 5860533168 sectors
/dev/sdc: native_max 5860533168 sectors
/dev/sdd: LBA, HPA, LBA48, DCO support
/dev/sdd: size 5860533168 sectors
/dev/sdd: user_max 5860533168 sectors
/dev/sdd: native_max 5860533168 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - 0 sectors, sector size=512
Warning: can't get size for Disk /dev/md - 0 B - 0 sectors (RO), sector size=512
Hard disk list
Disk /dev/sda - 3000 GB / 2794 GiB - CHS 364801 255 63, sector size=512 - WDC WD30EFRX-68AX9N0, S/N:WD-WCC1T0549413, FW:80.00A80
Disk /dev/sdb - 3000 GB / 2794 GiB - CHS 364801 255 63, sector size=512 - WDC WD30EFRX-68AX9N0, S/N:WD-WCC1T0528534, FW:80.00A80
Disk /dev/sdc - 3000 GB / 2794 GiB - CHS 364801 255 63, sector size=512 - WDC WD30EFRX-68EUZN0, S/N:WD-WCC4N0811191, FW:80.00A80
Disk /dev/sdd - 3000 GB / 2794 GiB - CHS 364801 255 63, sector size=512 - WDC WD30EFRX-68EUZN0, S/N:WD-WCC4N0822317, FW:80.00A80
Disk /dev/sde - 15 GB / 14 GiB - CHS 14663 64 32, sector size=512 - SanDisk Ultra, FW:1.00
Disk /dev/md2 - 8986 GB / 8369 GiB - CHS 2194060416 2 4, sector size=512
Partition table type default to EFI GPT
Disk /dev/md2 - 8986 GB / 8369 GiB
Partition table type: EFI GPT
Analyse Disk /dev/md2 - 8986 GB / 8369 GiB - CHS 2194060416 2 4
Bad GPT partition, invalid signature.
Trying alternate GPT
Bad GPT partition, invalid signature.
Current partition structure:
Bad GPT partition, invalid signature.
Trying alternate GPT
Bad GPT partition, invalid signature.
search_part()
Disk /dev/md2 - 8986 GB / 8369 GiB - CHS 2194060416 2 4
block_group_nr 3
recover_EXT2: part_offset problem
block_group_nr 5
recover_EXT2: part_offset problem
block_group_nr 5
recover_EXT2: part_offset problem
block_group_nr 5
recover_EXT2: part_offset problem
block_group_nr 7
recover_EXT2: part_offset problem
block_group_nr 7
recover_EXT2: part_offset problem
block_group_nr 7
recover_EXT2: part_offset problem
block_group_nr 7
recover_EXT2: part_offset problem
block_group_nr 9
recover_EXT2: part_offset problem
block_group_nr 9
recover_EXT2: part_offset problem
block_group_nr 9
recover_EXT2: part_offset problem
block_group_nr 9
recover_EXT2: part_offset problem
block_group_nr 25
recover_EXT2: part_offset problem
block_group_nr 25
recover_EXT2: part_offset problem
block_group_nr 25
recover_EXT2: part_offset problem
block_group_nr 25
recover_EXT2: part_offset problem
block_group_nr 27
recover_EXT2: part_offset problem
block_group_nr 27
recover_EXT2: part_offset problem
block_group_nr 27
recover_EXT2: part_offset problem
block_group_nr 27
recover_EXT2: part_offset problem
block_group_nr 49
recover_EXT2: part_offset problem
block_group_nr 49
recover_EXT2: part_offset problem
block_group_nr 49
recover_EXT2: part_offset problem
block_group_nr 49
recover_EXT2: part_offset problem
block_group_nr 81
recover_EXT2: part_offset problem
block_group_nr 81
recover_EXT2: part_offset problem
block_group_nr 81
recover_EXT2: part_offset problem
block_group_nr 81
recover_EXT2: part_offset problem
block_group_nr 125
recover_EXT2: part_offset problem
block_group_nr 125
recover_EXT2: part_offset problem
block_group_nr 125
recover_EXT2: part_offset problem
block_group_nr 125
recover_EXT2: part_offset problem
block_group_nr 243
recover_EXT2: part_offset problem
block_group_nr 243
recover_EXT2: part_offset problem
block_group_nr 243
recover_EXT2: part_offset problem
block_group_nr 243
recover_EXT2: part_offset problem
block_group_nr 343
recover_EXT2: part_offset problem
block_group_nr 343
recover_EXT2: part_offset problem
block_group_nr 343
recover_EXT2: part_offset problem
block_group_nr 343
recover_EXT2: part_offset problem
block_group_nr 625
recover_EXT2: part_offset problem
block_group_nr 625
recover_EXT2: part_offset problem
block_group_nr 625
recover_EXT2: part_offset problem
block_group_nr 625
recover_EXT2: part_offset problem
block_group_nr 729
recover_EXT2: part_offset problem
block_group_nr 729
recover_EXT2: part_offset problem
block_group_nr 729
recover_EXT2: part_offset problem
block_group_nr 729
recover_EXT2: part_offset problem
check_FAT: Bad number of sectors per cluster
block_group_nr 2187
recover_EXT2: part_offset problem
block_group_nr 2187
recover_EXT2: part_offset problem
block_group_nr 2187
recover_EXT2: part_offset problem
block_group_nr 2187
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 2401
recover_EXT2: part_offset problem
block_group_nr 3125
recover_EXT2: part_offset problem
block_group_nr 3125
recover_EXT2: part_offset problem
block_group_nr 3125
recover_EXT2: part_offset problem
block_group_nr 3125
recover_EXT2: part_offset problem
check_FAT: Bad number of sectors per cluster
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
block_group_nr 6561
recover_EXT2: part_offset problem
LVM magic value at 224379272/0/1
LVM magic value at 224387739/0/1
LVM magic value at 335940760/1/3
MS Data 3922719958 4629022203 706302246
FATX, 361 GB / 336 GiB
check_FAT: Bad jump in FAT partition
block_group_nr 19683
recover_EXT2: part_offset problem
block_group_nr 19683
recover_EXT2: part_offset problem
block_group_nr 19683
recover_EXT2: part_offset problem
block_group_nr 19683
recover_EXT2: part_offset problem
SYSV4 Marker at 757575011/0/4
recover_sysv4
MS Data 6060600091 30118946532122 30112885932032 [žžðÙÑD]
SysV4, 15417 TB / 14022 TiB
This partition ends after the disk limits. (start=6060600091, size=30112885932032, end=30118946532122, disk end=17552483328)
SYSV4 Marker at 814007470/1/1
recover_sysv4
Unknown 6512059764 6113002420315507 6112995908255744 [.Êþ2ÐÇ]
SysV4, 3129853 TB / 2846585 TiB
Partition not added.
cramfs Marker at 839163897/0/4
recover_cramfs
MS Data 6713311179 6721336247 8025068 [ý^:òC×z¤è80îÀ]
cramfs, 4108 MB / 3918 MiB
check_FAT: Bad number of sectors per cluster
SYSV4 Marker at 848854566/1/1
recover_sysv4
Unknown 6790836532 25501569259 18710732728 [ ¹ð¨ßw]
SysV4, 9579 GB / 8921 GiB
Partition not added.
Unknown 7140932470 8686052393 1545119924
FATX, 791 GB / 736 GiB
Partition not added.
check_FAT: Bad jump in FAT partition
LVM magic value at 912302832/0/2
check_FAT: Bad jump in FAT partition
check_FAT: Bad number of sectors per cluster
check_FAT: Bad number of sectors per cluster
check_FAT: Bad jump in FAT partition
SYSV4 Marker at 1033821955/1/2
recover_sysv4
Unknown 8270575645 8270575644 0 [Ž’ð-]
SysV4, 0 B
Partition not added.
Unknown 8351551539 5005260159094834 5005251807543296
WBFS, 2562688 TB / 2330752 TiB
Partition not added.
check_FAT: Bad jump in FAT partition
recover_EXT2: s_block_group_nr=0/22340, s_mnt_count=20/38, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 732043776
recover_EXT2: part_size 5856350208
MS Data 8761242728 14617592935 5856350208
ext3 blocksize=4096 Large_file Sparse_SB Recover, 2998 GB / 2792 GiB
block_group_nr 19683
recover_EXT2: "e2fsck -b 644972544 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=19683/22340, s_mnt_count=0/38, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 732043776
recover_EXT2: part_size 5856350208
MS Data 10296730622 16153080829 5856350208
ext3 blocksize=4096 Large_file Sparse_SB Backup_SB, 2998 GB / 2792 GiB
Unknown 17132501598 17838803843 706302246
FATX, 361 GB / 336 GiB
Partition not added.
Disk /dev/md2 - 8986 GB / 8369 GiB - CHS 2194060416 2 4
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (8986 GB / 8369 GiB) seems too small! (< 15420 TB / 14025 TiB)
The following partition can't be recovered:
MS Data 6060600091 30118946532122 30112885932032 [žžðÙÑD]
SysV4, 15417 TB / 14022 TiB
SIGHUP detected! TestDisk has been killed.
But funny thing is that the disk order shown here is different from what the original information i saw from the first recovery effort.
Order from Synology Support Logs (Disk 2,0,1,3)
Order from Reclaime Log (Disk 0,1,2,3)
Hence now, I need advise and help on how I should proceed on further.
Code: Select all
This is a plain-text general description of the reconstructed array layout.
The array type is RAID5.
The array consists of 4 disks.
The disks are ordered as follows:
#00: Disk 0 - WDC WD30EFRX-68AX9N0, Serial number WCC1T0549413, \\.\PhysicalDrive0
#01: Disk 1 - WDC WD30EFRX-68AX9N0, Serial number WCC1T0528534, \\.\PhysicalDrive1
#02: Disk 2 - WDC WD30EFRX-68EUZN0, Serial number WCC4N0811191, \\.\PhysicalDrive2
#03: Disk 3 - WDC WD30EFRX-68EUZN0, Serial number WCC4N0822317, \\.\PhysicalDrive3
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 P
5 6 P 4
9 P 7 8
P 10 11 12