On 10.09.17 17:14, Freek de Kruijf wrote:
Op zaterdag 9 september 2017 22:53:21 CEST schreef Freek de Kruijf:
Op zaterdag 9 september 2017 18:42:52 CEST schreef Freek de Kruijf:
Op dinsdag 5 september 2017 22:41:54 CEST schreef Freek de Kruijf:
Op dinsdag 5 september 2017 14:00:33 CEST schreef Andreas Färber:
Am 05.09.2017 um 12:11 schrieb Freek de Kruijf:
Op dinsdag 5 september 2017 08:53:02 CEST schreef Freek de Kruijf:
Op maandag 4 september 2017 14:28:24 CEST schreef u:
On 04.09.17 11:49, Freek de Kruijf wrote:
I used the latest JeOS image 2017.05.23-Build1.1 for the RPi1
(armv6l)
on
a SD card and booted the system, which went OK.
I repeated these steps, but now I only tried to update kernel-default
using
zypper which pulled in two other packages, wireless-regdb and crda.
There were no error messages. However a reboot did not succeed. The system
could not find an extX file system with a certain UUID.
So I put the SD card in my desktop and used fdisk to list the structure.
This structure is totally wrong. See below:
# fdisk -l /dev/sde
Disk /dev/sde: 3.7 GiB, 3991928832 bytes, 7796736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FF922924-6706-4675-8AED-BB4E3FC84450
Device Start End Sectors Size Type
/dev/sde1 2048 67587 65540 32M EFI System
/dev/sde2 69632 509955 440324 215M Microsoft basic data
/dev/sde3 512000 6763365 6251366 3G Microsoft basic data
/dev/sde4 6764544 7796702 1032159 504M Microsoft basic data
Only the first partition sde1 can be mounted. the last one sde4 is a swap
partition.
The error message when mounting sde2 or sde3 is:
wrong fs type, bad option, bad superblock on /dev/sdeX, missing codepage
or
helper program, or other error.
Bug in dracut?
No. I did put the SD card in the RPi1 and waited till ssh access was
established. I did a shutdown of the system and put the SD card in my
desktop. The result is the same as above.
So it is the initialization of the SD card, creating the swap partition,
splitting up the BOOT partition of 250M in 32 EFI and a 215M other
partition, and enlarging the system partition, that goes wrong.
I initialized the SD card started it in the RPI1 entered with ssh and did the
command: fdisk -l /dev/mmcblk0 . The output follows:
# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 3,7 GiB, 3991928832 bytes, 7796736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FF922924-6706-4675-8AED-BB4E3FC84450
Device Start End Sectors Size Type
/dev/mmcblk0p1 2048 67587 65540 32M EFI System
/dev/mmcblk0p2 69632 509955 440324 215M Microsoft basic data
/dev/mmcblk0p3 512000 6763365 6251366 3G Microsoft basic data
/dev/mmcblk0p4 6764544 7796702 1032159 504M Microsoft basic data
Right after writing the SD card on my desktop it is:
# fdisk -l /dev/sde
Schijf /dev/sde: 3,7 GiB, 3991928832 bytes, 7796736 sectoren
Eenheid: sectoren van 1 * 512 = 512 bytes
Sectorgrootte (logisch/fysiek): 512 bytes / 512 bytes
In-/uitvoergrootte (minimaal/optimaal): 512 bytes / 512 bytes
Schijflabeltype: dos
Schijf-ID: 0xfa09d6bb
Apparaat Op. Begin Einde Sectoren Grootte ID Type
/dev/sde1 2048 411651 409604 200M c W95 FAT32 (LBA)
/dev/sde2 413696 2680704 2267009 1,1G 83 Linux
The strange thing is that the Linux partition initially starts on 413696 and
none of the newly created partitions start on that location.
Well, sounds like something went wrong in the repartitioning step. I'm
not quite sure what though - in the EFI case we should be quite safe:
https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/JeOS/uboot-image-install.in?expand=1
So the only repartitioning happening *should be* the one coming from
kiwi itself, plus conversion to MBR (see lines 87ff).
I guess you could try to dd a vanilla image onto an SD card, remove the
kiwi hooks in /.kiwi-hooks and check the partition table layout after
that. If it's sane, do the gdisk steps in the script manually and see
what comes out of that.
Alex
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
