antron12345

I upgraded yesterday from 6.6.6 to 6.6.7 and now all my docker containers are not showing IP addresses in the docker console and non of my containers are network stable. SAB will open after a while and display the interface. Hitting F5 once will cause the interface to go away with a messgae in the browser stating that the page cannot be reached. Hitting F5 again might / might not display the interface again and it cycles thought this. This happens on all containers.

Thank you for the reply

I looked on my flash drive and see that there are thousands of .notify files in the config\plugins\dynamix\notifications\archive example file is "Community_Applications_1462794002.notify" some of these files go back to 2015 is there a mechanism to have these files deleted every so often (ex: 30 / 60 / 90 / etc... days). If not can these files be safely removed from the USB flash drive by hand. Thank you

I moved the IMG file from the unassigned drive and placed it on the cache drive and Docker came up. I re-installed all the Docker Apps and am back in business. Thank you for the help

I have entered the path in by hand and the docker tab still doesn't show up. I take it the RW: is only available once docker is started and you can re-install all the containers. That is the part I still cannot do since docker isn't starting up.

Looking more at the system when I click on the docker icon in setting I see that my unassigned device is not available in the drop down for "Default appdata storage location:" My App data folder is on a BTRFS formatted drive (the same one the docker.img file is supposed to be on)

I am having the same issue with no docker tab showing up after upgrading from V6.1.9 to V6.2. I have tried to move the img file off the btrfs drive (sdu) I upped the space for the new image file from 40 to 60gig I started docker and restarted I have rebooted the system none of these have worked so far. I have attached the diag logs. can you please assist me with this issue. Thank you nasunraid-diagnostics-20160918-1636.zip

Looks like that was it. tried for about 2 hours to get it install and I was getting that error. I'm good to go now. Thanks for the help

I am getting the following error when trying to install the docker container. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Netdata" --net="host" -e TZ="America/Los_Angeles" -v "/mnt/disks/samsung/.docker/netdata":"/etc/netdata":rw -v "/proc":"/host/proc":ro -v "/sys":"/host/sys":ro --cap-add SYS_PTRACE --log-opt max-size=50m --log-opt max-file=1 titpetric/netdata Unable to find image 'titpetric/netdata:latest' locally Pulling repository titpetric/netdata Get https://index.docker.io/v1/repositories/titpetric/netdata/images: dial tcp: lookup index.docker.io: connection refused The command finished successfully! I am running unRAID 6.1.9 Thanks

I was thinkinthe same thing that a connector might not be connected properly. I will get another drive and see what I can do. when I get home and am able to physicaly look at the machine. I really appricate all the help as always everyone here is very helpful. Thank you

I putty'ed into the system and cat /var/log/syslog On the image I posted the first box on the right sees 6:14am. Also I have the notifications setup and I received an e-mail at:615am saying Event: unRAID Parity disk SMART failure Subject: Alert: Parity disk failed SMART health check Description: HGST_HMS5C4040ALE640_PL2331LAGUHAUJ (sdk) Importance: alert

When I try to run the smart report command I get the following smartctl -t short /dev/sdk smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. As for the syslog the last 100 line are all from 01/10/2015 nothing newer. And from the looks of things the drive was disabled at around 614 this morning. Jan 10 20:38:05 tower sshd[19919]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:05 tower sshd[19924]: Accepted password for root from 172.17.0.43 port 38620 ssh2 Jan 10 20:38:05 tower sshd[19925]: Accepted password for root from 172.17.0.43 port 38621 ssh2 Jan 10 20:38:05 tower sshd[19924]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:05 tower sshd[19925]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:10 tower emhttp: read_line: client closed the connection Jan 10 20:38:10 tower sshd[20080]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:10 tower sshd[20081]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:10 tower sshd[20086]: Accepted password for root from 172.17.0.43 port 38762 ssh2 Jan 10 20:38:10 tower sshd[20087]: Accepted password for root from 172.17.0.43 port 38763 ssh2 Jan 10 20:38:10 tower sshd[20086]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:10 tower sshd[20087]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:15 tower emhttp: read_line: client closed the connection Jan 10 20:38:15 tower sshd[20203]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:15 tower sshd[20204]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:15 tower sshd[20211]: Accepted password for root from 172.17.0.43 port 38807 ssh2 Jan 10 20:38:15 tower sshd[20210]: Accepted password for root from 172.17.0.43 port 38806 ssh2 Jan 10 20:38:15 tower sshd[20211]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:15 tower sshd[20210]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:20 tower emhttp: read_line: client closed the connection Jan 10 20:38:20 tower sshd[20332]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:20 tower sshd[20333]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:20 tower sshd[20338]: Accepted password for root from 172.17.0.43 port 38837 ssh2 Jan 10 20:38:20 tower sshd[20339]: Accepted password for root from 172.17.0.43 port 38840 ssh2 Jan 10 20:38:20 tower sshd[20338]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:20 tower sshd[20339]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:25 tower emhttp: read_line: client closed the connection Jan 10 20:38:25 tower sshd[20491]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:25 tower sshd[20490]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:25 tower sshd[20496]: Accepted password for root from 172.17.0.43 port 38872 ssh2 Jan 10 20:38:25 tower sshd[20497]: Accepted password for root from 172.17.0.43 port 38873 ssh2 Jan 10 20:38:25 tower sshd[20496]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:25 tower sshd[20497]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:30 tower emhttp: read_line: client closed the connection Jan 10 20:38:30 tower sshd[20597]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:30 tower sshd[20598]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:30 tower sshd[20603]: Accepted password for root from 172.17.0.43 port 38897 ssh2 Jan 10 20:38:30 tower sshd[20604]: Accepted password for root from 172.17.0.43 port 38898 ssh2 Jan 10 20:38:30 tower sshd[20603]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:30 tower sshd[20604]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:35 tower emhttp: read_line: client closed the connection Jan 10 20:38:35 tower sshd[20762]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:35 tower sshd[20763]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:35 tower sshd[20768]: Accepted password for root from 172.17.0.43 port 38924 ssh2 Jan 10 20:38:35 tower sshd[20769]: Accepted password for root from 172.17.0.43 port 38925 ssh2 Jan 10 20:38:35 tower sshd[20769]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:35 tower sshd[20768]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:40 tower emhttp: read_line: client closed the connection Jan 10 20:38:40 tower sshd[20871]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:40 tower sshd[20870]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:40 tower sshd[20876]: Accepted password for root from 172.17.0.43 port 38949 ssh2 Jan 10 20:38:40 tower sshd[20877]: Accepted password for root from 172.17.0.43 port 38952 ssh2 Jan 10 20:38:40 tower sshd[20876]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:40 tower sshd[20877]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:45 tower emhttp: read_line: client closed the connection Jan 10 20:38:45 tower sshd[21003]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:45 tower sshd[21004]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:45 tower sshd[21009]: Accepted password for root from 172.17.0.43 port 38962 ssh2 Jan 10 20:38:45 tower sshd[21010]: Accepted password for root from 172.17.0.43 port 38963 ssh2 Jan 10 20:38:45 tower sshd[21009]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:45 tower sshd[21010]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:50 tower emhttp: read_line: client closed the connection Jan 10 20:38:50 tower sshd[21144]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:50 tower sshd[21145]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:50 tower sshd[21150]: Accepted password for root from 172.17.0.43 port 39079 ssh2 Jan 10 20:38:50 tower sshd[21151]: Accepted password for root from 172.17.0.43 port 39080 ssh2 Jan 10 20:38:50 tower sshd[21150]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:50 tower sshd[21151]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:55 tower emhttp: read_line: client closed the connection Jan 10 20:38:55 tower sshd[21251]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:55 tower sshd[21252]: Did not receive identification string from 172.17.0.43 Jan 10 20:38:55 tower sshd[21260]: Accepted password for root from 172.17.0.43 port 39117 ssh2 Jan 10 20:38:55 tower sshd[21259]: Accepted password for root from 172.17.0.43 port 39116 ssh2 Jan 10 20:38:55 tower sshd[21260]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:38:55 tower sshd[21259]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:39:00 tower emhttp: read_line: client closed the connection Jan 10 20:39:00 tower sshd[21421]: Did not receive identification string from 172.17.0.43 Jan 10 20:39:00 tower sshd[21422]: Did not receive identification string from 172.17.0.43 Jan 10 20:39:00 tower sshd[21423]: Accepted password for root from 172.17.0.43 port 39141 ssh2 Jan 10 20:39:00 tower sshd[21428]: Accepted password for root from 172.17.0.43 port 39142 ssh2 Jan 10 20:39:00 tower sshd[21428]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:39:00 tower sshd[21423]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:39:05 tower emhttp: read_line: client closed the connection Jan 10 20:39:05 tower sshd[21593]: Did not receive identification string from 172.17.0.43 Jan 10 20:39:05 tower sshd[21594]: Did not receive identification string from 172.17.0.43 Jan 10 20:39:05 tower sshd[21597]: Accepted password for root from 172.17.0.43 port 39177 ssh2 Jan 10 20:39:05 tower sshd[21600]: Accepted password for root from 172.17.0.43 port 39178 ssh2 Jan 10 20:39:05 tower sshd[21597]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:39:05 tower sshd[21600]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:39:10 tower emhttp: read_line: client closed the connection Jan 10 20:39:10 tower sshd[21769]: Did not receive identification string from 172.17.0.43 Jan 10 20:39:10 tower sshd[21768]: Did not receive identification string from 172.17.0.43 Jan 10 20:39:10 tower sshd[21775]: Accepted password for root from 172.17.0.43 port 39336 ssh2 Jan 10 20:39:10 tower sshd[21770]: Accepted password for root from 172.17.0.43 port 39334 ssh2 Jan 10 20:39:10 tower sshd[21775]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:39:10 tower sshd[21770]: error: Received disconnect from 172.17.0.43: 10: Jan 10 20:39:15 tower sshd[21869]: Did not receive identification string from 172.17.0.43 Jan 10 20:39:15 tower sshd[21870]: Did not receive identification string from 172.17.0.43 Jan 10 20:39:15 tower sshd[21875]: Accepted password for root from 172.17.0.43 port 39385 ssh2

I stopped the array so I cannot get a smart report for the parity drive. I guess the question is do I need to get a new drive (this one is less than a month old) or do I enable it and I have no problem re-running a parity check.

Sorry I posted this in the unRAID V5 forum and it should have be in V6 I have recreated it in the connect forum.

Woke up this morning to find that my Parity drive has been disabled. I have attached a screen shot My system specs are as follows unRAID: V6 Model: N/A System: ASRock - 990FX Extreme9 CPU: AMD FX-8350 Eight-Core @ 4 GHz Cache: 384 kB, 8192 kB, 8192 kB Memory: 16384 MB (max. 32 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 3.17.4-unRAID x86_64 OpenSSL: 1.0.1j The only thing I have found on how I might be able to resolve this was in the link below http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily Any help would be great thank you

Woke up this morning to find that my Parity drive has been disabled. I have attached a screen shot My system specs are as follows Model: N/A System: ASRock - 990FX Extreme9 CPU: AMD FX-8350 Eight-Core @ 4 GHz Cache: 384 kB, 8192 kB, 8192 kB Memory: 16384 MB (max. 32 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 3.17.4-unRAID x86_64 OpenSSL: 1.0.1j The only thing I have found on how I might be able to resolve this was in the link below http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily Any help would be great thank you

Once the system is sable I will check why the network card is not getting set to 1gig. Also while the system was rebuilding the drive on of the 2tb drives (sn: WRED) went to disabled. I have placed a new drive in the system and am rebuilding the data once again.

You guys are gods. I move the drives to different ports on the motherboard and changed out some cables, that fixed the issue with the system just freezing. of cause now the system needs to rebuild the parity drive as a check since the system came down a few time unclean.

I attached the syslog after a reboot. The array is not started. I have also attached the system specs from the info button on the web page Thanks you syslog_12122014.txt sysem_specs.txt

Thanks for the reply Yes the key file is in the config folder (not on the root) The drives are in the right slots but I did notice that the sd(x) are different. The array did start a few time and was working fine then it started freezing up and hanging.

I had a perfect running system using an asrock motherboard amd cpu with 2 gig memory. I wanted to get something faster and ready fro V6 so I purchased an asrock 990fx extreme 9 AMD 8 core CPU fx8350 and 16 gig memory I already had the controller -SUPERMICRO AOC-SASLP-MV8 PCI-Express x4 I didn't change anything on my boot usb drive and when I tried to start the array the system just hangs (freezes) and I cannot do anything put hit the power button. I removed all the plugins and the system does the same. I install V6 on the USB drive and I get the same results when I try to start the array. Please any help will be great the array is down and im going crazy. Thank you

Joe I wanted to thank you for all your help in getting my system back online and functioning as designed. I did the following to get my /sbin folder structure back online 1st I disabled all the plugins that I run one of which was OpenSSH 2nd I stopped the array and shut it down. Since /sbin was not there the shutdown command did not work so I needed to hit the power button 3rd rebooted the system and /sbin was there. This was verified using the monitor connected to the unRAID system. I then decided to check using putty (just for kicks) so I started OpenSSH (I didn’t want to us telnet) and SSH’ed into the box. When looking for /sbin it was not there and it was gone from the terminal. Stopping OpenSSH did not bring the folder back so I rebooted again and after the system came up /sbin was there. I have disabled OpenSSH and am using telnet to access the box remotely.

I have rebooted a few times and that did not work. There was some permissions work done that might not have needed to be done when i upgraded from 4.7 to 5.0 but the system has been rebooted since. I ran the ls -ld /sbin and it come back with nothing. ls -ld /sbin /bin/ls: cannot access /sbin: No such file or directory Does the /sbin get created every time after a reboot is it part of the bzroot and bzimage. Thank you

Im running unRAID version 5.0rc8a. This a system that has been upgraded from v4.7. The issue that I am seeing is that I don't have a /sbin folder this is causing alot of issue when tring to run certain commands one of which is a preclear on two new drives. it sees a the prompt ./preclear_disk.sh: line 1313: sfdisk: command not found Sorry: Device /dev/sdh is busy.: 127 when i do a search for sfdisk it only comes up with the below symbolic link which is colored red lrwxrwxrwx 1 root root 17 2012-09-17 17:49 sfdisk -> ../../sbin/sfdisk also I cannot shutdown the array using shutdown or poweroff. It like the whole /sbin structure is gone. Any help please Thank you

This is what I get when I run the command. This is after a reboot last night just to make sure everything is okay. root@tower:~# ls -l /sbin/sfdisk /bin/ls: cannot access /sbin/sfdisk: No such file or directory I also tried root@tower:~# ls -l /usr/sbin/sfdisk lrwxrwxrwx 1 root root 17 2012-09-17 17:49 /usr/sbin/sfdisk -> ../../sbin/sfdisk