Issues installing docker images after adding a 2nd cache drive

[Kohanime]

I recently added another nvme drive to run a mirrored cache pool, since then I haven't been able to install any docker images to it. Whenever I try and install one they end up getting stuck like this:

 

 

and then whole server hangs until I do a hard shutdown.

 

I had the same issue when I was using a single cache drive on btrfs, switching to xfs seemed to fix it, but that isn't an option with a cache pool.

 

Has anyone else had a similar issue?

starkonja-diagnostics-20190624-0449.zip

Edited June 24, 2019 by Kohanime

[JorgeB]

Weird issue, can you try using a different device for cache, any other SSD or even a spinner just for testing?

[Kohanime]

14 hours ago, johnnie.black said:

Weird issue, can you try using a different device for cache, any other SSD or even a spinner just for testing?

Hey thanks for the reply, I found a spare ssd for testing, I just tried installing a couple different dockers but I'm still having the issue described above. I tried searching to see if anyone else has had a similar problem but the only posts I found were about dns issues with docker pulls, I ended up changing my dns to cloudflare 1.1.1.1 & 1.0.0.1 but that didn't seem to change anything.

starkonja-diagnostics-20190625-2221.zip

[Squid]

Have you tried as of yet deleting the docker.img file?

[JorgeB]

You're getting a general protection error, same as before:

Jun 25 18:06:51 Starkonja kernel: general protection fault: 0000 [#1] SMP NOPTI
Jun 25 18:06:51 Starkonja kernel: CPU: 3 PID: 8710 Comm: loop2 Tainted: G    B             4.19.55-Unraid #1
Jun 25 18:06:51 Starkonja kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M Pro4, BIOS P3.30 05/10/2019
Jun 25 18:06:51 Starkonja kernel: RIP: 0010:memcpy_from_page+0x38/0x41
Jun 25 18:06:51 Starkonja kernel: Code: 00 09 00 00 bf 0b 00 00 00 48 c1 e7 29 48 01 fe bf 11 ff ff 01 48 c1 fe 06 48 c1 e7 27 48 c1 e6 0c 48 01 fe 4c 89 c7 48 01 d6 <f3> a4 ff 88 00 09 00 00 c3 41 54 55 53 48 8b 5f 18 48 8b 57 08 8b

We now know is not related to the cache devices, so most likely related to your hardware, looks for a bios update and/or use different hardware if you can.