danthekilla

Hey @Partition Pixel I am having an issue with this docker failing to sync to the chia blockchain due to the time inside the docker being incorrect. Do you have any ideas on how I can solve this? I tried changing the time with this but it wouldn't let me. As you can see the time is out by more than 10 hours root@BigRig:~# date Mon May 17 01:27:31 AEST 2021 root@BigRig:~# docker exec -it chia /bin/bash root@1afebfbb2b67:/chia-blockchain# date Sun May 16 15:27:37 Australia 2021 Thanks!

No idea, I think it was because my plex one got full a year or two ago and so I had to make it bigger to make it work again?

Oh right, i didnt realize there was another type of log. I have attached that here. And yes I had the vm service and docker service disabled. Thanks for all your help. tower-diagnostics-20190103-0720.zip

Yeah, so that didn't work. I did this correctly and set all my shares with data on the cache drive to Yes, but when I run the mover it "moves" for a while (20mins) and then nothing happens. I still have the same 32.9gb of data sitting on the cache. I have turned off my dockers. Any ideas? So I cannot remove my cache drive as I cannot move the data off it...

Ahh ok, I tried a scrub. I am not very skilled with linux. Yeah I have no idea how to do a backup and restore of the cache data. Ill read that page you linked, thanks. Anything else I should know?

So the power went out last night and my ups was disconnected (changing the battery) so yeah...... Now I cannot run or create VM's and some of my dockers like plex are not starting correctly. Plex for instance just says "Plex is starting" over and over again. This is the error I get when trying to make a new VM "operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd" I have attached my log. tower-syslog-20190102-0056.zip

I am having this exact issue with the latest unraid. Did you manage to get this fixed? I noticed that you received zero support for it which is disappointing...

I am using unraid 6.5 and the system becomes unresponsive frequently now after updating from 6.3.5 When I start the device I now just get Array Starting•Starting services...for ever. My parity drive has failed (no idea why) and I cannot access the logs via the log button on the webUI (is there another way?) System Information also takes forever to load if I click on it, after about ten minutes I get this Model: Custom M/B: Gigabyte Technology Co., Ltd. - B85M-HD3-A CPU: Intel® Core™ i5-4670K CPU @ 3.40GHz HVM: Enabled IOMMU: Disabled Cache: 256 kB, 1024 kB, 6144 kB Memory: 12 GB (max. installable capacity 32 GB) Network: eth0: 100 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.14.26-unRAID x86_64 OpenSSL: 1.0.2n Uptime: Unraid 6.5 is a nightmare for me. The last log I managed to get out was this, 3-4 hours ago. It took about 40 minutes before the log loaded after a reboot.

I fixed it by rolling back to 6.1.7

I'm also having this error, of empty pushbullet.sh files being generated, with notifications not working. Running v6.1.8

And then there were 3. I also get an empty pushbullet.sh file when attempting to enter the deets for pushbullet notifications.

I have attached the most recent diagnostics file. tower-diagnostics-20160117-2057.zip

Everything is stuck in read-only mode and nothing works! Here are 2 videos showing some of the issues. https://onedrive.live.com/redir?resid=31E84CF772E4B44E!318802&authkey=!AOeAB1QCHkqd7wc&ithint=folder%2c And here is a error when I try to install a docker app. Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system. Error pulling image (latest) from limetech/plex, Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system. Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system 2e494d81b33d: Error pulling image (latest) from limetech/plex, Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system Error pulling image (latest) from limetech/plex, Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system Please help guys!

They don't show up on my Edge browser (no adblock) or firefox without adblock or on my phone. Is it normal with adblock for adding one to say it deleted it? Like it did in the 2nd video?

Hmm yeah that's the exact path I have set. Maybe it has something to do with this other issue I am having? https://lime-technology.com/forum/index.php?topic=45662.0 Thanks for trying to help me!

Here are 2 video that shows my issues I am having. I have been struggleing with this for 2 days now, I don't know what I have done wrong. If anyone could have a quick look at these 30 second videos of my issue I would be very grateful. Basically my shares are missing that I had, and adding new ones is weird... Brand new computer, fresh unraid install. Here are the videos https://onedrive.live.com/redir?resid=31E84CF772E4B44E!318802&authkey=!AOeAB1QCHkqd7wc&ithint=folder%2c Also I was told it could be adblock but: They don't show up on my Edge browser (no adblock) or firefox without adblock or on my phone. Is it normal with adblock for adding one to say it deleted it? Like it did in the 2nd video?

I told it to make it the default (10GB), maybe I created it wrong... What is the correct way to tell it to make it on the cache drive?

I just purchased unraid to build a small 5 drive media server. I have 1 cache ssd. and 4 4tb WD red drives. Running on an i5 with 16gb of ram. I have got unraid setup correctly (I Think) and have created the array and got it started, it is still calculating parity but I figured I can setup apps on the ssd etc while this is happening? Here is my error log... Perhaps someone knows whats going on here, I have very little experience with Linux so, but can get my hands dirty if I need too. Here is a possibly related issue? http://i.imgur.com/TaABnUw.png IMAGE ID [latest]: Pulling from limetech/plex. IMAGE ID [83e4dde6b9cf]: Pulling fs layer. IMAGE ID [b670fb0c7ecd]: Pulling fs layer. IMAGE ID [29460ac93442]: Pulling fs layer. IMAGE ID [d2a0ecffe6fa]: Pulling fs layer. IMAGE ID [f21b69028ac0]: Pulling fs layer. IMAGE ID [fc06acda5256]: Pulling fs layer. IMAGE ID [ed3f43ffe5bc]: Pulling fs layer. IMAGE ID [e9f50c1887ea]: Pulling fs layer. IMAGE ID [adceb8df17bb]: Pulling fs layer. IMAGE ID [5bff4b31638c]: Pulling fs layer. IMAGE ID [1aad78fe625a]: Pulling fs layer. IMAGE ID [b8d9d902ef0e]: Pulling fs layer. IMAGE ID [da89c0bf9e44]: Pulling fs layer. IMAGE ID [3fb032ba7f72]: Pulling fs layer. IMAGE ID [2fa9ae8f74b0]: Pulling fs layer. IMAGE ID [1d1c8646379d]: Pulling fs layer. IMAGE ID [2e494d81b33d]: Pulling fs layer. Pulling repository limetech/plex. Pulling image (latest) from limetech/plex. Pulling image (latest) from limetech/plex, endpoint: https://registry-1.docker.io/v1/.'>https://registry-1.docker.io/v1/. Pulling dependent layers. IMAGE ID [83e4dde6b9cf]: Pulling metadata. Pulling fs layer. Error downloading dependent layers. IMAGE ID [2e494d81b33d]: Error pulling image (latest) from limetech/plex, endpoint: https://registry-1.docker.io/v1/,'>https://registry-1.docker.io/v1/, Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system. Error pulling image (latest) from limetech/plex, Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="PlexMediaServer" --net="host" --privileged="true" -e TZ="Australia/Sydney" -v "/mnt/cache/appdata/plexmediaserver":"/config":rw -v "/mnt/user/Media/":"/media":rw limetech/plex Unable to find image 'limetech/plex:latest' locally latest: Pulling from limetech/plex 83e4dde6b9cf: Pulling fs layer b670fb0c7ecd: Pulling fs layer 29460ac93442: Pulling fs layer d2a0ecffe6fa: Pulling fs layer f21b69028ac0: Pulling fs layer fc06acda5256: Pulling fs layer ed3f43ffe5bc: Pulling fs layer e9f50c1887ea: Pulling fs layer adceb8df17bb: Pulling fs layer 5bff4b31638c: Pulling fs layer 1aad78fe625a: Pulling fs layer b8d9d902ef0e: Pulling fs layer da89c0bf9e44: Pulling fs layer 3fb032ba7f72: Pulling fs layer 2fa9ae8f74b0: Pulling fs layer 1d1c8646379d: Pulling fs layer 2e494d81b33d: Pulling fs layer Pulling repository limetech/plex 2e494d81b33d: Pulling image (latest) from limetech/plex 2e494d81b33d: Pulling image (latest) from limetech/plex, endpoint: https://registry-1.docker.io/v1/ 2e494d81b33d: Pulling dependent layers 83e4dde6b9cf: Pulling metadata 83e4dde6b9cf: Pulling fs layer 83e4dde6b9cf: Error downloading dependent layers 2e494d81b33d: Error pulling image (latest) from limetech/plex, endpoint: https://registry-1.docker.io/v1/,'>https://registry-1.docker.io/v1/, Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system 2e494d81b33d: Error pulling image (latest) from limetech/plex, Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system Error pulling image (latest) from limetech/plex, Mktemp failed: mkdir /var/lib/docker/graph/_tmp: read-only file system The command failed.