Page 23 of 27
Re: MintPPC
Posted: Sat Oct 25, 2025 3:23 pm
by mintppc
Can’t you boot in recovery mode and do some updates/upgrades and then reboot?
Re: MintPPC
Posted: Sat Oct 25, 2025 6:00 pm
by Roland
mintppc wrote: Sat Oct 25, 2025 3:23 pm
Can’t you boot in recovery mode and do some updates/upgrades and then reboot?
If that is possible, I have not the slightest idea how to do that... Remember this is not a PC - grub is not used for booting and there is no usual boot menu with special options!
Christian: is it at all possible to boot X5000 in recovery mode?
Re: MintPPC
Posted: Sat Oct 25, 2025 8:55 pm
by Roland
@mintppc
I found a solution:
Code: Select all
sudo tune2fs -O ^orphan_file /dev/sdx
This command turns off that 'C-12' feature which older versions of e2fsck cannot understand. I had to run the command on Adelie as tune2fs of my older distros/installations do not understand that orphan_file parameter!
After that I was able to boot from the Mint 25 parttion normally. But when I checked the version of e2fsprogs already installed there it WAS the newest one (1.47.2-3). So why couldn't it check the partition while it had that feature 'C-12' switched on? Is it still too old to understand it? I cannot see any other explanation...
Re: MintPPC
Posted: Sun Oct 26, 2025 4:04 pm
by xeno74
Roland wrote: Sat Oct 25, 2025 6:00 pm
Christian: is it at all possible to boot X5000 in recovery mode?
Yes, it is possible. Single mode with writable mounted volumes (Only one user (root) has access. No networking, graphical interface, or multi-user services are started):
Code: Select all
setenv bootargs root=<your volume/partition> single
If you need a file system check then you need the following boot arguments:
Code: Select all
setenv bootargs root=<your volume/partition> ro systemd.unit=emergency.target
Re: MintPPC
Posted: Mon Oct 27, 2025 12:28 pm
by Roland
xeno74 wrote: Sun Oct 26, 2025 4:04 pm
Yes, it is possible. Single mode with writable mounted volumes (Only one user (root) has access. No networking, graphical interface, or multi-user services are started):
Code: Select all
setenv bootargs root=<your volume/partition> single
For some reason, the 'simple' argument did not have any effect on my machine. Booting ended to the normal desktop.
If you need a file system check then you need the following boot arguments:
Code: Select all
setenv bootargs root=<your volume/partition> ro systemd.unit=emergency.target
This worked ok, and I was able to login as root. Network, apt and e2fsck (1.47.2-3) were also available.
Re: MintPPC
Posted: Mon Oct 27, 2025 1:55 pm
by mintppc
Not ‘simple’ but ‘single’…
Single user mode
Re: MintPPC
Posted: Mon Oct 27, 2025 7:54 pm
by Roland
mintppc wrote: Mon Oct 27, 2025 1:55 pm
Not ‘simple’ but ‘single’…
Single user mode
Thanks for the correction! Now I got it working, too. e2fsck available at the terminal was the v. 1.47.2-3.
But can you explain where that mysterious e2fsck v. 1.46.5 is located? It is the version available at the 'CRepair:/#' prompt, which appears if booting is interrupted due to an error as I earlier explained. Christian only said e2fsck is not included in the kernel.
Could it be in the uInitrd which Christian has created especially for X5000? He did not reveal that when I asked, and I do not now how to check myself the contents of it..
Re: MintPPC
Posted: Tue Oct 28, 2025 3:19 am
by mintppc
I don’t know where that comes from, sorry. Maybe Christian can shed a light on this.
Re: MintPPC
Posted: Wed Oct 29, 2025 2:31 pm
by Roland
Isn't the command "mkimage" available for mintppc? I could not find it with apt.
Re: MintPPC
Posted: Thu Oct 30, 2025 12:44 am
by mintppc