Jump to content
Sign in to follow this  
1812

DYNAMIX UNASSIGNED DEVICES ATE MY ARRAY!

7 posts in this topic Last Reply

Recommended Posts

Posted (edited)

Ok, not really, but it did cause a reboot after making shares unaccessible. I was unable to download diagnostics, every time I'd click the download button this text would flash on the screen and then just return to the same page with no download initiated:

 

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

 

Additionally, green "array started" text at the bottom would flash back and forth between that an "array undefined"

 

1484974957_ScreenShot2019-06-10at7_44_13AM.png.5d82b148372d568254f857d8835c699a.png

 

and sure enough, it was. Unassigned devices went "nom-nom" on them.

 

578524691_ScreenShot2019-06-10at7_49_09AM.thumb.png.dfe61556ad317d7590589b264c622aac.png

 

 

 

 

fix common problems then popped up and said rootfs was full, but I wouldn't know why. nothing had changed really on the server.

 

1126307150_ScreenShot2019-06-10at7_43_20AM.png.278c2f69f93bba121c1b1344dccf46d2.png

 

 

I was able to get a quick look at the last bit of my syslog which showed numerous of these entries

 

Jun 10 04:03:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:04:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:05:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:06:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:07:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:08:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:09:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:10:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:11:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jun 10 04:12:01 B1 crond[1817]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null

 

 

I subsequently uninstalled the UD plugin and rebooted (unRaid 6.7.0) and reinstalled UD.

 

Just an FYI

 

 

 

Edited by 1812

Share this post


Link to post

This has happened to me also. Rebooted and installed the newest rc release over the 6.7.0 installed, All good so far. 

But it was the exact errors 1812 submitted. Couldn't download diagnostics, array would go to green, orange and log gave me the same errors. 

Share this post


Link to post

same here - was during an rsync clone to a remote smb mounted connection. I think that the connection dropped but Unassigned devices still accepted the data (maybe caching in ram until it was full?)

 

Edited by spants

Share this post


Link to post

I had this issue some time ago.  I bypassed the problem by writing a script that checks for the existence of a file on the unassigned disk path before allowing the copy to take place. Not the most elegant solution, but it works.

Share this post


Link to post
9 hours ago, MisterWolfe said:

I had this issue some time ago.  I bypassed the problem by writing a script that checks for the existence of a file on the unassigned disk path before allowing the copy to take place. Not the most elegant solution, but it works.

UD has been updated to solve this issue.

Share this post


Link to post

Before doing any writing to a UD mounted device you should check that it is mounted first.  You can do this in several ways.

MOUNTPOINT=/mnt/disks/DailyBackup

if [ -d $MOUNTPOINT ]; then
... do stuff
fi

or better

MOUNTPOINT=/mnt/disks/DailyBackup

if mountpoint -q $MOUNTPOINT; then
... do stuff
fi

 

Edited by dlandon

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this