Skip to content
View in the app

A better way to browse. Learn more.
Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

OrangePi PC no boot

hanni76
in Armbian build framework

Featured Replies

Hello,

all images for OrangePI PC (next) produced  since yesterday give the following output:

-----------------------------------

U-Boot SPL 2017.11-armbian (Dec 03 2017 - 17:13:28)
DRAM: 1024 MiB
Trying to boot from MMC1
Uncompressing Linux... done, booting the kernel.
Loading, please wait...
starting version 232
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
-------------------------------

 

An old image is booting fine.

 

Any ideas?

Thanks

 

  • Author

I found that UUID specified in armbianEnv.txt is wrong (???). I have no idea why this happened... One reason to come to my mind is that I mounted a Samba share to "armbian/build/output/images". I am going to try a new build without it.

It seems like the problem didn't exist couple of days ago.

 

--------------

ALERT!  UUID=4dc850bc-ea4c-436a-8a3f-57793795e7a4 does not exist.  Dropping to a shell!

--------------

The image was created in Virtualbox. I never seen this before when I was making builds on the "hardware" host.

I have attached serial port log.

minicom.log

  • Author

Here is the build log when image was created:

 

-------------------

[ o.k. ] Preparing image file for rootfs [ orangepipc stretch ]
[ o.k. ] Current rootfs size [ 942 MiB ]
[ o.k. ] Creating blank image for rootfs [ 1456 MiB ]
1.42GiB [70.7MiB/s] [================================================================================================================>] 100%
[ o.k. ] Creating partitions [ root: ext4 ]
[ .... ] Creating rootfs [ ext4 ]
[ .... ] Copying files to root directory 
        885.87M  99%   37.06MB/s    0:00:22 (xfr#30842, to-chk=0/38646)   

sent 888.22M bytes  received 620.71K bytes  37.82M bytes/sec
total size is 890.87M  speedup is 1.00
[ .... ] Copying files to /boot directory 
         24.57M  99%  133.73MB/s    0:00:00 (xfr#154, to-chk=0/161) 

sent 24.59M bytes  received 2.97K bytes  49.18M bytes/sec
total size is 24.57M  speedup is 1.00
[ o.k. ] Free space: [ SD card ]
Filesystem                     Size  Used Avail Use% Mounted on
udev                           2.0G     0  2.0G   0% /dev
tmpfs                          396M  5.9M  390M   2% /run
/dev/sda1                       57G   17G   38G  32% /
tmpfs                          2.0G     0  2.0G   0% /dev/shm
tmpfs                          5.0M     0  5.0M   0% /run/lock
tmpfs                          2.0G     0  2.0G   0% /sys/fs/cgroup
//192.168.3.50/smb-toolchains  170G   92G   69G  58% /home/sergey/Projects/armbian/build/cache/toolchains
//192.168.3.50/smb-qt5-build   170G   92G   69G  58% /home/sergey/Projects/qt5-build
//192.168.3.50/smb-boards      170G   92G   69G  58% /home/sergey/Projects/boards
tmpfs                          396M     0  396M   0% /run/user/1000
tmpfs                          2.6G  942M  1.7G  36% /home/sergey/Projects/armbian/build/.tmp/rootfs-next-orangepipc-stretch-no
/dev/loop0p1                   1.4G  957M  396M  71% /home/sergey/Projects/armbian/build/.tmp/mount-next-orangepipc-stretch-no
[ o.k. ] Writing U-boot bootloader [ /dev/loop0 ]
[ o.k. ] Done building [ /home/sergey/Projects/armbian/build/output/images/Armbian_5.36_Orangepipc_Debian_stretch_next_4.14.3.img ]
[ o.k. ] Runtime [ 26 min ]
 

-----------------------------------------------------------------------------------------------

 

One interesting detail:  /dev/loop0 is not unmounted in the end and is still visible in blkid.

 

  • Author
26 minutes ago, Igor said:


I can't confirm or deny if we have some problems since we changed few things and I haven't really made an image in the last 24h. 

Any idea why that UUID didn't match or didn't exist at all? When I check SD card on host Ubuntu it looks ok.

  • Author

Here is log file from "hardware" host:

 

------------------------

[ o.k. ] Free space: [ SD card ]
Filesystem      Size  Used Avail Use% Mounted on
udev            5,9G     0  5,9G   0% /dev
tmpfs           1,2G   27M  1,2G   3% /run
/dev/sda4       156G   22G  126G  15% /
tmpfs           5,9G  171M  5,7G   3% /dev/shm
tmpfs           5,0M  8,0K  5,0M   1% /run/lock
tmpfs           5,9G     0  5,9G   0% /sys/fs/cgroup
/dev/sda5       170G   97G   64G  61% /home/sergey/Projects
/dev/sda6        92G   68M   87G   1% /home/sergey/Public
/dev/sda7       105G   60M  100G   1% /home/sergey/Projects2
tmpfs           1,2G  100K  1,2G   1% /run/user/1000
tmpfs           7,8G  314M  7,5G   4% /home/sergey/Projects/armbian/build/.tmp/rootfs-next-orangepipc-stretch-no
/dev/loop0p1    547M  320M  205M  61% /home/sergey/Projects/armbian/build/.tmp/mount-next-orangepipc-stretch-no

 

 

 

  • Author

Hardware host, Ubuntu 16.04, produces working images. So the problem exists only in Virtualbox.

IMAGES (without any customization) CREATED IN VIRTUALBOX DO NOT BOOT.

i.e. Virtualbox can't be considered as a reliable platform for building Armbian images. At least until I find a reason why this happens.

  • Author

Ok, 

the problem is Stretch release only.  Stretch built on "hardware" host does not have any issue.

 

  • Author

Finally resolved the issue. It was caused by an issue in custom device tree file which made linux boot fail silent. 

Guest
This topic is now closed to further replies.
Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.