Jump to content

yeseul

Validating
  • Posts

    1
  • Joined

  • Last visited

  1. Hello, we contact you with Odroid booting issues. I've confirmed that the problem occurs from the next boot when the board is powered off while the armbian logo is displayed. (It happens with a high probability.) When booting, the following log is displayed and it does not boot. Loading, please wait... starting version 237 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block … done done. Gave up waiting for root device. Common problems: -Boot args (cat /proc/cmdline) -Check rootdelay= (did the system wait long enough?) -Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk1p1 does not exits. Dropping to a shell! BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs)_ After that, if you try to reboot about 5-6 times, one boot is possible. (This phenomenon does not disappear and continues.) The sd card is not physically damaged. This is because cloning the OS will reboot normally. Another feature is that the Armbian logo does not appear normally after booting problems. When there were no problems booting, the Armbian logo was always displayed. It appears that some file related to booting are crashed on an abnormal shutdown. This is because we found a file that is believed to be the cause. After a few tries I successfully booted from the sd card with this boot problem and checked the /boot/armbianEnv.txt file. And found that the file contents are broken. (The contents are different from normal files.) I got the armbianEnv.txt file from a general sd card that did not have the problem raised in this article, overwritten it, and then booted it, and it was confirmed that it boots normally without any problem. I think this happens if the file writes don't complete properly while boot.cmd is running. Is my guess correct? I've heard that armbianEnv.txt is giving incorrect kernel parameters for the root filesystem root=/dev/mmcblk1p1 if it is corrupted. On the other hand, the kernel recognizes the SD card as /dev/mmcblk0p1, so there is a problem when booting. Has this phenomenon ever been reported? I would like to know the exact cause of this phenomenon and how to fix it or prevent this problem? We are looking for a way to recover if this happens during boot up. For example running script that pass hard coded boot parameter to kernel each boot... Because the product must be used in an environment where it is difficult to restrict users, unexpected power off (whether booting or not) may occur. (However, the system must be restored and operational.) We are considering mass production, so I think this is a very important issue. Thanks in advance for the reply. ------------------------------------------------- Environment of use - board : odroid c4 - power : DC 9V, 0.5A - os : ubuntu 18.04 - sdcard : SanDisk Ultra micro 32GB
×
×
  • Create New...