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

Groups > linux.debian.user > #240888 > unrolled thread

failed upgrade buster -> bullseye

Back to article view | Back to linux.debian.user

Contents

  failed upgrade buster -> bullseye "D. R. Evans" <doc.evans@gmail.com> - 2021-10-05 00:20 +0200
    Re: failed upgrade buster -> bullseye "D. R. Evans" <doc.evans@gmail.com> - 2021-10-05 00:40 +0200
      Re: failed upgrade buster -> bullseye Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-05 09:10 +0200
      Re: failed upgrade buster -> bullseye "D. R. Evans" <doc.evans@gmail.com> - 2021-10-07 21:40 +0200
    Re: failed upgrade buster -> bullseye David Wright <deblis@lionunicorn.co.uk> - 2021-10-05 01:40 +0200
    Re: failed upgrade buster -> bullseye Greg Wooledge <greg@wooledge.org> - 2021-10-05 02:00 +0200

#240888 — failed upgrade buster -> bullseye

I just tried to upgrade my main desktop machine (this machine) from buster to 
bullseye.

The upgrade halted with:

----

...
Setting up libgnustep-base1.27 (1.27.0-3) ...
Processing triggers for shared-mime-info (2.0-1) ...
Setting up gnustep-base-runtime (1.27.0-3) ...
Setting up unar (1.10.1-2+b6) ...
Errors were encountered while processing:
  linux-image-5.10.0-8-amd64
  linux-image-amd64

Sub-process /usr/bin/dpkg returned an error code (1)

----

I have no idea what to do (other than to refrain from rebooting and hope that 
I don't lose power for so long that the UPS dies).

How do I start to find and fix the problem???

I do have a script record of the entire upgrade. It's about 6MB in length.

   Doc

-- 
Web:  http://enginehousebooks.com/drevans

[toc] | [next] | [standalone]

#240889

D. R. Evans wrote on 10/4/21 4:12 PM:
> I just tried to upgrade my main desktop machine (this machine) from buster to
> bullseye.
> 

I am suspicious that the problem is related to having root on ZFS on this 
machine. So I have posted a request for help on the zfsonlinux reflector, and 
probably it would be best if no one here spent much (or any) time thinking 
about the problem unless/until I am satisfied that the issue is unrelated to ZFS.

   Doc

-- 
Web:  http://enginehousebooks.com/drevans

[toc] | [prev] | [next] | [standalone]

#240903

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

On Lu, 04 oct 21, 16:36:49, D. R. Evans wrote:
> D. R. Evans wrote on 10/4/21 4:12 PM:
> > I just tried to upgrade my main desktop machine (this machine) from buster to
> > bullseye.
> > 
> 
> I am suspicious that the problem is related to having root on ZFS on this
> machine. So I have posted a request for help on the zfsonlinux reflector,
> and probably it would be best if no one here spent much (or any) time
> thinking about the problem unless/until I am satisfied that the issue is
> unrelated to ZFS.

Do you have linux-headers-5.10.0-8-amd64 installed?

It should be pulled automatically if you have linux-headers-amd64 
installed, but otherwise you must install it by hand. Without it 
dkms-zfs will fail to compile the necessary kernel modules.


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#241011

D. R. Evans wrote on 10/4/21 4:36 PM:
> D. R. Evans wrote on 10/4/21 4:12 PM:
>> I just tried to upgrade my main desktop machine (this machine) from buster to
>> bullseye.
>>
> 
> I am suspicious that the problem is related to having root on ZFS on this
> machine. So I have posted a request for help on the zfsonlinux reflector, and
> probably it would be best if no one here spent much (or any) time thinking
> about the problem unless/until I am satisfied that the issue is unrelated to ZFS.
> 

Indeed, the problem seems to have been caused by using root on ZFS. Running 
bullseye here now.

   Doc

-- 
Web:  http://enginehousebooks.com/drevans

[toc] | [prev] | [next] | [standalone]

#240891

On Mon 04 Oct 2021 at 16:12:49 (-0600), D. R. Evans wrote:
> I just tried to upgrade my main desktop machine (this machine) from
> buster to bullseye.
> 
> The upgrade halted with:
> 
> ----
> 
> ...
> Setting up libgnustep-base1.27 (1.27.0-3) ...
> Processing triggers for shared-mime-info (2.0-1) ...
> Setting up gnustep-base-runtime (1.27.0-3) ...
> Setting up unar (1.10.1-2+b6) ...
> Errors were encountered while processing:
>  linux-image-5.10.0-8-amd64
>  linux-image-amd64
> 
> Sub-process /usr/bin/dpkg returned an error code (1)
> 
> ----
> 
> I have no idea what to do (other than to refrain from rebooting and
> hope that I don't lose power for so long that the UPS dies).
> 
> How do I start to find and fix the problem???
> 
> I do have a script record of the entire upgrade. It's about 6MB in length.

So I would type:

$ col -b < your-typescript-file | less

and then the less commands:

-j 12 <RETURN>
/linux-image <RETURN>

and then n to see the next match for linux-image. That may give you
some idea of what failed. FAOD no space is typed between /linux-image
and the <RETURN> keystroke. col -b is not perfect so the file will
look a little messy in parts, with extra characters. -j is just to
give 12 lines of context before the matching string, to save scrolling.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#240892

On Mon, Oct 04, 2021 at 04:12:49PM -0600, D. R. Evans wrote:
> I just tried to upgrade my main desktop machine (this machine) from buster
> to bullseye.
> 
> The upgrade halted with:
> 
> ----
> 
> ...
> Setting up libgnustep-base1.27 (1.27.0-3) ...
> Processing triggers for shared-mime-info (2.0-1) ...
> Setting up gnustep-base-runtime (1.27.0-3) ...
> Setting up unar (1.10.1-2+b6) ...
> Errors were encountered while processing:
>  linux-image-5.10.0-8-amd64
>  linux-image-amd64
> 
> Sub-process /usr/bin/dpkg returned an error code (1)

You'll have to scroll back farther and find the actual error.  But
a good guess is "You ran out of space in /boot".  Very common.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web