Op maandag 11 september 2017 12:29:53 CEST schreef Alexander Graf:
> 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
The vanilla image should be openSUSE-Tumbleweed-ARM-JeOS-
raspberrypi.armv6l-2017.05.23-Build1.1.raw.xz I assume.
After dd of that image I found folder /kiwi-hooks on partition with label
ROOT. Renamed the folder to /kiwi-hooks.sav and booted the system.
The SD with fdisk and parted look like:
# fdisk -l /dev/sde
Schijf /dev/sde: 7,4 GiB, 7969177600 bytes, 15564800 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
# parted -l
Model: Generic- SD/MMC (scsi)
Disk /dev/sde: 7969MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 211MB 210MB primary fat16 lba, type=0c
2 212MB 1373MB 1161MB primary ext4 type=83
After starting the RPi1 with this SD card, I entered via ssh. I got the
following results of fdisk and parted:
# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 7,4 GiB, 7969177600 bytes, 15564800 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: dos
Disk identifier: 0xfa09d6bb
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 411651 409604 200M c W95 FAT32 (LBA)
/dev/mmcblk0p2 413696 14554890 14141195 6,8G 83 Linux
/dev/mmcblk0p3 14555136 15550919 995784 486,2M 82 Linux swap / Solaris
rpitestn:~ # parted -l
Model: SD SD08G (sd/mmc)
Disk /dev/mmcblk0: 7969MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 211MB 210MB primary fat16 lba, type=0c
2 212MB 7452MB 7240MB primary ext4 type=83
3 7452MB 7962MB 510MB primary linux-swap(v1) type=82
This looks normal.
It is not quite clear what gdisk commands I should perform. I did:
# more /mnt/ll/root/bin/makeMBR.sh
cat >> gdisk.tmp <<-'EOF'
x
a
1
2
64
m
EOF
# Convert GPT to hybrid GPT
cat >> gdisk.tmp <<-'EOF'
x
r
h
1 2 3
n
c
n
82
y
83
n
w
y
EOF
gdisk /dev/mmcblk0 < gdisk.tmp
rm -f gdisk.tmp
The resulting partitions look OK.
# gdisk -l /dev/mmcblk0
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Disk /dev/mmcblk0: 15564800 sectors, 7.4 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3E320E69-F543-431B-BAEB-31FDE58CF4C1
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15564766
Partitions will be aligned on 2048-sector boundaries
Total free space is 18150 sectors (8.9 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 411651 200.0 MiB 0700 Microsoft basic data
2 413696 14554890 6.7 GiB 8300 Linux filesystem
3 14555136 15550919 486.2 MiB 8200 Linux swap
However a reboot fails to find:
/boot/linux.vmx and /boot/initrd.vmx
In /boot/grub2/grub.cfg there are two menuentries asking for these two files,
but they are not there.
So I made two symbolic links in /boot
initrd.vmx -> initrd-4.11.1-1-default
linux.vmx -> zImage-4.11.1-1-default
Now the system boots and I have access via ssh.
All seems well. Will try to update all software.
--
fr.gr.
member openSUSE
Freek de Kruijf
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
