not sure where to post...... snapraid mystery

boelle · 20. März 2023

so i tried to simulate a dual drive fail

simply pulled 2 drives and put in 2 new and did a fix....

it said the rebuild was done... and so i did a diff between the old and new drives... i would expect snapraid to make the content the same as before for each of the 2 drives

they are not indentical...

root@bo-omv:~# ls /mnt/disk1

aquota.group aquota.user Backup Emoncmsbackup homedir lost+found Pictures snapraid.content snapraid.content.lock Video

root@bo-omv:~# ls /mnt/testdisk1

aquota.group aquota.user homedir lost+found Pictures snapraid.content.lock Video

root@bo-omv:~#

also the hdd led is still going on like mad....

if i try and do another fix i would expect it to say there is nothing to fix but it says snapraid is in use

that suggest that its doing something in the background even after it says rebuild is done...

can someone explain what is going on ?

gderf · 20. März 2023

In your snapraid.conf file what excludes are listed?

When you ran the fix, did you log it?

boelle · 20. März 2023

Zitat von gderf

In your snapraid.conf file what excludes are listed?

When you ran the fix, did you log it?

i use the web interface exclusive so i dont know what the content of the conf is

and the fix ended with "END OF LINE" so i would expect that means its done

but if you can tell me where the conf is i can ssh in and get the info from it

gderf · 20. März 2023

I suggest not using the web interface tools to do things like this, use the CLI instead.

You can view the config file from the web interface.

Also, was the array fully sync'd before you tried this?

boelle · 20. März 2023

Code

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

autosave 0
#####################################################################
# OMV-Name: sdb1_disk1  Drive Label:
content /srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/snapraid.content
disk sdb1_disk1 /srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24
#####################################################################
# OMV-Name: sdc1_disk2  Drive Label:
content /srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/snapraid.content
disk sdc1_disk2 /srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6
#####################################################################
# OMV-Name: sdd1_disk3  Drive Label:
content /srv/dev-disk-by-uuid-117385df-2092-4777-9a97-3ebd052d7581/snapraid.content
disk sdd1_disk3 /srv/dev-disk-by-uuid-117385df-2092-4777-9a97-3ebd052d7581
#####################################################################
# OMV-Name: sde1_disk4  Drive Label:
content /srv/dev-disk-by-uuid-cdac1b82-2335-45cd-b7f6-7b6852429514/snapraid.content
disk sde1_disk4 /srv/dev-disk-by-uuid-cdac1b82-2335-45cd-b7f6-7b6852429514
#####################################################################
# OMV-Name: sda1_disk5  Drive Label:
parity /srv/dev-disk-by-uuid-95c89948-db55-4f6e-817b-6fb065d1946b/snapraid.parity


exclude *.unrecoverable
exclude lost+found/
exclude aquota.user
exclude aquota.group
exclude /tmp/
exclude .content
exclude *.bak
exclude /snapraid.conf*

Alles anzeigen

boelle · 20. März 2023

Zitat von gderf

Also, was the array fully sync'd before you tried this?

yes i did both sync and scrub just to be on the safe side

gderf · 20. März 2023

From your initial post it looks like these two directories were not restored, is that correct?

Backup

Emoncmsbackup

Since you have no log of the fix operation, and those directories were not excluded, I have no answer.

boelle · 20. März 2023

Zitat von gderf

I suggest not using the web interface tools to do things like this, use the CLI instead.

reason i use the webinterface is that i'm not super comfu with cli

boelle · 20. März 2023

Zitat von gderf

From your initial post it looks like these two directories were not restored, is that correct?

correct.....

Q... if i remove all excludes...(i bet that is stupid) should it nore rebuild the disks 1:1 ?

boelle · 20. März 2023

Zitat von gderf

Since you have no log of the fix operation

i plan to have another go tomorrow.... what would the steps be to test this seen from CLI.. or can i do some of it in web?

gderf · 20. März 2023

See section 4.4 Recovering in the manual:

SnapRAID

boelle · 20. März 2023

just to check i understand it correct

from cli i then run:

snapraid -d sdb1_disk1 -l fix.log fix
snapraid -d sdc1_disk2 -l fix2.log fix

?

i have prepared 2 disks that have the same uuid, guid and part uuid as the "live" ones.. ie they should be 1:1 but clear of data

with that i assume i can just pull the live drives and put the testers in

gderf · 20. März 2023

Looks correct.

boelle · 21. März 2023

Q... it says in config:

# This file is auto-generated by openmediavault (https://www.openmediavault.org)

# WARNING: Do not edit this file, your changes will get lost.

so if i cant edit the file directly how do i change the excludes ?

boelle · 21. März 2023

so i did sync and scrub again and a blkid:

root@bo-omv:~# blkid

/dev/sda1: UUID="95c89948-db55-4f6e-817b-6fb065d1946b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="65676062-ad00-425d-860d-831d7c526ea8"

/dev/sdc1: UUID="7d46260d-a71f-4138-8ab1-8ae5bac8e8d6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2da483bf-2476-7645-ada9-6c0761a12304"

/dev/sde1: UUID="cdac1b82-2335-45cd-b7f6-7b6852429514" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9a3ac9ad-ba0b-4713-a993-e249b8ed6f69"

/dev/sdd1: UUID="117385df-2092-4777-9a97-3ebd052d7581" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="3360cbb3-d0dc-4302-a504-fe6c06e2aa7b"

/dev/sdb1: UUID="2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6ae70f91-5cc1-4697-8633-cfb97a700fcf"

/dev/sdf1: UUID="a42405ab-ec91-4140-b465-ed8e5a7ab7c6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c7c9adb0-01"

/dev/sdf5: UUID="e245982a-4178-4d31-9e41-19fc4b4900cc" TYPE="swap" PARTUUID="c7c9adb0-05"

removed the 2 drives and did blkid again

root@bo-omv:~# blkid

/dev/sda1: UUID="95c89948-db55-4f6e-817b-6fb065d1946b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="65676062-ad00-425d-860d-831d7c526ea8"

/dev/sde1: UUID="cdac1b82-2335-45cd-b7f6-7b6852429514" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9a3ac9ad-ba0b-4713-a993-e249b8ed6f69"

/dev/sdd1: UUID="117385df-2092-4777-9a97-3ebd052d7581" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="3360cbb3-d0dc-4302-a504-fe6c06e2aa7b"

/dev/sdf1: UUID="a42405ab-ec91-4140-b465-ed8e5a7ab7c6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c7c9adb0-01"

/dev/sdf5: UUID="e245982a-4178-4d31-9e41-19fc4b4900cc" TYPE="swap" PARTUUID="c7c9adb0-05"

then inserted the 2 blank drives, but otherwise they have the same uuid, guid and part uuid so they should in effect be the same but just blank

did blkid again and they show up as before just at the end of the list

root@bo-omv:~# blkid

/dev/sda1: UUID="95c89948-db55-4f6e-817b-6fb065d1946b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="65676062-ad00-425d-860d-831d7c526ea8"

/dev/sde1: UUID="cdac1b82-2335-45cd-b7f6-7b6852429514" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9a3ac9ad-ba0b-4713-a993-e249b8ed6f69"

/dev/sdd1: UUID="117385df-2092-4777-9a97-3ebd052d7581" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="3360cbb3-d0dc-4302-a504-fe6c06e2aa7b"

/dev/sdf1: UUID="a42405ab-ec91-4140-b465-ed8e5a7ab7c6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c7c9adb0-01"

/dev/sdf5: UUID="e245982a-4178-4d31-9e41-19fc4b4900cc" TYPE="swap" PARTUUID="c7c9adb0-05"

/dev/sdb1: UUID="2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6ae70f91-5cc1-4697-8633-cfb97a700fcf"

/dev/sdc1: UUID="7d46260d-a71f-4138-8ab1-8ae5bac8e8d6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2da483bf-2476-7645-ada9-6c0761a12304"

doing fix of the first say they are on the same device??

root@bo-omv:~# snapraid -d sdb1_disk1 -l fix.log fix

Self test...

Disks '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/' and '/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/' are on the same device.

You can 'fix' anyway, using 'snapraid --force-device fix'.

the blkid above shows the 2 uuid's on seperate disks so what did i do wrong here?

boelle · 21. März 2023

inside omv it seems the 2 disks are gone...

i try and edit the drives in the plugin and they are gone....

mount -a did the trick this time, but a lot of unrecoverable's..

will let it run and post the log's...

seems i have some changes to do.... ie i do not like unrecoverables

boelle · 21. März 2023

just for completeness sake my config... i commented out the excludes before i did the sync and scrub

snapraid touch

snapraid sync -h
snapraid -p 100 -o 1 scrub

Code

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

autosave 0
#####################################################################
# OMV-Name: sdb1_disk1  Drive Label:
content /srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/snapraid.content
disk sdb1_disk1 /srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24
#####################################################################
# OMV-Name: sdc1_disk2  Drive Label:
content /srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/snapraid.content
disk sdc1_disk2 /srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6
#####################################################################
# OMV-Name: sdd1_disk3  Drive Label:
content /srv/dev-disk-by-uuid-117385df-2092-4777-9a97-3ebd052d7581/snapraid.content
disk sdd1_disk3 /srv/dev-disk-by-uuid-117385df-2092-4777-9a97-3ebd052d7581
#####################################################################
# OMV-Name: sde1_disk4  Drive Label:
content /srv/dev-disk-by-uuid-cdac1b82-2335-45cd-b7f6-7b6852429514/snapraid.content
disk sde1_disk4 /srv/dev-disk-by-uuid-cdac1b82-2335-45cd-b7f6-7b6852429514
#####################################################################
# OMV-Name: sda1_disk5  Drive Label:
parity /srv/dev-disk-by-uuid-95c89948-db55-4f6e-817b-6fb065d1946b/snapraid.parity


#exclude *.unrecoverable
#exclude lost+found/
#exclude aquota.user
#exclude aquota.group
#exclude /tmp/
#exclude .content
#exclude *.bak
#exclude /snapraid.conf*

Alles anzeigen

boelle · 21. März 2023

holy.... th log is 500 mb

here is the first part of it

Code

version:12.2
unixtime:1679394030
time:2023-03-21 11:20:30
command:fix
argv:0:snapraid
argv:1:-d
argv:2:sdb1_disk1
argv:3:-l
argv:4:fix.log
argv:5:fix
selftest:
msg:progress: Self test...
conf:file:/etc/snapraid.conf
uuid:by-uuid:8:17:2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24: found ../../sdb1
uuid:by-uuid:8:33:7d46260d-a71f-4138-8ab1-8ae5bac8e8d6: found ../../sdc1
uuid:by-uuid:8:49:117385df-2092-4777-9a97-3ebd052d7581: found ../../sdd1
uuid:by-uuid:8:65:cdac1b82-2335-45cd-b7f6-7b6852429514: found ../../sde1
blocksize:262144
data:sdb1_disk1:/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/
data:sdc1_disk2:/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/
data:sdd1_disk3:/srv/dev-disk-by-uuid-117385df-2092-4777-9a97-3ebd052d7581/
data:sde1_disk4:/srv/dev-disk-by-uuid-cdac1b82-2335-45cd-b7f6-7b6852429514/
mode:par1
parity:0:/srv/dev-disk-by-uuid-95c89948-db55-4f6e-817b-6fb065d1946b/snapraid.parity
content:/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/snapraid.content
msg:progress: Loading state from /srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/snapraid.content...
msg:fatal: WARNING! Content file '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/snapraid.content' not found, trying with another copy...
content:/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/snapraid.content
msg:progress: Loading state from /srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/snapraid.content...
msg:fatal: WARNING! Content file '/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/snapraid.content' not found, trying with another copy...
content:/srv/dev-disk-by-uuid-117385df-2092-4777-9a97-3ebd052d7581/snapraid.content
msg:progress: Loading state from /srv/dev-disk-by-uuid-117385df-2092-4777-9a97-3ebd052d7581/snapraid.content...
msg:verbose:    27990 files
msg:verbose:        0 hardlinks
msg:verbose:        0 symlinks
msg:verbose:      890 empty dirs
uuid:by-uuid:8:1:95c89948-db55-4f6e-817b-6fb065d1946b: found ../../sda1
msg:progress: Searching disk sdb1_disk1...
msg:verbose: Excluding content '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/snapraid.content.lock'
msg:progress: Searching disk sdc1_disk2...
msg:progress: Searching disk sdd1_disk3...
msg:verbose: Excluding content '/srv/dev-disk-by-uuid-117385df-2092-4777-9a97-3ebd052d7581/snapraid.content'
msg:progress: Searching disk sde1_disk4...
msg:verbose: Excluding content '/srv/dev-disk-by-uuid-cdac1b82-2335-45cd-b7f6-7b6852429514/snapraid.content'
msg:progress: Selecting...
msg:verbose:     sdb1_disk1//
memory:used:182539191
memory:block:17
memory:extent:88
memory:file:192
memory:link:88
memory:dir:80
msg:progress: Using 174 MiB of memory for the file-system.
msg:progress: Initializing...
msg:progress: Selecting...
msg:progress: Fixing...
msg:error: Reading data from missing file '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/695' at offset 0.
error:0:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/695: Read error at position 0
msg:error: Missing file '/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/Music&amp;Sound/Bøger/Jane Austen/Emma.epub'.
error:0:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Emma.epub: Open error at position 0
entry:0:block:known:bad:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/695:0:
entry:1:block:known:bad:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Emma.epub:0:
strategy_error:0: No strategy to recover from 2 failures with 1 parity with hash
recover_sync:0:2: Failed with no attempts
recover_unsync:0:2: Skipped for nothing unsynced
unrecoverable:0:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/695: Unrecoverable error at position 0
unrecoverable:0:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Emma.epub: Unrecoverable error at position 0
status:unrecoverable:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/695
msg:error: Reading data from missing file '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/635' at offset 0.
error:1:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/635: Read error at position 0
error:1:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Emma.epub: Open error at position 1
entry:0:block:known:bad:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/635:0:
entry:1:block:known:bad:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Emma.epub:1:
strategy_error:1: No strategy to recover from 2 failures with 1 parity with hash
recover_sync:1:2: Failed with no attempts
recover_unsync:1:2: Skipped for nothing unsynced
unrecoverable:1:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/635: Unrecoverable error at position 0
unrecoverable:1:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Emma.epub: Unrecoverable error at position 1
status:unrecoverable:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/635
msg:error: Reading data from missing file '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/513' at offset 0.
error:2:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/513: Read error at position 0
msg:error: Missing file '/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/Music&amp;Sound/Bøger/Jane Austen/Mansfield Park.epub'.
error:2:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Mansfield Park.epub: Open error at position 0
entry:0:block:known:bad:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/513:0:
entry:1:block:known:bad:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Mansfield Park.epub:0:
strategy_error:2: No strategy to recover from 2 failures with 1 parity with hash
recover_sync:2:2: Failed with no attempts
recover_unsync:2:2: Skipped for nothing unsynced
unrecoverable:2:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/513: Unrecoverable error at position 0
unrecoverable:2:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Mansfield Park.epub: Unrecoverable error at position 0
status:unrecoverable:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/513
msg:error: Reading data from missing file '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/879' at offset 0.
error:3:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/879: Read error at position 0
error:3:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Mansfield Park.epub: Open error at position 1
entry:0:block:known:bad:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/879:0:
entry:1:block:known:bad:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Mansfield Park.epub:1:
strategy_error:3: No strategy to recover from 2 failures with 1 parity with hash
recover_sync:3:2: Failed with no attempts
recover_unsync:3:2: Skipped for nothing unsynced
unrecoverable:3:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/879: Unrecoverable error at position 0
unrecoverable:3:sdc1_disk2:Music&amp;Sound/Bøger/Jane Austen/Mansfield Park.epub: Unrecoverable error at position 1
status:unrecoverable:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/879
msg:error: Reading data from missing file '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/58' at offset 0.
error:4:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/58: Read error at position 0
msg:error: Missing file '/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/Music&amp;Sound/Musik/Itunes/Disturbed - Asylum (Deluxe Version)/controllers/credits.js'.
error:4:sdc1_disk2:Music&amp;Sound/Musik/Itunes/Disturbed - Asylum (Deluxe Version)/controllers/credits.js: Open error at position 0
entry:0:block:known:bad:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/58:0:
entry:1:block:known:bad:sdc1_disk2:Music&amp;Sound/Musik/Itunes/Disturbed - Asylum (Deluxe Version)/controllers/credits.js:0:
strategy_error:4: No strategy to recover from 2 failures with 1 parity with hash
recover_sync:4:2: Failed with no attempts
recover_unsync:4:2: Skipped for nothing unsynced
unrecoverable:4:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/58: Unrecoverable error at position 0
unrecoverable:4:sdc1_disk2:Music&amp;Sound/Musik/Itunes/Disturbed - Asylum (Deluxe Version)/controllers/credits.js: Unrecoverable error at position 0
status:unrecoverable:sdb1_disk1:homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/58
msg:error: Reading data from missing file '/srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/homedir/Malcolm/Borgbackup/Backup-Bo-OMV_NOVA/data/0/215' at offset 0.

Alles anzeigen

boelle · 21. März 2023

strategy_error:0: No strategy to recover from 2 failures with 1 parity with hash

but https://www.snapraid.it/faq#howmanypar says 1 parity drive covers 2-4 data disk

so with 2 down should i not be able to recover those?

chente · 21. März 2023

Zitat von boelle

strategy_error:0: No strategy to recover from 2 failures with 1 parity with hash
but https://www.snapraid.it/faq#howmanypar says 1 parity drive covers 2-4 data disk
so with 2 down should i not be able to recover those?

I think you have misunderstood.

1 parity disk can recover from 1 disk failure

2 parity disks can recover from the failure of 2 disks

.

For data sets from 2 to 4 disks -> 1 parity disk may be enough

For parity sets of more than 4 disks you should have at least two parity disks.

According to the image that you have published in post 12 your assembly has 4 data disks and 1 parity disk. Therefore you can only recover from a disk failure. If you want recovery from two drive failure you need to add another parity drive.

Jetzt mitmachen!