Removed Docker Plugin How Do I Get it Back?

[Archemedees]

So I removed my docker plugin while trying to fix some issues with Docker not starting. I had tried recreating the Docker image but it still wouldn't start so I jumped the gun and removed the plugin itself. For all other plugins it seems there's  community applications link. But for docker I cant for the life of me find the install URL to get it back. Any chance anyone has an idea?

[trurl]

There is no docker plugin so I don't know what you mean.

 

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

[ChatNoir]

Do you mean that you deactivated the Docker service in the settings ?

[Archemedees]

Apologies, was a long day, I removed the docker folder plugin and I thought I removed docker. Diagnostic is now attached. This is the error thaty seems to be the culprit. 

Dec 21 05:19:30 EnnsServer root: Creating new image file: /mnt/cache/appdata/docker.img size: 40G
Dec 21 05:19:30 EnnsServer root: touch: cannot touch '/mnt/cache/appdata/docker.img': Read-only file system
Dec 21 05:19:30 EnnsServer root: failed to create image file
Dec 21 05:19:30 EnnsServer emhttpd: shcmd (2602): exit status: 1

 

[Squid]

50 minutes ago, Archemedees said:

Read-only file system

 

10 hours ago, trurl said:

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

 

[Archemedees]

Sorry, meant to attach in the previous post

ennsserver-diagnostics-20201221-0924.zip

 

 

Edit: As an additional note, I just tried starting my Winbdows VM which started fine but I now get these errors in the log: 

Dec 21 06:29:53 EnnsServer kernel: loop: Write error at byte offset 37896192, length 4096.
Dec 21 06:29:53 EnnsServer kernel: print_req_error: I/O error, dev loop3, sector 74016
Dec 21 06:29:53 EnnsServer kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Dec 21 06:29:53 EnnsServer kernel: loop: Write error at byte offset 37961728, length 4096.
Dec 21 06:29:53 EnnsServer kernel: print_req_error: I/O error, dev loop3, sector 74144
Dec 21 06:29:53 EnnsServer kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
Dec 21 06:29:53 EnnsServer kernel: loop: Write error at byte offset 91570176, length 4096.
Dec 21 06:29:53 EnnsServer kernel: print_req_error: I/O error, dev loop3, sector 178848
Dec 21 06:29:53 EnnsServer kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
Dec 21 06:29:53 EnnsServer kernel: loop: Write error at byte offset 91635712, length 4096.
Dec 21 06:29:53 EnnsServer kernel: print_req_error: I/O error, dev loop3, sector 178976
Dec 21 06:29:53 EnnsServer kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
Dec 21 06:29:53 EnnsServer kernel: BTRFS: error (device loop3) in btrfs_commit_transaction:2267: errno=-5 IO failure (Error while writing out transaction)
Dec 21 06:29:53 EnnsServer kernel: BTRFS info (device loop3): forced readonly
Dec 21 06:29:53 EnnsServer kernel: BTRFS warning (device loop3): Skipping commit of aborted transaction.
Dec 21 06:29:53 EnnsServer kernel: BTRFS: error (device loop3) in cleanup_transaction:1860: errno=-5 IO failure
Dec 21 06:29:53 EnnsServer kernel: BTRFS info (device loop3): delayed_refs has NO entry
Dec 21 06:29:58 EnnsServer kernel: loop: Write error at byte offset 13426688, length 4096.
Dec 21 06:29:58 EnnsServer kernel: print_req_error: I/O error, dev loop3, sector 26224
Dec 21 06:29:58 EnnsServer kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 5, rd 0, flush 0, corrupt 0,

 

Edited December 21, 2020 by Archemedees

[trurl]

Corrupt filesystem on cache. See here except where it says replace cache you can just reformat that one:

 

[JorgeB]

Lots of checksum failures, you should run memtest.

[Archemedees]

On 12/21/2020 at 9:38 AM, trurl said:

Corrupt filesystem on cache. See here except where it says replace cache you can just reformat that one:

 

Thanks, this solved the issue. 

[Archemedees]

22 hours ago, JorgeB said:

Lots of checksum failures, you should run memtest.

I am running in UEFI mode, does memtest work now in UEFI or would I have to switch back? 

[itimpi]

Just now, Archemedees said:

I am running in UEFI mode, does memtest work now in UEFI or would I have to switch back? 

The memtest supplied with Unraid does NOT work in UEFI mode.    However you can download a version that does from the memtest86 site.