On Wednesday 27 March 2024, Andrei Borzenkov wrote:

On Wed, Mar 27, 2024 at 7:32 AM Michael Hamilton wrote:

...

I got an error on dup to 20240325. Is this something that I need to fix? I'm using ext4 for root, maybe that's a factor. After the dup, the system rebooted OK.

Last few lines of the dup where the error occured:

%transfiletriggerin(sdbootutil-1+git20240321.04bfbac-1.1.x86_64) script output:

Are you using systemd-boot?

No, just the standard grub from a normal install (although perhaps dating back a few years).

...

Error: Can't determine root subvolume warning: %transfiletriggerin(sdbootutil-1+git20240321.04bfbac-1.1.x86_64) scriptlet failed, exit status 1 Running post-transaction scripts ...................................................................... ...................................... [done] There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.

Thanks, Michael

On Wednesday 27 March 2024, Andrei Borzenkov wrote:

On Wed, Mar 27, 2024 at 11:59 AM Michael Hamilton wrote:

...

On Wednesday 27 March 2024, Andrei Borzenkov wrote:

...

On Wed, Mar 27, 2024 at 7:32 AM Michael Hamilton

wrote:

...

...

I got an error on dup to 20240325. Is this something that I need to fix? I'm using ext4 for root, maybe that's a factor. After the dup, the system rebooted OK.

Last few lines of the dup where the error occured:

%transfiletriggerin(sdbootutil-1+git20240321.04bfbac-1.1.x86_64) script output:

Are you using systemd-boot?

No, just the standard grub from a normal install (although perhaps dating back a few years).

So why do you have sdbootutil at all?

Good question. I have no idea. I just had a look: # zypper search -i --requires sdbootutil S | Name | Summary | Type --+--------------------+-------------------------------------+-------- i | sdbootutil | script to install shim with sd-boot | package i | sdbootutil-snapper | plugin script for snapper | package # zypper search -i --requires sdbootutil-snapper S | Name | Summary | Type --+------------+-------------------------------------+-------- i | sdbootutil | script to install shim with sd-boot | package My guess is the default install or some subsequent upgrade assumed snapper is going to be used and it dragged in sdbootutil-snapper. These dependencies seem circular, so what about removing sdbootutil: # zypper remove --dry-run sdbootutil The following 2 packages are going to be REMOVED: sdbootutil sdbootutil-snapper Seems OK. But interestingly I get a different answer if I remove sdbootutil-snapper: # zypper remove --dry-run sdbootutil-snapper The following 4 packages are going to be REMOVED: sdbootutil-snapper snapper snapper-zypp-plugin yast2-snapper So now I'm a little confused. Based on their names, and because I use ext4 for root, removing all these packages still seems safe. But I have plenty of spare space, perhaps I won't rock the boat. Michael

On Thursday 28 March 2024, Andrei Borzenkov wrote:

I suspect you had extra space between sdbootutil and -snapper.

That would get close to what I see, but not exactly. With space: zypper remove --dry-run sdbootutil -snapper The following 5 packages are going to be REMOVED: sdbootutil sdbootutil-snapper snapper snapper-zypp-plugin yast2-snapper Versus (without space): zypper remove --dry-run sdbootutil-snapper The following 4 packages are going to be REMOVED: sdbootutil-snapper snapper snapper-zypp-plugin yast2-snapper Quite puzzling.