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: Re: Problems still with xfs
Date: Fri, 09 Feb 2024 13:20:45 +0100	[thread overview]
Message-ID: <1cd61387-6d99-4428-8f84-a08d7b970363@ipfire.org> (raw)
In-Reply-To: <7FA3C905-6DAA-4433-89FA-077E1E93EC61@ipfire.org>

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

Hi Michael,

On 09/02/2024 13:00, Michael Tremer wrote:
> Hello Adolf,
> 
> Thanks for raising this. I had a look at this, but I believe it is a false alarm :)
:+1:
> 
>> On 8 Feb 2024, at 12:23, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> 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.
> 
> This is correct. Looking at the installation log, GRUB fails to install and shows a message. Sadly we don’t properly catch that on the installer.
> 
>> 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.
> 
> Yes, this is also correct. We rebuilt the update with GRUB 2.06 after seeing some problems with GRUB 2.12-rc1. But we actually only changed the updater and did not change the installation images.
> 
> This has two reasons: Mainly changing the images is a pain. We have ~30 mirrors and getting them all up to date is too difficult. People might download parts of the file from different servers which results in an utterly broken image.

I now remember you mentioning this for an earlier change but I had forgotten that.
Can understand that it would be a right pita.

> 
> The other one is that the problem has an easy workaround: Don’t use XFS. So installation of IPFire is possible. If you really want XFS, install the previous version and update.
> 
>> 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.
> 
> That should actually work. I just tested the current master image (https://nightly.ipfire.org/master/2024-02-02%2007:52:09%20+0000-8c43d148/x86_64/) and this boots fine on XFS.
Ah. That might be where my problem was. I used the CU182 nightly build.

https://nightly.ipfire.org/core182/2024-01-10%2021:49:02%20+0100-c903d67c/x86_64/

The changelog for that mentioned the grub revert commit so I thought that was the one I should use.

Is master now the 182 version? I thought it was still the 183 testing one?

Anyway, I will test out the one from your link to confirm.
> 
> 
> 
>>
>> 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.
> 
> That might be, but it should be fine from Core Update 183.
I hadn't actually tested out the Core Update version, so I will also try and confirm that.

Sorry for any noise. I just thought it was worth having an xfs based system on my testbed so at least I can check the update and booting when a Testing release is done.

Regards,
Adolf.
> 
> -Michael
> 
>>
>> Regards,
>>
>> Adolf.
>>
> 

       reply	other threads:[~2024-02-09 12:20 UTC|newest]

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

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=1cd61387-6d99-4428-8f84-a08d7b970363@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