Hi good day,

I need help here. One of my nvme ssd on my cache pool suddenly inaccessible.

This is the error that i able to capture. Immediate action that I do is rebooting the server. After the server rebooted, seems the nvme ssd appear back but the docker service failed to start.

Here i attach diagnostic file after the server rebooted. Silly me, I am accidently override the diagnostic file that i export before I reboot the server with the file after rebooted.

aiesb-svr-01-diagnostics-20260330-1654.zip

Any idea what should i do?

Thanks.

Edited March 30Mar 30 by Muhamad Aidil Karim
add information

Diags show that both devices dropped in the past; scrub the pool and post the results from the GUI.

Hi @JorgeB ,

Thank you for the fast reply.

I have completed scrub the pool.

This is also latest diagnostic file.

aiesb-svr-01-diagnostics-20260330-2337.zip

Should i try reboot the server again?

Thanks for your help.

No need to reboot for now, just recreate the Docker image, but you should monitor the pool for any future issues: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

Dear @JorgeB ,

Thank you for your feedback and guide. I am able to re-create docker image and reinstalling the docker application.

I cannot check my custom docker network since the docker service are failed to start. But it is ok since i only have 1 custom docker network.

I also have few corrupted VM since it is also on the same cache pool but i think I'll manage since it on VM OS itself..

Thank you.