Both VSIDO FSA's were updated to the new 6.11.5-amd64 kernel

You can download the btrfs and ext4 fsarchives at the VSIDO download site here

There is also a How To on how to effectively use fsarchiver to get VSIDO installed

There is a current a package list that shows everything that is installed in VSIDO. Please review this file and let me know of anything needed, removed or added

*poof*

And out of nowhere I throw myself in the mix.......

Just downloaded and it took less than two min. Thanks for all your hard work, guys!

Both VSIDO FSA's were updated to the new 6.10.12-amd64 kernel

You can download the btrfs and ext4 fsarchives at the VSIDO download site here

There is also a How To on how to effectively use fsarchiver to get VSIDO installed

There is a current a package list that shows everything that is installed in VSIDO. Please review this file and let me know of anything needed, removed or added

Both VSIDO FSA's were updated to the new 6.10.11-amd64 kernel

You can download the btrfs and ext4 fsarchives at the VSIDO download site here

There is also a How To on how to effectively use fsarchiver to get VSIDO installed

There is a current a package list that shows everything that is installed in VSIDO. Please review this file and let me know of anything needed, removed or added

Quote from: DeepDayze on August 30, 2024, 03:32:13 PM

Quote from: VastOne on April 18, 2024, 02:42:23 PM

Quote from: DeepDayze on April 18, 2024, 01:41:59 PMBummer. Fsarchiver as a backup/restore tool for BTRFS then is no bueno. There should be some sort of override so that you can restore a BTRFS .fsa with its original UUID.

It's really a security feature to make sure that you don't have multiple instances of the same UUID booting.. IMO, the ext4 part should do the same but does now.

You could try this format above using the uuid you want to see if it would work, I never tried to restore with the exact same uuid, it may be possible. I'll test this as well

You should be able to restore your own .fsa's with same UUID.

Recent updates now allow this to happen. Not sure when it started, but you can now install on same machine with same uuid on it elsewhere

Both VSIDO FSA's were updated to the new 6.10.7-amd64 kernel

You can download the btrfs and ext4 fsarchives at the VSIDO download site here

There is also a How To on how to effectively use fsarchiver to get VSIDO installed

There is a current a package list that shows everything that is installed in VSIDO. Please review this file and let me know of anything needed, removed or added

Quote from: VastOne on April 18, 2024, 02:42:23 PM

Quote from: DeepDayze on April 18, 2024, 01:41:59 PMBummer. Fsarchiver as a backup/restore tool for BTRFS then is no bueno. There should be some sort of override so that you can restore a BTRFS .fsa with its original UUID.

It's really a security feature to make sure that you don't have multiple instances of the same UUID booting.. IMO, the ext4 part should do the same but does now.

You could try this format above using the uuid you want to see if it would work, I never tried to restore with the exact same uuid, it may be possible. I'll test this as well

You should be able to restore your own .fsa's with same UUID.

Both VSIDO FSA's were updated to the new 6.10.6-amd64 kernel

You can download the btrfs and ext4 fsarchives at the VSIDO download site here

There is also a How To on how to effectively use fsarchiver to get VSIDO installed

There is a current a package list that shows everything that is installed in VSIDO. Please review this file and let me know of anything needed, removed or added

Solved! The workaround was as followed which layed out here by Ash Joubert and within a chroot settings I did exactly as Ash said

Workaround was to boot from an older kernel/initrd, manually download the previous packages, downgrade to them, and then hold them.

dpkg -i kmod_32+20240611-1_amd64.deb libkmod-dev_32+20240611-1_amd64.deb libkmod2_32+20240611-1_amd64.deb
apt-mark hold kmod libkmod-dev libkmod2
I am now booted back into the nvme system. This shows how important it is to search for the exact messages which I got when I ran update-initramfs -k 6.10.4-amd64 -u in chroot and it showed the KMOD5 errors.

Thanks, that is the end of my TED speech for tonight, thank you all for attending

Found the issue but not the answer here. I need to somehow down grade LIBKMOD_5 in a chroot setting