XU4 next + nand-sata-install + USB disk --> rootfs not found


tkaiser

Recommended Posts

I'm struggling with XU4/HC1 and the try to have the rootfs on a connected USB disk. All attempts end up with:

Gave up waiting for root file system 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/sda1 does not exist.  Dropping to a shell!
Rebooting automatically due to panic= boot argument

I tried USB disks on USB3 and USB2 ports, according to leds and spin-up sound the SSDs/HDDs get power but device doesn't show up. I remember vaguely that we had such issues on other platforms where it was just a small missing bit in kernel config. But I don't get it even after spending an hour on searching around.

 

2 times boot log with high verbosity, maybe someone else has a clue: https://pastebin.com/ffnQK2Pm 

Link to post
Share on other sites
Donate and support the project!

19 minutes ago, tkaiser said:

I remember vaguely that we had such issues on other platforms where it was just a small missing bit in kernel config. But I don't get it even after spending an hour on searching around.

I beleve it was CONFIG_CHR_DEV_SG, and it is set to built-in on xu4-next. And even if it was a module it would be loaded from initrd.

You can try investigating it further by replacing "panic=10" with "break=premount" in the build script kernel command line, it should give you a minimal shell.

Link to post
Share on other sites
On 7.9.2017 at 6:51 PM, zador.blood.stained said:

Just tested XU4 next, install to USB drive (new board support package but an older boot script) and it worked fine for me.

 

Sorry for the late feedback. In the meantime I tested a new build with latest bootscript and it didn't boot at all. Was too lazy to connect serial console (since running a test on HC1 in parallel where the adapter was connected to) and thought 'Seems Zador is preparing whole switch to armbianEnv.txt so let's wait for this happen'. But now I wonder whether you're still preparing stuff or not?

Link to post
Share on other sites
4 minutes ago, tkaiser said:

Sorry for the late feedback. In the meantime I tested a new build with latest bootscript and it didn't boot at all.

Didn't boot before nand-sata-install or after?

 

5 minutes ago, tkaiser said:

But now I wonder whether you're still preparing stuff or not?

Currently a bit busy, but since I bought a bunch of fresh SD cards for tests several days ago at least I won't be having a problem with finding a good card for the test.

Link to post
Share on other sites
1 minute ago, zador.blood.stained said:

Didn't boot before nand-sata-install or after?

 

Before. And highly frustrated that day since wasted hours already due to stupid mistakes I made and some unfortunate decisions (build host related). Boot failure --> putting XU and HC1 in the drawer waiting for you finalizing armbianEnv.txt vs. boot.ini stuff.

 

Only positive result from this day back then was the finding that symlinking cache/sources and cache/toolchains from a btrfs force-compression=zlib partition doesn't hurt performance wise (while savong over 100% needed storage)

Link to post
Share on other sites
1 minute ago, tkaiser said:

waiting for you finalizing armbianEnv.txt vs. boot.ini stuff.

Unfortunately currently there is a "hack" for all boot.ini based configurations that deletes armbianEnv.txt, and we can either getting rid of it all together (requires tests on Odroid C1/C0 boards which use a very old u-boot) or introducing more hacks on top of existing ones.

Link to post
Share on other sites
12 minutes ago, zador.blood.stained said:

Unfortunately currently there is a "hack" for all boot.ini based configurations that deletes armbianEnv.txt, and we can either getting rid of it all together (requires tests on Odroid C1/C0 boards which use a very old u-boot) or introducing more hacks on top of existing ones.

 

Well, I would prefer the least hackish attempt but fear I can't help much since I've no serial cable for my C1+ / C2 (as I understood the serial cable for XU4/HC1 is not compatible to the other boards since 1.8V vs. 3.3V)?

Link to post
Share on other sites
16 minutes ago, tkaiser said:

as I understood the serial cable for XU4/HC1 is not compatible to the other boards since 1.8V vs. 3.3V

The wiki suggests that it's compatible (it has a 4th wire for voltage reference)

 

_____UART____
|Pin 4 - GND|
|Pin 3 - RXD|
|Pin 2 - TXD|
|Pin 1 - VCC|
\___________|

1.8V LVTTL for ODROID-U3/XU3/XU4/X2/X
3.3V LVTTL for ODROID-C1/C1+/C0/C2/W

RxD pin is input and TxD pin is output.

The VCC pin is not a power source but a reference voltage input.
It is used for detecting the IO voltage like a VIO or a VDDIO.
Support for I/O interface voltages down to 1.8 V is provided via a VIO pin.

 

Link to post
Share on other sites
23 hours ago, tkaiser said:

Sorry for the late feedback. In the meantime I tested a new build with latest bootscript and it didn't boot at all.

Maybe this has something to do with it

Processing file /home/zador/armbian/patch/u-boot/u-boot-odroidxu4-next/cfgload-support-ext4.patch
1 out of 2 hunks FAILED -- saving rejects to file cmd/cfgload.c.rej

I'll update the patch and push the fixes a bit later.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.