Eric Hollebone

Update #1 - was watching the zpool mount during array start and captured the following from the system log but after the array starts, I can mount the pool and have it function correctly by using: zpool import storage What seems to be missing is the extra special vdev for the metadata mirror from the scripted import cmd. I'm thinking my post to this topic likely should be moved to a new thread as it does not relate to the original topic, and classified as a enhancement to support special vdevs

@JorgeB Here is the screen shot of main. This is done after I remount the zpool manual. if you need a picture of it before, please let me know. and the zpool status if it helps

Think I have the same or similar issue. My larger zpool with 18 hdd and 2 nvme drive does not mount automatically after a restart and I have to mount the zpool manually. Once added, the pool operates normally. The pool is on a netapp ds2448, 24 disk shelf via a LSI SAS 9201-e16 But the Main page indicate the pool is "Unmountable: Unsupported or no file system found" for all 18 drives. I have added manually a special vdev, mirrored 1TB nvme, to this pool for metadata and small files to speed up some operations, which may be a complicating factor. Just in case, upload the diagnostic file unraid-diagnostics-20240401-1712.zip

Based upon your description, is this a bug then? Because for me, branch is always set to "Stable" when the page is initially loads and I manually switch it to check. I would rather it be set to always be forward looking as either "Next" or "beta/rc". Really anything but "Stable"

Hi Limetech, First, I am unsure if this is the right forum for this but didn't see a better fit. I hope this is a doable feature request to cover off a small inconvenience. Can a change be made so that users can set the desired branch in the Tools, Update OS tab and be remembered and checked based upon the user's preference instead of the currently installed OS? My use case is I run two instances of Unraid, a production server on the main branch and a virtualized Unraid (i.e.Unraid on Unraid) on the next branch for testing. For my test version of Unraid, I would like it to be set and updated to the "Next" branch all the time. If this isn't clear, I'm happy to expand on idea.

May have traced this down to the electricbrainuk/unraidapi docker app (https://hub.docker.com/r/electricbrainuk/unraidapi). Running some test with it enable and not for a week or so to see if it is the problem