Jump to content

TheThingIs

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by TheThingIs

  1. 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):

     

    Capture.JPG.862e20cd442a28c94ba36f5b8380a67d.JPG

     

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

  2. 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. 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!

     

  4. 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

  5. it wasn't an empty space, just empty as I'd never touched it. However, changing the pattern to something like "eee" does make the missing datasets with a space in appear

     

    thanks :)

     

    oh and a quick suggestion if I may. When you manipulate the datasets, create or destroy etc, do an immediate refresh. If you have the refresh quite high then your changes take a while to appear and it makes you wonder if the action worked.

  6. Quote

    Kind of. You can not create them from the user interface (Next update I will fix that), but you can list them and operate over them.

    Interesting, mine isn't showing any datasets which have a space in their name.

  7. Other plugins install fine. The only thing that stands out to me is that there was a requirement to install zfs plugin which I already had installed so maybe it can't see that it's already installed.

     

    Thanks for looking into it though, I'll post in the 6.11 thread as you suggested.

×
×
  • Create New...