Jump to content
roboko

Help unRAID 6.6.7 - VM crashing

5 posts in this topic Last Reply

Recommended Posts

Hi, could you make me some hint, what's wrong? My VM based on Debian linux still crashing daily. No need to publish it, it could be issue with my config or hardware, but I am not sure what to repair. Thanks a lot. R.

nas-diagnostics-20190226-1847.zip

Share this post


Link to post

Looking at syslog, trouble begins here:

Feb 25 23:00:04 nas bunker: Verify task for disk4 started, total files size 1.10 TB
Feb 25 23:00:04 nas sSMTP[1796]: Creating SSL connection to host
Feb 25 23:00:04 nas sSMTP[1796]: SSL connection using ECDHE-RSA-AES256-GCM-SHA384
Feb 25 23:00:05 nas sSMTP[1796]: Sent mail for email@removed.com (221 2.0.0 Bye) uid=0 username=xxx outbytes=659
Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby  -A /dev/sdm
Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby  -A /dev/sdq
Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby  -A /dev/sdf
Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby  -A /dev/sds
Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby  -A /dev/sdn
Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby  -A /dev/sdt

Not sure what that "Resource temporarily unavailable" means - probably an out-of-memory condition.  What is that 'Verify task for disk4 started' referring to?  Maybe that is consuming all available RAM?

Share this post


Link to post

I just upgraded to 6.6.7, and now getting VM crashing or failing to start with the following error.

 

 internal error: process exited while connecting to monitor: sh: fork: retry: Resource temporarily unavailable qemu: pthread_create: Resource temporarily unavailable

Share this post


Link to post

Unfortunately still having this issue. I am trying to isolate error, but till now without success. After reboot some time cca 1 hour with issue, but then some strange lines in dmesg appears:

...

Mar 5 21:40:52 nas kernel: br1: port 1(eth1) entered blocking state
Mar 5 21:40:52 nas kernel: br1: port 1(eth1) entered forwarding state

... 

may be it is not connect with the issue, but in 6.6.1 there was nothing like that in dmesg 😞

Share this post


Link to post
On 2/28/2019 at 5:16 PM, limetech said:

What is that 'Verify task for disk4 started' referring to?

It looks like the Dynamix File Integrity plugin running a scheduled checksum check.

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.