Hi guys,

 

Tried using some dockers today, but it seemed off (sonarr was slow to operate and was unable to successfully search indexers). Thinking it was Sonarr, I tried to restart it, but there was an error starting it back up (can't remember error message sorry). 

 

I tried a system reboot, after start up, navigated to the dockers tab, error: no dockers.img available.

 

Checked the main tab and my Cache drive that I use for dockers is unmountable.

 

I found this forum post:

 

Following some of the solutions that JorgeB supplied, that helped others:

 

I tried:

stop array, unmount pool drives, start array, stop array, mount pool drives (i can reassign The problem drive, I cannot mount it).

 

I also tried:

btrfs rescue zero-log /dev/nvme1n1 

Result: ERROR: Could not open ctree 

 

Both with no luck.

 

Not sure what's gone wrong as I haven't been playing with any settings or installed any new docker templates/plugins/vms. Maybe a dead nvme? Or an auto update has gone wrong somewhere?

 

Please see attached for diagnostics following the two methods I tried above.

 

Thanks in advance!!

 

 

mantis-diagnostics-20241219-2327.zip

Edited December 19, 20241 yr by MatBar
Improve clarity - added result of rescue zero-log

9 hours ago, MatBar said:

I also tried:

btrfs rescue zero-log /dev/nvme1n1 

 

Note that this command should only be used if the log tree is the problem, in this case it is, at least one of them, but the device was not correct, type:

 

btrfs rescue zero-log /dev/nvme1n1p1

 

Then restart the array and post new diags.

Amazing, thanks JorgeB!! (And for everything you do for the community!) 

The nvme is back online, my docker containers are showing up again - the "Version" column for each container is showing "not available" - and individual docker containers GUI's are not working.

Should I try "Check for Updates" button?

Please see attachment for updated Diagnostics since array restart.

Small aside for my future reference, where should I have found the correct device label?

Thank you again!

Edit***

- Did not try "Check for Updates" on docker containers
- Restarted Array again and had same problem with that drive (Unmountable).
- Repeated step above to get the drive back so i can view file system.

Is it best to copy data from cache drive to array, re-format cache drive, and move data back?

Thanks!
 

mantis-diagnostics-20241220-1102.zip

Edited December 20, 20241 yr by MatBar
Please see Edit*** note

49 minutes ago, MatBar said:

Restarted Array again and had same problem with that drive (Unmountable).
- Repeated step above to get the drive back so i can view file system.

If the issue recurs, recommend backing up and recreating the pool, it usually means that there are other issues.

Eventually got around to recreating the pool, and everthing is back to normal.

 

Thanks for your help Jorge!!