Jump to content
  • [7.0.0-beta.1] after update a docker not possible to reboot


    Anym001
    • Minor

    Hello,


    I have updated from 6.12.10 to 7.0.0-beta.1 and then initiated a container update.
    The container update could not be carried out. -> Update ran in an endless loop.
    Docker page no longer accessible.
    Subsequent reboot no longer possible.

    Cold start necessary and after downgrade to 6.12.10 parity rebuild.

     

    Screenshots and diagnostics attached.

     

    grafik.thumb.png.196a59cb8fd02cffbbdf7f4e41430d0b.png

     

    Reboot attempt, recorded via PiKVM.

    grafik.thumb.png.d39bed710d952e3dab11b95368eef1c1.png

    sirius-diagnostics-20240705_0905.zip




    User Feedback

    Recommended Comments

    There have been multiple reports of a plugin, possible zfs master or other, causing issues, and I do see a zfs related call trace, please try again in safe mode.

    Link to comment
    26 minutes ago, JorgeB said:

    There have been multiple reports of a plugin, possible zfs master or other, causing issues, and I do see a zfs related call trace, please try again in safe mode.

    I have now updated some containers in gui safe mode. -> no problems
    As you already suspected, it looks like a plugin is causing problems here.

    • Like 1
    Link to comment

    Please see if you can confirm which plugin is the problem, I would start with zfs master.

    Link to comment
    Anym001

    Posted (edited)

    Unfortunately I cannot confirm exactly what the problem is.

     

    I have uninstalled zfs master + znapzend and updated to 7.0.0-beta.1.
    After that container update without problems.
    znapzend installed again
    Container update still without problems.

     

    Then I wanted to downgrade to 6.12.10 again, but got a call trace. Again cold start necessary.

     

    grafik.thumb.png.a9e00f338c7fba536bea2e99062a4352.png

    Edited by Anym001
    Link to comment
    1 hour ago, Anym001 said:

    Then I wanted to downgrade to 6.12.10 again

    But the call trace was still with 7.0.0 right?

     

    If yes, please try using a docker image instead and see if you get the same call traces.

    Link to comment

    I'm now almost certain that this is not a plugin issue, but a zfs issue with docker, this was just reported today, looks like the exact same issue:

     

    https://github.com/openzfs/zfs/issues/16324

     

    I think that the best bet for now, is to change to a docker image, or if you really want a docker folder, switch to xfs or btrfs.

    • Thanks 1
    Link to comment
    59 minutes ago, JorgeB said:

    I'm now almost certain that this is not a plugin issue, but a zfs issue with docker, this was just reported today, looks like the exact same issue:

     

    https://github.com/openzfs/zfs/issues/16324

     

    I think that the best bet for now, is to change to a docker image, or if you really want a docker folder, switch to xfs or btrfs.

    Yes, the problem topic starter describes, is exactly like mine, including the garbled screen.

    Link to comment

    Same problem here, can I use docker image with ZFS of do I need to swicth the cache pool off my docker/appdata back to BTRFS?

    Link to comment

    Shoudl I choose BTRFS vdisk or XFS vdisk then? My cache volume where my docker/appdata resides is ZFS RAID1

    Link to comment
    18 minutes ago, Kopernikus said:

    Shoudl I choose BTRFS vdisk or XFS vdisk then?

    Should be the same.

    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.

×
×
  • Create New...