Hello,

My parity check log seems to have become corrupted when restored my boot drive from a backup. It now shows one check from today and one completed from 1.1.1970:

1970 Jan  1 01:00:00|-1487685544|nan B/s|0|

I do have a backup of the old parity-check.log but it seems to get overwritten when I try to replace the corrupt one with the working one. Is there a trick to make the restored backup stick?

The file is /boot/config/parity-checks.log and it looks something like this:

Quote

2016 Nov 16 00:45:16|32637|153.2 MB/s|0|0

2016 Nov 19 13:12:51|36916|135.5 MB/s|0|0

2016 Dec  1 15:14:13|36852|135.7 MB/s|0|0

2016 Dec  8 02:34:31|37072|134.9 MB/s|0|0

2017 Feb  1 15:10:57|36656|136.4 MB/s|0|0

2017 Feb  4 23:16:02|36777|136.0 MB/s|0|0

2017 Feb 18 09:30:28|36899|135.5 MB/s|0|0

 

Yes thanks, I should have phrased my post differently.

I've edited/replaced /boot/config/parity-checks.log with the good backup but it gets overwritten or appended with the faulty entry periodically (or whenever I reboot)

I can see how bad entries might get added to the end but I don't understand how the file itself could be overwritten. Perhaps you have some corruption on your boot device. It would be worth shutting down, removing it and checking it on a PC. It might be worth getting a fresh download of the unRAID installer zip and replacing the three bz* files in the root of your boot device in case they've become damaged somehow.

1 hour ago, lionceau said:

Yes thanks, I should have phrased my post differently.

I've edited/replaced /boot/config/parity-checks.log with the good backup but it gets overwritten or appended with the faulty entry periodically (or whenever I reboot)

The GUI checks if the last recorded parity-check is present in the history file. If not it will be appended (not overwritten).

 

Thanks for the input. I'm currently running a parity check so I can't try anything but I'll check tomorrow.