Jump to content
  • 0

Unbootable images? Only old image I am using seems to work


0xFF
 Share

Question

Good morning,

 

I cannot seem to get the the newest image (22.08 Bullseye) to boot.  I've noticed the disk arrangement is significantly different than the known working image I am using.

 

Here is what I see on the known working image...

#fdisk -l

Disk /dev/mmcblk0: 28.9 GiB, 30985420800 bytes, 60518400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2A33F1A5-75EA-4125-AC19-16C0435D774A

Device          Start      End  Sectors  Size Type
/dev/mmcblk0p1     64     8063     8000  3.9M Linux filesystem
/dev/mmcblk0p2  16384    24575     8192    4M Linux filesystem
/dev/mmcblk0p3  24576    32767     8192    4M Linux filesystem
/dev/mmcblk0p4  32768   262143   229376  112M EFI System
/dev/mmcblk0p5 262144 60518366 60256223 28.7G Linux filesystem

 

#cat /etc/debian_version 
9.9

 

 

The newest image is in has a DOS partition table and only one partition.

Disk /dev/sdc: 28.91 GiB, 31016878080 bytes, 60579840 sectors
Disk model: STORAGE DEVICE  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1640add5

Device     Boot Start     End Sectors  Size Id Type
/dev/sdc1       32768 3833855 3801088  1.8G 83 Linux

 

 

Also may be important to note my rock pi S has no onboard flash, only SD slot. 

 

Am I missing something?  Thank you for your time.

 

 

 

 

Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0
7 hours ago, 0xFF said:

Good morning,


Good evening :rolleyes: This image (I assume you tried that) https://redirect.armbian.com/rockpi-s/Bullseye_edge boots on my Rockpi S Logs: https://paste.armbian.com/huvaluwuvi

 

7 hours ago, 0xFF said:

disk arrangement is significantly different

 

Armbian images are not using vendors proprietary partition arrangements. Most (almost all) our images are single partition. 

 

7 hours ago, 0xFF said:
cat /etc/debian_version


Irrelevant information. "Debian" plays not role here:

https://docs.armbian.com/User-Guide_FAQ/

https://www.armbian.com/bugs (console boot log would be extremely helpful)

 

7 hours ago, 0xFF said:

Also may be important to note my rock pi S has no onboard flash, only SD slot. 

 

My has it and in that case you need to follow instructions on this page https://www.armbian.com/rockpi-s/ Perhaps your hardware revision is unable to boot modern software?

 

@brentr Any ideas?

Link to comment
Share on other sites

Armbian Linux community supported weekly builds download

  • 0

hello again and thank you for your response.

 

1. Yes the link you have provided to  Armbian_22.08.7_bullseye_edge is the image i have tried with no luck on the SD card.  It does not even seem to load the bootloader, and I have no serial output with the 22.08.7 image.  Could the SD card require a different partition expectation than the on board flash?   I am still new regarding how the board knows where to look in which flash device for how to boot.

 

The serial output of the working image (rockpis_debian_stretch_minimal_arm64_190806_0234-gpt.img) I have placed here https://paste.armbian.com/lubowiroji .  If this image is pushed on to an SD card it loads without pushing any buttons.

 

2. For the difference in partitioning, in the radxa image has partition 4 as EFI and contains the kernel/rd.  Would it be of any value to try and replicate the partition by extracting the contents of the boot directory in the Armbian bullseye image?  I would like to help.

 

 

 

Link to comment
Share on other sites

  • 0
3 hours ago, 0xFF said:

Could the SD card require a different partition expectation than the on board flash?


Partition type is not relevant as boot process happens outside. Don't know exactly how different is RK3308 from this https://opensource.rock-chips.com/wiki_Boot_option but you get the picture.

 

3 hours ago, 0xFF said:

I have no serial output with the 22.08.7 image


Are you listening on correct UART? Stock firmware could use a different one. You are clearly having different hardware revision as our test device and this could already be good enough reasons why it doesn't boot. Perhaps modern boot loader does not have support for different memory chips or similar. 

 

3 hours ago, 0xFF said:

I would like to help.


We can help dealing you with your problem more, when our problems are covered. Since budget for what you are asking here is way less then zero, we can only provide best effort support. If you want to help boosting this hardware support for you, everyone else and our competition, just find a way to finance development. 

 

If you want to help, forget about your problem and focus on common problems. List is a bit outdated, because HR staff also wants to eat something.

Link to comment
Share on other sites

  • 0

Hello @0xFF, I have the same issue as you, last working image for me is Armbian_21.08.1_Rockpi-s_bullseye_current_5.10.60_minimal.img.xz

All newer images could not boot, and UART is silent.

 

As a workaround I flashed and booted that version and then just did :

 

apt update && apt upgrade

 

then the new version Armbian 22.11.4 Bullseye with Linux 5.15.89-rockchip64 booted up without any issue.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...