Old Cache drive SSD 1T

I added a second drive to the cache pool nvme 2TB

Raid1, And let it clone it self.

 

Afterwards I tried to enable docker  and VMs only to find neither of them would work.

I tried pathing the vdisk to the cache drive  I also tried pathing the libvirt.img location but nothing seems to be working.

(Fix Common Problems)  keep saying Unable to write to cache

 

Any help would be greatly appreciated.

 

I tried removing the second drive from the app pool, but then I got a error to many profiles.

tower-diagnostics-20230613-2025.zip

When I set the system to maintenance mode and do a Check Filesystem on the cache drive

I get the warning device 2 is missing and errors found in extended allocation tree or chunk allocation.

 

Looks like i have to blow out the whole thing and restore from a back up.

Had to blow it all out and restore from backups.

I just went with a single cache drive and used the 2TB nvme this time.

wow everything went to heck. I was restoring my backups then everything stopped responding. I checked the server itself and it said something about a critical Kernel error.

rebooted stopped all dockers and vms system is running parity check now; estimating 9 days 47 errors found total  raid size 4.11TB out of 21TB. not moving past .3%

 

I think I'm done with unraid.

every time I try to do something simple everything goes wrong.

All drives reporting healthy and good temps.

 

Browser interface stopped respoding. Here is picture of the server screen.

 

Looks like the nvme is not responding.

 

Please any thoughts.

tower-diagnostics-20230613-2230.zip

I reverted all my upgrades.

Removed the nvme drive and the extra 32gb of ran I installed.

 

I set the cache drive back to the 1TB SSD and  formatted it.

Hopefully it will rebuild now without crapping out again.

ok this time around 2 minutes elapse on parity check and I'm past .4%

says only 10 hours for rebuild. Guess I'll head to bed and check again in the morning.

Hope it doesn't crap itself out and freeze up again.

 

I tell you want, undraid is a adventure every time you try to change anything.

tower-diagnostics-20230613-2309.zip

So it looks like all my troubles were caused by a bad brand new NVMe drive I got from Amazon.

creating a pool of cache drives with it caused all kinds of madness to happen.

Probably why it was saying it was read only and in other places it would save device 2 was missing.

 

I would recommend people stay away from fanxiang branded drives yes they are super cheap but seem to be total crap.

 

Waiting on Parity to finish to restore docker and vm's

Thankfully I did have backups of all that.