While testing the Xubuntu 26.04 daily release it seems to be having problems finding system drives during install, I’ve tried full and minimal, enabled and disabled secure boot and nothing seems to work, what could be causing this ?
Some drive modes can do it. Make sure it’s set to AHCI.
It’s definitely set to AHCI in Bios as I have a previous Xubuntu install for 24.04.
In the live session, before starting the installer, open a terminal and check if the drives are being recognized.
lsblk
sudo fdisk -l
Yeah lsblk and fdisk -l are both seeing the drives and snap mounts just fine, but it seems that when running the installer it see’s no drives connected (could it be because installer is snap-based ?).
I would suggest filing a bug report on Launchpad.
1 Like
Believe me I’ve tried, I’ve jumped through so many hoops and sign in’s looking for a bug report page for this one issue, which is why I’m here trying to talk to some actual people in the hope of a simple fix.
Does this describe the issue you are seeing?
2 Likes
Yeah, you get to “How do you want to install?” screen and nothing appears.
Please post the output here of sudo fdisk -l, wrapped with code tags.
Have you tried manually formatting the relevant drive with GParted before starting the installer?
I’m experiencing the same situation, I’ve tried installing Ubuntu 26.04 beta and Ubuntu Budgie 26.04 beta, my system has a 1tb NVME drive, I’m booting from a USB using Ventoy. When I run “sudo fdisk -l” I get a list of loop entries, I see my USB (2 partitions) and my NVME (I tried with MBR and GPT). Any other suggestions of what to do?
I switched to Kubuntu 26.04 and their installer works fine 
I had a USB laying around and I made it into a bootable USB, and that fixed the problem, I just finished installing it. I think using Ventoy to boot is what causes issues with the Ubuntu Installer.
Did you try my suggestion of manual partitioning before starting the Xubuntu installer?
If I have time over the weekend, I will test it in a VM and report back here with any findings.
EDIT: sorry, was not able to reproduce this scenario.
Downloaded the latest daily build and everything ran and installed as expected.
I must add that it might be this. I had the exact same problem while using a Ventoy drive. I burned the ISO traditionally and I could proceed after the disk setup screen.