Good day everyone

 

I was hoping someone could help me out here. I have been trying to run a parity check for a few days now. The system has frozen up on me a few times, resulting in me having to do force shutdowns. I have tried following other posts to see if any issues from previous user issues apply to me, and at this point, I am throwing in the towel and asking for assistance. It is a fairly new build and install of Unraid, so I am sure something I did playing around is causing the issue. I just need to fix it, but I don't know how.

 

I am a newbie to anything Linux. I did play around with Linux waaayyyy back when I was 19 using Mandrake and SUSe and haven't touched it since. So, my knowledge is lackluster at best, and I will most likely need to be spoken to as someone with little experience and any last exposure was 25 years ago. Ugggh old age

 

System Specs:

CPU: Intel i7-1200K (new)
Ram: (4) 32 GB DDR5 G. Skill (new)

Mobo: ASRock z790 Riptide Wifi (new)

PSU: Corsair RM850x (new)

GPU: Asus GeForce RTX 3060 (used)

 

Parity:

Parity Drive: WD 16 TB (shucked from Easydrive (a few months old-maybe a year old)

 

Array:

Disk 1,2,3: Seagate 16 TB Exos (new)

 

Cache (POOL):

Drive 1: Samsung 1 TB 990 Pro (new)

Drive 2: WD 1 TB Black 770 (new)

 

Incoming File (POOL:

Drive 1: WD 1 TB Black 770 (new)

Drive 2: WD 1 TB Black 770 (new)

 

Things that have happened/I have done from installation to this point:

1. After the initial installation of Parity, Array, and Just one of the Cache drives. The system did its initial parity, and roughly two days later, parity was completed with no errors

 

2. Installed many applications and plugins to see what they offer. I have since uninstalled many of the applications and plugins thinking there may be some conflict or I set something up wrong that is causing an issue

 

3. I Started copying my TV shows files over the network from an external drive attached to my laptop over to the server using TeraCopy for file verification. I had a power glitch and had, I think, four files that failed verification. I recopied those files, and they were all copied over without issue.

 

4. Due to how long it was taking to copy files I searched for a quicker alternative to copy files. Learned about Unassigned Drives Application. Installed it, mounted drives, and finished copying over my TV shows using Krusader. I had an issue where I wasn't thinking and disconnected the external drive from the server, causing an obvious connection issue with the drives. I quickly reconnected and continued transferring files. No apparent issues were noticed (or that my old ass can remember)

 

5. Hurricane Milton was heading my way. I decided it was best to properly shut down the server before losing power. The system shut down with no issue. I was offline for two days while power and internet were restored.

 

6. Purchased and installed 3 WD Black 770 NVMe drives. Applied one to the cache pool for redundancy. For the other two drives, I decided to add to a separate pool for any incoming files from downloads, uploads, etc.

 

7. After drives were added, parity started, but I stopped it. I didn't want to wait two days for it to go through check then and was reading on how to increase parity checks speed or at a more opportune time. I came across and installed Parity Check Tuning. I left everything as default and started the parity check. I woke up the next morning to the server frozen with the parity check information I could see on the screen. I think it was 300 (something) days, at 200 (something) kb, and around 35 errors. Tried everything I could think of to try and reboot as safely as I could. I had to resort to a straight, hard power down.

 

8. I started the system and ran the parity check again—the same issue. The system had locked up with errors, and the parity check took a long time. I don't remember values because, at this time, I was a little frustrated. I started reading up on parity check errors, issues, resolutions, etc. After each of these steps, I ran a parity check until I noticed it was dropping from 200mb/s to 400kb/s and then stopped the parity check and forced reboots

     1. Decided to run a quick memtest (1 run, no errors),

     2. then, I decided something I installed was causing the issue, installed everything I had installed since the last parity check, and removed all files/folders. I thought something may have been writing to one of the disks and couldn't figure out what it could be, so I just wanted to get rid of everything

     3. Disabled all NFS/SMB shares and removed all other folders that were not system folders (read that SMB shares turned on could cause an issue) even though they were set, just not set on any computer to access the share. I was just trying to eliminate any possibilities. 

     5. I disabled the two drives in the Incoming array I had set as I felt it was the safest option to do so.

     6. I checked all drive power connections, reset them, and distributed the power to two legs coming off the power supply instead of one. Swapped a few SATA cables and ordered brand new ones that came in this morning.

 

9. I Ran another parity check and checked this morning to see this and finally decided to give up and post here:

 

I know it's a lengthy post, but I wanted to try and give as much information as I could remember so you all have a good round idea of how stupid I am lol 🤣 (it's OK, no safe spaces needed here, I grew up in the 80's/90's let's keep it real)

 

At this point, because I only have my TV shows moved over (I would "like" to save those if at all possible) but everything else can be wiped clean and start over if I can.

 

Or if anyone has any insights as to how to fix this. There is no way I can go 300-400 days waiting for a parity check, and I have about 48TB of data externally that I want to move over to the array so that I can reformat the 3 16TB Exos drives I have externally with data on them and add them to the array. 

 

Syslog and Diag attached

vader-diagnostics-20241017-0917.zip vader-syslog-20241017-1318.zip

Enable the syslog server, run a parity and post that after the crash.

I enabled syslog server and I am running parity now. 

 

Just to be clear I haven't had a crash so to speak in a few days where everything freezes up. However, today when I tried to stop the parity and shut down it took forever and had to force shutdown again. At what point would you like me to stop the parity check? Lately what I have been noticing is that it will go fine for a few hours at around 200mb with a 1 day 18 hours or whatever completion time and then at some point I decide to check to see how it is doing and the speeds are in the kb/s and completion time in the 300-400 days to complete. When I stopped it this time the parity time was at 623 days to complete.

 

The current parity check is looking like this right now which I can live with and seems normal

 

11 minutes ago, Kymbl said:

Just to be clear I haven't had a crash so to speak in a few days where everything freezes up.

Post the persistent syslog if it happens again.

On 10/17/2024 at 1:22 PM, JorgeB said:

Post the persistent syslog if it happens again.

Ok JorgeB. Parity check finished with 26 errors but was able to complete and stayed steady at 170-2015 MB/s. Attaching the syslog and diag. Wondering what the errors exactly mean and if it is anything I should be concerned about before moving over data from my external drives, installing apps etc.

vader-syslog-20241018-1832.zip vader-diagnostics-20241018-1432.zip

A few sync errors are expected after an unclean shutdown, just correct them, and you can then run another to confirm no more errors.

6 hours ago, JorgeB said:

A few sync errors are expected after an unclean shutdown, just correct them, and you can then run another to confirm no more errors.

Thank you sir. Beer money coming your way. SO far everything has looked good. Going to mark resolved

Glad to hear, and thanks!