February 3, 20188 yr This has been happening for the past 4 days, and I've only just now captured the diagnostic data to upload, hence the topic. Four days ago when I was adding or removing the pihole docker from community apps I got the "Transport endpoint is not connected" error. All my user shares disappeared making most of my docker containers useless. After some time, the whole unRAID server freezes including command line with the keyboard. Nothing is displayed on the monitor before it freezes. Sometime between 9:10am and 9:38am in the diagnostic data I'm attaching all my user shares just disappeared, disk shares are still accessible. I also got a screencap of the WebUI for good measure. Unfortunately, I couldn't capture the syslog after the system froze. EDIT: I forgot to mention that when the problem first occurred I was actually on 4.2.0-rc8q. I had been running it happily for a month or more without a problem. When the problem occurred I thought I'd update the BIOS and OS for good measure. Unfortunately, neither of those things helped. There were no errors or anything at all reported on the console on the monitor it's hooked up to. EDIT 2: I've also run a full Memtest86 test over 8 hours on my 32GB of DDR4 and have zero errors with my RAM. Ruling that out as the potential problem. Another curious thing I noticed was that the user0 folder was still working. See attached screenshots. Diagnostic Data: mcnugen-unraid-diagnostics-20180203-0952.zip Edited February 12, 20188 yr by MarkusMcNugen Remove info that was useless
February 3, 20188 yr Unrelated, but uninstall Advanced Buttons plugin. When you go to use it under 6.4.1, you're going to lose all of your docker containers
February 3, 20188 yr Author 9 hours ago, Squid said: Unrelated, but uninstall Advanced Buttons plugin. When you go to use it under 6.4.1, you're going to lose all of your docker containers I only ever used it to stop all containers on the dashboard menu. It worked just fine for that, but Ive removed it anyways Edited February 4, 20188 yr by MarkusMcNugen
February 5, 20188 yr Author UPDATE: Had another crash occur, this time I had started without UEFI mode and finally had some output at the CLI, however, there was only one output displayed which doesn't seem particularly useful to me, perhaps not an unRAID dev. Edited February 5, 20188 yr by MarkusMcNugen
February 5, 20188 yr Author 9 minutes ago, johnnie.black said: Are you using the Ryzen workaround and have C-States disable in the bios? I did not. I apparently glossed over that when going through the BIOS options. I had applied the "zenstates --c6-disable" workaround from 4.2.0-rcq18 but that doesnt appear to have been working at all according to the logs. I'll see if this solves the problem now that I have "Global C-state Control" disabled in the BIOS.
February 5, 20188 yr Your go script needs to specify the full path to "zenstates", currently it is not being run at boot. See
February 5, 20188 yr Author 39 minutes ago, ljm42 said: Your go script needs to specify the full path to "zenstates", currently it is not being run at boot. 1 Ah... I should have realized that after looking at the emhttp line. I just copied the zenstates line verbatim from rc18f where I first remembered seeing it. Edited February 5, 20188 yr by MarkusMcNugen
February 5, 20188 yr Hey @Squid, I think it would be good for FCP to highlight this problem (zenstates in go script without full path). The instructions were fixed in the 6.4.0 thread a few days ago: but I didn't realize they have been wrong since 6.4.0-rc18f, that's a full month of incorrect information being published Taking it a step further, it would be nice if FCP could detect a Ryzen CPU and recommend zenstates, for the folks who didn't read release the notes I don't have Ryzen though, so I'm not sure how to detect it.
February 5, 20188 yr 1 hour ago, ljm42 said: Hey @Squid, I think it would be good for FCP to highlight this problem (zenstates in go script without full path). The instructions were fixed in the 6.4.0 thread a few days ago: but I didn't realize they have been wrong since 6.4.0-rc18f, that's a full month of incorrect information being published Taking it a step further, it would be nice if FCP could detect a Ryzen CPU and recommend zenstates, for the folks who didn't read release the notes I don't have Ryzen though, so I'm not sure how to detect it. PM me. I'm not at my computer for about a week, and I'll forget about it if not via a PM
Archived
This topic is now archived and is closed to further replies.