search

commontorizon / meta-common-torizon

Fork of the TorizonCore OpenEmbedded Distro Layer to create Common TorizonCore
MIT License
8 stars 8 forks source link

Unable to boot after ostree admin unlock --hotfix #28

Open tcikel opened 4 months ago

tcikel commented 4 months ago

Hello,

After using "ostree admin unlock --hotfix" system doesnt boot anymore. I used ostree admin unlock --hotfix and after that modified systemd service file and after rebooting system is stuck on splash screen.

I am using Torzion OS v6.4.0-common and running it on RaspberryPi CM4. Here is the log:

U-Boot 2022.01 (Jan 01 1970 - 00:00:00 +0000)

DRAM: 1.9 GiB RPI Compute Module 4 (0xb03140) MMC: mmcnr@7e300000: 1, mmc@7e340000: 0 Loading Environment from FAT... OK In: serial Out: serial Err: serial Net: eth0: ethernet@7d580000 PCIe BRCM: link down starting USB... No working controllers found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 1217 bytes read in 10 ms (118.2 KiB/s)

Executing script at 02400000

2783 bytes read in 20 ms (135.7 KiB/s) WARNING: could not set bootargs FDT_ERR_NOSPACE. 24283648 bytes read in 1052 ms (22 MiB/s) 11425011 bytes read in 500 ms (21.8 MiB/s) Moving Image from 0x80000 to 0x200000, end=1a20000

Flattened Device Tree blob at 2eff2c00

Booting using the fdt blob at 0x2eff2c00 Using Device Tree in place at 000000002eff2c00, end 000000002f002fff

Starting kernel ...

[ 1.518831] brcm-pcie fd500000.pcie: link down Starting version 250.5+

I tried this multiple times and got same result, also i tried it without changing any file and got same result.

microhobby commented 4 months ago

Hey @tcikel thanks to report, I'm checking if the same occurs in the upstream.

drewmoseley commented 4 months ago

This does seem to occur in upstream. It does not happen in Torizon 5 but does in Torizon 6. It seems likely that something in OSTree has changed.

BhupiMAD commented 4 months ago

In my experimental build, i am getting a similar error for imx8mp. The error could be related to my configuration but thought of mentioning it. Link to issue

tcikel commented 4 months ago

Is there any fix i could apply to resolve this issue? I noticed that kirsktone does use quite old version of ostree, since this issue happens in upstream as well I assume that the only solution is to upgrade ostree to newer version where hopefully the issue is resolved right? This would mean that I have to upgrade some other layers as well to maintain compatibility which would take a lot of time so I dont wanna do it unless I really have to.

drewmoseley commented 4 months ago

@tcikel at the moment I don't know of any specific workarounds. I played with it some but it was not obvious what is changed in the failure case. I have passed this onto the Torizon development team for further analysis.

Please let us know if you find any acceptable workarounds.

tcikel commented 4 months ago

I have managed to build an image with ostree 2023.2 version and the issue is still there, I tried to build image with latest version 2024.3 but with that one I couldn't even boot the system. I might try some other version from end of 2023 later this week. Not sure if I should try to find issue somewhere else I assume this issue is directly in ostree and not somewhere else.I am surprised this issue wasn't fixed fast as it seems like a key feature at least from my point of view.

tcikel commented 2 months ago

Hello is this bug still present in ostree 2024 ? I noticed that you upgraded to 2024.4 version and I try to build my image with that but I am unable to boot unfortunately , so I wanted to ask if that issue is still present and it is worth for me to spent some time to get it work, because if its not i will just wait for next release of ostree and upgrade later.