Hello,
I run Armbian on Banapi M1 (use it as samba file server with OpenMediaVault) and recently after apt-get upgrade and reboot the Bananapi is stuck in boot loop.
I have tried the following to eliminate possibility that it's a HW failure:
booted into fresh Armbian image with different SD card: success -> the board is OK
dumped whole Armbian installation as image from the original SD card, overwrote it with fresh Armbian image and booted with it: success -> the SD card is OK
wrote the dumped Armbian installation image onto a different SD card and booted from it: stuck in boot loop
wrote the dumped Armbian installation image onto a second different SD card and booted from it: stuck in boot loop
thus I believe the problem must be in the Armbian installation itself, not in HW
I don't know how to get hold of the boot messages since I never get to the login prompt but I've at least filmed the whole boot on the monitor.
The system always reboots right after the following lines:
[ 4.681580] systemd-udevd[144]: starting version 215
[ 5.847373] device-mapper: uevent: version 1.0.3
[ 5.849275] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
Since I have dump of the SD card I mounted the image on a different machine to have access to the filesystem. I reconciled the filmed boot loop with the armhwinfo.log content of previous boots and it seems the following lines are missing compared to successful boots:
...
[ 4.237054] mmc0: host does not support reading read-only switch, assuming write-enable
[ 4.239588] mmc0: new high speed SDHC card at address b368
[ 4.240515] mmcblk0: mmc0:b368 SD 7.52 GiB
[ 4.242469] mmcblk0: p1
...
and the system never reaches the following point:
...
[ 4.619783] Freeing unused kernel memory: 1024K (c0e00000 - c0f00000)
[ 4.681580] systemd-udevd[144]: starting version 215
[ 5.847373] device-mapper: uevent: version 1.0.3
[ 5.849275] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
<--- this is the last line, the system reboots right after here after a while
[ 6.346419] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
<--- assuming this means the root filesystem is mounted, the system never reaches here
[ 6.864213] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[ 6.864741] systemd[1]: Detected architecture 'arm'.
[ 6.912254] systemd[1]: Set hostname to <bananapi>.
...
What I conclude out of this is that the system has trouble remounting the root filesystem on the SD card (though the SD card is physically OK and the system at least can read the /boot part out of the SD).
Unfortunately I have no clue where to look to see why the root filesystem can't be mounted
Could anyone point me in the right direction? I tried looking into things like apt-get history log and there are several core looking packages that got upgraded recently (like linux-dtb-next-sunxi, linux-u-boot-bananapi-next, others...) but I don't know which ones could cause such problems.
Thanks for any hints!
T.