Solved (partially) Re: What happened?
Dennis Wicks wrote on 4/16/22 18:16:
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!
Mark this SOLVED (partially): software problem.
dpkg continued to kill the system trying to setup
linux-headers. I discovered that dpkg will purge the
linux-headers package and then I can try installing again.
On one try I was running pg on dkms in an attempt to see
what was going on that killed the machine. Two times I got a
long screen full of tasks running various types of cc just
before the crash.
I set up my pg to repeat every few secs and spooled the
output to a file. Then I started a tail on that spool file.
Surprise!! It ran to completion!
Here is my analysis: I have a big system. An AMD 8 core
Ryzen running at 3.8GHz with 64GB of memory. I think that
without any other load on the machine some task is getting
started before it should and either steps on a task that
should have finished by that time or can't find something
that was supposed to be created by a task that hasn't run
yet. It has to be something serious because all the
screens/sessions are cleared and the system is frozen. I
have to use the reset button to re-start and once or twice I
have had to cycle the power to get re-booted.
No progress on other problems. I will open other threads for
them.
Thanks for the comments. They got me thinking!
Dennis
Reply to: