Being on Mrfixit2001 V1.4: Unable to boot from SD card
11-17-2019, 01:12 PM
(11-17-2019, 12:45 PM)vfr400racer Wrote:(11-17-2019, 11:25 AM)Der Geist der Maschine Wrote:(11-17-2019, 11:10 AM)vfr400racer Wrote: This is a bit different from the other 'cant boot from sd' threads, I think. It seems other people's boot problems have been solved by updating to mrfixit's os version V1.4. But I am on this version.
So this is what happened:
I dd'd mrfixit's debian image to the SD card. Synced multiple times. When shutting down and trying to boot from SD card, it didn't came up. I waited about 10 minutes, but nothing happened. After booting from eMMC and inserting the SD card, I could see that the root file system has been expanded to 64G. So I guess it started booting from SD card , but got stuck at some point. Any ideas what might be the problem here?
"I could see that the root file system has been expanded to 64G. So I guess it started booting from SD card". Very good observation!
The journal is unfortunately not persistent. Make it persistent in /etc/systemd/journald.conf of the SD card and boot one more time.
(11-17-2019, 11:25 AM)Der Geist der Maschine Wrote:(11-17-2019, 11:10 AM)vfr400racer Wrote: This is a bit different from the other 'cant boot from sd' threads, I think. It seems other people's boot problems have been solved by updating to mrfixit's os version V1.4. But I am on this version.
So this is what happened:
I dd'd mrfixit's debian image to the SD card. Synced multiple times. When shutting down and trying to boot from SD card, it didn't came up. I waited about 10 minutes, but nothing happened. After booting from eMMC and inserting the SD card, I could see that the root file system has been expanded to 64G. So I guess it started booting from SD card , but got stuck at some point. Any ideas what might be the problem here?
"I could see that the root file system has been expanded to 64G. So I guess it started booting from SD card". Very good observation!
The journal is unfortunately not persistent. Make it persistent in /etc/systemd/journald.conf of the SD card and boot one more time.
I think, Mrfixit's OS has sshd enabled and a default password. Can you ssh into the failed boot and look around?
I set "Storage=persistent" on the sd cards's journald.conf. After booting /var/log/messages ends with
Nov 17 15:01:48 Debian-Desktop kernel: [ 6.072196] wl_run_escan: LEGACY_SCAN sync ID: 0, bssidx: 0
Nov 17 15:01:49 Debian-Desktop kernel: [ 6.820847] EXT4-fs (mmcblk0p2): resizing filesystem from 1280000 to 15559168 blocks
Nov 17 15:01:49 Debian-Desktop kernel: [ 7.025774] EXT4-fs (mmcblk0p2): resized filesystem to 15559168
Assuming system time is somehow ok, this entry is from my first boot from the sd card. boot process never started kernel afterwards (that is my interpretation).
When mounting the sd card, I get this in my /var/log/messages:
FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Maybe this is the problem during boot?
ad ssh-ing the pinebook: It can't be pinged while 'booting'. So I think the problem occurs very early in the boot process.
I looked at my very first boot messages. I got the same Fat-fs non-recommendation as well as the filesystem resize messages. After that, /var/log/messages continues with the next boot. I assume your problem is in the followup boot.
To see, the boot messages, remove from /boot/extlinux/extlinux.conf the tokens "quiet" and "console=ttyS2,1500000n8" and then disable the systemd service _splash via
# ln -s /dev/null /etc/systemd/system/_splash.service
I think the earliest boot logs are printed to the serial console only. Big mistake if you don't have one
