Jump to content

Cant unraid stop when array already unmounted?


Recommended Posts

Hey,

so ive got the standard "cant restart because something blablablablabla".

 

I killed all associated processes (mergefs and rclone). Still not working, so i tired to unmount it myself which worked flawlessly. 

 

root@Unraid-Server:~# fusermount -uz /mnt/cache/

 

now im getting

Sep 30 10:48:40 Unraid-Server emhttpd: Retry unmounting disk share(s)...
Sep 30 10:48:45 Unraid-Server emhttpd: Unmounting disks...
Sep 30 10:48:45 Unraid-Server emhttpd: shcmd (329): umount /mnt/cache
Sep 30 10:48:45 Unraid-Server root: umount: /mnt/cache: not mounted.
Sep 30 10:48:45 Unraid-Server emhttpd: shcmd (329): exit status: 32
Sep 30 10:48:45 Unraid-Server emhttpd: Retry unmounting disk share(s)...
Sep 30 10:48:50 Unraid-Server emhttpd: Unmounting disks...
Sep 30 10:48:50 Unraid-Server emhttpd: shcmd (330): umount /mnt/cache
Sep 30 10:48:50 Unraid-Server root: umount: /mnt/cache: not mounted.
Sep 30 10:48:50 Unraid-Server emhttpd: shcmd (330): exit status: 32
Sep 30 10:48:50 Unraid-Server emhttpd: Retry unmounting disk share(s)...

 

So does that mean it doesnt go on because its already unmounted? A little bit stupid if u ask me? Or is there something it does which i cant see? My guess is "not mounted" is the same error code like "cant unmount"?

 

If that is so, that should be changed.

 

Bestes thing is, i cant change settings (i would like to disable auto start...) while this whole crap is happening, so i have to hard restart and have the same problem again lol 

Edited by NewDisplayName
Link to comment
  • 1 month later...

FYI, I found in a comment under one of SpaceInvaderOne's video on YouTube that someone figured out how to finalise the "stop array" operation when this problem occurs :

 

Quote

I created a local virtual disk using `dd if=/dev/zero of=diskX bs=1M count=310` (xfs requires at least 300mb disk), created filesystem with `mkfs -t xfs diskX` and mounted as `mount diskX /mnt/diskX`. Almost immediately after doing that, the stopping of the array was able to complete (cleanup the created virtual disks by running `rm diskX` after the array is stopped)

 

(link to source - see the "highlight reply" below the video)

 

I hope this workaround will help until, hopefully, this issue is fixed.

Edited by Opawesome
  • Like 1
Link to comment
  • 1 month later...
On 11/4/2023 at 1:34 PM, Opawesome said:

FYI, I found a comment under one of SpaceInvaderOne's video on YouTube that someone figured out how to finalise the "stop array" operation when this problem occurs (link) :

 

 

I hope this workaround will help until, hopefully, this issue is fixed.

 

This worked for me as well.

  • Like 1
Link to comment
18 minutes ago, NewDisplayName said:

could u post it here? So it can help others?

The workaround is a few posts above:

 

On 11/4/2023 at 5:34 PM, Opawesome said:

I created a local virtual disk using `dd if=/dev/zero of=diskX bs=1M count=310` (xfs requires at least 300mb disk), created filesystem with `mkfs -t xfs diskX` and mounted as `mount diskX /mnt/diskX`. Almost immediately after doing that, the stopping of the array was able to complete (cleanup the created virtual disks by running `rm diskX` after the array is stopped)

 

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.

×
×
  • Create New...