by exequos » Sun Jun 30, 2013 8:06 am
You said that one disk is broken, what did you use in R-Studio as its substitute?
It was runtime package software - what i only was to try as I couldn't mount the vim file under captain nemo
So in general only R-Studio shows me resonable results (some files were 0bytes some more and readable with proper data)
Quite possible.
No difference except file size limitations during recovery.
My idea for this situation is that some files were uploaded to degraded volume which brokes suddenly so the files doesn't copy properly to raid strips
I've tryied different RAID5 settings with runtime nas recovery, but only one show results - in case of R-studio it was much simpler just drop and drag with the biggest partitions and checking if the virtual raid show proper volume.
What i thought maybe as a possibility was that for example settings with 4KB or 64KB block will show the some file structure and 0bytes files can have proper size.
In this case it looks rather as broken structure data than wrong reading settings yes?
Pls have a look for the NAS data recovery settings I've tried to use with NAS recovery with no results (64KB block/128sectors, left 1-2-3, partition start 3 164 805) - I have only HDD1 and HDD2 (HDD3 is missing)
Code: Select all
Testing 2 drives...
Parsing partition tables for 2 drives...
Parsing partition table for DISK1:, 2 930 277 168 sectors (1,36 TB)...
Drive DISK1: has 3 partitions
Partition #1 at sector 63, 1 060 227 sectors: Prime or Linux swap or Solaris UNIX (130)
Partition #2 at sector 3 164 805, 2 925 532 890 sectors: Linux (131)
Partition #3 at sector 1 060 290, 2 104 515 sectors: Linux (131)
Parsing partition table for DISK2:, 2 930 277 168 sectors (1,36 TB)...
Drive DISK2: has 3 partitions
Partition #1 at sector 63, 1 060 227 sectors: Prime or Linux swap or Solaris UNIX (130)
Partition #2 at sector 3 164 805, 2 925 532 890 sectors: Linux (131)
Partition #3 at sector 1 060 290, 2 104 515 sectors: Linux (131)
StartSector 3164805, 2925532890 sectors is possible data start on drive DISK1:
StartSector 3164805, 2925532890 sectors is possible data start on drive DISK2:
Creating RAID list...
Testing possible start 3 164 805 (length 2 925 532 890)...
...for XFS superblock on DISK1:
...for XFS superblock on DISK2:
...for EXT2FS superblock on DISK1:
...valid EXT2FS superblock found, building RAID
...adding DISK1:
...adding DISK2:
...adding missing drive
Completing RAID list...
Setting level of RAID no 0 to 5
Finding drive order...
Testing 6 possible drive orders with a probe size of 5 000 000 sectors, requiring 20%
Best combination after 100096 sectors: 0,1,2 with entropy 0,1849 versus 0,2170 (17%)
Best combination after 110080 sectors: 0,1,2 with entropy 0,1742 versus 0,2075 (19%)
Best combination found after 120064 sectors: 0,1,2 with entropy 0,1633 versus 0,1993 (22%)
Applying...
-------------
Raid settings
-------------
Raid level 5
3 drives
Drive 1: DISK1:
Drive 2: DISK2:
Drive 3: (n/a)
Partition start: 3 164 805
Partition length: 2 925 532 890 sectors (1,36 TB)
Volume length: 1 556 098 048 sectors (742 GB)
1 data drives are required
Stripe count: 0
Stripe size: 128 sectors
Rotation: left-symmetric
last but not least: the HDD are connected to PC in the some order as in nas (HDD1 - ch1, HDD2 - ch2 but they are not only hdd's under the controller, ch0 is system, ch3 is data)
[quote]You said that one disk is broken, what did you use in R-Studio as its substitute?[/quote]
It was runtime package software - what i only was to try as I couldn't mount the vim file under captain nemo
So in general only R-Studio shows me resonable results (some files were 0bytes some more and readable with proper data)
[quote]Quite possible.
No difference except file size limitations during recovery.[/quote]
My idea for this situation is that some files were uploaded to degraded volume which brokes suddenly so the files doesn't copy properly to raid strips
I've tryied different RAID5 settings with runtime nas recovery, but only one show results - in case of R-studio it was much simpler just drop and drag with the biggest partitions and checking if the virtual raid show proper volume.
What i thought maybe as a possibility was that for example settings with 4KB or 64KB block will show the some file structure and 0bytes files can have proper size.
In this case it looks rather as broken structure data than wrong reading settings yes?
Pls have a look for the NAS data recovery settings I've tried to use with NAS recovery with no results (64KB block/128sectors, left 1-2-3, partition start 3 164 805) - I have only HDD1 and HDD2 (HDD3 is missing)
[code]Testing 2 drives...
Parsing partition tables for 2 drives...
Parsing partition table for DISK1:, 2 930 277 168 sectors (1,36 TB)...
Drive DISK1: has 3 partitions
Partition #1 at sector 63, 1 060 227 sectors: Prime or Linux swap or Solaris UNIX (130)
Partition #2 at sector 3 164 805, 2 925 532 890 sectors: Linux (131)
Partition #3 at sector 1 060 290, 2 104 515 sectors: Linux (131)
Parsing partition table for DISK2:, 2 930 277 168 sectors (1,36 TB)...
Drive DISK2: has 3 partitions
Partition #1 at sector 63, 1 060 227 sectors: Prime or Linux swap or Solaris UNIX (130)
Partition #2 at sector 3 164 805, 2 925 532 890 sectors: Linux (131)
Partition #3 at sector 1 060 290, 2 104 515 sectors: Linux (131)
StartSector 3164805, 2925532890 sectors is possible data start on drive DISK1:
StartSector 3164805, 2925532890 sectors is possible data start on drive DISK2:
Creating RAID list...
Testing possible start 3 164 805 (length 2 925 532 890)...
...for XFS superblock on DISK1:
...for XFS superblock on DISK2:
...for EXT2FS superblock on DISK1:
...valid EXT2FS superblock found, building RAID
...adding DISK1:
...adding DISK2:
...adding missing drive
Completing RAID list...
Setting level of RAID no 0 to 5
Finding drive order...
Testing 6 possible drive orders with a probe size of 5 000 000 sectors, requiring 20%
Best combination after 100096 sectors: 0,1,2 with entropy 0,1849 versus 0,2170 (17%)
Best combination after 110080 sectors: 0,1,2 with entropy 0,1742 versus 0,2075 (19%)
Best combination found after 120064 sectors: 0,1,2 with entropy 0,1633 versus 0,1993 (22%)
Applying...
-------------
Raid settings
-------------
Raid level 5
3 drives
Drive 1: DISK1:
Drive 2: DISK2:
Drive 3: (n/a)
Partition start: 3 164 805
Partition length: 2 925 532 890 sectors (1,36 TB)
Volume length: 1 556 098 048 sectors (742 GB)
1 data drives are required
Stripe count: 0
Stripe size: 128 sectors
Rotation: left-symmetric
[/code]
last but not least: the HDD are connected to PC in the some order as in nas (HDD1 - ch1, HDD2 - ch2 but they are not only hdd's under the controller, ch0 is system, ch3 is data)