woke up to very odd array status

Can0n · September 29, 2019

this morning after having had to force reboot due to stuck unassigned devices plugin, it was 40% through a parity check when i came across a ton of off lines in the main tab in the gui and this when i logged in via ssh

Starting diagnostics collection...

Warning: file_put_contents(): Only 0 of 5 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 80

Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 12 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 588 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in /var/local/emhttp/disks.ini on line 240

in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 342 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 1781 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 4020 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 2844 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 11 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in /var/local/emhttp/disks.ini on line 240

in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 90

Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 93

Warning: implode(): Invalid arguments passed in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 100

Warning: file_put_contents(): Only 0 of 74 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 100

Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 118

Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120

echo: write error: No space left on device

Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: file_put_contents(): Only 0 of 25 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: file_put_contents(): Only 0 of 42 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: file_put_contents(): Only 0 of 35 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: file_put_contents(): Only 0 of 50 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: file_put_contents(): Only 0 of 27 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: file_put_contents(): Only 0 of 40 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 158

Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in /var/local/emhttp/disks.ini on line 240

in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 178

Warning: array_merge_recursive(): Argument #1 is not an array in /usr/local/emhttp/plugins/dynamix/include/CustomMerge.php on line 17

Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 185

Warning: file_put_contents(): Only 0 of 846 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 208

done.

ZIP file '/boot/logs/tower-diagnostics-20190929-0926.zip' created.

the USB should not even be close to full as I have a 32GB in there and just the other day it was at not even close to 50%

I tried to stop the array but it says mover is running and a mover stop command is saying mover is not runniing..

still trying to reboot this gracefully and recover the diagnostics as i post this but might have to force shut down to get those diagnostics

Squid · September 29, 2019

Hard to say. I would guess that the flash drive is mounted read-only, but would need diagnostics to confirm.

TQ · September 29, 2019

Hard to say. I would guess that the flash drive is mounted read-only, but would need diagnostics to confirm.

Something definitely read-only.
Unraid (and many Linux OS) protects itself by doing this

Sent from my iPhone using Tapatalk

Can0n · September 29, 2019

heres the diagnostics, the only thing that was running were a few dockers one of which was Duplicati and compressing and backup up over unassigned devices to another server here are the diagnosticstower-diagnostics-20190929-0926.zip, defintely wiers as they came up as tower and i changed the name three years ago

here is a video of the Webgui too

Can0n · September 29, 2019

just double checked my duplicati settings and it was set to use RAM (/tmp) for temp files

I was backing up well over 2TB and have 32GB ram i presume this crashed unraid and the array in general safe to say?

Squid · September 29, 2019

That would do it

Can0n · September 29, 2019

yeah changed the mapped "temp folder" in duplicati to a place on the array where there is 13TB free that should help a lot trying to take my 67TB server to compress and backup loacally to another server that currently has 32TB hoping to cut the file sizes in half but can always increase the backup server size with larger drives added

mgutt · April 21, 2020

I do not have a good start with Unraid. My first try ended maybe because of a defective usb stick or because I used the USB 3.0 port. Now I started again from the scratch. New stick, USB 2.0 port, moved license.. everything is new. And again I killed Unraid ^^

What I did:

I started a wget command to fetch my files from the old server as follows:

wget --background --quiet --recursive --level 0 --no-host-directories --cut-dirs=2 --no-verbose --timestamping --backups=0 --user=<ftp_username> --password=<ftp_password> "ftp://10.1.2.3/video/Filme/GH/" --directory-prefix=/mnt/user/Movies

As the performance was bad I killed the wget process through the terminal and "pkill wget". Then I searched for an alternative method and I found the smbclient command. My first try ended in an error message (did not found directory), but this one worked:

smbclient //10.1.2.3/video <smb_password> -U <smb_user> -c 'prompt ON; recurse ON; cd \Filme\KL\; lcd /mnt/user/Movies/KL/;mget *'

The speed on the source NAS was good so I reloaded the Unraid Webclient and bamm.. everything was messed up:

Quote

Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in state/disks.ini on line 588 in /usr/local/emhttp/plugins/dynamix/include/ShareList.php on line 18

Warning: array_keys() expects parameter 1 to be array, bool given in /usr/local/emhttp/plugins/dynamix/include/ShareList.php on line 64

Warning: array_diff(): Expected parameter 1 to be an array, null given in /usr/local/emhttp/plugins/dynamix/include/ShareList.php on line 64

Warning: array_filter() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/dynamix/include/ShareList.php on line 64

And on the main tab:

Quote

Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in state/disks.ini on line 588 in /usr/local/emhttp/plugins/dynamix/include/DeviceList.php on line 20

So I checked the network monitor of Google Chrome and found this URL to the API:

http://10.1.2.3/webGui/include/DeviceList.php

I reloaded it multiple times without passing parameters and randomly it returned the above syntax error. Of course I stopped the smbclient process, too. This time by pressing CTRL+C in the terminal.

So I checked through the terminal what could be happend and I found it out fast. My smbclient process wrote the file directly onto the stick instead of the target disk ^^ (file has a size of 16G = size of the stick)

1033936530_2020-04-2200_06_40.png.aff1f572d5b67be302e8d2f8ff5ad5f3.png

Of course Unraid was not able to write any more config data to the stick and this caused the error. I deleted the file and after that the errors are gone:

1024508385_2020-04-2200_08_51.png.4a71f705d10122de8efe53c2c4dc48ff.png

I'm not sure if my first smbclient command was wrong or the second. And I need to find out why "prompt ON" and "lcd" did not work. But this should not be part of this topic. This is only for you as feedback what could be the reason for such errors

Maybe Unraid should reserve a partition on the stick to avoid such user produced errors?!

woke up to very odd array status

Recommended Posts

Can0n

Link to comment

Squid

Link to comment

TQ

Link to comment

Can0n

Link to comment

Can0n

Link to comment

Squid

Link to comment

Can0n

Link to comment

mgutt

Link to comment

Join the conversation