[Solved][Cubox-i] Not Booting after uboot-cubox-i update

[slycat]

Ran pacman -Syu, included a uboot-cubox-i update, allowed the flash to happen to /dev/mmcblk0
Cannot reboot system after this

Broken or did something wrong happen during the flash?

[moonman]

Any boot log? The nice thing about cubox is that uart converter is built in, jist need a micro usb cable.

[slycat]

Flashed a backup i made before the last update, no dice

I do not have a microUSB on me, but I did see errors along the lines of
$this->bbcode_second_pass_code('', 'File /boot.scr not found
File /zImage not found
File /uEnv.txt')
It seems like the boot folder is not being seen during the boot up

Tried duping the boot folder from a fresh install tarball and flashed the SPL & u-boot.img, and no luck

Any idea? or should I hunt down a friend with a microUSB cable?

[moonman]

Uboot is not the problem then. If you are seeing these messages then SPL and uboot have been loaded successfully. Check your uEnv and make sure it passes the right partition to the kernel, especially if your rootfs is on a different storage device or partition. For reference this is what I have in my uEnv:
$this->bbcode_second_pass_code('', 'mmcargs=setenv bootargs root=PARTUUID="77d79668-01" rootwait rw elevator=bfq console=tty1 console=ttymxc0,115200 consoleblank=0 video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24,bpp=16 dmfc=3 ahci_imx.hotplug=1 pci=nomsi loop.max_part=15')

fsck your drive also.

If nothing above helps then yeah, you will need that cable to see what's going on.
(BTW, the messages you are seeing are expected as uboot tries to load those files from different locations)

[slycat]

Copy, I can confirm that a number of items for the startup are also being initiated (brcmf, ata connection, mounting fstab entries) but ends at the "Enter root password to enter Maintenance Mode" break.

I can't look at my backup img until later today but I know for a fact I do not have the "root=PARTUUID=" flag nor the loop.max_part (unsure what this is though) in my backup uEnv.txt. The box ran fine and would reboot without issue before.

Also I tried using the uEnv.txt from a fresh install tarball into my backup img; fresh install works but this method of duping the boot dir does not, even on older backup imgs.
Besides the /boot dir what could cause a boot failure: missing files in /bin, /proc, /sys?

will fsck the microSD after I check the uEnv.txt, and thanks for pointing out the usual boot messages

[moonman]

$this->bbcode_second_pass_quote('slycat', 'C')opy, I can confirm that a number of items for the startup are also being initiated (brcmf, ata connection, mounting fstab entries) but ends at the "Enter root password to enter Maintenance Mode" break.

[slycat]

Played with fstab and commented out all entries: nothing
Checked uEnv.txt and saw for some reason it was pointing mmcroot to mmcblk0p2 (use to point to p1); changed back: nothing

Decided to use just the uEnv.txt from a fresh install onto my backup image mixed with the fstab edit and all is running. Seems like my old system had boot stored on a separate partition and was still trying to find it.

Solved. Thanks moonman

[moonman]

Glad you solved it