Op dinsdag 12 september 2017 22:14:54 CEST schreef Freek de Kruijf: > Op dinsdag 12 september 2017 11:32:13 CEST schreef Freek de Kruijf: > > I will connect my USB serial cable to the proper pins of the RPi-card to see > if any message appears on the console.
Indeed I got the culprit in booting this upgraded system. In the start process things go well until /sysroot needs to be mounted. The log shows this: [ 10.250295] rpitestn systemd[1]: Reached target Basic System. [ 10.264108] rpitestn systemd[1]: Starting File System Check on /dev/disk/ by-id/mmc-SD08G_0x7c498e75-part2... [ 10.598506] rpitestn systemd-fsck[197]: ROOT: clean, 35270/425088 files, 329975/1767649 blocks [ 10.971425] rpitestn systemd[1]: Started File System Check on /dev/disk/by- id/mmc-SD08G_0x7c498e75-part2. [ 10.996954] rpitestn systemd[1]: Mounting /sysroot... [ 11.175363] rpitestn systemd[1]: sysroot.mount: Mount process exited, code=exited status=32 [ 11.164599] rpitestn kernel: EXT4-fs (mmcblk0p2): Unrecognized mount option "size=100%" or missing value [ 11.181939] rpitestn systemd[1]: Failed to mount /sysroot. Somewhere, I can't find it now, an error was reported that the parameter rootflags=size=100% was not recognized, which was the reason for not mounting /sysroot. So I looked into /boot/grub2/grub.cfg and found this parameter twice there. I removed it and started the RPi1. Hooray!!!! The system now boots and I get a prompt on the console. Also ssh connection works. All in all; The upgrade of the system has an error on the FAT32 partition and the parameter bootflags=size=100% in the grub configuration is in error. Should I file bug report? -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
