After following spaceinvader1's latest guide of upgrading your cache drive to zfs I can't reboot my server. It just hangs trying to unmount drives. Trying to destroy a dataset on that pool states that it is busy so I believe that is the issue also affecting unmounting and reboot. What can I do?

 

oh, Unraid v6.12.2

Edited July 4, 20233 yr by TheThingIs

Please post the diagnostics.

Here ya goserver-diagnostics-20230705-1149.zip

Not seeing the error on the diags posted.

hmm ok

 

I can create and destroy a dataset on main-cache

I can't destroy an empty dataset on main-cache created prior to a forced reboot, pool is busy

I can't reboot as it hangs at unmounting main-cache

 

is it something to do with the appdata folder or a docker image or vm not closing and being released properly?

 

looking at logs and it's full of this line:

Jul 5 13:23:57 Server kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!

 

Edited July 5, 20232 yr by TheThingIs

22 minutes ago, TheThingIs said:

Jul 5 13:23:57 Server kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!

This is hardware/firmware related, it won't affect shares.

 

22 minutes ago, TheThingIs said:

I can't destroy an empty dataset on main-cache created prior to a forced reboot, pool is busy

Was this a one time thing or you can reproduce?

 

 

 

I was trying to take my array offline this morning, and was met with the same issue.

I ended up doing sudo shutdown -r now via command which seemed to kick the server, albeit uncleanly.

I'm going to move the system share off of cache to see if that resolves my issue.

 

Moving the system folder off of the zfs dataset seems to have resolved my issue. I'm going to guess it's because of the always in-use syslog files. That's pure speculation though, if anyone has more information.

 

Thanks!

17 minutes ago, iaw6 said:

I'm going to guess it's because of the always in-use syslog files.

Do you mean from the syslog server? Docker logs should shutdown when the service is stopped.

13 minutes ago, JorgeB said:

Do you mean from the syslog server? Docker logs should shutdown when the service is stopped.

yes

Yeah, that would likely cause a problem.

Yeah, I had the syslog server on historically for troubleshooting. I've turned it off and will move /system/ back to cache and report back if I have any other issues with the locking of zfs datasets.

3 hours ago, JorgeB said:

Was this a one time thing or you can reproduce?

not sure exactly what you mean but I have a dataset right now inside the appdata dataset "Test 1 2 3" which won't destroy and I can't do a clean reboot.

 

another odd thing that is also happening is I created a pool called "paris" and moved alot of unimportant shares there. I've set the shares to be on that pool only and not use the array but files are still being created on the array. Fix common problems alerts me to the problem that it sees shares on the array which are set to pool only so I manually go and move them. This has only started happening since I set the pool as ZFS

3 minutes ago, TheThingIs said:

I have a dataset right now inside the appdata dataset "Test 1 2 3" which won't destroy and I can't do a clean reboot.

Anything inside that dataset?

 

3 minutes ago, TheThingIs said:

another odd thing that is also happening is I created a pool called "paris" and moved alot of unimportant shares there.

There's no such share in the diags previously posted, you can post new ones so we can check the share settings.

server-diagnostics-20230705-1727.zip

no nothing inside the "Test 1 2 3" dataset

 

oh and thanks JorgeB, I appreciate you taking the time to look at this with me

35 minutes ago, JorgeB said:

There's no such share in the diags previously posted

Oops, misread, go to each share you want to use the pool only and set primary storage=paris secondary storage=none, see if that helps.

 

26 minutes ago, TheThingIs said:

no nothing inside the "Test 1 2 3" dataset

For this I have no other solution other than to force a reboot by typing "shutdown" in the CLI, then after the reboot you should be able to destroy the dataset.

1 hour ago, JorgeB said:

Oops, misread, go to each share you want to use the pool only and set primary storage=paris secondary storage=none, see if that helps.

 

that's the way they are set already

 

using shutdown in the cli hung just the same and I had to cold reset. Looking at the remote console before I power cycled looked like this (if it helps):

 

 

also after reboot I still can't destroy that dataset, pool is busy

13 hours ago, TheThingIs said:

also after reboot I still can't destroy that dataset, pool is busy

Sorry, but no more ideas, if there's nothing there can't see how it's busy, I assume you didn't change any container or other paths to use that dataset.