On 2022-04-16 at 22:32, Nicholas Geovanis wrote: > On Sat, Apr 16, 2022, 6:17 PM Dennis Wicks <w...@mgssub.com> wrote: > >> When I first installed Debian 10, I installed Win 10 in a >> virtual machine using KVM/QEMU and everything just worked. I >> could copy/paste between host and vm and access host disks >> in the vm. And zfs file systems worked. >> >> The main problem was that dpkg would kill the system trying >> to setup >> linux-image-4.19.0-18-amd64. >> >> I decided to bite the bullet and upgrade to Debian 10.11. >> That process managed to install linux-image-4.19.0-19-amd64 >> and everything was fine. Then somewhere in the process of >> installing additional software apt? killed the system trying >> to setup linux-image-4.19.0-20-amd64. (I found out that I >> could do dpkg --configure for each package individually and >> skip the linux image and headers.) >> >> And, now I can't copy/paste between host and vm, can't >> access host disks from the vm, and the zfs file system >> doesn't work! And then because dpkg killed the system so >> many times the archive file is locked somehow and the >> various apt(x) programs and dpkg won't run, so I can't >> install any tools or different software to try and fix the >> problems!! >> >> ARGHHH! >> >> If anybody has any hints or tips or pointers toward any >> possible solutions I would appreciate hearing them! >> >> TIA, >> Dennis >> >> PS; dpkg says; >> >> > E: dpkg was interrupted, you must manually run 'sudo dpkg --configure >> -a' to correct the problem. >> > W: Could not lock the cache file; this usually means that dpkg or >> another apt tool is already installing packages. Opening in read-only >> mode; any changes you make to the states of packages will NOT be preserved! > > First: See if there are apt processes from previous attempts that are still > running. Maybe uselessly spinning thru CPU cycles, maybe pegging a CPU. > Kill those processes, you'll need to use the "-9" or KILL signal.
Also, check that the relevant partition (probably /var, if you're using separate partitions for such things) isn't full. I'd also suggest checking under /var for lock files that look relevant, but I just checked on *my* computer right now and there are several relevant-looking lock files even though neither dpkg nor apt is running, so I don't think messing with those would be safe. > For your issue that brought you there: it sounds like maybe a filesystem > filled during the installation? Guessing. My guess is that the upgrade in question was carried out while the VM was running, and when the upgrade tried to unload one or more relevant kernel modules, the kernel refused to let that happen because the module was in use. I've seen the reverse - the module gets unloaded, and then the VM hypervisor program dies hard, taking the guest VM down with it - happen before, with VirtualBox, back when I was still running that under Linux. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
