New Seagate usb hdd to use for backups. Successfully attached to Personal vm according to Qubes. But after opening Personal: Files the drive isn’t showing up as an option in + Other Locations . In the Personal: Terminal entering lsusb shows the drive present on usb bus 002. I would prefer to access the drive via the gui if possible for backups. Looking in the Qubes Documentation hasn’t led to seeing anything promising. What am I missing please?
Some progress. But now a new puzzle. I connected an old sata hdd in a usb 3.0 external case, attached it to the Personal vm and was also not able to see this drive in the + Other window → until it magically appeared sometime after an hour later. I was then able to do a backup on this drive. So I then reattached the Seagate usb hdd, which I was originally trying to use for backups and let it sit for quite some time, after which this drive did appear as well for use. The refined original question now becomes, why the delay? It’s definitely a Qubes thing, as both drives are readily accessible on another box running linux mint.
1 Like
Try to open your HDD in sys-usb. It should work like on a regular Linux system. If it doesn’t or you can’t connect it to other qubes, it’s probably a bug like these:
opened 07:15AM - 27 Apr 22 UTC
T: bug
P: default
hardware support
C: usb proxy
needs diagnosis
[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/)
#… ## Qubes OS release
Qubes 4.0
### Brief summary
An external USB drive is sometimes not detected by the system at all. Unplugging and replugging the drive does nothing. No messages in `journalctl` in sys-usb or dom0. No notifications. `qvm-block` remains empty. Rebooting dom0 usually fixes it, but only temporarily until it stops working again. The machine (ThinkPad T450s) is suspended each day, which may or may not be related to the problem.
### Steps to reproduce
1. Have a USB drive plugged in.
2. Start sys-usb.
### Expected behavior
sys-usb consistently detects the USB drive.
### Actual behavior
sys-usb sometimes detects the USB drive and sometimes does not. When it stops working, dom0 has to be restarted before it will work again.
Please let me know if there any other logs I can check.
USB device attach failed · Issue #5997 · QubesOS/qubes-issues · GitHub
opened 06:26PM - 24 Jul 20 UTC
T: bug
C: core
P: default
hardware support
needs diagnosis
No answer in #qubes IRC.
**Qubes OS version**
R4.0
**Affected component(s… ) or functionality**
sys-usb
**Brief summary**
Trying to attach an device from sys-usb to another HVM, it works when using a different device, the mounting works great as well.
**To Reproduce**
(1) sys-usb or dom0 terminal.
(2) attach the usb to the HVM.
$ qvm-usb attach "HVM machine" sys-usb:"id"
Domain 'HVM machine': qrexec not connected
When trying a different USB-device, it works and I can mount it to the "HVM machine".
**Expected behavior**
Should be able to attach and mount USB-device.
**Actual behavior**
qrexec not connected on "USB-device(1)"
Works fine on "USB-device(2)"
**Solutions you've tried**
Attaching a different "USB-device", + mount, works.
**Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted**
https://www.qubes-os.org/doc/usb-devices/
opened 03:11PM - 15 Dec 19 UTC
T: enhancement
C: Xen
P: default
**Qubes OS version**
R4.0 with all updates
**Affected component(s) or func… tionality**
Kernel? dom0? sys-usb?
**Brief summary**
HW: Thinkpad T470s, Orico NVME M.2 SSD enclosure
If I plug in the USB-C SSD **into the USB-C/Thunderbolt port**, there is no reaction at all. lsusb in sys-usb does not show it, the usb menu does not show it.
If I plug it **into a normal USB3 port** (using a cable that converts from USB-C to USB-A connector), it works as expected: shows up in lsusb, shows up in the usb menu, can be assigned to a VM, can be used in a VM.
The external SSD case is based on the JMicron 152d:0583 USB-C to PCIe bridge and has a Samsung M.2 NVME/PCIe SSD inside.
**Solutions you've tried**
I have installed all Qubes updates, did a cold boot of the machine.
Also checked the Thinkpad T470s' BIOS to see whether Thunderbolt/USB-C functionality is disabled (it is not, it is enabled, "no security" thunderbolt setting).
Also cold booted with the USB-C device already attached, did not help.
Also tried another USB-C cable, did not help.
opened 08:17PM - 25 Apr 19 UTC
T: bug
C: manager/widget
P: default
needs diagnosis
I'm experiencing a strange issue during testing, at times attaching a device (yu… bikey) does nothing at all. The device does not get attached. Although the device does show in the list it simply does not get attached to the vm. The only solution is to kill qui-devices which then restarts itself and then its possible to attach again, or to attach the device via command line (qvm-usb)
_Originally posted by @yubiguel in https://github.com/QubesOS/qubes-issues/issues/4849#issuecomment-486752685_
opened 01:56PM - 28 Jun 18 UTC
T: bug
C: Fedora
### Qubes OS version:
R4.0
### Affected component(s):
qubes-usb-proxy (pre… sumably)
---
### Steps to reproduce the behavior:
Create an appvm based on Fedora28 and set the AppVM to use the fedora distribution kernel.
Start the AppVM and then try to attach a USB device to it.
### Expected behavior:
I expect the USB device to be available in the AppVM
### Actual behavior:
The attaching operation fails with an error notification but no actual error message. The dmesg output of the AppVM shows messages like:
```
[ 6718.250243] audit: type=1100 audit(1530193705.290:218): pid=2645 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:authentication grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success'
[ 6718.253883] audit: type=1103 audit(1530193705.292:219): pid=2645 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:setcred grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success'
```
(full log is included below)
### General notes:
Kernel Version:
`Linux app-vm-name 4.16.9-300.fc28.x86_64 #1 SMP Thu May 17 06:39:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux`
qubes-usb-proxy version:
```
$ sudo dnf install qubes-usb-proxy
Last metadata expiration check: 2:58:45 ago on Thu 28 Jun 2018 12:55:33 PM CEST.
Package qubes-usb-proxy-1.0.18-1.fc28.noarch is already installed, skipping.
```
---
### Related issues:
None of this would be an issue for me if it would be possible to compile kernel modules for the qubes kernel instead of only the fedora distribution's own kernel ( https://github.com/QubesOS/qubes-issues/issues/3835 and https://github.com/QubesOS/qubes-issues/issues/2844 )
### Full errror log:
```
[ 6718.250243] audit: type=1100 audit(1530193705.290:218): pid=2645 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:authentication grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success'
[ 6718.253883] audit: type=1103 audit(1530193705.292:219): pid=2645 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:setcred grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success'
[ 6718.272225] audit: type=1101 audit(1530193705.311:220): pid=2646 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:accounting grantors=pam_unix acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 6718.278249] audit: type=1006 audit(1530193705.311:221): pid=2646 uid=0 subj=kernel old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=5 res=1
[ 6718.281222] audit: type=1105 audit(1530193705.311:222): pid=2646 uid=0 auid=0 ses=5 subj=kernel msg='op=PAM:session_open grantors=pam_selinux,pam_selinux,pam_loginuid,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 6718.317358] audit: type=1130 audit(1530193705.354:223): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=user@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 6718.320294] audit: type=1105 audit(1530193705.355:224): pid=2645 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_lastlog acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success'
[ 6719.563729] audit: type=1106 audit(1530193706.603:225): pid=2645 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_lastlog acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success'
[ 6719.569140] audit: type=1104 audit(1530193706.603:226): pid=2645 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:setcred grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success'
[ 6719.590771] audit: type=1131 audit(1530193706.630:227): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=user@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
```
You might want to contribute your logs to an issue or create another one.
Thanks fsflover. I had a look at the links, but so far haven’t been able to figure the problem out. If I open Qubes Devices on the top menu, the plugged-in drive is listed at the bottom: sys-usb:3-6 - Seagate_Expansion_HDD, etc. If I highlight that line, vm’s including Personal appear in the submenu box, but no sys-usb. I seemingly can successfully attach the Seagate to the Personal vm, the sys-usb:3-6 line shows up in Bold and the progress notifications state that the drive has been attached to the Personal vm. But then, if I open Personal-files-and then click on +Other Locations, I don’t get the Seagate listed, where I’m expecting to see it.
adw
May 5, 2022, 7:28am
5
After you attach the device to your personal qube using the Qubes Devices widget, what’s the output of qvm-block in dom0?
It should say that the device is attached to the personal qube as xvdi or similar. Perhaps the problem is that the storage device hasn’t been formatted with an appropriate filesystem or something. If the device is accessible from inside the personal qube, you could try formatting it with, e.g., mkfs.ext4. (Obviously don’t do this if there’s any data on it you care about, but you said it’s new, so it sounds like it’s already empty.)
adw
May 5, 2022, 7:43am
6
Oops, didn’t read the subsequent updates about the time-delayed puzzle. I have no idea, sorry.
The HDD goes to sys-usb automatically, before you connect to anything else. It should appear in its filesystem immediately when you connect it. This VM accepts and isolates all USB devices; they should work in it like in a regular Linux distro.