Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #247316

Re: What happened?

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

n Sat, Apr 16, 2022, 6:17 PM Dennis Wicks <wix@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.

For your issue that brought you there: it sounds like maybe a filesystem
filled during the installation? Guessing.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

What happened? Dennis Wicks <wix@mgssub.com> - 2022-04-17 01:20 +0200
  Re: What happened? Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-04-17 04:40 +0200
    Re: What happened? The Wanderer <wanderer@fastmail.fm> - 2022-04-17 05:10 +0200
      Re: What happened? Stefan Monnier <monnier@iro.umontreal.ca> - 2022-04-17 07:30 +0200
        Re: What happened? The Wanderer <wanderer@fastmail.fm> - 2022-04-17 13:30 +0200
        Re: What happened? Dan Ritter <dsr@randomstring.org> - 2022-04-17 13:30 +0200
          Re: What happened? Charles Curley <charlescurley@charlescurley.com> - 2022-04-17 23:30 +0200
            Re: What happened? Dan Ritter <dsr@randomstring.org> - 2022-04-18 01:50 +0200
  Solved (partially) Re: What happened? Dennis Wicks <wix@mgssub.com> - 2022-04-21 20:40 +0200
    Re: Solved (partially) Re: What happened? The Wanderer <wanderer@fastmail.fm> - 2022-04-22 00:20 +0200
      Re: Solved (partially) Re: What happened? Dennis Wicks <wix@mgssub.com> - 2022-04-23 04:50 +0200

csiph-web