tradel
Cadet
- Joined
- Dec 19, 2023
- Messages
- 4
I did an upgrade from 23.10.0.1 to 23.10.1 and my system would no longer boot. I reinstalled 23.10.1 from the ISO and it still wouldn't boot -- kept telling me "boot-pool not found".
Bug #1: if you choose not to create the 16GB swap partition during installation, Cobia will not boot afterwards.
Re-running the installer and choosing to create the swap partition let me boot back up. Went into the UI and started setting everything back up, imported my ZFS pools, etc.
Bug #2: Timezone is stuck on America/Los_Angeles. Trying to enter a different TZ doesn't pop up the autocomplete suggestions. I typed in "America/New_York" and it wouldn't let me save, saying "timezone is required":
As I was trying to set things up, I saw lots of errors from the UI about not being able to connect to dbus:
Restarting dbus cleared up most of those errors, but I need to do this every time I boot, as if there's a race condition between dbus and other daemons. I also couldn't launch a VM until I restarted libvirtd.
Just a few issues I noticed :)
Server config:
Bug #1: if you choose not to create the 16GB swap partition during installation, Cobia will not boot afterwards.
Re-running the installer and choosing to create the swap partition let me boot back up. Went into the UI and started setting everything back up, imported my ZFS pools, etc.
Bug #2: Timezone is stuck on America/Los_Angeles. Trying to enter a different TZ doesn't pop up the autocomplete suggestions. I typed in "America/New_York" and it wouldn't let me save, saying "timezone is required":
As I was trying to set things up, I saw lots of errors from the UI about not being able to connect to dbus:
Code:
File "pystemd/dbuslib.pyx", line 446, in pystemd.dbuslib.DBus.call_method pystemd.dbusexc.DBusBaseError: b'org.freedesktop.DBus.Error.Spawn.ChildExited'[err -5]: b'Launch helper exited with unknown return code 1' This is DBusBaseError, a base error for DBus (i bet you did not see that coming) if you need a special error, enhance pystemd.sysd exc module!.
Restarting dbus cleared up most of those errors, but I need to do this every time I boot, as if there's a race condition between dbus and other daemons. I also couldn't launch a VM until I restarted libvirtd.
Just a few issues I noticed :)
Server config:
- Motherboard: MSI Z690 Pro Wifi
- CPU: 12th Gen Intel(R) Core(TM) i7-12700K
- RAM: 64GB
- boot-pool: 2x Crucial_CT275MX300SSD1 SSD
- pool1: 2x Samsung SSD 970 EVO Plus 1TB NVMe
- pool2: 4x TOSHIBA HDWG21C SATA
- SATA controller: Intel Corporation Alder Lake-S PCH SATA Controller [AHCI Mode]
- Ethernet controller: Intel Corporation Ethernet Controller I225-V