November 5, 20178 yr Community Expert 7 minutes ago, darrenyorston said: format the disk and restore data. That means after recovering the data format the cache and restore data, but it may not be clear for users with a pool so I'll edit that to make it clearer. 9 minutes ago, darrenyorston said: Removing and replacing a SATA cable shouldnt result in such problems. It doesn't normally, I can't see what in the logs but something went wrong during that operation, you can even connect any disk to a different cable on a different controller and normally there aren't any issues.
November 5, 20178 yr Author It may not have been the replacing of the SATA cable. As I mentioned originally one of the VMs was pausing. It looked like that unRAID was reserving 200GB of the cache. I had stopoed the Array to adjust the min free space on the cache, but also took the opprtunity to adjust the SATA cable at the same time. When I restarted the array all the problems occured. ie. One of the cache disks showed as unmountable and both docker and vms were inaccessible. The command line seemed problematic as well. The copy command you posted kept reporting the mounted /x disk was read only, I followed your guide, but when I utilised the mouse to select copy in midnight commander it worked fine. At the moment I have access to my files but docker containers dont appear to have access to the internet and VMs seem flaky, sometimes they work, other times they report not being able to find their vdisks. Seems to be a pretty serious problem and I am thankfull I didnt loose my data, though I did have an older back up of site if I had.
Archived
This topic is now archived and is closed to further replies.