• Posts

  • Joined

  • Last visited

  • Days Won


Report Comments posted by JonathanM

  1. That worked, thanks!

    I added a few steps, but the end result was the same. I first selected auto as the file system type, and as expected, it imported the existing BTRFS pool. Then I did the erase and reset.


    BTW, the three way default after I did the erase and selected ZFS was RAID0, don't know if that's intended.

  2. Maybe order matters?


    Already had 3 device pool that originally had the 3 SSD's in a BTRFS 3 way, but slots were empty.

    Clicked on first device, changed format to ZFS, 1 group 3 members, applied changes

    Assigned 3 devices to the 3 empty slots, confirmed ZFS still was selected

    Started array, formatted pool.


    I guess to recreate try first setting up a 3 way BTRFS, format it, stop the array, unassign pool slots, start/stop array to commit change, change first pool slot to ZFS, assign disks.

  3. 18 minutes ago, Joshndroid said:


    Thanks, should I be doing this always anyway as a future reference? (as if so, is there a line i should add to my script to run this inline with my shutdown command after a sleep of say 30s)

    Shouldn't be necessary, it's just a troubleshooting step to see if the array stops in a reasonable period of time. There is likely something keeping the array from stopping, causing the shutdown to kill the array prematurely, triggering a parity check on startup.


    If that's the case, you need to figure out what is keeping the array from stopping.

    • Like 1
  4. My speculation is that this looping happens when the list of containers too be updated is not current. I have been able to induce a loop by NOT rechecking for updates, updating one of the containers that had an update available from the automatic check, then clicking update all. It tries to pull updates for all the containers that were listed before I updated the single container, but it still includes the container I just manually updated, pulls zero bytes, and starts looping.


    If that is the case, you can work around the issue by first checking for updates, then hitting update all. That way you should be guaranteed to have the latest list.

  5. Keep in mind that the memory speed limitation may very well NOT be the memory DIMMs, it can be the memory controller on the CPU or the motherboard itself.


    Putting 200MPH rated tires on a toyota corolla is not going to allow the car to go that fast.


    All parts in the memory access path must be able to sustain the targeted speed. Run the system at stock speed (no XMP) and see how it behaves. Memtest can only prove the memory is bad, passing memtest doesn't mean the memory is working 100% under all conditions.

  6. 17 minutes ago, limetech said:

    Note this is documented in the Release Notes:

    🤣🤣 What is this thing you refer to? Release Notes? Who reads those? 🤣🤣

    18 minutes ago, limetech said:

    Should we add anything to that description?

    That's sufficient, more would be redundant.


    Is the quoted text also in the inline help system next to the exclusive setting?


    (I know, I know, spin up a trial and look for myself)

  7. 1 minute ago, ljm42 said:

    when you start the array the system checks for "sharename" on all your disks. If it only exists on the specified pool then "exclusive mode" is enabled and you will get the speed benefits of the bind mound to that pool.

    So content manually added to the sharename folders on a foreign pool will be hidden until the array is restarted?


    That's fine, I just wanted to confirm the behaviour so we can help people who will inevitably have a container writing to the wrong location.

  8. When is the additional check evaluated? Only when an attempt is made to change the status from NO to YES?


    What happens if the share config is manually manipulated?


    What happens if an exclusive access share has content added to another pool? Does the check happen every time an exclusive : YES share is mounted? If so, when content is added to the share folder on a "foreign" pool, is the content then made available when the array is stopped and restarted forcing exclusive to NO?

  9. Quote

    Exclusive shares

    If Primary storage for a share is a pool and Secondary storage is set to "none", then we can set up a bind-mount in /mnt/user/ directly to the pool share directory. (An additional check is made to ensure the share also does not exist on any other volumes.) There is a new status flag, 'Exclusive access' which is set to 'Yes' when a bind-mount is in place; and, 'No' otherwise. Exclusive shares are also indicated on the Shares page.

    Quick clarification please, for the minority of us that have leveraged "only" and "no" in unconventional ways, i.e. to access all the content of both the array and pool but NOT automatically move things around, manually moving things as needed, does the "additional check" force exclusive access to NO, and continue to work as before showing a fuse mount of array and pool content?


    I just want to be sure before I get a nasty surprise where most of my VM's suddenly lose their images. I currently have domains set to cache:only, so new VM's get created on the pool, but if I don't plan to use the VM very often I'll manually move the vdisk to the array, and move it back if I need to.

  10. 9 minutes ago, luzfcb said:

    Great. I asked the question because there is no information about Memtest86+ in the Release Notes for 6.12.0-rc1 and 6.12.0-rc2

    Yeah, probably because there really isn't any updated info, it is what it is.


    What I'd LIKE to see is a way to have the end user download the files, and copy them to the USB stick, with a custom boot option. A talented developer could probably come up with a plugin to do it, but since you can't run it without rebooting anyway, the extra steps of downloading the new version and making a memtest USB stick isn't really that huge of a deal. Developing and supporting a plugin that alters the Unraid USB stick like that is probably too much work and risk for too little benefit.

  11. 58 minutes ago, luzfcb said:

    Will the Unraid 6.12 also update the Memtest86+ version to the latest version available?

    It already includes the latest version that is licensed for 3rd party redistribution.


    Newer versions must be directly downloaded from the original website.