• After upgrade to 6.12.9 - array stuck at mounting disk


    bigernie71
    • Solved Minor

    The array will not start and seems stuck on "mounting disk" after updating to 6.12.9, updating all apps/plugins, and then rebooting after receiving the notification it was OK to reboot. I have rebooted a second time but the array still is not starting.
    I have downgraded back to 6.12.8 and the array is still not starting and stuck on "mounting disk".
    See attached diagnostics. Please let me know if you need anything further.

    tower-diagnostics-20240401_0701.zip




    User Feedback

    Recommended Comments

    After downgrading to 6.12.8 the array seemed to still hang on mounting disk. From settings, I change the VM Manager and Docker Manager to "NO" so they are not set to start. After doing that, the array started. I suspect me changing VM and Docker manager to "no" had no bearing. I think it was just a coincidence in timing.
    However, I did try 6.12.9 again with the VM and Docker manager auto start set to NO and the array still will not mount.

    UPDATE: As I was writing this and collecting more diagnostics, the array started. I believe it took around 15 mins to mount disk and start.
     

    tower-diagnostics-20240401-1138.zip

    Link to comment

    You cache pool is taking a long time to mount, don't see any disk or filesystem errors, but unlikely the issue is v6.12.9, and according to you it also took a long time to mount with 6.12.8, possibly one of the disks has an issue and is extra slow, or the zfs pool has some problem, or a lot of metadata/small files making it extra slow.

     

    You can retest by manually importing the pool, it should take the same amount of time, stoop the array and type:

     

    zpool import cache

    time how long it rakes to get the cursor back, then export the pool before array start

    zpool export cache

     

    Link to comment
    2 hours ago, bigernie71 said:

    I did 1 more reboot with 6.12.9 and the array finally started after 26 mins of uptime. I have attached another diagnostics and will downgrade to 6.12.8 for now.

    tower-diagnostics-20240401-1234.zip


    Thanks for the feedback JorgeB.
    The initial start after downgrading from 6.12.9 to 6.12.8 did take some time.

    I stopped the array (running 6.12.8) and then started it again and it took 2-3 mins.

     

    I stopped the array and performed the actions you suggested (zpool import cache). It took about 1 min or less.

    I performed a reboot running 6.12.8 and the array started at server uptime of 3 mins.

    Link to comment

    6.12.9
    First reboot - array started at server uptime 6 mins (not sure why but much better)

    Second reboot - array started at server uptime 6 mins
    Third reboot - testing a theory, array started at server uptime 6 mins

    Im not sure what happened with the first and second install of 6.12.9 but this seems to be a non issue after the 3rd install. Probably not needed but I uploaded my diagnostics I pulled after the 3rd reboot. Thanks for the assist, very much appreciated!

    tower-diagnostics-20240402-0837.zip

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.