Odroid C1 no boot partition Topic is solved

[Raoul]

Hi everyone,

My first post here to share a problem, but first I want to thanks all dev team for this wonderfull distro that I use on my odroid HC1 since a while now.
I found my old odroid C1 and wanted to install Dietpi on it. But there's a problem with images. After flashing with Balena there's a ext4 partition on it (system) and that's it, no boot partition . I try STrech and Buster, same result (see attach screenshot).
So If you can, it will be great to recompile the odroid C1 image with the boot partition.
Thanks dev for all their work!

Raoul

[MichaIng]

The Odroid C1 image is based on Armbian, hence it is a single partition image. /boot is located as well on the ext4 partition. I know the downside is that it cannot easily be pre-configured on a Windows machine .

[Raoul]

Thanks for your reply. I try ARMbian image too and try to change config on an ubuntu desktop, but nothing hapen.
In fact when I power up the odroid C1 the "Alive" led is still ON and the devicee won't appear on my network, with other distro (Official minimal ubuntu) this led is blinking and the device is reachable via ssh. I'm on it now and it's working.

[trendy]

Maybe some configuration change you did was wrong?
Can you try to boot it with defaults and let it acquire settings from dhcp?

[Raoul]

There's what I did:

-Dietpi Jessie, fresh flash, ethernet wired, power on. on 4gb sd card and 32gb (uhs)
Led status, blink (like heart pulse)
dhcp = up
ssh ok but can't pass throught dietpi first run (some sources lacks I think)

-Dietpi Stretch, fresh flash, ethernet wired, power on. on 4gb sd card and 32gb (uhs)
Led status, always on
dhcp = nothing

-Dietpi Buster, fresh flash, ethernet wired, power on. on 4gb sd card and 32gb (uhs)
Led status, always on
dhcp = nothing

-Armbian fresh install, ethernet wired, power on. on 4gb sd card and 32gb (uhs)
Led status, always on
dhcp = nothing

I try to chang only the Uhs line in config after that and nothing change

-Ubuntu minimal 18.04 fresh flash, ethernet wired, power on. on 4gb sd card and 32gb (uhs)
led status : blink (like heart pulse)
dhcp = up
ssh ok

There's no emergency, I was just trying dietpi to install pihole on it but I don't know if it's only me or all C1 owners.

[trendy]

-Dietpi Jessie, fresh flash, ethernet wired, power on. on 4gb sd card and 32gb (uhs)
Led status, blink (like heart pulse)
dhcp = up
ssh ok but can't pass throught dietpi first run (some sources lacks I think)

There's no emergency, I was just trying dietpi to install pihole on it but I don't know if it's only me or all C1 owners.

I have a C1 but the dietpi was flashed long time ago and I do not recall any issues like this.
Can you show us the logs of what fails during first run?

[Raoul]

After a new flash with jessie, I boot directly without updates. Can't launch any dietpi scripts because the system can't find them this is what i try:

Code: Select all

root@DietPi:~# dietpi-config
-bash: /DietPi/dietpi/dietpi-config: No such file or directory
root@DietPi:~# cd /boot/
root@DietPi:/boot#
root@DietPi:/boot# ls
boot.ini         dietpi.txt           System.map-3.10.107        uInitrd
config-3.10.107  initrd.img-3.10.107  System Volume Information  uInitrd-3.10.107
config.txt       meson8b_odroidc.dtb  uImage
dietpi           README.md            uImage-3.10.107
root@DietPi:/boot# cd dietpi/
root@DietPi:/boot/dietpi# ls
boot              dietpi-cleaner     dietpi-drive_manager    dietpi-process_tool  dietpi-sync
conf              dietpi-cloudshell  dietpi-launcher         dietpi-ramdisk       dietpi-update
dietpi-autostart  dietpi-config      dietpi-letsencrypt      dietpi-ramlog        func
dietpi-backup     dietpi-cpuinfo     dietpi-logclear         dietpi-services      login
dietpi-banner     dietpi-cpu_set     dietpi-morsecode        dietpi-software      misc
dietpi-bugreport  dietpi-cron        dietpi-obtain_hw_model  dietpi-survey        patch_file
root@DietPi:/boot/dietpi# dietpi-update
-bash: /DietPi/dietpi/dietpi-update: No such file or directory
root@DietPi:/boot/dietpi# ./dietpi-update
./dietpi-update: line 30: /DietPi/dietpi/func/dietpi-globals: No such file or directory
./dietpi-update: line 31: G_CHECK_ROOT_USER: command not found
./dietpi-update: line 32: G_CHECK_ROOTFS_RW: command not found
grep: /DietPi/dietpi.txt: No such file or directory
grep: /DietPi/dietpi.txt: No such file or directory
./dietpi-update: line 270: G_DIETPI-NOTIFY: command not found
sed: can't read /DietPi/dietpi/.version: No such file or directory
sed: can't read /DietPi/dietpi/.version: No such file or directory
./dietpi-update: line 91: G_DIETPI-NOTIFY: command not found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   196    0   196    0     0    664      0 --:--:-- --:--:-- --:--:--   664
./dietpi-update: line 109: G_DIETPI-NOTIFY: command not found
./dietpi-update: line 91: G_DIETPI-NOTIFY: command not found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    74  100    74    0     0    358      0 --:--:-- --:--:-- --:--:--   359
100    14  100    14    0     0     38      0 --:--:-- --:--:-- --:--:-- 14000
./dietpi-update: line 109: G_DIETPI-NOTIFY: command not found
./dietpi-update: line 155: G_DIETPI-NOTIFY: command not found
root@DietPi:/boot/dietpi#

[Joulinar]

well Jessie is not really supported anymore. And with DietPi 6.29 all scripts are moved from /DietPi directoty to /boot. What you could try to is to create a sym link

Code: Select all

ln -s /boot /DietPi

[Raoul]

Thanks,
after some tries, jessie does not see ext4 partition. but I will not do other test, as you say Jessie is a little bit obsolete, I was trying to be sure that was not a problem with my board or sd cards.

[Joulinar]

well as long as the Armbian base image is not working, DietPi will not be working as well. Behause DietPi needs to have a running Debian Base Image.