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 September 30, 20232 yr by NewDisplayName

Hi,

 

i am currently facing that problem during a critical shrink array operation:

Have you been able to find a solution to complete the stop array operation properly ?

I was thinking about mounting the drive manually via CLI, to see if that would fix that error but I am unsure whether this is a good idea.

 

I didnt heared anything from limetech. I couldnt do anything just hard reset.

 

maybe @limetech can bring some light in the shadow... 

Edited November 4, 20232 yr by NewDisplayName

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 January 12, 20242 yr by Opawesome

I think the problem is that its not correctly handled on unraids side, so that would be probably a very easy fix if "already unmounted" = dont try to unmount... 

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.

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

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)

 

ah i just followed the link...  (btw forum smileys are broken)

Edited December 23, 20232 yr by NewDisplayName

I was struggling to fix this with the directions.  There's a step missing that wasn't clear to me. In case it helps:

 

1. Create a local virtual disk using `dd if=/dev/zero of=diskX bs=1M count=310` (where "X" is the disk number) in some folder like `/tmp`
2. Created filesystem with `mkfs -t xfs diskX`
3. Create a folder at `/mnt/diskX` (again where "X" is the disk number)
4. Mount the local virtual disk as the missing drive with `mount diskX /mnt/diskX`. 

On 9/4/2024 at 6:27 PM, tmchow said:

I was struggling to fix this with the directions.  There's a step missing that wasn't clear to me. In case it helps:

 

1. Create a local virtual disk using `dd if=/dev/zero of=diskX bs=1M count=310` (where "X" is the disk number) in some folder like `/tmp`
2. Created filesystem with `mkfs -t xfs diskX`
3. Create a folder at `/mnt/diskX` (again where "X" is the disk number)
4. Mount the local virtual disk as the missing drive with `mount diskX /mnt/diskX`. 

just want to say, this saved my bacon on a remote server.  thanks!