On 2025-02-01 12:39, Andrew M.A. Cater wrote:
On Sat, Feb 01, 2025 at 10:07:49AM -0700, g...@extremeground.com wrote:
On 2025-02-01 09:29, g...@extremeground.com wrote:
BTW: the same happens with the previous kernel. Also, this is a
Debian/Buster server running on AMD64 hardware. I've fsck'd the partition
and it's fine.
I rebooted today after installing the latest updates - which included a new
linux-image.
Do you mean Buster ie Debian 10 ?
When you say systemrescue - do you mean a systemrescue live image that is
not from Debian for example the one from https://www.system-rescue.org/ ?
I'd suggest maybe using a Debian netinst image in rescue mode and
chroot-ing into the target partition, perhaps or using a Debian live
image to access the filesystem.
All the very best, as ever,
Andrew Cater
(amaca...@debian.org)
Sorry - I meant Debian/Bookworm (Debian 12). My mental faculties are
going downhill rapidly. ;)
