Bug#1111649: apt: Fails to detect systemd on mdadm system during dist-upgrade

"Adam D. Barratt" <[email protected]>
Newsgroups gmane.linux.debian.apt.devel
Message-ID <bc9cf191bb88aab019b4360a74920f2cd7762f79.camel__44936.001829204$1755710297$gmane$org@adam-barratt.org.uk>
Control: reassign -1 mdadm 4.4-11

On Wed, 2025-08-20 at 15:09 +0000, Thorsten Behrens wrote:

[...]
>    I am coming from a Debian 12 system to Debian 13 using apt dist-
> upgrade. This gives me an error message
>    that systemd cannot be found. The system uses mdadm and is a bare
> metal server by provider OVH. In
>    some cases when testing this, grub EFI wasn't updated and restart
> failed.
[...]
>      apt showed an error message:
>      ```
>      no systemd init system detected
> 
>      The root filesystem of this system was detected to be on a RAID
> device, so mdadm might be required to run during boot to properly
> start your system.
> 
>      Beginning with newer versions of the madm package, init-system
> integration is available for systemd only. This system seems to use
> an alternative init-system which might or might not leave your system
> unbootable and will not run any of the maintenance jobs
> automatically.

That error message is being producd by the mdadm package. Thus
reassigning this bug there.

Regards,

Adam
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.