Jump to content

ferro

Validating
  • Posts

    1
  • Joined

  • Last visited

Everything posted by ferro

  1. Hello, After successfully installed and booted Armbian 23.02.2 Jammy from SD card on Odroid M1, I ran armbian-install script with using option "boot from SD, system on SSD" to move system to SSD. The process finished successfully, see the logs from armbianmonitor (taken before reboot): https://paste.armbian.com/folivedane After reboot, system failed to boot automatically from SSD due to error: [ 13.766854] 8644d43f-c78d-4586-ab61-14dfa2e740ea: Can't open blockdev [ 13.774855] systemd[1]: Starting Rule-based Manager for Device Events and Files... [ 13.781860] systemd[1]: media-mmcboot.mount: Mount process exited, code=exited, status=32/n/a [ 13.781889] systemd[1]: media-mmcboot.mount: Failed with result 'exit-code'. [ 13.783141] systemd[1]: Failed to mount /media/mmcboot. [ 13.785392] systemd[1]: Dependency failed for /boot. It asked for root password to go to maintenance mode. I found, boot failed because of wrong entry in /etc/fstab: root@odroidm1:~# cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 8644d43f-c78d-4586-ab61-14dfa2e740ea /media/mmcboot ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 /media/mmcboot/boot /boot none bind 0 0 UUID=832c2ac5-7666-4725-a85f-c8a015d9995a / ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 as you can see there is missing "UUID=" before uuid string for /media/mmcboot entry. After I fixed this problem by mounting /media/mmcboot and /boot (bind mount) manually and exited from maintenance mode it booted OK. I collected another armbianmonitor logs after boot, see: https://paste.armbian.com/qohidenowu When the broken line is fixed in the /etc/fstab: UUID=8644d43f-c78d-4586-ab61-14dfa2e740ea /media/mmcboot ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 system is booting normally. The same issue is present also when I used image Armbian 23.02.2 Bullseye Could you fix this bug, please? I think problem in nand-sata-install script (line 371). Thanks in advance!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines