[6.12.2] Array stop stuck on "Retry unmounting disk share(s)"


Go to solution Solved by ljm42,

Recommended Posts

If anyone is running a storj node, it likes to leave open files even with docker stopped.

 

 

Use the "Open Files" plugin to see what it's not closing and kill that process after making sure the Docker is stopped. This happens fairly often.

 

In this case, CLI from web works if this plugin doesn't....window popped up blank so :

 

kill 41524

 

 

image.thumb.png.f3e8e690fd0cfdae78f84e1e783652c3.png

Edited by RealActorRob
add kill command
Link to comment
  • 3 weeks later...

i just got this on 6.12.6. 

 

  

On 12/20/2023 at 12:44 PM, rbroberts said:

Just happened to me today. I had removed two of my four cache SSDs (they're Samsung 870 EVOs that are going out for warranty repair/replacement). I did them one at a time, and was stopping the array just to reduce the cache size to 2 disks when it hung for over an hour. I had walked away and came back to find it in that state.

 

Opening a web terminal and unmounting /var/lib/docker did the trick, so this has the same symptoms as the original, but I'm on Unraid 6.12.6.

 

thanks, this did the trick.  

 

it's kind of sad how after all this time, unraid still cannot reliably shut an array down.  

Edited by oliver
Link to comment
  • 2 weeks later...
On 8/23/2023 at 11:57 AM, ljm42 said:

 

Hmm, let's see what is going on:

  • stop the array to reproduce the problem (don't do a full shutdown because you won't be able to grab diagnostics)
  • show the output of `losetup` so we can see what /dev/loop2 points to on your system.
  • run `umount /dev/loop2` to resolve the issue and let the array stop
  • generate and upload your diagnostics.zip (from Tools -> Diagnostics) so we can see logs of the problem happening
  • feel free to start the array again

I'm having this issue on 6.12.3.

 

losetup returns

NAME       SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE                                    DIO LOG-SEC
/dev/loop1         0      0         1  1 /boot/bzfirmware                               0     512
/dev/loop2         0      0         1  0 /mnt/appdata-disk/system/docker/docker.img     0     512
/dev/loop0         0      0         1  1 /boot/bzmodules                                0     512
/dev/loop3         0      0         1  0 /mnt/appdata-disk/system/libvirt/libvirt.img   0     512

 

I ran 'umount /dev/loop2 twice, on the second time it reported that /dev/loop2: not mounted.

 

The array is still trying to unmount shares

 

Link to comment
9 hours ago, Surgikill said:

I ran 'umount /dev/loop2 twice, on the second time it reported that /dev/loop2: not mounted.

 

Glad you got past it. 6.12.6 has additional protections for this issue with the Docker image.

 

9 hours ago, Surgikill said:

The array is still trying to unmount shares

 

This means something is holding the share open. Be sure to close any open web terminals or SSH shells, if they are open to a share that will prevent the array from stopping.

 

Link to comment
  • 4 weeks later...

So Docker has still been holding the /var/lib/docker mount open for some folks. If you have been affected, please test Unraid 6.12.7-rc2 which does a "lazy unmount" of /var/lib/docker. This means instead of trying to unmount and giving up if it can't, it will wait until it is not in use and then automatically unmount. This should eliminate the need to ever have to manually run `umount /var/lib/docker` again.

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.