gandalf15

Ok so without XMP the first parity check corrected antoher 150ish errors. Another one after that showed 0 errors. it is stable now and runs very well. Thank you for the support!

This is exactly what I did. With XMP 2 / 1 I got FAILED. I deactived it and the test PASSED. I guess the new mainboard and ram dont like each other with XMP. Since it passed I did a parity check again - once it finishes I will rerun one and see if there are still errors. Maybe this was the reason for the crashes. Edit: A full Parity check takes 2.5 days - I will report back once done!

It runs stable now - but the parity sincy reported 166 errors. Could be sync it crashed a few times I thought. But new parity sync started jsut after the first reports again 15 Errors. I never had an error before. I guess something is still not right. Anyone some tips what to do?

Thank you I will try So far no errors in the log - but I dont know if it runs stable. Also I saw that the boot log said to check the flash drive (boot drive) for errors. Did a ckdsk on it and it corrected / restored like 5 files. I will report back if it still crashes and or freezes

It is enabled - anything I can do to check? Now it runs, all docker up but the Docker page wont load... it is like nothing in patricular but everything isnt working good Edit: Feb 20 18:32:37 Igor kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:07:00.0 Feb 20 18:32:37 Igor kernel: atlantic 0000:07:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Feb 20 18:32:37 Igor kernel: atlantic 0000:07:00.0: device [1d6a:07b1] error status/mask=00000001/0000a000 My log is spammed with that. I think atlantic is my 10gbit nic from asus. I added the section of this threat:

Dear Unraid Users This weekend I updated my Mainboard, CPU, NVME and RAM. After the update I had some problems with my HBA, which did first not see the drives. I had to disable fast booting, after that the box booted up and all was fine. 2 Hours later the server got instantly out - puff. I checked all wires and everything, unplugged everything and plugged it in again. After that it was working. Now after severall hours the webui got unresponsive. I ssh'd into the server and all looked fine. So I rebooted the box - and this night again the same. I attacked the diagnostics - since I changed a lot of hardware - I have no idea where to beginn. Every help is appreciated - Thank you! igor-diagnostics-20240220-0535.zip

Well, I run that node for over 3 years already with a cache drive - and it beginns to pay now The Idea of a separate ZFS array though would make sense. I might keep that in mind for the futur.

Thank you very much for those informations. I guess I will just let it run then. Obviously, there is some "idle time" - but storj node runs 24/4 and is writting to the disks. Media center is up and someone of the family might watch. Backups from other boxes run at night already and so on. There isnt really a "from midnight to 6 am" idle window. So it might be smarter to just let it run and let it take a month to sync - and after that make a check every 6 months or so.

basicly there is 24/7 use. I guess it will just run beside the operation. Or is there any harm if the drives spinn for that long?

Thank you - so basicly parity is nothing for me (a normal 20 TB drive will take like 2 days I think I read). I cant stop everything for 2 days all the time.

So the slowdown is due to that? As I said - I cant stop the server for a parity sync / check. So from your response I read, that this is normal due to the acess of the server?

Hi fellow "unraiders" Since my data was not important in the past I did not use a Parity drive. That changed now - basicly since I had a drive "left over" and set it as parity. This is the stat on parity sync after almost 2 days: As you can see, its really slow. Some informations: There are lots of tiny files (only a few kb, but also a big files (100+ GB). Its in total a 284 TB array. The drive is a Exo 20TB (X20 model ST20000NM007D) for parity. All drives are eighter 16TB or 20TB drives. The parity was precleared at an average speed arround 200 MB/s. I cant stop the array for a parity since (and cant in the futur for parity check). There is data being written during the sync (not often though). currently it read at 350-450 MB/s on all drives - and writes with 12-19 MB/s. The drives ( in Total 15) are all in a server hot swappable case with SAS2 connections on a HBA. I use an expander to get to all drives. The case uses a backplane. I read that it shouldnt take that long - but is it possible that it is so slow since I have A LOT of tiny files? More precise I run a storj node that uses arround 15TB of all data. I also attached the diagnostics Thank you for every help (even though you tell me this is normal).

Backblaze has a new client available (v.9) with the possiblity to restore without zip files. Would love to see an update of the backblaze personal container to support that! I hope this is the right channel to ask for that - was directed here by the help page on the docker!

Thank you!

@JorgeB Could you please make JoeUnraidUser's post the solution. Seems better than mine (although I dont know if it works since I used the way I posted). Thank you!