Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[James Addison]

Package: d-i.debian.org
Followup-For: Bug #1031923
Control: forcemerge 1031622 -1

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[Cyril Brulebois]

Hi,

Cesar Enrique Garcia Dabo  (2023-02-27):
> Thank you for the answer. Good to know that it is a known issue and is being
> taken care of.
> 
> Regarding why I took that image. I just followed the official Debian
> webpages:
> 
> https://www.debian.org/CD/http-ftp/index.en.html

Many thanks for the follow-up…

> From there I clicked on "Official CD/DVD images of the "testing"
> distribution (/regenerated weekly/)
> "
> 
> https://cdimage.debian.org/cdimage/weekly-builds/ -> amd64 -> iso-cd -> 
> https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
> 
> So from my perspective I wasn't using a "random" image, but rather an
> official one, as the web pages indicate.

… now I understand what you went through.

Unfortunately, I wasn't aware of those instructions, and that looks utterly
buggy. How can we claim to publish “official images” that are snapshots, built
using debian-installer daily builds, that can be broken by random packages in
unstable, and left unfixed for weeks?!

We already have specific instructions on the d-i page[1] regarding
*actual* official releases (as soon as testing gets an Alpha 1), plus
snapshots. My first instinct would be to entirely scrap testing-related
things from the page you started from[2], and just redirect to [1]
instead.

 1. https://www.debian.org/devel/debian-installer/
 2. https://www.debian.org/CD/http-ftp/


That link should be updated too… http://debian-cd.debian.net/


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[Cesar Enrique Garcia Dabo]

Thank you for the answer. Good to know that it is a known issue and is 
being taken care of.


Regarding why I took that image. I just followed the official Debian 
webpages:


https://www.debian.org/CD/http-ftp/index.en.html

From there I clicked on "Official CD/DVD images of the "testing" 
distribution (/regenerated weekly/) 
"


https://cdimage.debian.org/cdimage/weekly-builds/ -> amd64 -> iso-cd -> 
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso


So from my perspective I wasn't using a "random" image, but rather an 
official one, as the web pages indicate.


Best regards,



Hi,

Andrew, please use reply-all, to reply to the bug and to the bug
submitter. A list-only reply doesn't quite help…

Andrew M.A. Cater  (2023-02-25):

I have installed Debian testing (bookworm) from one of the latest ISO images
(https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-
amd64-netinst.iso from 2023-02-21) and after an apparently succesfull
installation the system cannot be booted.

Enrique, thanks for the report.

We've published an official release one week ago. I'm not sure why
you're not using that instead of a random weekly build.


This is a known issue - try using the Alpha 2 installer in which this
issue is not present.

The e2fsprogs mismatch with grub is likely to be fixed by reverting
problematic versions.

No, the problem here is that e2fsck is from testing, while the
filesystem has been created by mke2fs from unstable, and the former
doesn't know about a new feature turned on by the latter.


Cheers,

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[Cyril Brulebois]

Hi,

Andrew, please use reply-all, to reply to the bug and to the bug
submitter. A list-only reply doesn't quite help…

Andrew M.A. Cater  (2023-02-25):
> > I have installed Debian testing (bookworm) from one of the latest ISO images
> > (https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-
> > amd64-netinst.iso from 2023-02-21) and after an apparently succesfull
> > installation the system cannot be booted.

Enrique, thanks for the report.

We've published an official release one week ago. I'm not sure why
you're not using that instead of a random weekly build.

> This is a known issue - try using the Alpha 2 installer in which this
> issue is not present.
> 
> The e2fsprogs mismatch with grub is likely to be fixed by reverting
> problematic versions.

No, the problem here is that e2fsck is from testing, while the
filesystem has been created by mke2fs from unstable, and the former
doesn't know about a new feature turned on by the latter.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[Enrique Garcia]

Package: d-i.debian.org
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: cqu...@arcor.de

I have installed Debian testing (bookworm) from one of the latest ISO images
(https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-
amd64-netinst.iso from 2023-02-21) and after an apparently succesfull
installation the system cannot be booted.

The screen shows this message when trying to boot:



/dev/mapper/hostname--vg-root has unsupported feature(s): FEATURE_C12
e2fsck: Get a newer version of e2fsck

/dev/mapper/hostname--vg-root: * WARNING: Filesystem still has errors
**

fsck exited with status code 12
The root filesystem on /dev/mapper/hostname--vg-root requires a manual fsck



And after that a BusyBox prompt is offered. I have tried several times the
installation all of them with the same result. Installing Debian bullseye
proceeded without errors in the same system.