dave

Question about Dolphin - is it possible to browse files on a disc inserted into a DVD or BD drive?

Hi trurl, Running the 'date' command on the server returns the correct timestamp so that seems fine. Thinking back to earlier this year, I had a problem on the same disk: I can rebuild disk 5 again but first: is the error on the parity drive of any concern? That was not there last time.

Hi all, I just got back from an extended leave and am now facing a few errors across two drives in my server. Could someone please help me determine what the next steps to take are? I have attached the diagnostics to this post. Thanks! tower-diagnostics-20170905-0938.zip

Edit the Docker container and change the Repository field to "homeassistant/home-assistant:0.37.3" or whatever version you want.

Thanks, that worked!

I understand having secure remote access is the reason to do this but, silly question, what are the downsides to doing so?

Same question here. Anyone have some tips? Thanks!

Rebuild was a success. No errors. Running another parity check now, at 70% with no errors. Hopefully it was just a loose cable. When I opened up the case I took the time to blow out all the dust and re-seat all the HDD cables. Thanks again!

Thanks bjp, after some delay I was able to verify the simulated contents and the dozen or so files I checked looked fine. Nothing "mission critical" was on the disk so that helps. Rebuild is going now, should be done later today. I'll post again with a final update.

Hmm, interesting. Makes sense as I moved the server two weeks ago to the basement after getting a cat5e down there... Odd that it would be fine for a while then "act up." I'll check it now! Is there anything I should run after re-seating the connector? Parity check?

Just looked up the warranty status of the drive - it's covered until December!

Hi everyone, One of my WD Red 3TBs red-balled tonight and I am not sure how to proceed. On the /main page there are 4 errors. In the syslog.txt there are read and write errors. This appeared to happen around the same time that I updated a Docker image but that shouldn't have any effect because Docker runs on my cache SSD. Attached are the syslog and the SMART report for the disk. These were both just output from the Diagnostics screen a few minutes ago. Please take a look - any input would be greatly appreciated. Thanks! syslog.txt WDC_WD30EFRX-68EUZN0_WD-WCC4N7CVA9LF-20170130-2044.txt

I believe it works, but you have to run it on port 80, and to do that, you have to move the unraid gui to a different port (instructions for that are on the forum that you should be able find easily) Yeah, I was reading on the Vera forum that Google Home requires it to be on port 80 to connect. Thanks for the tip - I plan to try it this weekend!

Has anyone tried the HA bridge container with Google Home yet? https://github.com/bwssytems/ha-bridge/blob/master/README.md#google-assistant

You can do a force update to get it to the new .23 How do you force an update?

In the past I've seen coupons/discounts for Crashplan, anyone know of any current ones? I'm gonna sign up soon.

I also deleted the /appdata folder too just in case. The command finished successfully! MakeMKV Docker is up and running! Thanks everyone for your help, this was really bizarre and hopefully doesn't happen again.

Ok, rebooted, no changes. Can't even get Docker to run. How should I proceed now? Delete docker.img from /cache ? Or is there more to it than that...

I'll try the reboot first! I'm not opposed to re-creating the Dockers as I don't have very many or complex setups.

You made me do the math... My docker.img is 10GB. The dockers I have are: 2.114GB, 1.15 GB, 2.132 GB, 1.024 GB, 541.5 MB, 603.9 MB 2114+1150+2132+1024+541.5+603.9 = 7565.4 Should have ~2.5 GB of free space in there still.

Ok, I did that and now the Docker tab is not re-appearing. Hmmm... root@Tower:~# docker -d INFO[0000] [graphdriver] using prior storage driver "btrfs" INFO[0000] Listening for HTTP on unix (/var/run/docker.sock) FATA[0000] Error starting daemon: Couldn't create Tag store: EOF

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f92a0a4d2e20 l3iggs/owncloud "/root/startServers. 5 days ago Up 5 days 0.0.0.0:8000->80/tcp, 0.0.0.0:8443->443/tcp ownCloud cfdb258b9c04 sparklyballs/handbrake "/sbin/my_init" 3 weeks ago Up 3 weeks 0.0.0.0:1010->8080/tcp HandBrake 3661cf18e903 captinsano/rutorrent "/docker-entrypoint. 4 weeks ago Exited (137) 5 days ago ruTorrent 8e2dc27dce5a needo/plex "/sbin/my_init" 4 weeks ago Up 3 weeks PlexMediaServer Maybe there's something "stuck" in the background with Docker? Is there a way to stop/restart the Docker engine? I can always reboot the entire machine to try and get back to a clean slate.

REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE <none> <none> 9242a6055753 12 days ago 2.114 GB tobbenb/makemkv-rdp latest 9fcc556701fc 13 days ago 1.15 GB l3iggs/owncloud latest a68bea84a28f 4 weeks ago 2.132 GB sparklyballs/handbrake latest 7912e0056bbc 8 weeks ago 1.024 GB captinsano/rutorrent latest 3f638c0d04d3 4 months ago 541.5 MB needo/plex latest 8906416ebf13 5 months ago 603.9 MB

Same error but with a different image ID.

I get this error message: Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker rmi 9fcc556701fc Error response from daemon: No such image: 9fcc556701fc Error: failed to remove images: [9fcc556701fc] The command failed.