sactoking

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

sactoking's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Nope, never got this resolved. Still occurs when I move files.
  2. Interesting. It was working fine this morning and we haven't had any power issues. Oh well, makes sense at least. Time to transfer the license to a new flash I guess. At least it seems to be working fine in all other matters. Thank you!
  3. I just posted here b/c Unraid told me to. I didn't follow instructions in my first post, technically Unraid said this: Something really wrong went on during dismiss_warning Post the ENTIRE contents of this message in the Community Applications Support Thread <br /> <b>Warning</b>: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php</b> on line <b>43</b><br /> <br /> <b>Warning</b>: array_replace_recursive(): Expected parameter 2 to be an array, bool given in <b>/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php</b> on line <b>43</b><br /> <br /> <b>Warning</b>: file_put_contents(/boot/config/plugins/community.applications/accepted): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/community.applications/include/exec.php</b> on line <b>385</b><br /> {"status":"warning dismissed"} That's what pops up on the Apps tab of Unraid. tower-diagnostics-20200303-1932.zip
  4. Just got an Unraid Docker error: <br /> <b>Warning</b>: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php</b> on line <b>43</b><br /> <br /> <b>Warning</b>: array_replace_recursive(): Expected parameter 2 to be an array, bool given in <b>/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php</b> on line <b>43</b><br /> <br /> <b>Warning</b>: file_put_contents(/boot/config/plugins/community.applications/accepted): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/community.applications/include/exec.php</b> on line <b>385</b><br /> {"status":"warning dismissed"} All of my Docker apps appear to be functioning properly, I can still access the Plex data from Roku for example, but the Docker tab is missing from mu Unraid GUI.
  5. It may be worth pointing out that when this occurs I lost complete terminal responsiveness and one of the CPU threads stays pegged at 100%, so maybe it's not a network issue. Are there any known threading bugs or anything that could be causing this?
  6. Here is an updated diagnostic ZIP. I Stopped the array, rebooted, started the array, moved a series of files totaling ~16GB, then ran the diagnostic. During the file transfer I had the speed drop to 0 several times. Checking the dashboard I never had CPU usage above 8% or so, RAM usage above 3% or so, and the cache drive had 40+ GB of space available so I'm pretty sure it wasn't a resource issue from those perspectives. tower-diagnostics-20190609-0312.zip
  7. Ok, good to know that what I was seeing is just Docker info. I've attached my diagnostic ZIP as requested hoping there might be something useful in there. tower-diagnostics-20190608-1917.zip
  8. I'm having issues with my Unraid network connection that started recently. I replaced most of the non-drive hardware due to some failures and it seems like the issue started after the replacements were made. While transferring files through the Windows view of my shares I notice that the transfer speed often drops to 0. While running the Mover I was reviewing the logs and noticed the following: Jun 8 10:41:44 Tower kernel: veth3b0a86f: renamed from eth0 Jun 8 10:41:44 Tower kernel: docker0: port 1(veth7bf85ae) entered disabled state Jun 8 10:41:46 Tower kernel: docker0: port 1(veth7bf85ae) entered disabled state Jun 8 10:41:46 Tower avahi-daemon[2464]: Interface veth7bf85ae.IPv6 no longer relevant for mDNS. Jun 8 10:41:46 Tower avahi-daemon[2464]: Leaving mDNS multicast group on interface veth7bf85ae.IPv6 with address fe80::80a5:37ff:fec9:96f1. Jun 8 10:41:46 Tower kernel: device veth7bf85ae left promiscuous mode Jun 8 10:41:46 Tower kernel: docker0: port 1(veth7bf85ae) entered disabled state Jun 8 10:41:46 Tower avahi-daemon[2464]: Withdrawing address record for fe80::80a5:37ff:fec9:96f1 on veth7bf85ae. Jun 8 10:41:55 Tower kernel: docker0: port 1(vethc23cdc5) entered blocking state Jun 8 10:41:55 Tower kernel: docker0: port 1(vethc23cdc5) entered disabled state Jun 8 10:41:55 Tower kernel: device vethc23cdc5 entered promiscuous mode Jun 8 10:41:55 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethc23cdc5: link is not ready Jun 8 10:42:13 Tower kernel: eth0: renamed from veth4e1344b Jun 8 10:42:13 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc23cdc5: link becomes ready Jun 8 10:42:13 Tower kernel: docker0: port 1(vethc23cdc5) entered blocking state Jun 8 10:42:13 Tower kernel: docker0: port 1(vethc23cdc5) entered forwarding state Jun 8 10:42:14 Tower avahi-daemon[2464]: Joining mDNS multicast group on interface vethc23cdc5.IPv6 with address fe80::78a5:6ff:fe07:4839. Jun 8 10:42:14 Tower avahi-daemon[2464]: New relevant interface vethc23cdc5.IPv6 for mDNS. Jun 8 10:42:14 Tower avahi-daemon[2464]: Registering new address record for fe80::78a5:6ff:fe07:4839 on vethc23cdc5.*. It looks like something's happening to the network link but I'm not fluent in Linux. I do have Unraid set up on a static network address and have the network addressed through the router's DHCP, though oddly (to me) the server does not show up in the DHCP list of active devices (I DO have an active, working internet and network connection). Any ideas on what might be causing these intermittent drops? Thanks in advance!
  9. Thank you. Google wasn't helping because I felt like I didn't even know what I was searching for. Even just telling me "new permissions script" was enough to get me there, so I've got that running now and hopefully my shares should be working again when it finishes.
  10. Using the information provided by trurl for the other thread, I've got my disks back up and running. Now I've got a new issue: I can't access 2nd level folders on any of my shares. Example: I have a share called Data. I've mapped it to a network drive in Win7 so that it's Q: (\\tower\data). When I go to a file in the Data share (Q:\file.pdf) it works but when I try to open a folder in the Data share (Q:\folder\) it says "Q:\folder\ is not accessible. Access is denied." If I go to the Data share through the webgui it works fine, so it looks like there's some permission issue that I can't track down. I don't have any security on any of my shares and the Win7 computer can see the files and folders just fine, it just can't access the folders.
  11. I was on 4.7 prior. I've attached a syslog and a VARS file. if you look at the VARS file for disk 2 you can see that the id and idsb don't match; the idsb is missing 4 characters. syslog.txt VARS.txt
  12. Hey all. Finally got the $$ for a parity drive and when I logged into the webui is was busted. Ended up having to update to 5.0.5 to get the webui back. Now when I boot one of my disks is wrong. Looking at the serial number, it looks like disk 2 is missing 4 characters in the listing for what unRAID thinks the serial should be. How do I fix this?