Discussion:
Bug#1091617: mdadm: broken debian-installer support
Add Reply
Cyril Brulebois
2024-12-28 19:50:01 UTC
Reply
Permalink
Control: notfound -1 4.2-5
Control: found -1 4.2+20230508-3

Sorry, missed that edit before submitting.


Cheers,
--
Cyril Brulebois (***@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Cyril Brulebois
2024-12-28 20:50:02 UTC
Reply
Permalink
Control: tag -1 patch pending
Spotted by Steve while testing tentative Trixie Alpha 1 images: mdadm is
broken, with a systemd-related problem.
# if system has root on md
if findmnt / 2>/dev/null | grep -qs \/dev\/md && \
# and system is not a container
! grep -qs ':cpuset:/$' /proc/1/cgroup && \
# and system is not a chroot
[ "$(stat -c %d/%i /)" != "$(stat -Lc %d/%i /proc/1/root 2>/dev/null)" ] && \
# and systemd is not running
[ -z "$(pidof systemd)" ]
then
db_input high mdadm/init-system-not-systemd || true
db_go
fi
- On my laptop I'm getting this: 64770/2 == 64770/2
- In my sid devel schroot I'm getting: 64774/1196038 != 64770/2
I've reproduced the “mdadm shows a note that really doesn't make sense
in that context” problem, and confirmed the proposed attached patch
avoids this problem.
I'm awaiting some feedback from the images team to see if my plan would
work for them, but my initial reaction would be to confirm the trivial
bugfix (if it's easy enough to test, within the installer's environment)
then upload + fast-track mdadm into testing, before respinning images.
What I've seen doesn't exactly quite match the early report, so I'm
still waiting on some more information before a possible upload. What
I've seen locally was a successful installation of mdadm and tasksel
running as usual, but that was just with a dummy RAID0 and a single
device, so maybe there are other problems lurking in the shadows that
I haven't spotted yet.


Cheers,
--
Cyril Brulebois (***@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Loading...