[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Your message dated Wed, 1 Mar 2023 08:32:13 +0100
with message-id <20230301073213.m47xk7d3ixzfnpfy@mraw.org>
and subject line Re: Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck
has caused the Debian Bug report #1031923,
regarding d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1031923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031923
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: d-i.debian.org
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: cquike@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.

--- End Message ---
--- Begin Message --- 
Cyril Brulebois <kibi@debian.org> (2023-02-27):
> 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/

Just pushed:
  https://salsa.debian.org/webmaster-team/webwml/-/commit/3b306bd46ff504f215e2758f81199d663bc27d0a
  https://salsa.debian.org/webmaster-team/webwml/-/commit/eadc4392f9f84dc7a3ce1881472a18a42a52d748
  https://salsa.debian.org/webmaster-team/webwml/-/commit/554e4e9521a3d022ea052a28fdc6a215cc1f3c5b

Note the website is built every few hours, and those updates will need
to be picked up by translators.

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

No idea whether that's still useful/maintained, but switched to
https:// along with other external links getting adjusted:

  https://salsa.debian.org/webmaster-team/webwml/-/commit/3d70cb0d8821c3f8ec922ac96298ad77e041fc7e

At least right now, it's reporting 11.5.0 as been the latest, which is
obviously wrong…


Closing this bug report I've been using to track buggy claims on the
website.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: