Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Boot Environment question

    Scheduled Pinned Locked Moved
    Plus 24.03 Development Snapshots (Retired)
    4
    7
    503
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jaltman
      last edited by jaltman

      The update from 23.09.1 to 24.03.b.20240322.1708 went smoothly. The new System> Boot Environments page looks great.

      However, I have boot environment named "default" from the 23.09.a.20230907.0600 alpha release which is displayed with a spinner and no option to select it for deletion. Any suggestions on how to remove it?

      260ed39c-0e03-4dea-8331-043ad2ac122b-image.png

      Thanks.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Hmm, what does bectl list show?

        J 1 Reply Last reply Reply Quote 0
        • J
          jaltman @stephenw10
          last edited by jaltman

          @stephenw10

          BE                                              Active Mountpoint Space Created
auto-auto-default-20230919151208-20231207221334 -      -          588M  2023-12-07 22:13
auto-default-20230826121709                     -      -          793M  2023-08-26 12:17
auto-default-20230919151208                     NR     /          5.46G 2024-04-03 13:42
auto-default-20230919151208_20240403134223      -      -          570M  2023-09-19 15:12
default                                         -      -          1.29G 2023-08-21 15:14

          BE/Dataset/Snapshot                                                Active Mountpoint Space Created

auto-auto-default-20230919151208-20231207221334
  pfSense/ROOT/auto-auto-default-20230919151208-20231207221334     -      -          24K   2023-12-07 22:13
    pfSense/ROOT/auto-default-20230919151208@2023-12-07-22:13:34-0 -      -          588M  2023-12-07 22:13

auto-default-20230826121709
  pfSense/ROOT/auto-default-20230826121709                         -      -          35.7M 2023-08-26 12:17
    pfSense/ROOT/auto-default-20230919151208@2023-08-26-12:17:09-0 -      -          758M  2023-08-26 12:17

auto-default-20230919151208
  pfSense/ROOT/auto-default-20230919151208                         NR     /          5.46G 2024-04-03 13:42
  auto-default-20230919151208@2023-08-26-12:17:09-0                -      -          758M  2023-08-26 12:17
  auto-default-20230919151208@2023-09-19-15:12:08-0                -      -          596M  2023-09-19 15:12
  auto-default-20230919151208@2023-12-07-22:13:34-0                -      -          588M  2023-12-07 22:13
  auto-default-20230919151208@2024-04-03-13:42:27-0                -      -          569M  2024-04-03 13:42

auto-default-20230919151208_20240403134223
  pfSense/ROOT/auto-default-20230919151208_20240403134223          -      -          756K  2023-09-19 15:12
    pfSense/ROOT/auto-default-20230919151208@2024-04-03-13:42:27-0 -      -          569M  2024-04-03 13:42

default
  pfSense/ROOT/default                                             -      -          728M  2023-08-21 15:14
    pfSense/ROOT/auto-default-20230919151208@2023-09-19-15:12:08-0 -      -          596M  2023-09-19 15:12
          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, it's probably an artifact from an earlier piece of code. That has changed quite a bit during bug solving. Might have to wait for @cmcdonald to confirm.

            You may be able to remove it from the command line with bectl.

            J 1 Reply Last reply Reply Quote 0
            • J
              jaltman @stephenw10
              last edited by

              @stephenw10

              bectl destroy default

              succeeded.

              T 1 Reply Last reply Reply Quote 2
              • B
                behemyth
                last edited by

                We just renamed the top line to default and deleted the second thing when we were testing that a couple weeks ago.

                1 Reply Last reply Reply Quote 0
                • T
                  tedquade @jaltman
                  last edited by

                  @jaltman Hit this issue today, different BE. Destroy did the trick.

                  Thanks!
                  Ted

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post