boot failure #125
Comments
|
Unfortunately this
is not related to your problems. It means the kernel is expecting a built-in initramfs, but it's not, we load it separately. I have the same same message, it's harmless. Afaict you are having at least 2 problems.
|
|
@htot Thanks for taking the time to reply. From uboot, I can do If I boot into rescue, I do get a prompt and I can poke around. The partitions seem to be fine, as Contents of fstab: Checking for those partitions (at least in the intramfs env): I am using zeus. I also see in the boot log But what I can't find is what/where the requests for mounting |
|
Did a little more digging. By using the |
That's not normal. U-Boot can these days actually boot directly from the SD card. I don't see why mounting home failed, still. This happens by the init script which is inside the initrd. After executing, loading needed modules and mounting it does a switchroot to systemd, same environment as do_rescue. You can find it here: https://github.com/edison-fw/meta-intel-edison/blob/zeus/meta-intel-edison-distro/recipes-core/initrdscripts/initramfs-framework/init Installing the btrfs image, you get a slightly modified fstab. This is what I use so it is better tested. Still the ext image worked last time I tried. Good that btrfs image is working though. |
|
I have discovered that in the non-btrfs path of |
|
I had the intention not to break the home partition :-( But good that the recovery partition works. |
|
I see your intent. Sometimes there are scripts that fire on first boot. If there is such a thing in this environment, could it be used to check for the existence of an ext4 fs on the home partition, and make one if it is missing? Otherwise at least a note in the online documentation might be helpful. Either way, I'm happy to close this issue. |
|
I have seen reports with the original firmware that if home is damaged you couldn't boot. There is a script that runs on first boot (post-install.sh). But I think it runs after systemd. Best thing would be to have systemd fsck the partition if it's broken or create one if missing. But I thought it already did that. |
|
@htot The following warnings apply for me as well. Could we quiet them somehow?
|
|
Hi @mwallnoefer it is done by this script (in the initrd) https://github.com/edison-fw/meta-intel-edison/blob/master/meta-intel-edison-distro/recipes-core/initrdscripts/initramfs-framework/init Question: are you using Zeus or Dunfell? And are you booting ext4 or btrfs image? |
|
Dunfell with ext4 |
|
Ok so it seems Other then that it's harmless. |
I have an Edison on a stack of sparkfun carrier boards, including the base block, the SD card block, and the UART block. I have tried multiple things, but in all cases the board fails to boot to the root fs. I think the root of the issue may be related to the following line:
Initramfs unpacking failed: invalid magic at start of compressed archiveThe full boot log is here:
The recovery boot log is here, with the same issue:
I have tried building directly on my host system running Ubuntu 20.04, as well as in dockerized environments based in Ubuntu18.04 and even 16.04. Results are always the same. I have tried changing the load address of the initramfs. Results are always the same. I have tried checking out different branches of this repo. Results are always the same, except for old ones like sumo which fail
make setupdue to a patch that won't apply and warrior that failsmake imagedue toundefined reference to stime.Can someone point me in the right direction?
The text was updated successfully, but these errors were encountered: