Docker not starting after reboot

[jackfalveyiv]

This morning my unRAID console was down.  After a quick look at things, I attempted a reboot of my instance and was met with a DB Disk Image Malformed error on my Radarr docker.  I also noticed that Sonarr wouldn't load correctly, so I rebooted again just to see if I got the same result.  Lo and behold, I am now receiving this when I go to my docker tab:

 

 

I'm fine with deleting my docker image and creating a new one, but I just want to ensure that is the correct course of action before doing anything.  Any help would be appreciated, thank you.  Also attaching a diagnostic.

trescommas-diagnostics-20230222-0927.zip

[jackfalveyiv]

I received an error in Fix Common Problems stating it's "unable to write to cache".  Cache is under 50% utilized.

[trurl]

What do you get from command line with this?

ls -lah /boot/config/shares

 

[jackfalveyiv]

There's a lot of data returned, but the final few lines look like this:

 

-rw-------  1 root root  435 Mar  5  2021 Zulu\ (1964).cfg
-rw-------  1 root root  462 Feb 15 22:20 appdata.cfg
-rw-------  1 root root  468 Feb 12 21:57 backups.cfg
-rw-------  1 root root  573 Feb 24  2021 bettercallbinge.cfg
-rw-------  1 root root  461 Mar  8  2021 books.cfg
-rw-------  1 root root  572 Feb 24  2021 bootlegconcerts.cfg
-rw-------  1 root root  593 Feb 24  2021 commprojectsandmisc.cfg
-rw-------  1 root root  462 Feb 19 21:57 data.cfg
-rw-------  1 root root  440 Feb 12 21:57 dmz.cfg
-rw-------  1 root root  467 Feb 12 22:14 domains.cfg
-rw-------  1 root root  453 Feb 27  2021 downloads.cfg
-rw-------  1 root root  435 Mar  6  2021 downloads_postprocessing.cfg
-rw-------  1 root root  436 Feb 26  2021 guacamole.cfg
-rw-------  1 root root  466 Feb 28  2021 handbrake.cfg
-rw-------  1 root root  567 Feb 24  2021 homemovies.cfg
-rw-------  1 root root  459 Feb 12 21:57 isos.cfg
-rw-------  1 root root  435 Mar  5  2021 ma\ ma\ (2015).cfg
-rw-------  1 root root  450 Mar 13  2021 movies.cfg
-rw-------  1 root root  555 Feb 24  2021 music.cfg
-rw-------  1 root root  559 Feb 24  2021 nfl.cfg
-rw-------  1 root root  470 Feb 27  2021 postprocessing.cfg
-rw-------  1 root root  459 Mar  7  2021 prerolls.cfg
-rw-------  1 root root  460 Feb 12 22:15 system.cfg
-rw-------  1 root root  445 Feb 21 22:23 temp.cfg
-rw-------  1 root root  469 Feb 12 21:57 timemachinebackups.cfg
-rw-------  1 root root  499 Feb 12 21:57 transcode.cfg
-rw-------  1 root root  439 Mar  5  2021 tv.cfg
-rw-------  1 root root  464 Feb 12 21:57 windowsdisk.cfg
-rw-------  1 root root  563 Feb 24  2021 workoutvideos.cfg

[JorgeB]

Cache filesystem is corrupt, best to backup and re-format.

[trurl]

11 minutes ago, jackfalveyiv said:

unable to write to cache

Feb 22 09:20:52 TresCommas kernel: BTRFS: error (device sdb1: state A) in do_free_extent_accounting:2852: errno=-22 unknown
Feb 22 09:20:52 TresCommas kernel: BTRFS info (device sdb1: state EA): forced readonly

Corrupt

 

You will have to try to copy it somewhere and reformat. Disable Docker and VM Manager in Settings until you get cache fixed.

 

 

Unrelated, just something you might clean up:

1 minute ago, jackfalveyiv said:

There's a lot of data returned, but the final few lines look like this

You apparently accidentally created a lot of user shares at some point. Any folder at the top level of array or pools is automatically a user share. Maybe you gave some docker access to /mnt/user or /mnt/<somedisk> and it created a lot of top level folders.

 

The only user shares you have currently are

appdata                           shareUseCache="prefer"  # Share exists on cache
b-----s                           shareUseCache="yes"     # Share exists on cache, disk1, disk2, disk3
d--a                              shareUseCache="yes"     # Share exists on cache, disk1, disk2, disk3, disk4
d-z                               shareUseCache="no"      # Share exists on disk2, disk3
domains                           shareUseCache="prefer"  # Share exists on cache
isos                              shareUseCache="yes"     # Share exists on disk2, disk3
system                            shareUseCache="prefer"  # Share exists on cache
t--p                              shareUseCache="prefer"  # Share exists on cache
t----------------s                shareUseCache="no"      # Share exists on disk2, disk3
t-------e                         shareUseCache="yes"     # Share exists on disk1
w---------k                       shareUseCache="yes"     # Share exists on disk2, disk3, disk4

You can delete those other .cfg files in /boot/config/shares.

[jackfalveyiv]

Thank you both, I suspected this was what had to be done but didn't want to push buttons without verifying.  I will also be cleaning up the cfg files, thank you for that. 

 

I'm copying data now to another source, but what is the best way to format the cache drive?

[trurl]

https://wiki.unraid.net/Manual/Storage_Management#Reformatting_a_drive

[jackfalveyiv]

Thank you

[jackfalveyiv]

I appreciate the help, my system is back up and running as normal.

 

One question, and maybe a fundamental misunderstanding I have regarding unRAID shares and how the file systems are organized.  How can I find this share:

/boot/config/shares

 

I understand the command that I can run through Terminal, and I understand where it should be, but I've tried mounting this path in Krusader as a new host path and I can't access anything in the directory.

[itimpi]

If you have the Dynamix File Manager plugin installed then you can simply get to its contents by going to the Boot Device on the Main tab.  Easier than trying to do it via Krusader.

[jackfalveyiv]

Have the plugin, but don't see Boot listed:

[trurl]

51 minutes ago, jackfalveyiv said:

How can I find this share:

/boot/config/shares

That path isn't a share, it is on the flash drive. Krusader won't be able to find it either unless you have a mapping to /boot.

 

26 minutes ago, jackfalveyiv said:

Have the plugin, but don't see Boot listed

 

42 minutes ago, itimpi said:

going to the Boot Device on the Main tab.

Main - Boot Device. Click on the icon under VIEW

[jackfalveyiv]

Got it, thank you.