Anyone else getting a boot error after upgrade from 189 > 190 error in file system after upgrade from 189 to 190 I begin to wonder if its anything to do with the change to EXT4 with ext4 with journal being the default .
All my installs I (am lazy) choose just EXt4 so it was one of these I upgraded , prior to upgrade no smart errors and file system was clean , I did a reinstall and recovery then ran the upgrade again same thing drops to Ctrl D for maintenance and that goes no where and gets in a boot loop ?
I have not updated any of my IPFires yet. I usually wait for a weekend when I have time to investigate any issues that crop up. But I will be watching this thread with interest.
I had no problems and I updated it again to ver. 191. But soon I will be finished with building up a replacement machine and will be trying the 190 or 191 iso (what ever is available to download).
I’m going to try out ZFS format to see if there is any performance over EXT4. Has anyone done this?
ext4 is the recommended filesystem for IPFire.
In this update process, we did not touch anything regarding the filesystem on existing installation. There is only no more option to use ext4 without a journal in the installer when you are installing a new system.
If your filesystem got corrupted, you might either have a hardware problem, or there was an unclean shutdown.
IPFire does not support ZFS. And there is no reason why we would as it does not have any massive advantages over the existing filesystem options.
Just curious about if ZFS would fair any better than EXT4. Another thought since ram is cheap now these days, if moving ipfire in a ram environment would improve performance. Similar to the puppy linux. But certain files and logs like the dchp expired clients needs better management.
Thanks , yes i have l always opted for EXT4 , it was just I read something about only the journal version from now on.
Its not a hardware issue so far as I know its running fine and I recovered it to 189 without issue I ran another upgrade and exactly the same result it went off to do the reboot and had corrupt file system ill try a few more . Just fyi this was a HP ‐ ProLiant ML310e Gen8 v2 running in SATA mode: www.ipfire.org - Profile ba63e71bc0ae9cf3329afc8ab475ecd20ae3cbd9 The funny thing is it managed to update the profile ( it shows 190 prior to the reboot but its now back to a 189 post recovery 
I also have a question about the update to CU 190. Is it normal for a test version to not receive an update when a stable release comes out?
Yes. The Testing and the Release versions are on two separate branches in the git repo.
You need to change the repository from Testing to Stable, then change the setting in the /opt/pakfire/db/core/mine from 190 to 189.
Then refresh the lists on the Pakfire WUI page just to be sure and you will have a notification that there is an update from 189 to 190 available. Press the update button and you will get the latest released CU190 version installed.
1 Like
To make it a bit easier to reduce the core update no., you can use the following command in terminal:
M=/opt/pakfire/db/core/mine ; cat $M ; echo $(( $(cat $M) - 1 )) > $M ; cat $M
then go to pakfire 
stable and refresh the list it in the way @bonnietwin stated.
Seasons greetings to ya’ll!