OMV 6.9.4-2. Fully updated.
My original OMV 6.x OS disk got corrupted and of course I didn't have a backup. I installed the latest OMV on a new USB stick and reconfigured everything (mergerfs, snapraid, shares, etc). Nothing fancy.
All disks are present and apparently with the original data. My seperate backup disk is also untouched so I have a backup of all the files.
The 6 Data disks (Content and Data checked) have been readded as has been the 1 Parity disk (Parity checked). I have checked and double-checked the disks to make sure data is actually data and parity is parity and that the backup disk is not being referenced by mergerfs or snapraid.
I'm going to begin with snapraid status:
Why is loading state being done from one of my Data disks and not the Parity disk? Does this have to do with the Data disk holding the actual information? (Content & Data)
0 on D5 and D6?
Sync in progress 99% and Scrub 99% has been this way ever since I got the OMV and the plugins set up again.
Almost all basic sync commands have returned erros and if I execute snapraid sync it tells me to run force-full and force-empty. Execution takes seconds and tells me to run the other command. Stuck in a loop.
I never erased the Parity disk after I reinstalled OMV on the new OS USB stick. Is snapraid reading old information and getting all mixed up?
Thanks in advance.
Self test...
Loading state from /srv/dev-disk-by-uuid-4e886be0-9d71-4368-b228-79e8cbe1ca57/snapraid.content...
WARNING! With 6 disks it's recommended to use two parity levels.
Using 534 MiB of memory for the file-system.
SnapRAID status report:
56%| o
| o
| o
| o
| o
| o o
| o o
28%| o o
| o o
| o o
| o o
| o o
| o o
| o o
0% |o__oo___o__o___o_____o
103 days ago of the last scrub/sync 81
The oldest block was scrubbed 103 days ago, the median 98, the newest 81.
WARNING! The array is NOT fully synced.
You have a sync in progress at 99%.
The 99% of the array is not scrubbed.
You have 1140 files with zero sub-second timestamp.
Run the 'touch' command to set it to a not zero value.
No rehash is in progress or needed.
No error detected.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OMV 6.9.4-2. Fully updated.
My original OMV 6.x OS disk got corrupted and of course I didn't have a backup. I installed the latest OMV on a new USB stick and reconfigured everything (mergerfs, snapraid, shares, etc). Nothing fancy.
All disks are present and apparently with the original data. My seperate backup disk is also untouched so I have a backup of all the files.
The 6 Data disks (Content and Data checked) have been readded as has been the 1 Parity disk (Parity checked). I have checked and double-checked the disks to make sure data is actually data and parity is parity and that the backup disk is not being referenced by mergerfs or snapraid.
I'm going to begin with snapraid status:
Thanks in advance.
Self test...
Loading state from /srv/dev-disk-by-uuid-4e886be0-9d71-4368-b228-79e8cbe1ca57/snapraid.content...
WARNING! With 6 disks it's recommended to use two parity levels.
Using 534 MiB of memory for the file-system.
SnapRAID status report:
Files Fragmented Excess Wasted Used Free Use Name
Files Fragments GB GB GB
217225 1817 6079 - 808 1158 42% D1
82384 10 34 - 355 627 37% D2
176783 2145 6456 - 789 1177 41% D3
211736 2571 6446 - 791 1176 41% D4
0 0 0 - 0 - - D5
0 0 0 - 0 - - D6
688128 6543 19015 0.0 2744 4140 40%
56%| o
| o
| o
| o
| o
| o o
| o o
28%| o o
| o o
| o o
| o o
| o o
| o o
| o o
0% |o__oo___o__o___o_____o
103 days ago of the last scrub/sync 81
The oldest block was scrubbed 103 days ago, the median 98, the newest 81.
WARNING! The array is NOT fully synced.
You have a sync in progress at 99%.
The 99% of the array is not scrubbed.
You have 1140 files with zero sub-second timestamp.
Run the 'touch' command to set it to a not zero value.
No rehash is in progress or needed.
No error detected.