The_N4RF

Has anyone had this issue with autodiscripper? It just cycles through startup with this error. Standard ripping (via the GUI) is working fine. [autodiscripper] ERROR: Cannot access state directory. Verify UMASK value. I've already confirmed both the default and autodiscripper directories are 777. Thanks!

Mmm yes, also curious about this. Just preparing to buy my first DL380 G8 myself, so no experience yet :(.

Update: I was still dealing with some crashing. Realized my trusty boot usb stick was failing. Deployed to a new stick and now my server has been running 48 days on the trot.

Yes, Windows automatically uppercases anything you put on the drive name. Good clarification.

Confirmed this also worked for my SanDisk FIT 16GB USB2 drive. Renaming to "unraid" through file explorer _while_ the tool is stuck at "syncing the filesystem" allowed the deployment to continue. Anecdotally this seems to relate to >8GB drives. All of my other drives worked fine, but this is the first >8GB drive I've deployed to.

Yes, but I can get those low capacity drives really cheaply :). Removing the USB drive from long-term use appears to be the solution. I'm using a SATA drive as an unassigned device now and the server appears to be back to 100%. Thank you!

Seems like a very likely scenario. The RAM test is proving successful, so I'm going to try to reconfigure the server to use a sata drive for the video streams and see if my uptime improves. Thanks for the help!

Mmhmm. Got it working by unplugging an external usb3 hdd before booting. I'm using all of my sata ports right now, so I had one unnassigned device plugged in via USB just for writing my security footage to. Didn't want to ruin my parity disk by having to keep up with a 24/7 stream of video data. Maybe that's a bad idea.

Thanks for the idea. I may still be stuck even there. I plugged a monitor into my tower and started it up. At the boot options I chose "memtest86+". The command line responded "/loading memtest... ok", then the machine just rebooted and brought me to the same boot options screen. A few attempts yielded the same results. Another hint is greatly appreciated. I'm still investigating.

Hi Everyone, Still dealing with a very frustrating issue. My unraid server (onprem) continues to become unresponsive after about 24 hrs of uptime. Both the webviewer and the CLI seem to enter a semi-crashed state. The server stops responding to shutdown commands (via web, console, terminal), so I have to hard-boot the server to get it to work again. Some of the initial symptoms include nonsense cpu load reports in the web viewer, and the "unnassigned devices" in the Main section never loads. Eventually the web viewer stops loading completely and I'm just greeted with this: Has anyone seen this? This is new behavior for me since 6.8. onprem-diagnostics-20200224-1309.zip

Yup, worked for 2 days with the VM running. All I did was stop the VM, then 8hrs later I find the unraid server effectively crashed. Nonsense CPU load reporting. WebGUI eventually stops responding. SSH connects, most commands seem to work but will not shutdown/restart. Next step? It seems to be isolated to the VM. What changes when I stop the VM?

Failed again (VM was stopped). Will try again and leave the VM running. -webgui showing several CPUs maxed, but htop is showing idle. -Unassigned Devices won't load. (should be a 2.5" USB harddrive here) These are the initial display errors. Eventually the page will not load at all anymore.

Ok, usb flash drive is moved to USB2 port and all of the data for appdata, system, and domains are hosted only on the Cache. Thanks for the help, we'll see how it goes! I did notice this week that if I left my Win10 VM running it seemed to be fine. But if I stopped or force-stopped the VM I would find the unraid server unusable soon after. This has only been tested twice though.

Thanks, I'll try to get those moved as well. I'll update after these changes.

Booting from USB2 thumbdrive installed in a USB3 port. Thanks for the tip, I will switch it on next reboot. Ok, diagnostics after starting array: onprem-diagnostics-20200122-1743.zip