Iain Hodge

I'm going to close this thread down for now. My plan is to spend the next few days copying my data back to my venerable old Drobo for safety. Then I will update the bios with one I've found in the depths of the CWWK website. Then I will run Memtest86+ for a few days to see if I get any errors. Then I will boot into a Linux distro so I can run Prime95 for a while. If that all runs clean, then I will get a new flash drive and start a new install and try again. Otherwise I will have to RMA the CPU and hope that I get a good one in return... Thanks for your help so far. Regards, Iain.

Ok - I've done that - recovered the licence key and rebooted but I'm still seeing squashfs errors in the logs. As well as other errors. Is my CPU fried? and if so can I simply get a RMA and drop in the replacement - will this cpu still be plagued by errors when I can't find a later bios than the one installed? I'm really stuck here - its been pottering on for 8 months and only now when I've started to populate it do I have all these errors. All help appreciated. Regards, Iain. sol-diagnostics-20260117-1706.zip

I can’t find a later bios from CWWK than the one that I’m running now ☹️ Ok - I’m running MemTest at the moment - all seems well. For my own sanity, can someone please check that my proposed next steps are corrent. Power down and pull the flash disk out Put the flash into my Mac and copy the config folder off of it. Use the USB Creator tool to flash with the latest UnRaid release. Put the flash disk back into my machine and power up. Watch the see you soon syslog for errors and pray the gods that it’s clean. Regards, Iain.

I’ll try that in the morning - and run another memtest to see if that’s an issue. Cheers. Iain

Ok - how do I do a new install without screwing up my current data drives - I have copied all my config off of the flash drive. BTW - safe mode seems to still have all the squashfs errors

OK - new flash drive worked. Re-copied existing config. Booted and I'm getting this... Jan 16 22:03:43 Sol kernel: mdcmd (36): check correct Jan 16 22:03:43 Sol kernel: md: recovery thread: check P Q ... Jan 16 22:03:45 Sol unassigned.devices: Mounting 'Auto Mount' Remote Shares... Jan 16 22:03:45 Sol emhttpd: Unraid Management Agent started on port 8043 with log level info Jan 16 22:03:45 Sol unassigned.devices: Using Gateway '192.168.1.1' for Remote Shares. Jan 16 22:03:45 Sol unassigned.devices: Waiting 5 secs before mounting Remote Shares... Jan 16 22:03:45 Sol sudo: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/bash -c '#012 INTERVAL_SYSTEM=5 INTERVAL_ARRAY=10 INTERVAL_DISK=30 INTERVAL_DOCKER=10 INTERVAL_VM=10 INTERVAL_UPS=10 INTERVAL_GPU=60 INTERVAL_SHARES=60 INTERVAL_NETWORK=60 INTERVAL_HARDWARE=600 INTERVAL_ZFS=300 INTERVAL_NOTIFICATION=30 INTERVAL_REGISTRATION=600 INTERVAL_UNASSIGNED=60 /usr/local/emhttp/plugins/unraid-management-agent/unraid-management-agent --logs-dir /var/log --port 8043 --log-level info boot#012' Jan 16 22:03:45 Sol sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jan 16 22:03:51 Sol kernel: php-fpm[9257]: segfault at 3 ip 00000000008d8e1f sp 00007fff818c3c50 error 6 in php-fpm[4d8e1f,600000+3fb000] likely on CPU 8 (core 16, socket 0) Jan 16 22:03:51 Sol kernel: Code: 01 00 00 8b 46 14 45 85 f6 41 89 44 24 28 75 c3 48 8b 56 08 8b 46 10 48 8b 9d 98 fe ff ff 48 89 53 08 89 43 10 f6 c4 ff 74 03 <83> 02 01 48 8b 85 98 fe ff ff c6 00 01 48 81 c4 98 01 00 00 5b 41 Jan 16 22:03:51 Sol nginx: 2026/01/16 22:03:51 [error] 7957#7957: *193 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.43, server: , request: "POST /plugins/unassigned.devices/include/UnassignedDevices.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "sol.local", referrer: "https://sol.local/Main" Jan 16 22:03:51 Sol php-fpm[6903]: [WARNING] [pool www] child 9257 exited on signal 11 (SIGSEGV) after 112.695171 seconds from start Help??? I'm lost as to where to start debugging this. Regards, Iain. sol-diagnostics-20260116-1936.zip

Yes and no - I ran MemTest several times as I seemed to have a kernel failing error - but the last run overnight gave no errors in 9 passes. No I haven't got a flash backup - have I corrupted it?

Hello guys. I've been having a number of errors with my system and it seems to be very sad for itself. I've attached the diagnostics - could someone point me in the direction of a starting point in my hunt for my errors. Regards, Iain. sol-diagnostics-20260116-2014.zip

OK - I think it was a RAM seating error - I shutdown and ran MemTest86+ on the system. After 2 passed I had 6 errors coming up so I shutdown and removed on stick of RAM. MemTest86+ then ran overnight with NO errors in 13 passes. I then swapped the sticks of RAM and reran the meatiest. Again. no errors across multiple passes. So I put both sticks back in and tried again - this time 13 passes of memtest showed no errors. I fired up UnRaid again and seemed to get no matching errors so I think I can resolve this one. I have lots of other errors which I'd better raise different threads for. Thanks for your help Iain.

Ok. Firstly, where do you see that the driver crashed - so I can learn to spot problems myself - the diagnostic data is a little overwhelming… Secondly, do I need to do the memtest and bios update outside of the unraid environment? I’m still learning about the hardware side of things - despite having been a desktop programmer for 30 years… Thanks, Iain.

My NAS seems to be suffering an issue. The parity check after a reboot gets stuck at a few percent and tells me is has a thousand days to finish. No other problems that I can see. Regards Iain . sol-diagnostics-20260114-1216.zip