I used ventoy to transfer the file to an external ssd like I do with all my OS files but I’m un able to install Qubes unless I used the testing release file which does initiate but gets stuck stating issue with anaconda install. Every other method just brings me right back to my main pop OS login. I am new to Linux in general hoping this is is easy fix. Please help extremely aggravated this isn’t working for me. hope the picture helps. I’m using a Lenovo ideapad AMD ryzen 7
Qubes is picky with how you create install USB. Best method is using dd
QubesOS won’t install from Ventoy.
You must use either dd or Fedora Image Writer or Rufus with “dd” writing method or maybe Unebotin if it have “dd” writhing method.
1 Like
Whats DD? Sorry my linux lingo is bottomshelf lol ill try rn
Is that an option within an image writer? its saying rufus isnt available for linux
Hi cleverusername - and welcome to the forum! 
The install guide got this section:
1 Like
DD is a command line program, don’t use it if you are new to Linux… you can accidentally wipe your main OS drive
Rufus is for windows. Maybe try fedora image writer. I don’t know, I just use dd, it’s built in to every Linux distro and it always work with Qubes
If you are not knowledgeable with Linux, qubes will be hard to understand. Also, the default is fedora qubes mostly and pop is debian.
I think I got the genereal understanding of how it works I just dont know any of the commands really. From what I have deduced you need to be in the directory that the fike is located in, know the file size and the name of your destination right? If you show me the command i can fill it on with my data. I’m nott as green as I may have portrayed initially. plus I really need the multiple VM layout and admire the security and capabilities! Thank you guys for aiding me btw I will get through this I swwear.
I tried to use popsicle to flash it just becasusr it was already installed and ot did had the same issue
Sure, just open up gparted or gnome disks to see all your attached disks. Make sure not to use any of the /dev/ devices except the USB you want to write the installer USB to.
Then open the terminal in the folder that has the iso (right click open in terminal)
sudo dd if=nameOFiso of=/dev/sdx bs=32M status=progress
Where name of iso is the if= part and /dev/sdx is replaced with USB path (maybe /dev/sdb or a depending on how many sata drives you have connected
The install guide adds:
conv=fsync
to the dd-command … and from the man dd [1] this result in:
fdatasync
physically write output file data before finishing
fsync likewise, but also write metadata
– without the fsync, parts of the data might still only be in memory and not yet on the USB-stick. If you leave out the conv=fsync, you can manually flush the data to disk, by running the command sync.
[1]: You can use q to quit man
1 Like
Wait, i need to add this to the end of my command?
Hi cleverusername.
The documentation has the command as:
sudo dd if=Qubes-RX-x86_64.iso of=/dev/sdY status=progress bs=1048576 conv=fsync
… so if you follow the documentation, you should already have the conv=fsync in your command.
If you don’t have conv=fsync, you should flush the data from memory to the disk with sync, before you remove the USB-stick[1].
[1]: A shutdown of the computer, should also flush the data from memory to the disk.
ok. Bs is byte size right? i have to enter the size of the fike here? so gb would be 4gb is 4000000
From man dd and searching (by typing /bs=) it should be:
bs=BYTES
read and write up to BYTES bytes at a time (default: 512); over‐
rides ibs and obs
further down, there is the section:
N and BYTES may be followed by the following multiplicative suffixes:
c=1, w=2, b=512, kB=1000, K=1024, MB=1000*1000, M=1024*1024, xM=M,
GB=1000*1000*1000, G=1024*1024*1024, and so on for T, P, E, Z, Y, R, Q.
Binary prefixes can be used, too: KiB=K, MiB=M, and so on. If N ends in
’B’, it counts bytes not blocks.
does this have to be in there to insure the entire file is written? I have seen others just use the from and to locations. they were not trying to copy stubborn qubes either though
Hi cleverusername.
You want to put the ISO on the device (/dev/sdX) and not on a partition (/dev/sdXy). With the /dev/sda1 you try to put it on the first partition (y='1') … and note, that everything on the device will be lost, so make sure you have the right device-name in the command (in your example, X='a').
1 Like
It’s not specifying the byte size (or total size of the iso), it is the block size (specifying how big each chunk of data it writes is). Higher number means faster transfer, the default is stupid low. You can use what Chris specified or what I did. I specified M for mine because I don’t want to write out that long oddly specific number. It’s certainly not the total file size for the iso because that changes each version and they’d need to update it
I know the fsync is suggested by qubes docs but I’ve never used it and done about 50 qubes iso dd operations with zero issues
so don’t hit enter on what I have in that picture? I already accidentally erased everything on that dang hard drive so it doesn’t matter