[frostschutz]

Mh, could be the soldered-in memory needs a slightly different storage driver, which may not be included in the whatever you're booting there. Thus the internal storage would be invisible. Basically it's not mounted neither, so 'mount' just lists sd card stuff, yes? OTOH it does not make sense since according to the direct firmware download, H2O and Aura are family, use same firmware and same kernel.

So - no idea what's going on there. Unless it is, after all, the internal storage you're seeing. Does the system crash when you take out the SD card and then do something like, uh, `find /` or `cat /dev/mmcblk0 > /dev/null`? or whatever?

With/out access to the internal storage there is not much you can do.

Can you post the output of this script?

#!/bin/sh
set -x
mmc_detect() {
    local error=1
    for driver in /sys/bus/platform/drivers/*/unbind
    do
        driver=$(dirname "$driver")
        for device in "$driver"/*/
        do
            if [ -e "$device"/mmc_host/mmc${1:-0} ]
            then
                MMC_DRIVER="$driver"
                MMC_DEVICE=$(basename "$device")
                error=0
            fi
        done
    done

    return $error
}
mmc_detect
echo $MMC_DRIVER $MMC_DEVICE

(This is part of my Magic Memory Upgrade mod)

----

Also I tried to boot from the ext. SD slot on the H2O to no avail. If this can be done somehow, it's not an [entirely] automatic process. Simply putting the int. card in the ext. slot does not do the trick. Putting an empty/zeroed card in the int. slot does not change anything either. My guess is it would at least need U-Boot and somehow make U-Boot detect it needs to run the ext. SD card instead the internal one.

----

Also, the output of `hexdump -C -s 512 -n 64 /dev/mmcblk0`?

It should show a serial number. If it starts with N250 it should be a H2O image you're seeing. Maybe just changing that to something Aura (not sure which number it uses) would somehow make it operate in Aura mode.