public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Problems still with xfs
Date: Thu, 08 Feb 2024 13:23:05 +0100	[thread overview]
Message-ID: <decb91dc-ad78-4833-992e-248cda798db3@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

Hi Michael and Arne,

I decided to build a vm testbed clone that would have an xfs filesystem.

I did the installation from Core Update 182 downloaded from the website. After the reboot during the installation the screen went blank and nothing more happened.

I then checked the sha256 hash for the website version with the one in the nightly build for Core Update 182 with the grub reversion and they are different.

I then built a system with xfs filesystem using the CU182 from the nightly build with the grub reversion but it still failed at the reboot stage of the installation.

I then did an xfs build using the CU181 website download version and that built without any problems.

I then did a pakfire update from CU181 to CU182 and that went without any problems, including the reboot.

Not sure what is going on but there seems to still be a problem with doing a fresh installation with xfs using either the website or nightly build versions of CU182.

Regards,

Adolf.


             reply	other threads:[~2024-02-08 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 12:23 Adolf Belka [this message]
     [not found] <7FA3C905-6DAA-4433-89FA-077E1E93EC61@ipfire.org>
2024-02-09 12:20 ` Adolf Belka
2024-02-09 13:11   ` Adolf Belka
2024-02-15 14:53     ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=decb91dc-ad78-4833-992e-248cda798db3@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox