after upgrading to 25.03_Beta Cloned boot environment - now have PHP Fatal error code and blank blue page when attempting to access boot environments

[The Party of Hell No]

@stephenw10 I did not remove any of the boot environments. I have no access to the boot environments because of this error - other than at boot when I can select the boot environments.

I ended up with this error as I said above after editing the boot environment name - added a comma and it refused the name, corrected the name (Removed the comma) and attempted to save and then the error appeared.

[The Party of Hell No]

@stephenw10 How would I remove, or inspect boot environment names without access through: System - Boot Environments?

[stephenw10]

You can use the command line: bectl list

Then you can bectl destroy <name> if needed.

[The Party of Hell No]

@stephenw10

I do not see any errors in the names. Maybe you see errors?
So my plan, since I am currently booted in to:
Active-Current_25.03_BETA_Updated_From_24.11_RELEASE_24.11.r.20241112.1813_LAST_ACTIVE, is to reboot and boot into:
Archived_Active-Current_24.11_RELEASE_UPDATED_FROM_24.11.r.20241112.1813_clone_2 and then use the bectl to eliminate the two BE created on 5/11 since this is the date of when the error first appeared.

For my own education. for this error to appear across all BE means the changes and additions to the BE file are written across/to all BEs, or is a separate file residing on the HDD independent of the BEs?

[stephenw10]

The list of BEs is the same in all BEs. So if you create BE that somehow cannot be disaplayed it will hit the error in any/all BEs.

The actual list of allowed characters doesn't include .
We had excluded that because all your BE's have names containing that but....

I would try renaming the last created BE to something far simpler and test that.

[The Party of Hell No]

So no "." periods. Is there a way to "renaming the last created BE" through the command prompt or in the boot process? I A better question is how to rename without access from the GUI to the BE list and editing.
The difficulty I have with naming is when trying to choose a BE at boot... more details in the name is usually helpful.

[stephenw10]

Yes you should be able to just use: bectl rename oldname newname

See: https://man.freebsd.org/cgi/man.cgi?query=bectl

I would at least try the most recent BE as a test there. It's unclear to me why that is hitting the issue and none of the previous ones did though.

[The Party of Hell No]

@stephenw10 This was surprisingly easy after I understood the syntax.
I edited the last BE title I created... no change, rebooted, no change - still get blue screen with Boot Environments, Configuration History and Reboot.
I then used the bectl destroy to remove two of the older BEs.
Edited the last two BEs titles removing all the (.) (See attached screen shot) and - rebooted no change still giving me the blue screen.

Have any other ideas?

[stephenw10]

Hmm, still the same PHP error traggered?

[The Party of Hell No]

@stephenw10 Current:
[13-Jun-2025 14:08:34 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/www/system_be.php(89): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781
[13-Jun-2025 14:09:31 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/www/diag_confbak.php(78): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781
[13-Jun-2025 14:16:14 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/pfSense/include/www/system_be.inc(566): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 /usr/local/www/diag_reboot.php(170): be_gen_select_list(Object(LibbeHandle))
#4 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781
[13-Jun-2025 14:16:25 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/www/system_be.php(89): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781
[13-Jun-2025 14:22:06 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/pfSense/include/www/system_be.inc(566): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 /usr/local/www/diag_reboot.php(170): be_gen_select_list(Object(LibbeHandle))
#4 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781

Previous:
[11-May-2025 23:48:01 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/www/system_be.php(89): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781
[11-May-2025 23:48:16 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/www/system_be.php(89): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781

[The Party of Hell No]

@The-Party-of-Hell-No I finally rolled back to 24.11 pre 25.03 release BE, used the "bectl destroy" command on the saved 25.03 BETA BE and the php errors disappeared and all choices that lead to the blank blue screen now work correctly.

So this php error appears to be the wrong naming of a BE (unknown/wrong syntax) which requires a destroy of the BE. It appears using the bectl rename will not correct the php error.

Finally, resolved.

[stephenw10]

Huh that's weird.

Which BE was causing that? Do you have the name that was used?