Bug#778849: Support restoring initrd on shutdown and pivoting into it
Hi Joseph.
The last paragraph of this e-mail is specifically addressed to you, but
most of this e-mail is addressed generally.
Also, apologies if this message is a bit rushed. I have a few things to
do today.
> I have yet to investigate intrigeri's suggestions from 2017,
I was planning to try out intrigeri's solution on a VM but have not had
the chance to do this.
> however I would suggest that this is something that needs to be
> upgraded from wishlist in 2022, and here's the reason simply enough:
>
> root@aki:~# nvme smart-log /dev/nvme0
> Smart Log for NVME device:nvme0 namespace-id:ffffffff
> [..]
> unsafe_shutdowns : 106
> [..]
> num_err_log_entries : 284
> [..]
> root@aki:~# nvme smart-log /dev/nvme1
> Smart Log for NVME device:nvme1 namespace-id:ffffffff
> [..]
> unsafe_shutdowns : 121
> [..]
> num_err_log_entries : 291
> [..]
I agree that this should be higher than wishlist for the above reason
plus Lukas's ZFS shutdown problem mentioned in the initial
description/submission of this bug.
This really should be fixed for Bookworm.
Awhile back, I did have a look around the fix. From what I remembered,
intrigeri's solution used a systemd shutdown 'script' to check for
devmaps or whatever of LVMs, ZFS partitions, etc... and runs specific
commands to umount the partitions.
However, I think my memory may be bad because I "now" don't see evidence
of such umounts in intrigeri's solution!
I would like to try things out today but maybe too rushed.
Jo, have you been able to try out intrigeri's solution (in GENERAL as
opposed to his specific patch/fix, which is mentioned in this bug report
and may have bits missing)? The reason I say this is because you would
have the exact recreation steps and be able to do it easily. For me, it
would be a shot in the dark or awkward for me to recreate. I would only
be able to check that root LVM on LUKS would not cause any untoward
problems.
Thanks,
Gervase.
Reply to: