Okay, where do I start.... Armianmonitor: https://paste.armbian.com/oletimumob I have this ancient Opi+. AND I KNOW THOSE TYPES OF UPDATES ARE NOT SUPPORTED. Yet, they often succeeds and I want to upgrade my system via do-release-upgrade For last six months I am stuck on this, attaching output from putty login screen AND lsb_release as a printscreen My sources.list.d look like this orangepiplus:sources.list.d:% dir armbian-config.sources armbian.list ubuntu.sources orangepiplus:sources.list.d:% cat armbian-config.sources Types: deb URIs: https://github.armbian.com/configng Suites: stable Components: main Signed-By: /usr/share/keyrings/armbian.gpg orangepiplus:sources.list.d:% cat armbian.list deb [arch=armhf signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com jammy main jammy-utils jammy-desktop orangepiplus:sources.list.d:% cat ubuntu.sources Types: deb URIs: http://ports.ubuntu.com/ubuntu-ports/ Suites: jammy jammy-updates jammy-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg orangepiplus:sources.list.d:% Update package noble.tar.gz is downloaded and run, but then it results in this, not sure why? Updating repository information No valid mirror found While scanning your repository information no mirror entry for the upgrade was found. This can happen if you run an internal mirror or if the mirror information is out of date. Do you want to rewrite your 'sources.list' file anyway? If you choose 'Yes' here it will update all 'jammy' to 'noble' entries. If you select 'No' the upgrade will cancel. Continue [yN] y Generate default sources? After scanning your 'sources.list' no valid entry for 'jammy' was found. Should default entries for 'noble' be added? If you select 'No', the upgrade will cancel. Continue [yN] I agree to this but then it results in buttload of Hit/Err 404 errors, for some reason, it is a small part of it: n http://archive.ubuntu.com/ubuntu noble/universe armhf Packages Err http://archive.ubuntu.com/ubuntu noble/restricted armhf Packages 404 Not Found [IP: 91.189.91.81 80] Err http://archive.ubuntu.com/ubuntu noble/main armhf Packages 404 Not Found [IP: 91.189.91.81 80] Err http://archive.ubuntu.com/ubuntu noble/multiverse armhf Packages 404 Not Found [IP: 91.189.91.81 80] Err http://archive.ubuntu.com/ubuntu noble/universe armhf Packages 404 Not Found [IP: 91.189.91.81 80] Ign http://archive.ubuntu.com/ubuntu noble/restricted armhf Packages Ign http://archive.ubuntu.com/ubuntu noble/main armhf Packages Ign http://archive.ubuntu.com/ubuntu noble/multiverse armhf Packages Ign http://archive.ubuntu.com/ubuntu noble/universe armhf Packages Err http://archive.ubuntu.com/ubuntu noble/restricted armhf Packages 404 Not Found [IP: 91.189.91.81 80] Ign http://archive.ubuntu.com/ubuntu noble/main armhf Packages Ign http://archive.ubuntu.com/ubuntu noble/multiverse armhf Packages Ign http://archive.ubuntu.com/ubuntu noble/universe armhf Packages Fetched 508 kB in 6s (84.5 kB/s) It ends like this: es 404 Not Found [IP: 185.125.190.82 80], E:Failed to fetch http://security.ubuntu.com/ubuntu/dists/noble-security/main/binary-armhf/Packages 404 Not Found [IP: 91.189.91.82 80], E:Some index files failed to download. They have been ignored, or old ones used instead. Restoring original system state Aborting Reading package lists... Done Building dependency tree... Done Reading state information... Done === Command detached from window (Wed Apr 30 22:07:17 2025) === By trial and error I managed to overcome this by fully commenting out ubuntu sources (whole file) like this: #Types: deb #URIs: http://ports.ubuntu.com/ubuntu-ports/ #Suites: jammy jammy-updates jammy-security #Components: main restricted universe multiverse #Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Then it does not ask me twice about generating default sources. And this way today it updated around 240 packages, asked for a restart too. But the system remained on 22 jammy. Not sure why it worked. After I run this again i get a buttload of "no candidate ver" errors and it just aborts - this is not a full output. No candidate ver: libpython3.10-minimal No candidate ver: libqt5core5a No candidate ver: libqt5gui5 No candidate ver: libssl3 No candidate ver: python3.10-minimal No candidate ver: resolvconf No candidate ver: rng-tools Restoring original system state Aborting Reading package lists... Done Building dependency tree... Done Reading state information... Done After this, now the system's time is approx 30 min late. Cant seem to fix it either. Unable to systemd-timesyncd because some missing dependency but I will not go into details at this moment. The same happens both on beta releases and stable. Fully updated via armbian-upgrade Where do I start? Clean install would be my LAST effort. I'd hate to do this Where do I begin

I see. For last six months or so I had a hard time upgrading to noble. But this probably needs a separate thread with separate story since it is not really related.

Hello, now tested with 6.12.23 -> handling of my user modules without problems. Regards, Rainer

Hi there, Seems like the kernel is waiting for the wrong filesystem to become available. If blkid shows you PTUUID="8cdc55ae-c576-6f4c-a793-0397a48dccf0 and not any UUID=... associated with a filesystem on that partition, that means that either you do not have a [root] filesystem on that partition or that your root filesystem is on another partition of your SDcard. A PTUUID is the UUID for the partition itself, not for a filesystem. i.e. An empty partition still has a PTUUID. Most (if not all) filesystems have a UUID. Using a UUID makes it easier to have the kernel identify where a/the root filesystem is located. as it is not guaranteed how the storage devices are discovered at boot time. A UUID is linked to the filesystem and not to the device where it is stored on. If you are convinced that you have a root filesystem on a certain partition of your SDcard, you can always use rootdev=/dev/mmcblk1p1 (or wherever your root filesystem lives) in your /boot/armbianEnv.txt to instruct the kernel to expect a root filesystem there. ...but that partition does need to actually have a root filesystem, unless you end up in the same situation you are describing. Can you share the output of sudo parted /dev/mmcblk1 u s pr and sudo blkid -g followed by sudo blkid /dev/mmcblk* ? Groetjes,

Today 6.12 is the current kernel.