Hello all,

hoping someone can help me.

I am 6.12.4 and has been rock solid for over a year since my last upgrade.

Recently i decided to replace the last 6tb disk in my array. To do this i bought a 16tb disk and installed as parity.

All rebuilt ok. I then took the old parity drive and replaced the last 6tb disk. So now i have 

16tb Parity 4 x 12tb data with NVME raid 1 cache and SSD Raid 1 cache

the replacement disk successfully completed the data rebuild and all looked good. 

However, i noticed the docker web page wouldn't load kept crashing and I would have to power off the server.

I managed to trace this to the docker vdisk being read only as it been shrunk to 20gb i increased the size and all the dockers apps came up ok and all seemed good there.

However, the server keeps crashing/ going unresponsive in the web ui, it will just freeze after clicking around on settings and just browsing it.

I can still ssh in and have to do a force reboot, but I can't access file shares or any docker apps once it hangs

This is happening every time I do this, if I just leave the server alone it seems to stay stable.

I cant see anything myself in the logs but its probably not my strong point troubleshooting unraid logs.

Its making the server unusable and am starting to get a little concerned about the data.

I've attached my diags zip file so if anyone could help would be appreciated.

The only thing that has changed is this disk upgrade seems hard to believe it would be the cause, and i cant really put it back to where it was now.

 

thanks

 

bourne-diagnostics-20231206-2046.zip

Nothing in the logs that I can see, does booting in safe mode help?

Thanks for looking Jorge,

it was still crashing in safe mode.

One thing i did notice last night was a crc error on the ssd cache pool, this was after i made the first post.

I deleted the pool formatted the disks and recreated it but for now havent allocated it to any shares.

this morning it hasnt crashed but i havent had chance to put any load on it just yet

 

thanks

So i got to the bottom of it,

Seems the docker image file was corrupt, it had been put in read only mode after the disk upgrade had set it to 20gb for some reason.

Even after i reset it to 100gb it was causing the unresponsiveness.

The fix was to -

- stop the array

- rename the docker.img file

- restart array and enable docker

- this allowed the file to be re-created, from here it was a case of adding each container back in by clicking add container and selecting from the template drop down list.

- the configs were still there so just a case of adding them back in where required gave me the opportunity to tidy them up as well

 

hope this helps someone else

 

cheers

dan