kernelpaniced

Thanks Jorge! I'll keep an eye on it and see what happens.

I ran an extended SMART test and it returned with no error. Warning: ATA error count 38528 inconsistent with error log pointer 2 ATA Error Count: 38528 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 38528 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 08 11:47:40.284 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 11:47:40.284 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 11:47:40.284 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 a0 08 11:47:40.284 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 11:47:40.283 IDENTIFY DEVICE Error 38527 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 11:47:40.284 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 a0 08 11:47:40.284 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 11:47:40.283 IDENTIFY DEVICE c8 00 08 b0 d0 05 ef 08 11:47:40.272 READ DMA ef 10 02 00 00 00 a0 08 11:47:40.271 SET FEATURES [Enable SATA feature] Error 38526 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 08 11:47:40.284 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 11:47:40.283 IDENTIFY DEVICE c8 00 08 b0 d0 05 ef 08 11:47:40.272 READ DMA ef 10 02 00 00 00 a0 08 11:47:40.271 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 11:47:40.270 IDENTIFY DEVICE Error 38525 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 08 b0 d0 05 ef Device Fault; Error: ABRT 8 sectors at LBA = 0x0f05d0b0 = 252039344 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 b0 d0 05 ef 08 11:47:40.272 READ DMA ef 10 02 00 00 00 a0 08 11:47:40.271 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 11:47:40.270 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 11:47:40.270 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 a0 08 11:47:40.270 SET FEATURES [Enable SATA feature] Error 38524 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 08 11:47:40.271 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 11:47:40.270 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 11:47:40.270 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 a0 08 11:47:40.270 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 11:47:40.269 IDENTIFY DEVICE

Hi Jorge, Thank you for the reply. I have included the diagnostic archive below. kms2-diagnostics-20251028-1542.zip

Hi, I have a disk that is giving the error below. I tried switching the SATA cable and due to the way the motherboard is layed out I had to connect the SATA cable to a different port on the motherboard. I restarted and I'm still getting this error. I checked SMART data and there doesn't appear to be anything flagged in there. I did not replace the SATA power. Would that be the next step? Oct 28 10:05:18 server kernel: I/O error, dev sdc, sector 3911194184 op 0x0:(READ) flags 0x0 phys_seg 168 prio class 0 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194120 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194128 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194136 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194144 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194152 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194160 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194168 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194176 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194184 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194192 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194200 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194208 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194216 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194224 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194232 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194240 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194248 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194256 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194264 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194272 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194280 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194288 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194296 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194304 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194312 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194320 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194328 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194336 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194344 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194352 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194360 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194368 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194376 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194384 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194392 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194400 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194408 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194416 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194424 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194432 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194440 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194448 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194456 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194464 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194472 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194480 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194488 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194496 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194504 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194512 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194520 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194528 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194536 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194544 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194552 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194560 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194568 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194576 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194584 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194592 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194600 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194608 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194616 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194624 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194632 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194640 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194648 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194656 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194664 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194672 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194680 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194688 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194696 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194704 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194712 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194720 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194728 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194736 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194744 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194752 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194760 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194768 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194776 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194784 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194792 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194800 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194808 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194816 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194824 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194832 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194840 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194848 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194856 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194864 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194872 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194880 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194888 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194896 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194904 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194912 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194920 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194928 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194936 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194944 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194952 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194960 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194968 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194976 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194984 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194992 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195000 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195008 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195016 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195024 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195032 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195040 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195048 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195056 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195064 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195072 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195080 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195088 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195096 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195104 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195112 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195120 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195128 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195136 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195144 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195152 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195160 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195168 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195176 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195184 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195192 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195200 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195208 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195216 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195224 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195232 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195240 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195248 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195256 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195264 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195272 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195280 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195288 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195296 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195304 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195312 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195320 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195328 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195336 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195344 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195352 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195360 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195368 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195376 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195384 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195392 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195400 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195408 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195416 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195424 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195432 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195440 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195448 Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195456

Alright thank you! I have one other question if you don't mind. When I reformatted the disk that had the bad cable unraid never prompted me for a parity rebuild. What steps would I have had to take to have parity rebuilt? I want to avoid data loss in the future if I end up in a situation like this again.

Hey JorgeB, replaced the SATA & power cable. I just started a parity check and speeds are looking correct now. Should I wait until the check is complete before I can confirm this issue is fixed? I have the write corrections to disk during parity check off will this not fix parity errors?

Hi all, My system has a fault some where. Been having an issue the last few days and I am not sure what to do. This is a secondary NAS. Context: In June one of my drives was throwing a lot of errors. I replaced that drive and everything seems to be running fine. Three or four days ago parity check started and I noticed that the hardware was making a beep and the HD light on the front was blinking at the same time. The parity sync was also showing an incredible long completion time. After a few restarts after some attempts to boot in safe mode and disable docker / vms the new drive showed as unreadable and unraid offered the format option. When I did this parity build was not offered so I believe this data is now lost. After a few days of fiddling with it I am not sure where to go so hoping somebody can help. I have included some screenshots, a video, and the diagnostics log. When I run a parity check my unraid box starts making a beep every 5 to 7 seconds, I do not think this is a motherboard beep as it's short and quiet. The parity check. The check is extremely slow. I looked at history and saw there were errors. I had automatic parity error correction on until last month. Finally after a few restarts upon one boot a drive was marked as unreadable and required formatting. When I formatted there was no parity rebuild option so I'm assuming that data is now gone forever. Is this a normal thing? Did I do this procedure wrong? kms2-diagnostics-20250706-0735.zip

Just wanted to share a quick summary of an issue I had and how it was resolved, in case it helps someone else down the line. My Unraid WebUI became unresponsive, and when I SSH’d into the box, I noticed /mnt/usr/ was empty. After some great troubleshooting help from JorgeB, we found the cache drive was faulty—it was throwing errors and preventing the array from mounting properly. Replacing the cache drive fixed everything. Hope this helps anyone facing a similar problem.

Gotcha can do. Right now I am using nohup and rsync to copy the from /mnt/cache to a new share I setup with array only. Then once I install the new drive I can just copy them back to /mnt/cache pool correct?

Yes after that error I disabled docker again and, it has been over 24 hours and everything is still running. So it looks like the cache drive and or the docker image could be the issue? How can I trouble shoot this? I have only one nvme slot on the board I would have to replace the entire drive if switching the drive is recommended.

syslog.txt Yes sorry here is the booted version. One note. I removed a few plugins that I had hoped were causing the issue. Doesn't look like it fixed it. So, I booted to safe mode and it seemed to be ok there. So I booted back to normal, disabled docker via settings, then started array and it seemed ok. I then started docker and it was ok but updated some containers and now it's unresponsive. This syslog is from the unresponsiveness.

Hey Jorge, Thank you for the response sorry for the delay. I have the sys log here in this post. syslog.txt

Hi, I am on Unraid 7.1. I have an Intel skylake i7, 32 GB of ram, 6 HDs with 2 of them acting as parity drives. My Unraid box’s web UI is unresponsive after starting and entering my encryption phrase. I have tried reimagining the flash drive from a backup, but that did not help. The issue seems to occur almost immediately after the race starts and parody check has begun. If I boot and let unread come up, the box will sit there and I can navigate the unread – no problem. The issue seems to only occur after the array starts. I can SSH in but the documentation I have found from Google seems to he depreciated which is frustrating probably my fault for not finding the right link but old commands were on Unraid wiki that Google returned. I can not access any SMB share. My docker container appear to be running but syncthing doesn’t appear to be able to sync any data. I do not use cloud services for data syncing and rely heavily on this box with sync thing to sync my data. I have spent 2 weeks trying different things on and off so as a last ditch effort posted here for help. Hopefully somebody has seen this it’s been very frustrating being without my data automatically syncing for 2 weeks.

Thanks for the reply! I may end up switching to OPNsense eventually. I left Unifi because I wanted to simply my router management some and have extra software packages. Maybe pfsense isn't it and OPNsense is! My unraid is assigned a static IP so I assigned the port forward to that. I have successfully done the same for Syncthing and Plex. I am able to connect to my Plex and Syncthing services VIA my public IP while connected to my LAN. The rule was set to TCP / UDP I have now changed it to just UDP. I did another test and was still unable to connect via WAN address. The docker container's network type is bridge is that ok?

Hi all, TLDR: Can't access container VIA WAN ip but can access via LAN ip. Did test outside of network to see about NAT reflection issue. Is issue pfsense or docker? Issue: I have another port forwarding issue. Sorry. I have Palworld on a container. I can access VIA my LAN ip so 10.0.0.1:8211 for example. However my WAN isn't accessible. I have tested from both inside my network and outside of it. Network Setup: I have a pfsense firewall. I do have port forwarding working for my plex server for example. When I forward TCP / UDP for 8211 to my docker container it doesn't seem to reach though. I did assume it was a NAT reflection issue but again I tested outside of the network as well on another machine and still could not connect. Question: Should I map another port or is this some sort of pfsense firewall NAT forwarding issue?

If you have a lot of plugins installed then try to boot into safe mode and see if your system is more stable. I had issues with a plugin causing my server to lock up and found it by doing this.

I used many solutions for a NAS before Unraid. Started with freenas then moved onto Windows 10 Storage Spaces (ew) finally I landed with Unraid thanks to Linus Tech Tips. I love the VM management, docker containers, and interface to manage the server. This month will mark a full year for me and I plan to stay with Unraid and recommend it anytime some person I know wants to build their own NAS. Thanks Unraid and the Unraid community for all the work!

Hello all! After a little digging and checking to confirm flash drive was not the issue I went ahead and rolled back to 6.6.5 and it appears to have fixed the problem. Figured this might be the easiest test and it seems to have fixed the problem. Not too sure what caused the issue in 6.6.6 does not seem to be an issue for anybody else so probably is my setup. Sorry about not posting screenshot / attaching diag will do next time. I have included them in this post.

Here is the diagnostic ZIP. https://drive.google.com/open?id=1MmEfjnv3mpSzCKEdebKpHJgDOg7AYzoD

Hi, As the title says whenever I stop or start the array (have not tested with shutdown / restarting machine) my unraid starts a parity check. Currently I do have the scheduler turned on and it is set to run every 3 months. The last check was completed with no errors. I am running unraid 6.6.6 not sure how to start diagnosing this.