BeagleBone Black 2.166 - Kernel panic

clean install of new image ver. 2.166 on BeagleBone Black - Kernel panic:

[code]Volumio data partition succesfully resized
Model: SD USD (sd/mmc)
Disk /dev/mmcblk0: 8010MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 4.19MB 62.9MB 58.7MB primary fat16 boot, lba
2 64.0MB 2500MB 2436MB primary ext4
3 2500MB 8010MB 5510MB primary ext4

mount: mounting /mnt/static on /mnt/ext/union/static failed: Invalid argument

Finish initramfs, continue booting Volumio
switch_root: can’t execute ‘/sbin/init’: No such file or directory
[ 39.104744] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 39.104744]
[ 39.113993] CPU: 0 PID: 1 Comm: switch_root Not tainted 4.8.13-botic7-rc3 #1
[ 39.121094] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 39.127294] [] (unwind_backtrace) from [] (show_stack+0x11/0x14)
[ 39.135122] [] (show_stack) from [] (panic+0xa5/0x1b8)
[ 39.142077] [] (panic) from [] (do_exit+0x84f/0x85c)
[ 39.148843] [] (do_exit) from [] (do_group_exit+0x2f/0x90)
[ 39.156133] [] (do_group_exit) from [] (SyS_exit_group+0x13/0x14)
[ 39.164036] [] (SyS_exit_group) from [] (ret_fast_syscall+0x1/0x4c)
[ 39.172116] —[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 39.172116]

yes, we noticed a similar crash on cubox and working on it. This will take a little time.
Sorry about this.

The issue has been resolved, click here to download version 2.173

No kernel panic anymore, booting properly. Thanks for update.
shairport-sync is still old (2.4) in 2.173 - what a pity!

Why isn’t this pushed yet? The website’s download page is still stuck at 2.166.

but does not stop you from downloading the corrected version, does it?

Sorry if this sounds rude,
but is it asked for too much for just noting at the download page that there the newest image (2.166) isn’t working? I wasted several hours of my life in trying to get the new version running on my BBB. Even the release notes don’t have a note for this bug! I know this can happen, but this is not best practice at all. And IF someone here in the forum is writing that the “newest” image isn’t working, please don’t let it even appear on your download page!
Yes, I’m angry, because of the waste of time. And not only mine!
Otherwise I like to use Volumio, but please take more care in getting the old things to work, when the people start to feel that the quality, stability and reliability of volumio is starting to degrade, they will look for another solution. It would be really a pity!
E.g., your alsa or another part seems to have a bug in comparision to volumio 1.55, because the split command isn’t working, as you can reed in, look for miero’s thread.
Volumio has the chance to become the technological most advances distribution, just because it supports the BBB, because the BBB has the best I²S interface by hardware design, and this is a great chance! But is has to work flawlessly.

Hi Matthias, we will work to solve this issue, with miero work.
Please understand that BBB, as other devices, is developed on a best effort basis, since we cannot give the same attention to everything.