Fairly new user of qubes os and learning as i go along. I have read alot on this forum plus done research privately.
I have a usb stick attached to my personal cube that i want to have my qubes backup stored on, However there is not enough space remaining on the usb to store the back up to and i want to know how i can format the usb stick from qubes.
Attach your key on a Vm.
Find the key with df -h.
umount it like sudo umount /dev/xvdi1 (where xvdi1 is your key for example]
Then format it:
for for fat32: sudo mkfs.vfat -F 32 /dev/xvdi1
for ntfs: sudo mkfs.ntfs /dev/xvdi1
i tried the df -h in dom0 and did not saw the usb. ever since then each time i try to attach the usb to a vm i get this error. ââattaching device usb_flash_disk() to personal failed. Error : QubesDaemonAccessError-Got empty response from qubesd. See journalctl in Dom0 for details.ââ.
I tried removing the usb and inserting and attempt to attach to qubes and i get the same error message
then click on your usb stick and then on the icon at the top right with the 3 dots
choose the disk format option
then according to image 2 click âformatâ
You mean Disks app? Itâs preinstalled in GNOME templates (e.g. debian-12) but itâs not preinstalled in XFCE templates (e.g. debian-12-xfce) so you need to install it there before you can use it.
@zach2mack For the record, formatting a USB stick (or 99% of tasks, for that matter) is identical on Qubes OS as it is on whatever Linux distribution your template is based onâŚonce you are able to get the VM to be able to interact with the resource you want.
In plain English, this means that if you know how to format a USB stick on GNU/Linux, you know how to format a USB stick on Qubes OS once you can get it into the VM.
@zach2mack This error is concerning. It suggests that your sys-usb qube is malformed, of if you donât have a sys-usb qube, youâre qubesd configs are corrupted, or misconfigured.
@Tezeria is right in that getting an empty response from qubesd when trying to attach a block device to a VM means that something somewhere isnât doing what it should be doing.
In plain English, it means that sys-usb asked dom0 to attach your USB stick to a VM, and dom0 basically ignored it.
This is by design.
VMs are not supposed to receive a response to requests that they are not authorised by dom0 to issue, in case they are compromised (hacked) and start trying to âmapâ your machine internally
But that defeats the whole purpose of sys-usb, if you canât use it to pass devices through
Is there any chance you could upload some of your system journal when this happened? (redact any sensitive information, of course)
If all else fails, and you feel comfortable using a terminal, you should be able to open a sys-usb terminal and issue the relevant commands to format your USB stick.