Updated to 6.12, docker and libvirt VM won't start anymore

[xHorn]

This is one of those times where I did a bit of research, tried a few things, but fear that if I do much more myself I may cause more harm than good. So, I humbly ask the community for help.

- Docker and VM's both worked before update
- Update restarted the machine, Docker and VM's never came back up.
- After some research, I thought it apropos to delete docker.img (through docker settings)
- No new docker.img gets created.

 

oilpan-diagnostics-20230619-1932.zip

[trurl]

Connection problems with cache, probably corrupt filesystem as a result.

[xHorn]

Solution?
I've got CA backing up the cache appdata to an external at the moment, but what next?

[JorgeB]

Replace cables for cache1 and post new diags after array start.

[xHorn]

Any chance someone could show me which part of the diagnostics are indicating this? That might make it easier for me to troubleshoot the connection. All cache's look fine on the Unraid "Main" page, so I'm just wondering how to know when I've gotten a bit further in troubleshooting

 

[trurl]

1 hour ago, xHorn said:

which part of the diagnostics are indicating this?

syslog starting here and all the way to the end:

Jun 19 19:31:27 OILPAN kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

 

[xHorn]

Well, a new cable hasn't worked.
Kinda bummed that I updated now, she's been rock steady for 2 years!

Seeing that I have two cache drives in  a pool (the available file size is somewhere between both drive sizes) would I be able to just remove one and run on the other for now without losing data?

[itimpi]

30 minutes ago, xHorn said:

would I be able to just remove one and run on the other for now without losing data?

 

Only if the pool is set up to provide redundancy (i.e. RAID1).  Your comment on size suggests this may not be the case.    If you provide your system's diagnostics zip file then we can check for you.

[JorgeB]

23 hours ago, JorgeB said:

post new diags after array start.