Hi,

Had a quick search and couldn't find anything, but i am currently in the process of the parity swap procedure (https://wiki.unraid.net/The_parity_swap_procedure)

I am at step 4 and my array is just not stopping. It is displaying 'Retry unmounting disk shares(s)' at the bottom and has been so for the last 15 minutes. I can't get see the log as it just sits waiting for tower.
Is it safe for me to just power down and proceed?

The help is appreciated

Cheers,

Michael

Edited March 1, 20197 yr by miccos
solved

Oh i am on version 6.6.6 also

Do you have any console sessions open where the current directory is on the array?   If so this will stop the disks unmounting correctly.

No console sessions open. Not being used apart from me watching the main screen

managed to get this: (repeated over and over)

 

Mar 1 19:43:37 Tower root: umount: /mnt/cache: target is busy.

Mar 1 19:43:37 Tower emhttpd: shcmd (67326): exit status: 32

Mar 1 19:43:37 Tower emhttpd: Retry unmounting disk share(s)...

Mar 1 19:43:42 Tower emhttpd: Unmounting disks...

Mar 1 19:43:42 Tower emhttpd: shcmd (67327): umount /mnt/cache

Mar 1 19:43:42 Tower root: umount: /mnt/cache: target is busy.

Mar 1 19:43:42 Tower emhttpd: shcmd (67327): exit status: 32

Mar 1 19:43:42 Tower emhttpd: Retry unmounting disk share(s)...

only dockers use the cache and since the array is 'stopping' the dockers aren't showing as running.

Mar 1 18:41:20 Tower nginx: 2019/03/01 18:41:20 [error] 1808#1808: *3949889 upstream timed out (110: Connection timed out) while reading upstream, client: MYPCIP, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "tower", referrer: "http://tower/Main"

 

if this sheds anymore light?

Ok so I just ended up powering down.

In the end I needed to disable docker in order for it to release the hold on the cache drive.

Copying files from old to new parity now. Hopefully no more hiccups. 

Thanks

2 hours ago, miccos said:

Copying files from old to new parity now.

I'm guessing this is not what you meant to say. Parity doesn't have any files on it.

 

I suspect it's copying the entire drive bit for bit from the old parity drive to the new one.

 

Pedantic? Yes. But in IT, sometimes accurately stating what is happening prevents bad misunderstandings and possible data loss.

1 hour ago, jonathanm said:

I'm guessing this is not what you meant to say. Parity doesn't have any files on it.

 

I suspect it's copying the entire drive bit for bit from the old parity drive to the new one.

 

Pedantic? Yes. But in IT, sometimes accurately stating what is happening prevents bad misunderstandings and possible data loss.

I totally agree about the misunderstandings. Some users have even thought they needed to use parity swap when they didn't really.

 

For anybody that might be confused, parity swap allows you to replace a disabled or failing data disk with the existing parity disk and then use a larger disk in the parity slot. It is not needed any other time.

 

Parity swap was invented so people could use a disk larger than current parity when a data disk needs replacement. The larger disk becomes the new parity, the old parity becomes the replacement data disk.