dhomas

Thanks for looking into it! I updated from the unraid update utility. After some time (I think it might have been upgrading the internal DB?), it came up and started working again. It connected up to my other Syncthing agent in version 1.30. Now I just have to figure out how to compile version 2.0.2 myself for my other NAS (a Drobo 5N2).

So, I stopped the container and tried starting it via 'docker run' which didn't fail at startup, but seemed to hang. I may have not started it correctly, though. I ended up rolling back to Syncthing v1.3.0 and everything is back to normal. I think the binhex container will need to be tweaked to work with version 2.0.0, though.

So, Syncthing proposed an update to version 2.0.0 today. I've previously updated from older versions to newer from within the web interface, but this time it didn't come back up. I see this in the logs: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2025-08-12 09:34:47,319 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23158311906064 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stdout)> 2025-08-12 09:34:47,319 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23158312503344 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stderr)> 2025-08-12 09:34:47,319 WARN exited: start-script (exit status 80; not expected) 2025-08-12 09:34:47,319 DEBG received SIGCHLD indicating a child quit 2025-08-12 09:34:50,323 INFO spawned: 'start-script' with pid 86 2025-08-12 09:34:50,340 DEBG 'start-script' stderr output: syncthing: error: unknown flag -c, did you mean one of "-h", "-C", "-D", "-H"? 2025-08-12 09:34:50,341 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23158312310160 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stdout)> 2025-08-12 09:34:50,341 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23158312312608 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stderr)> 2025-08-12 09:34:50,341 WARN exited: start-script (exit status 80; not expected) 2025-08-12 09:34:50,341 DEBG received SIGCHLD indicating a child quit 2025-08-12 09:34:51,342 INFO gave up: start-script entered FATAL state, too many start retries too quickly ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I would try to change the startup script but I don't know where to do it. Anyone else having this issue and/or know how to fix it?

Running a repair in Windows seems to have fixed it. Triggered another parity check, though, on restart. Thanks for your help!

I'll try that after my parity check completes. I just found it odd that I only started getting the error after upgrading. Thanks for the tip! I'll report back after doing the repair to confirm the solution.

Hello all! I just updated to unraid 6.12.12 and upon reboot, I received this error message via email: "Event: USB flash drive failure Subject: Alert [UNDOM] - USB drive is not read-write Description: DataTraveler_2.0 (sda) Importance: alert" I tried to reboot again and the error message reappeared. This second reboot also triggered a parity check, not sure why. I've seen some other posts about this error message, but it seems suspect to me that the error message only appeared after updating. I've checked and this is the very first time I received this message. When I check syslog, I can see the following error message repeating every minute: Aug 21 15:49:39 unDOM flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 15:50:00 unDOM kernel: FAT-fs (sda1): error, corrupted directory (invalid entries) I've also included diagnostics, if it can be helpful. What do I need to do to avoid a crash? Thanks for any help! undom-diagnostics-20240821-1552.zip

Did anyone ever figure this out? I still don't have full driver support on my Asus Prime Z790M-Plus motherboard.

I've got 2 sticks of 48GB. I'll plan some downtime (this is my "production" Plex server) to test the sticks individually. Right now, I've been up for 1 day 16 hours and parity check has completed (after the unclean shutdowns). Thanks again for your support!

I really thought it was bad RAM, too. But I tested it for over 13 hours and 8 passes. Could a bad USB flash drive cause something like this? It shouldn't, I think, since unraid is loaded to RAM on boot from my understanding. But I think I've had a crash before when I bumped the USB boot drive, so I'm not sure.

I started up again and so far no errors after about 2 hours. SHFS crashed within about 1h20m last time. I hope it will complete the parity check this time around (only 22 hours to go! ). I noticed another segfault at startup for a process that I'm unfamiliar with (and for which searching didn't provide much of use): Apr 10 06:23:29 unDOM kernel: update-mime-dat[1575]: segfault at 150000 ip 00001517c54af159 sp 00007ffc1f731778 error 4 in libc-2.37.so[1517c536c000+169000] likely on CPU 12 (core 24, socket 0) Apr 10 06:23:29 unDOM kernel: Code: 77 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 37 01 00 00 <c5> fd 74 0f c5 fd d7 c1 85 c0 74 5b f3 0f bc c0 c5 f8 77 c3 0f 1f In any case, I'll keep monitoring. When it works, unraid is so very powerful. Coming from a Drobo that only just barely served files (their "DroboApps" were laughable), it's been a blast to use. I just really need it to be stable. Thanks for your help!

Here is the syslog leading up to the crash (syslog.log) as well as the syslog created upon startup to recover the files (syslog-new.log). Thanks for any help! syslog.log syslog-new.log

Syslog is already enabled, but I could not retrieve it as the filesystem was no longer accessible and SCP was not working. I will turn it on again and retrieve the syslog and post it here.

Hello there! I am still relatively new to unraid, having build my machine and installed it about December 2023. In my time using unraid, it has been quite unstable and I don't know why. I tried many things to stabilize it, but it's only gotten worse. Here is a timeline of events: Install on 6.2.18 around December 2018 Imported about 60TB from old NAS Started installing some containers in parallel Some containers may have been setup incorrectly as the system became unstable after installing them; uninstalled all containers System was stable-ish Upgraded to 6.2.19 Every so often (maybe once a week), the system would lock up: WebUI unavailble, no response from keyboard presses, no activity on attached monitor, single-press power button did not trigger shutdown Tried to update BIOS, which resulted in my RAM no longer being correctly recognized by my motherboard (issue raised to Asus) Downgraded BIOS; tested RAM extensively (8 passes on MemTest86+, see attached) Installed Immich Upgraded to 6.2.20 Now extremely unstable; cannot even stay up long enough to complete parity check The WebUI remains accessible, but all shares disappear. I can shut down via the WebUI. This is also the case if I start in safe mode Diagnostics are attached. Thanks for any help! This is driving me bonkers! undom-diagnostics-20240410-0833.zip

Thanks for the reply! I only now noticed it.

Hello there! I had a question about giving my spare license away. In a fit of FOMO, I bought an unraid license just before the pricing model change. The license has yet to be used or associated to a USB key. I talk about unraid to all my friends (even though I'm a pretty recent convert myself) and just convinced another friend to take the plunge. I would like to "gift" him the spare license I bought a few days ago so he, like me, can benefit from the unlimited lifetime upgrades. I saw this thread that touches on the topic: However, this appears to be to transfer a "used" license to someone else. Mine has not been used yet, so I thought my case warranted its own thread. I can see on the invoice that the license is attributed to my name and email address. Can I send the unactivated license key to my friend for him to use? Or will he need to activate it using my name and email address? Thank you for any advice! Cheers! Dhomas