1 1
Aoz

Cubox-i does not boot anymore after the last armbian upgrade

Recommended Posts

Hi,

 

I am running Debian Strech on a headless server with armbian (since 2014 on wheezy), on a Cubox-i 4 Pro.

My system is on /dev/sda1

 

After an upgrade, few minutes ago, my device is no more reachable by ssh neither answering to ping.

It seems to boot the kernel but I am not even sure of that (as nothing appears in the console after "booting the kernel").

 

Here is the full console log:

U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...


U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   vga
Err:   vga
Net:   FEC [PRIME]
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Hit any key to stop autoboot:  0
mmc0 is current device
** File not found /boot.scr **
** File not found /uEnv.txt **
** File not found /zImage **
** File not found /uImage **
1816 bytes read in 127 ms (13.7 KiB/s)
Running bootscript from mmc ...
## Executing script at 10800000
** File not found .next **
48 bytes read in 114 ms (0 Bytes/s)
36853 bytes read in 826 ms (43 KiB/s)
4636514 bytes read in 411 ms (10.8 MiB/s)
5839840 bytes read in 482 ms (11.6 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x591be0 ]
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4636450 Bytes = 4.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800bff4

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

 

Files located in /boot on the SDCard (same files list in sda/boot):

-rw-r--r-- 1 root root   48 janv. 30 18:28 armbianEnv.txt
-rw-r--r-- 1 root root   79 janv. 30 18:28 armbianEnv.txte
-rw-r--r-- 1 root root 1,8K sept. 20 22:33 boot.cmd
-rw-r--r-- 1 root root 1,8K sept. 20 22:33 boot.scr
-rw-r--r-- 1 root root  360 déc.  27  2015 boot.txt
-rw-r--r-- 1 root root 160K févr.  8 09:33 config-4.14.98-cubox
-rw-r--r-- 1 root root 162K févr.  8 09:38 config-4.19.20-cubox
lrwxrwxrwx 1 root root   17 févr. 16 17:47 dtb -> dtb-4.19.20-cubox
drwxr-xr-x 2 root root  12K févr. 16 17:42 dtb-4.14.98-cubox
drwxr-xr-x 2 root root  12K févr. 16 17:31 dtb-4.19.20-cubox
-rw-r--r-- 1 root root 4,2M févr. 16 17:09 initrd.img-4.14.98-cubox
-rw-r--r-- 1 root root 4,5M févr. 16 17:09 initrd.img-4.19.20-cubox
-rw-r--r-- 1 root root 2,5M févr.  8 09:33 System.map-4.14.98-cubox
-rw-r--r-- 1 root root 2,6M févr.  8 09:38 System.map-4.19.20-cubox
lrwxrwxrwx 1 root root   21 févr. 16 17:47 uInitrd -> uInitrd-4.19.20-cubox
-rw-r--r-- 1 root root 4,2M févr. 16 17:09 uInitrd-4.14.98-cubox
-rw-r--r-- 1 root root 4,5M févr. 16 17:09 uInitrd-4.19.20-cubox
-rwxr-xr-x 1 root root 5,4M févr.  8 09:33 vmlinuz-4.14.98-cubox
-rwxr-xr-x 1 root root 5,6M févr.  8 09:38 vmlinuz-4.19.20-cubox
lrwxrwxrwx 1 root root   21 févr. 16 17:48 zImage -> vmlinuz-4.19.20-cubox

 

$ more boot.txt  
setenv bootargs root=/dev/sda1 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi ahci_imx.hotplug=1 consoleblank=0 vt
.global_cursor_default=0 quiet
ext2load mmc 0 0x18000000 /boot/dtb/${fdt_file}
ext2load mmc 0 0x12000000 /boot/zImage
bootz 0x12000000 - 0x18000000

 

$ more armbianEnv.txt
verbosity=1
rootdev=/dev/sda1
usbstoragequirks=

 

What else could I provide as information to get help?

Thanks a lot to anybody that could give me some support...

 

Board: Cubox-i, Hummingboard / Gate & Edge

Share this post


Link to post
Share on other sites

I changed "verbosity" to 7 in armbianEnv.txt but nothing more is displayed.

 

I also tried to boot with the hard drive *not* plug to the cubox-i and the output is exactly the same... strange no?

Share this post


Link to post
Share on other sites
19 minutes ago, Aoz said:

I changed "verbosity" to 7 in armbianEnv.txt but nothing more is displayed.

Make sure that you have "console=serial" in /boot/armbianEnv.txt and use USB-TTL Serial dongle to watch the boot logs .

Share this post


Link to post
Share on other sites

Thank for the support.

 

Here is now the full content of /boot/armbianEnv.txt:

verbosity=7
rootdev=/dev/sda1
console=serial   
usbstoragequirks=

What does "usbstoragequirks=" means?? Should I erase that?

 

Anyway, it is now much verbose!

 

And I can see that, at the end of the boot logs:

 

Begin: Will now check root file system ... fsck from util-linux 2.29.2
[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1
kiposSystem contains a file system with errors, check forced.
random: crng init done                                        - 16.8%
random: 7 urandom warning(s) missed due to ratelimiting
Inode 397759, end of extent exceeds allowed value
        (logical block 64, physical block 559296, len 24)


kiposSystem: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
fsck exited with status code 4
done.
Failure: File system check of the root filesystem failed
The root filesystem on /dev/sda1 requires a manual fsck

I am going to fsck the hard drive...

Share this post


Link to post
Share on other sites

After running fsck and correcting some error, everything went fine...   \o/

 

Thank you a lot martinayotte!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
1 1