USB fails to boot on one computer, but succeeds on other, and the USB listed in device selection menu's storage volume is waaay lower than it really is

26 views
Skip to first unread message

Frogfessor

unread,
Jun 27, 2020, 4:28:57 AM6/27/20
to qubes-users
I thought it would be pretty fun to start a project like this when I'm always stuck at home, though I haven't been through this many headaches in a while. - __ -  So, the first problem (not the first I've encountered, but the first I'm needing help with) is that whenever I try to boot up the USB containing the Qubes downloader, it starts to boot up like it would usually do, with text scrolling down with (VDT) or whatever it had on the left. Then after a couple seconds, it craps out on me and leaves me with a black screen. Yes, this is flashed with Rufus, set it to MBR, FAT32, and DD. I've tested it out another laptop built about 20 years ago that originally ran Windows XP and it managed to boot up the USB without any problems, except that it doesn't support virtualization. But, either way, I was planning to just flash it onto a live USB anyways. But, my 64gb USB, which has been formatted to FAT32 and has no filed on it, is said to have only about 900 kilobytes of free storage left. When I check in Window's file manager, it says it has full capacity of free storage and I'm able to move files in and out, but the DISKPART manager says it has 0 bytes of free storage! My main computer that's having problems starting the USB is an ACER Nitro, so fairly new. The USB containing the downloader is a 32gb SanDisk 2.0, and the USB I would like to download Qubes to is a 64gb SanDisk 3.0. I'm fairly new to Linux 'n all, but please, I've spent 5 days jumping hurdle after hurdle and researching more and more just to get to this point. ANY help would be greatly appreciated, as I just cannot stand looking over the same web pages and being told to download 3rd party software promising to fix my problems. And please, don't think I'm mad at the devs or anything, I'm sure this is an amazing program, but I'm just pretty tired of this and I've already spent 20 bucks on USBs, so you bet I'm not giving up. Again, any help is greatly appreciated.

dhorf-hfre...@hashmail.org

unread,
Jun 27, 2020, 4:46:42 AM6/27/20
to Frogfessor, qubes-users
On Sat, Jun 27, 2020 at 01:28:57AM -0700, Frogfessor wrote:
> that it doesn't support virtualization. But, either way, I was planning to
> just flash it onto a live USB anyways. But, my 64gb USB, which has been
> formatted to FAT32 and has no filed on it, is said to have only about 900
> kilobytes of free storage left. When I check in Window's file manager, it

you can not install qubes to a fat partition.
delete the fat partition to make the space usable for qubes.
you should be able to do that from the installer.


> the USB I would like to download Qubes to is a 64gb SanDisk 3.0. I'm fairly
> new to Linux 'n all, but please, I've spent 5 days jumping hurdle after
> hurdle and researching more and more just to get to this point. ANY help

i would recommend starting with a plain qubes install in this case
instead of some not-recommended "creative" franken-installation.




Frogfessor

unread,
Jun 27, 2020, 4:57:54 AM6/27/20
to qubes-users
Thanks for the help, I've heard that the download USB should be a fat format but I couldn't find what a live usb should be, so this should help when I try it out. And as for the franken-installation, the website did mention that pretty much the only change needed was to switch to a USB to have a live USB, so if it's not that simple, they should update their website I guess, not to throw shade or anything.

Tobias Gilberg

unread,
Jun 27, 2020, 6:42:55 PM6/27/20
to Frogfessor, qubes-users
Your errors while insalling could probably result from the UEFI
implementation of you Laptop. In the Qubes Documentation under
https://www.qubes-os.org/doc/uefi-troubleshooting/ you find more
information on this.

Installing on a USB Stick is OK for testing but not a complete real
Live System. You normaly can't have a USB-Qube when booting from
USB-Stick, if you have more than one physical USB controller you could
assign all USB controllers to sys-usb exept of the one that you used to
boot. The missing USB qube would only be a problem if BadUSB attacks are
in your threadmodel, otherwise you could just ignore it.

And using it on another machine would result in many problems. It
would likely not boot, because the boot entry is not set (there is a
workaround on this in the uefi-troubleshooting page). And all your AppVMs
with a PCI-Device (e.g. sys-net) attached would likely not boot or boot
in an unexpected behaviour, because the wrong PCI-Device is assigned to
them. This could even result in a crash and reboot, if the wrong
PCI-Device is a GPU.
Reply all
Reply to author
Forward
0 new messages