Not sure what’s going on here. I get as far as the GRUB(?) Screen asking me how I want to boot (regular install (NOT Grub2), then select the install option that does not have the baud rate that would indicate a serial connection).
Then it throws this error and drops me to an initramfs recovery prompt. find: /l1b/modules/6.6.44-production+truenas/kernel/drivers/md: No such file or directory
I’m using Ventoy to load the boot ISO off a USB flash drive. I’ve used this same Ventoy disk to load the Proxmox Backup Server installer to run memtest86, as well as an Ubuntu 22.04 distro to use some disk tools, both with no issues.
I installed the previous version of TrueNAS Scale (24.04) onto this system with no issues, and it ran fine.
Any suggestions?
EDIT: I still have the 24.04.2.2 ISO. It booted just fine. I’m going to attempt to install that, upgrade to 24.10.2, and import my 24.10.2 config.
For whatever reason, the truenas installer doesn’t work with ventoy. I tried it when i setup my fangtooth test system but it simply wouldn’t work. flashing the iso to a usb with etcher worked.
@LarsR , @neofusion , thanks for that info. I suspected that might be my issue. Unfortunately, and this sounds so stupid to say, I can’t find any other free USB sticks. -_-
As noted in my edit to the original post, I still have the 24.04.2.2 ISO. It booted just fine through Ventoy. I’m now staring at the 24.04.2.2 boot menu. … Unlike my edit above, I’m now scared to attempt installing with it.
Next time choose Grub2. It doesn’t change anything about the installer itself. It’s a menu option created by Ventoy for detected ISOs. It can sometimes allow you to boot the ISO if the first option (“Regular”) does not work.
Thanks! I went ahead and installed 24.04.2.2 since I still had the ISO and I knew it worked, and upgraded that to 24.10.5 once I was into the web console.
24.10 fresh installs don’t use a 16 GB swap file on the install disk, so I didn’t use a swap when the 24.04.2.2 installer asked for one.
Now … the nerve-wracking moment of reimporting my previous config from my old install.
I tried this with ventoy recently. Choosing grub2 results in the same error. It would seem something changed in the installer between 24.04 and 24.1. I haven’t tried writing it directly to a usb device (ssd or flash). Had 24.04 on ventoy so installed and upgraded that.
Ventoy has put out a beta which appears to fix this issue.
Personally, I don’t mind using ventoy in testing purposes, but anything that will go into actual production will get the iso/img written directly to usb media (flash drive, ssd, etc). It’s probably nothing, but I feel safer doing so.
Using actual real install media is absolutely the way, but … it’s become really inconvenient in the last few years, oddly enough.
Even super-garbage free USB 3.0 USB flash drives that just get given away are like 128 GB now–and those are junk and do misbehave.
I’ve accumulated a small collection of good 128-512 GB flash drives, but wiping and flashing them with something like a 3 GB ISO always feels wasteful and makes me wonder if I’m killing the drive faster than I should.
I need to find some actual good 8-16 GB USB 3 flash drives.
Ventoy, for all its faults, is faster and feels less wasteful when you just need to throw a random ISO around.
Ideally, I’d finally get an in-network PXE-boot system set up that can serve ISOs, and point blank systems at that.
That’s why I use an external ssd. I imagine that controls where on the flash writes occur better than a flash drive (where sector 0 is likely the same physical place each time).
When I mount an iso on a vps, before installing I’ll run a sha256sum after booting into it.
Compare this to the sha256sum ran on the iso itself. Still, I suppose this only accounts for the mounted iso being unaltered. With ventoy, can’t really verify memory contents. It’s not out of the realm of possibility to inject something that runs at a lower layer.
PXE booting using fully open source tools sounds like the right way to go.
