Device No Longer Boots After Armbian Update

  • I'm running OMV 7.5.0-1 on Armbian 24.11.1 on a Radxa Rock Pi 4A. Like so many others, I fell prey to the loss of network access after the update to OMV 7.5, but being a hoarder of computer equipment -- and existing in the same physical space as my device, unlike some unfortunate souls -- I was able to connect a monitor and keyboard, run omv-firstaid, and get back in business. That's not what this post is about, though.


    Another automated update occurred shortly after the one above, including the following items: armbian-firmware, base-files, linux-dtb-current-rockchip64, linux-headers-current-rockchip64, linux-image-current-rockchip64. When I rebooted the system as instructed, the device would no longer boot to completion.


    I have since disassembled my NAS, which required disconnecting the drive array (4 SSDs in a RAID 5 configuration), and now my device will boot again (though I have no HOME partition, since that's located on the array). This leads me to believe that OMV is no longer able to mount the drive array, and that this is preventing the boot process from continuing.


    Can someone with the relevant knowledge suggest to me what the best course of action would be to solve this issue? I have a high level of comfort with Linux, but physical devices have never been my strong suit.


    Thanks!


    Matt

    Radxa 4GB ROCK 4A, 32GB eMMC, 4x Samsung 1TB 860 EVO SSD in RAID 5

    OMV 7.5

    Armbian Bookworm

    • Official Post

    When I rebooted the system as instructed, the device would no longer boot to completion.

    Any error messages during boot process when you connect a display to see them?


    Are you able to enter a terminal and check the logs, e.g. with dmesg

  • It would appear that my issue is ultimately one with Armbian. I found a post on the Armbian forums from someone who is having a similar issue. It appears that the change in kernel from 6.6.63 to 6.12.9 resulted in the drives connected to the NVMe interface to no longer be recognized.


    I have a display and keyboard connected and there haven't been any pertinent error messages, but also in my effort to roll back the kernel version, I managed to cause the device not to boot for other reasons. I am able to boot off of an SD though, and I can mount the onboard eMMC, so once I've preserved anything that I might need, I may just start over again from scratch.

    Radxa 4GB ROCK 4A, 32GB eMMC, 4x Samsung 1TB 860 EVO SSD in RAID 5

    OMV 7.5

    Armbian Bookworm

  • The issue was absolutely because of the kernel update. I changed all of the relevant links in /boot to use 6.6.63 versions instead of 6.12.9 versions and I'm back in business again, exactly as before.

    Radxa 4GB ROCK 4A, 32GB eMMC, 4x Samsung 1TB 860 EVO SSD in RAID 5

    OMV 7.5

    Armbian Bookworm

  • chente

    Added the Label resolved
  • chente

    Added the Label OMV 7.x

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!