Re: upgrading ci.d.n s390x host to trixie failed

[Philipp Kern <pkern@debian.org>]

Hi,

On 5/31/25 9:52 PM, Paul Gevers wrote:
> I just tried to upgrade the ci.debian.net s390x host to trixie. It seems
> to have gone wrong. The host lost connection (I scheduled a reboot after
> a successful upgrade) and didn't come back up again.

I tried to get out of this bind and haven't tried to upgrade any host to
trixie yet. I guess technically I could spend some time with a test VM.

> When I log in via x3270 and issue an "IPL 150", I get the following. Do
> you have suggestions for me?
> 
> Paul
> 
> ...
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> done.
> Gave up waiting for root file system device.  Common problems:
>  - Boot args (cat /proc/cmdline)
>    - Check rootdelay= (did the system wait long enough?)
>  - Missing modules (cat /proc/modules; ls /dev)
> ALERT!  /dev/mapper/sysvg-root does not exist.  Dropping to a shell!
I'd assume that modules are missing.

Did you try booting the previous kernel? It should still be in the zipl
menu that comes after you IPL (vmlinuz.old). Does that one also not
boot? You might need to prefix your selection with a dot (is what my
brain tells me for some reason).

Kind regards
Philipp Kern