Pjhal

So i used the bios setting that Squid linked too. But i just got this: ''ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen'' see short remote log: All_2022-2-14-20 11 1.html full Unraid logs: silverstone-diagnostics-20220214-2013_anon.zip The system hasn't crashed (yet) but i am a bit concerned that might do so soon. edit: this seems like the same issue to me: 6.9.0/6.9.1 - KERNEL PANIC DUE TO NETFILTER (NF_NAT_SETUP_INFO) - DOCKER STATIC IP (MACVLAN) At least the same one i am seeing in the logs right now, not sure if it is the same as the original issue i have. I have now deactivate my second physical Ethernet. How do i need to change my setup to fix the above? I am using at least 7 different ip adress on dockers, sometimes more. Using the mcvlan feature. (custom br0) And several using the default bridge.

Thx for your response, I will try the bios options. I should note though that it was never an issue until recently and i have had this server running Unraid sinds 2019. Also the post suggests updating the BIOS but i cannot update the the bios on this system. I updated to a P version this was a issues fix/beta bios because of issues with the ipmi kvm and apparently you cannot upgrade from that version. And the motherboard has been end of life for a while now. The memory part of that post also doesn't apply to me, seeing as it passed such a long memtest. My hardware btw: ASRockRack X470D4U American Megatrends Inc., Version P3.30 BIOS dated: Monday, 2019-11-04 CPU: AMD Ryzen 7 3700X 8-Core @ 3600 MHz my ram is 2 sticks of 16GB ECC udimm and from the supported list of the motherboard.

My system froze/hanged several times requiring a forced shutdown. (completely unresponsive to everything (no web-ui, no ssh, no smb shares) but clearly still powered on). I did ping the system but i think that also got me nothing,(not 100% sure its been a few days). The full local logs are lost but the quote above is a part from the log as capture by my log server on a synology. (i tried to format it, hope its readable). This to me seemed like it might be the issue i wanted to include the full logs a s captured over the network by a synology nas. But i think the external version of the log file is too big at 50 MB. Upload fails I did fix the cache file system (XFS) several time because of the dirty shutdowns, i used this guide by Spaceinvader One on Youtube. And did a parity check on the array. Now the external log made it look like it might have been a memory issue to a layman like myself so i ran a memtest. I ran the built in memtest on my 2*16GB ECC udims. It ran for well over a 150 hours, partly because i didn't have the time or energy to keep troubleshooting and ''fixing'' the system so i just left it to its own devices. I forgot to take a picture of the screen but trust me it was a lot of passes with zero errors! On a side note somewhere in the mids of all of this i replaced 2 * 8TB (WD white label chucked) disc 1 data and 1 parity with 2 18Tb discs (WD white label chucked). And sinds then the s.m.ar.t part of the webGUI stopt working, the disc do pas the checks but it doesn't display the data in the Gui properly. I did find a post on the forum about this but none of the fixes worked for me. ( changing the Default SMART controller type, etc i tried all of them) All new discs pass have recently passed short and extended smart at least 2 times, plus the preclear script has been used using the binhex-preclear docker image. Edit: i have added a cut down version (removed older entries) of the externally captured log file: All_2022-2-12-21 28 6 - Copy.csv Logs of the system as it is ''now''": silverstone-diagnostics-20220212-2021_anon.zip

After disabling spin down on all disks and restarting the server it has now been running for 1d and 3 hours without any errors, so i am assuming it is fixed.

Shutdown server, re plugged HBA and all Disks. Then started it up again. After some time new errors The weird thing that stands out to me is that the errors occur after the 2 disk happen to spin down. Could that be related? Also if it is a hardware defect....I don't have a spare HBA, proper size power supply or SAS cable to do any testing (by swapping them out ) so i am at a loss as to how i should handle this right now. Is there anything i can do? silverstone-diagnostics-20210522-1828.zip

Well the errors are back again now on Disk 6 and 7. silverstone-diagnostics-20210522-0008.zip

As far as i can tell, everything seems to be normal and working again. thx again

Thank you for your responses btw! How should i handle the 22 errors that 6 Disks are reporting?

But this issue happened after downgrading from 6.92 back to 6.83 nothing else changed. I also read that some people had compatibility issues with the newer version. I use a: https://www.broadcom.com/products/storage/host-bus-adapters/sas-9300-8i What can i do to fix this? I understand that it is hypothetically possible that my power supply failed or that it is a cable failure but it seems incredibly unlikely to me that this happens at the exact time that that i run into OS issues due to updating and downgrading my OS version. Edit: oke i disconnected and reconnected the HBA and my array is back so maybe it was a badly plugged in connect?

Yes they are, but the Disks them selves are fine according to SMART. This happened after upgrading to 6.9.2 and then downgrading again to 6.8.3. So i am hoping that it is just some limited file inconsistency. And not a mayor failure of hard drives or the whole array.

Oke it got worse i finished the Parity check with no errors and then tried to start the array normally now i have 6 unmountable Disks. That is every Data Disk except Disk 5... Edit: i included new diagnostics silverstone-diagnostics-20210520-2253.zip

Thank you for your response. I have rebooted, Unraid then reported zero errors. Then i started the array in maintenance mode, now doing a Parity check (read only). After that ill try starting the array normally.

As the title says. Screen shot shows the discs, diagnostics logs included. Also: Wen using crusader i cannot access disk 3. /mnt/disk 3 is somehow a file of zero bytes and not a folder silverstone-diagnostics-20210518-2122.zip I put Unraid in maintenance mode and ran a short smart test on Disk 3 it completed with no errors. Disk 3 XFS check with -n ********************************************************************************************************** Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_fdblocks 456165658, counted 458312794 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 6 - agno = 4 - agno = 7 - agno = 5 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. ********************************************************************************************************** Edit: i added the SMART diagnostics of all 5 disks with errors after running short SMART on all of them. Disk numbers appended( Disk 1 etc). Disk 3 is also running the extensive SMART check atm. WDC_WD80EMAZ-00W_7HKJT7EJ_35000cca257f1e771-20210518-2240 - Disk 3.txt WDC_WD80EMAZ-00W_7HKJWUXJ_35000cca257f1f4f1-20210518-2244 - Disk 4.txt WDC_WD80EZAZ-11T_2SG8U7JJ_35000cca27dc401ba-20210518-2245 Disk 7.txt WDC_WD80EZAZ-11T_2SG9465F_35000cca27dc4271a-20210518-2244 Disk 6.txt WDC_WD80EZAZ-11T_7HJJ6AVF_35000cca257e38cc8-20210518-2243 Disk 1.txt What should i do ? How bad is this?

After recently upgrading to the latest version (6.9.2 ) my server crashed(not immediately, but alter a a time i wasn't using it so don't know exactly wen) i lost the logs so i setup my synology nas to recieve logs from my unraid server in the future. Now only days later the unraid server didn't fully crash, my dockers containers are still running! But unraid cannot be accessed at all. Neither through the webui or WinSCP. Included are the unraid logs as captured by my synology NAS hence the unusual format. All_2021-5-14-23 15 38.html Edit: oops i just noticed the typo in the title, it should be a server error. Edit2: ultimately i did gain access through WinSCP and used shutdown now. Edit3: I couldn't figure out how to fix it and got no responded on this thread so i am simply going to roll back to an older version. Hopefully what ever this is will get fixed.

What I like most, about Unraid is the community. I would love to see a built in file browser.