eagle470

Yeah, I found that, it's very freaky when your shares drop out from under you at about 9PM. I was terrified I had lost everything. I haven't been able to afford a backup right now so I'm running on hopes and dreams at the moment.

Not sure what's going on right now, I'm hoping you can assist! Mya rray will start, but /mnt/user is not there. /mnt/user: Transport endpoint is not connected unraid1-diagnostics-20200509-2057.zip

Makes me wonder what I wouldn't gain from a motherboard upgrade. But I think I'll wait a while longer. No sense in unnecessarily spending a bunch of money in the middle of all this.

I will check, I am running an older motherboard though. I am still on the latest though. No new patches since September: https://www.asus.com/us/Motherboards/PRIME-X370-PRO/HelpDesk_BIOS/

Actually a user script to 'touch' a file every 29:59 minutes. I came across this as I was looking for an answer for my dad who is running a windows VM with BlueIris and 3 1TB laptop drives in a raid in storage spaces through Unassigned drives. I made a windows scheduled task to keep the drives from spinning down. I thought I'd share it here. You will be able to import that in Windows 7 or higher. Drive Keep Alive - File Touch.xml

While I understand that what I reported doesn't help anyone, I have no logs to provide. If I did, I would have given them to you. My machine locked up and became entirely non-responsive and the ONLY thing I could have done was taken a picture with my phone of the cash cart monitor. I didn't think about that until I had already reset the system the first time and the second time I was running in GUI mode, so all I would have taken a picture of was the frozen lock screen. I have logs being written off to the syslog server, but apparently the system locked up so fast no useful information was laid down as the last syslog roll up I had was from the day prior. I didn't have a secondary system up and running to capture logs, though that is something I can setup now. I'm not trying to be unhelpful, I'm just VERY limited on the information that I have to provide. If the kind of reporting that I CAN provide is annoying or undesired, I'll simply stop posting any results at all.

I ran into this issue as well. I originally thought it was BOINC causing the problem, but I had it happen after I ran a parity check and had turned off BOINC and F@H. So I ended up reverting back to 6.8.3 for now, looking forward to a more stable version in the future!

One thing I would really like to see is a CPU Scaler to limit the app from pegging the CPU.

I agree with Hoopster, mine was pegged out even though I had the usage level set to 70%. perhaps the load leveling doesn't work well, especially with other processes (Plex, SABnzbd, PiHole, etc.) Though the other BOINC container works fine and I'm able to manage the alternative choice from a different server using your the RDP-BOINC container..

Any thoughts on why BOINC would be crashing my server?

I'm not seeing any work units at this point on either of my systems for folding@home. BOINC causes my AMD Ryzen 9 system to crash per my last post in this thread.

I would like to see a reduced cost license that allows you to use the cache pool for Dockers and VM's, but you cannot use the array function.

Running an AMD Ryzen 9 3900X and I'm getting bad RPC calls that are crashing the server when running rpd-BOINC.

well....I don't know if that is checked...I will look at that when this check ends later today.

I've had a few unclean shutdowns in the past months, but none since my last parity check. Yet I have 7 corrections this check with an equal number last time. Does anyone have any advice? Just to be clear, I've attached SMART reports to be thorough, but I ran an extended test on all drives recently and everything came up roses. unraid1-diagnostics-20200210-1230.zip unraid1-smart-20200210-1300 (11).zip unraid1-smart-20200210-1300 (12).zip unraid1-smart-20200210-1300 (13).zip unraid1-smart-20200210-1300.zip unraid1-diagnostics-20200210-1230.zip unraid1-smart-20200210-1300 (1).zip unraid1-smart-20200210-1300 (2).zip unraid1-smart-20200210-1300 (3).zip unraid1-smart-20200210-1300 (4).zip unraid1-smart-20200210-1300 (5).zip unraid1-smart-20200210-1300 (6).zip unraid1-smart-20200210-1300 (7).zip unraid1-smart-20200210-1300 (8).zip unraid1-smart-20200210-1300 (9).zip unraid1-smart-20200210-1300 (10).zip