PROBLEM ..."Q.parity is smaller than the expected 3155724861440"
A backup program for disk arrays
Brought to you by:
amadvance
Menu
▾
▴
Newbie here. Thank you for this great program Andrea!
I am using the elucidate GUI. Snapraid returns the above warning and I believe therefore I am not protected from 2 drive failures. I enclose my snapraid config file and the relevent snippet of the warning.
Configuration for snapraid via Elucidate
Defines the file to use as Parity storage
It must NOT be in a data disk
parity Z:\SnapRAID.parity
Defines the file to use as Q-Parity storage
If specified, it enables a double failures protection like RAID6
It must NOT be in a data disk
q-parity H:\SnapRAID.Q.parity
Defines the file to use as content list
You can use multiple specification to store more copies of the file
It's suggested to have at least N+1 copies of the file, where N is the number of parity files.
It can be in a data disk
It can be in the disks used for parity storage
content N:\SnapRAID.content
content Q:\SnapRAID.content
content U:\SnapRAID.content
content E:\SnapRAID.content
content V:\SnapRAID.content
content G:\SnapRAID.content
content F:\SnapRAID.content
content W:\SnapRAID.content
content J:\SnapRAID.content
content K:\SnapRAID.content
content X:\SnapRAID.content
content Y:\SnapRAID.content
content L:\SnapRAID.content
content Z:\SnapRAID.content
content H:\SnapRAID.content
Defines the data disks to use
The order is relevant for parity, do not change it
disk d0 N:\
disk d1 Q:\
disk d2 U:\
disk d3 E:\
disk d4 V:\
disk d5 G:\
disk d6 F:\
disk d7 W:\
disk d8 J:\
disk d9 K:\
disk d10 X:\
disk d11 Y:\
disk d12 L:\
Excludes hidden files and directories (uncomment to enable).
nohidden
Defines files and directories to exclude
Remember that all the paths are relative at the mount points
Format: "exclude FILE"
Format: "exclude DIR\"
Format: "exclude \PATH\FILE"
Format: "exclude \PATH\DIR\"
exclude *.unrecoverable
exclude Thumbs.db
exclude \$RECYCLE.BIN
exclude \System Volume Information
exclude \Program Files\
exclude \Program Files (x86)\
exclude \Windows\
Defines the block size in kibi bytes (1024 bytes).
Default value is 256 -> 256 kibi bytes -> 262144 bytes
block_size 256
Automatically save the state when synching after the specied amount of GiB processed.
This option is useful to avoid to restart from scratch long 'sync'
commands interrupted by a machine crash.
The SIZE argument is specified in gibi bytes -> 1073741824 bytes
Default value is 0, meaning disabled.
Format: "autosave SIZE_IN_GiB"
autosave 250
AND
2015-01-28 19:17:31.7575[6] INFO Elucidate.Elucidate: StdOut[Saving state to H:/SnapRAID.content...]
2015-01-28 19:17:31.7575[8] WARN Elucidate.Elucidate: Verbose[DANGER! The 2-Parity file H:/SnapRAID.Q.parity is smaller than the expected 3155724861440.]
2015-01-28 19:17:31.7575[6] INFO Elucidate.Elucidate: StdOut[ 407119 files]
2015-01-28 19:17:31.7575[8] WARN Elucidate.Elucidate: Verbose[If this happens because you are using an old content file,]
2015-01-28 19:17:31.7575[6] INFO Elucidate.Elucidate: StdOut[ 0 hardlinks]
2015-01-28 19:17:31.7575[8] WARN Elucidate.Elucidate: Verbose[you can 'sync' anyway using 'snapraid --force-full sync']
2015-01-28 19:17:31.7575[6] INFO Elucidate.Elucidate: StdOut[ 0 symlinks]
2015-01-28 19:17:31.7575[8] WARN Elucidate.Elucidate: Verbose[to force a full rebuild of the parity.]
Both the parity drives are 4TB (same as largest in the pool)
Any thoughts?
Last edit: thegrandwazoo 2015-01-30
Hi thegrandwazoo,
Does the Q.parity file is smaller than the parity one ? The expected size of both is of exactly of 3155724861440 bytes.
It seems that something bad happened at Q.parity, and it's smaller than expected.
At this point recreating the parity seems the best option. You can use:
Note that it will take a lot of time. But during the process you will be still protected, as the existing content and parity files will be used as starting point.
Ciao,
Andrea
Well that was easy! Seems to rebuilding now. Thank you...I'll update on progress.