I just added a second parity drive, and now im getting these errors on the docker page:

Fatal error: Uncaught UnexpectedValueException: RecursiveDirectoryIterator::__construct(/boot/config/plugins/dockerMan/templates): failed to open dir: Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:90 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(90): RecursiveDirectoryIterator->__construct('/boot/config/pl...', 4096) #1 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(122): DockerTemplates->listDir('/boot/config/pl...', 'xml') #2 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(236): DockerTemplates->getTemplates('all') #3 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(313): DockerTemplates->getTemplateValue('binhex/arch-lid...', 'Icon') #4 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(288): DockerTemplates->getIcon('binhex/arch-lid...') #5 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerContainers.php(39): Dock in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 90

 

I'm not sure what happened, did adding a parity drive mess up the docker?  
Edit: i did move my usb drive from a port on the I/O of the mobo to a usb adapter that adds a usb 2.0 port off the motherboard.  

Edit2: i just tried updating CA Fix Common Prob and i got this

tower-diagnostics-20200508-0658.zip

Edited May 8, 20206 yr by danimal86

So i pulled the flash drive, and removed it from the header adapter and put it back in the port on the I/O of the motherboard.  Its still doing the same thing, but it looks like its running a parity check....dang these take forever.  

for some reason its stuck on the apps tab with the unraid logo waving.  I'm sure my cpu is pegged doing the parity check, so maybe its just hung up.  

Edited May 8, 20206 yr by danimal86

Pull the flash, toss it into a Windows box and run the file system checks on it

 

May  7 20:36:07 Tower kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0)

 

47 minutes ago, Squid said:

Pull the flash, toss it into a Windows box and run the file system checks on it

 

May  7 20:36:07 Tower kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0)

 

I should probably wait till the parity check is complete?

Yesterday i planned on swapping out the pos flash drive i used for a kingston.  So i have the new bootable flash drive i made from a backup yesterday (before i did the additional parity drive).  Should i just throw the new one in?

Edited May 8, 20206 yr by danimal86

It'll wind up wanting to do another parity check anyways after this one (because the flash drive is read-only currently, and can't mark down that it isn't an unclean shutdown)

46 minutes ago, Squid said:

It'll wind up wanting to do another parity check anyways after this one (because the flash drive is read-only currently, and can't mark down that it isn't an unclean shutdown)

Thanks!  I did a shutdown, plugged it into windows and it picked up the error and repaired it automatically.  I got unraid fired up and dockers show up and are starting to fire up.  Parity check started again so everything is sloooow.