Re: [opensuse-arm] Re: JeOS-efi.aarch64-2018.02.22: Failed to mount ext2 filesystem

[Matwey V. Kornilov]

2018-02-26 0:06 GMT+03:00 Alexander Graf :
>
>
>> Am 25.02.2018 um 16:37 schrieb Matwey V. Kornilov 
>> :
>>
>> 25.02.2018 18:22, Matwey V. Kornilov пишет:
>>>
>>> Hi,
>>>
>>> I am faced the issue that recent JeOS builds cannot be read by u-boot:
>>>
>>> ls mmc 1:2 /
>>> Failed to mount ext2 filesystem...
>>> ** Unrecognized filesystem type **
>>
>> Hm, Now I see. Why do you use btrfs for having separate /boot partition?
>> Is there any reason for it?
>
> I assume that change came with the seitch to python-kiwi. I assume the main 
> rationale would be snapshotting of /boot, so you can load old kernels.
>

/lib/modules are on the separate partition, so it won't work anyway.
We could have united / and put dtb files onto separate EFI partition
for snapshotting kernels.

> I guess there is an xml tag we can provide to make /boot ext4 again?
>
> Alex
>
>>
>>>
>>> And then dtb files cannot be read from /boot partition.
>>>
>>> Even without dtb, EFI application cannot be read correctly here:
>>>
>>> reading efi/boot/bootaa64.efi
>>> MMC: block number 0x18005 exceeds max(0x1dacc00)
>>> MMC: block number 0x18005 exceeds max(0x1dacc00)
>>> Invalid FAT entry
>>> 6144 bytes read in 11 ms (544.9 KiB/s)
>>> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>>> ## Starting EFI application at 0200 ...
>>> Unknown Relocation off ffe type f
>>> ## Application terminated, r = 9223372036854775806
>>> EFI LOAD FAILED: continuing...
>>>
>>
>>
>> --
>> To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
>> To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
>>
>



-- 
With best regards,
Matwey V. Kornilov
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Re: JeOS-efi.aarch64-2018.02.22: Failed to mount ext2 filesystem

[Alexander Graf]

> Am 25.02.2018 um 16:37 schrieb Matwey V. Kornilov :
> 
> 25.02.2018 18:22, Matwey V. Kornilov пишет:
>> 
>> Hi,
>> 
>> I am faced the issue that recent JeOS builds cannot be read by u-boot:
>> 
>> ls mmc 1:2 /
>> Failed to mount ext2 filesystem...
>> ** Unrecognized filesystem type **
> 
> Hm, Now I see. Why do you use btrfs for having separate /boot partition?
> Is there any reason for it?

I assume that change came with the seitch to python-kiwi. I assume the main 
rationale would be snapshotting of /boot, so you can load old kernels.

I guess there is an xml tag we can provide to make /boot ext4 again?

Alex

> 
>> 
>> And then dtb files cannot be read from /boot partition.
>> 
>> Even without dtb, EFI application cannot be read correctly here:
>> 
>> reading efi/boot/bootaa64.efi
>> MMC: block number 0x18005 exceeds max(0x1dacc00)
>> MMC: block number 0x18005 exceeds max(0x1dacc00)
>> Invalid FAT entry
>> 6144 bytes read in 11 ms (544.9 KiB/s)
>> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>> ## Starting EFI application at 0200 ...
>> Unknown Relocation off ffe type f
>> ## Application terminated, r = 9223372036854775806
>> EFI LOAD FAILED: continuing...
>> 
> 
> 
> -- 
> To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
> To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
> 

--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

[opensuse-arm] Re: JeOS-efi.aarch64-2018.02.22: Failed to mount ext2 filesystem

[Matwey V. Kornilov]

25.02.2018 18:22, Matwey V. Kornilov пишет:
> 
> Hi,
> 
> I am faced the issue that recent JeOS builds cannot be read by u-boot:
> 
> ls mmc 1:2 /
> Failed to mount ext2 filesystem...
> ** Unrecognized filesystem type **

Hm, Now I see. Why do you use btrfs for having separate /boot partition?
Is there any reason for it?

> 
> And then dtb files cannot be read from /boot partition.
> 
> Even without dtb, EFI application cannot be read correctly here:
> 
> reading efi/boot/bootaa64.efi
> MMC: block number 0x18005 exceeds max(0x1dacc00)
> MMC: block number 0x18005 exceeds max(0x1dacc00)
> Invalid FAT entry
> 6144 bytes read in 11 ms (544.9 KiB/s)
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> ## Starting EFI application at 0200 ...
> Unknown Relocation off ffe type f
> ## Application terminated, r = 9223372036854775806
> EFI LOAD FAILED: continuing...
> 


-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

[opensuse-arm] JeOS-efi.aarch64-2018.02.22: Failed to mount ext2 filesystem

[Matwey V. Kornilov]

Hi,

I am faced the issue that recent JeOS builds cannot be read by u-boot:

ls mmc 1:2 /
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **

And then dtb files cannot be read from /boot partition.

Even without dtb, EFI application cannot be read correctly here:

reading efi/boot/bootaa64.efi
MMC: block number 0x18005 exceeds max(0x1dacc00)
MMC: block number 0x18005 exceeds max(0x1dacc00)
Invalid FAT entry
6144 bytes read in 11 ms (544.9 KiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
## Starting EFI application at 0200 ...
Unknown Relocation off ffe type f
## Application terminated, r = 9223372036854775806
EFI LOAD FAILED: continuing...

-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org