Hi guys new to unraid 6.8.3 which I've set up on a Ryzen 2400G (10 dockers and 1 VM). It's been working fine for the last 2 weeks, however, this morning I was unable to access the webgui with the following error:

Warning: session_write_close(): write failed: No space left on device (28) in /usr/local/emhttp/login.php on line 33

Warning: session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php) in /usr/local/emhttp/login.php on line 33

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/emhttp/login.php:33) in /usr/local/emhttp/login.php on line 35

 

I came across another forum post advising to run win 10 chkdsk on my usb (cruzer 2.0) and it appeared to correct errors on the drive. Up and running again the system has started an automatic parity check. But after a few minutes various Warning: errors started to appear in the dashboard and main page all containing the following lines:

Quote

/usr/local/emhttp/plugins/dynamix/include/Dashupdate.php or DeviceList.php

I'm unable to run diagnostics in Tools (click and nothing happens). Can't access system stats either.

RAM usage is higher than normal at 75% - usually between 40-50%

Fix common problems is advising that: rootfs file is getting full (currently 100% used) and invalid folder cache/disk 1,etc within /mnt

Help please!

 

 

 

Edited May 21, 20206 yr by unraid20

Check your USB stick and change the port. Sounds like strange issues that happen due to disconnected stick.

 

You might also want to attach diagnostics (Tools -> Diagnostics -> attach whole zip file).

I've already plugged the USB stick into a different port. Is there any other way to check the USB?

I'm not able to download diagnostics from Tools (it just pauses). Neither can I shutdown from the webgui (I'm using hard reset - power button 5s). The buttons on the webgui are generally unresponsive.

Edited May 15, 20206 yr by unraid20

29 minutes ago, unraid20 said:

I've already plugged the USB stick into a different port. Is there any other way to check the USB?

I'm not able to download diagnostics from Tools (it just pauses). Neither can I shutdown from the webgui (I'm using hard reset - power button 5s). The buttons on the webgui are generally unresponsive.

Unfortunately no other ways. You can try getting an internal USB 2.0 to external USB 2.0 cable off Amazon / ebay and see if it helps.

I've searched for the cable but came across these instead

 

1) https://www.amazon.co.uk/StarTech-com-USBMBADAPT-Female-Motherboard-Header-Black/dp/B000IV6S9S/ref=sr_1_14?dchild=1&keywords=internal+USB+2.0+to+external+USB+2.0&qid=1589546446&sr=8-14

2) https://www.amazon.co.uk/STARTECH-COM-USBMBADAPT2-Motherboard-Header-Adapter/dp/B002GNU2V6/ref=psdc_430451031_t1_B000IV6S9S

 

Can't seem to find the cable you mentioned. If you have a link I would be grateful.

Also, I take it you're certain this is a port issue and I don't need to run any further diagnostics (SSH)?

Edited May 15, 20206 yr by unraid20

4 minutes ago, unraid20 said:

I've searched for the cable but came across this instead https://www.amazon.co.uk/StarTech-com-USBMBADAPT-Female-Motherboard-Header-Black/dp/B000IV6S9S/ref=sr_1_14?dchild=1&keywords=internal+USB+2.0+to+external+USB+2.0&qid=1589546446&sr=8-14

 

Can't seem to find the one you mentioned. If you have a link I would be grateful.

Also, I take it you're certain this is a port issue and I don't need to run any further diagnostics (SSH)?

That header thingie is exactly what I meant.

I'm leaning towards the stick being the issue and was hoping that running it at USB 2.0 speed (i.e. through that header thingie) would help with any corruption / disconnection issue.

 

From the command line (or SSH), type diagnostics and see if it creates the diagnostics zip.

The hanging when you do it through the interface could very well be because the stick has dropped offline / corrupted so it can't save the diagnostic zip.

Sorry I had edited my post above. What do you make of the second adapter? I've got a 10-1 pin usb 2.0 motherboard connector but I think either should work okay?

 

Other thing to note is I was using the unrar commmand (terminal) on some password protected rar files which was producing an error ("ioctl" related). Would this have caused the crash?? Because I've rebooted the system and it's been stable now whilst during parity check.

 

EDIT: issue resolved. unrar within terminal doesn't appear stable. used winrar from windows VM instead.

 

Edited May 21, 20206 yr by unraid20