root fs not mountable after upgrade

[heikow]

Hi there,
after upgrade Armbian today the Device (banana-pi) doesnt come up again telling that the root fs couldnt be mount because mmcblk0p1 is not available.
After checking SD Card everything seems ok, filesystem is there and doesnt have any error. But still no boot.
Then after applying a backup things are fine again.
Started the upgrade again and same error like before.

When applying those two updates there is repeatedly a dead system afterwards. Tested on different devices now.

root@gluster01:~# apt list --upgradable
Listing... Done
armbian-config/unknown 25.5.0-trunk.330.0402.205255 all [upgradable from: 25.5.0-trunk.286.0324.065110]
linux-image-current-sunxi/bullseye 25.2.3 armhf [upgradable from: 25.2.3]
root@gluster01:~#

Could someone other also confirm this or is there any idea about what is going wrong?

Thanks!!

best regards,
Heiko

 

[Igor]

Moved to Allwinner section as this is not an user space problem. 

 

1 hour ago, heikow said:

after upgrade Armbian today the Device (banana-pi)

 

Percentage of breakage on not supported and (also not supported) trunk / untested / nightly build is very high. What you experience, under those circumstances, it is normal and expected. 

[heikow]

Hi Igor;
thanks for your fast answer and sorry for the wrong section!!

Not sure if I got this right ... do you mean that my banana-pi isnt supported or the trunk I use is not supported? ...
I checked this and dont see any repo like untested or nightly build. Its configured to just use main and stable as I see.

 

[Igor]

This is custom hardware world, not general purpose Linux.

 

53 minutes ago, heikow said:

banana-pi

There are 15 x Bananapi https://www.armbian.com/download/?tx_maker=sinovoip and every device has its own firmware. There are similarities, sure, which help, but if one boots and works fine, perhaps others won't. We keep images for those too, as some still might work.
 

53 minutes ago, heikow said:

trunk I use is not supported?

Trunk = development branch, changes daily. There was never ever support for that. This is for developers and experienced users, which are able to fix the problems as such.

 

And even when "standard support" is declared, when whole SW stack is stabilized to some degree, it means "high level of software maturity" and you are welcome to share your frustration with everyone. Nobody can provide warranty on software support where users contribute less then 0.5% of costs for making it usable. In general. 

For specific - you need to share all data and logs, and then maybe someone will have a clue on what is happening here.

 

[eselarm]

2 hours ago, heikow said:

linux-image-current-sunxi/bullseye 25.2.3 armhf [upgradable from: 25.2.3]

If your userspace is also still Bullseye, you have to provide more info or just figure out yourself. I updated my BananaPi-M1 earlier this week, but runs Bookworm. I need to look-up what U-Boot I have installed, but I have a serial console cable permanently connected to another SBC, so in case it does not come online (no IP connection), I look at what the serial console port spits out. That is what you also need to do I guess. Kernel 6.6.75-current-sunxi work fine for me, was unattended upgrade+reboot.

[heikow]

thanks for helping

sorry @Igor my post should not sound like frustration or any other bad thing!! I really appreciate the work and for sure many many hours everybody puts into this project!! 
I just wondered why things stop working after an upgrade which looks "easy"  for a noob like me and try to find out if this is something I made wrong or if others also run into the same thing 

Here some more details about my setup, sorry to miss this initially

Banana-Pi M1 (yes, the old one with native SATA )
Here the actual version which is running fine for me.
 

root@gluster03:~# uname -a
Linux gluster03 6.6.75-current-sunxi #1 SMP Sat Feb  1 17:37:57 UTC 2025 armv7l GNU/Linux

 

Then I have started an update as there are two packages which are outdated

 

root@gluster03:~# apt update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease                                      
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease                                    
Hit:5 https://github.armbian.com/configng stable InRelease                                         
Hit:4 http://netcup.armbian.com/apt bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@gluster03:~# 

 

root@gluster03:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  armbian-config linux-image-current-sunxi
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/40,6 MB of archives.
After this operation, 139 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 41042 files and directories currently installed.)
Preparing to unpack .../armbian-config_25.5.0-trunk.330.0402.205255_all.deb ...
Unpacking armbian-config (25.5.0-trunk.330.0402.205255) over (25.5.0-trunk.298.0327.034426) ...
Preparing to unpack .../linux-image-current-sunxi_25.2.3_armhf.deb ...
Armbian 'linux-image-current-sunxi' for '6.6.75-current-sunxi': 'prerm' starting.
Armbian 'linux-image-current-sunxi' for '6.6.75-current-sunxi': 'prerm' finishing.
Armbian 'linux-image-current-sunxi' for '6.6.75-current-sunxi': 'preinst' starting.
Armbian 'linux-image-current-sunxi' for '6.6.75-current-sunxi': 'preinst' finishing.
Unpacking linux-image-current-sunxi (25.2.3) over (25.2.3) ...
Armbian 'linux-image-current-sunxi' for '6.6.75-current-sunxi': 'postrm' starting.
Armbian 'linux-image-current-sunxi' for '6.6.75-current-sunxi': 'postrm' finishing.
Setting up linux-image-current-sunxi (25.2.3) ...
Armbian 'linux-image-current-sunxi' for '6.6.75-current-sunxi': 'postinst' starting.
dkms: running auto installation service for kernel 6.6.75-current-sunxi:.
update-initramfs: Generating /boot/initrd.img-6.6.75-current-sunxi
Armbian: update last-installed kernel symlink to 'zImage'...
'/boot/zImage' -> 'vmlinuz-6.6.75-current-sunxi'
Armbian: Debian compat: linux-update-symlinks install 6.6.75-current-sunxi boot/vmlinuz-6.6.75-current-sunxi
Armbian 'linux-image-current-sunxi' for '6.6.75-current-sunxi': 'postinst' finishing.
Setting up armbian-config (25.5.0-trunk.330.0402.205255) ...
root@gluster03:~# 

so far so good .. looks fine for me and I am just wondering about the linux image which tells the same version before and after upgrade .. same for Kernel 6.6.75

Now after reboot I get the output attached as Image as I have no serial adapter for the console messages.

When I check the SD Card everything is fine and there are no errors .. all files seems fine ... but this is where boot ends from now on.
What I am wondering is that the fsck works for exactly the device (mmcblk0p1) which was reported as not available in the next step.

If there are other things needed please give me a little hint .. I am not a developer so those things are new to me as it just worked like a charm for at least 10 years until yesterday 

 

[Igor]

27 minutes ago, heikow said:

why things stop working after an upgrade

 

Without maintaining, those boards (upgrades) simply stop working. This is one of the ways how it manifests. Features starts to break apart and we have to spent insane amount of time trying to keep this herd operational. Every board has its own caveats. And here we also have OS release upgrade - deprecated OS. There are enough of troubles without that.

 

35 minutes ago, heikow said:

for a noob like me

 

Start with a new image and see if it works. Upgrade from Bullseye to Bookworm is problematic and I advise you to not deal with that if you are not experienced.