USB hard disk falls asleep when inserted in USB 3.0 port and attached to AppVM

Singer · December 27, 2023, 1:11pm

Does anyone know the phenomenon that a USB disk falls asleep when it is mounted by sys-usb in an AppVM? It is then not displayed in Nautilus in the AppVM and therefore cannot be used. However, the phenomenon only occurs if the hard disk designed for USB 3.0 is plugged into a USB 3.0 port. Does anyone know how to use the hard disk not only in sys-usb, but also in an AppVM?

apparatus · December 27, 2023, 1:26pm

Maybe there is some debug info in the logs in sys-usb or AppVM to which you’re attaching it?

Singer · December 27, 2023, 2:53pm

Do you know, where to look for the log file?

apparatus · December 27, 2023, 3:16pm

You can see the logs using journalctl command.
You can also run this command in VM:

sudo journalctl -f

Then attach the USB and check the logs output during this time.

Singer · December 27, 2023, 3:26pm

I ran

sudo journalctl -f

in sys-usb before attaching the drive to my AppVM. This is the error log:

Dec 27 18:20:26 sys-usb-dvm systemd[1]: Started User Manager for UID 0.
Dec 27 18:20:26 sys-usb-dvm systemd[1]: Started Session c4 of user root.
Dec 27 18:20:26 sys-usb-dvm kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
Dec 27 18:20:26 sys-usb-dvm kernel: sd 2:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 27 18:20:26 sys-usb-dvm kernel: usbip-host 3-2: usbip-host: register new device (bus 3 dev 3)
Dec 27 18:20:26 sys-usb-dvm kernel: usbip-host 3-2: stub up
Dec 27 18:20:26 sys-usb-dvm mtp-probe[1645]: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:07.0/usb3/3-2"
Dec 27 18:20:26 sys-usb-dvm mtp-probe[1645]: bus: 3, device: 3 was not an MTP device
Dec 27 18:20:28 sys-usb-dvm xdg-desktop-por[1536]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Dec 27 18:20:48 sys-usb-dvm kernel: usbip-host 3-2: unlinked by a call to usb_unlink_urb()

The drive shuts down when trying to attach it to the AppVM.

apparatus · December 27, 2023, 3:32pm

What’s the output of this command in AppVM when you attach drive to it?

sudo journalctl -f

Singer · December 27, 2023, 4:35pm

It says:

Dez 27 19:28:52 AppVM kernel: usb 2-1: USB controller vhci_hcd.0 does not support streams, which are required by the UAS driver.

The full output is:

Dez 27 19:28:51 AppVM qrexec-agent[2132]: 2023-12-27 19:28:51.739 qrexec-agent[2132]: qrexec-agent-data.c:244:handle_new_process_common: executed: root:QUBESRPC qubes.USBAttach dom0 (pid 2134)
Dez 27 19:28:51 AppVM qrexec-agent[2134]: pam_unix(qrexec:session): session opened for user root(uid=0) by (uid=0)
Dez 27 19:28:51 AppVM systemd[1]: Created slice User Slice of UID 0.
Dez 27 19:28:51 AppVM systemd[1]: Starting User Runtime Directory /run/user/0...
Dez 27 19:28:51 AppVM systemd[1]: Finished User Runtime Directory /run/user/0.
Dez 27 19:28:51 AppVM systemd[1]: Starting User Manager for UID 0...
Dez 27 19:28:51 AppVM systemd[2136]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Dez 27 19:28:51 AppVM systemd[2136]: Queued start job for default target Main User Target.
Dez 27 19:28:51 AppVM systemd[2136]: Created slice User Application Slice.
Dez 27 19:28:51 AppVM systemd[2136]: Reached target Paths.
Dez 27 19:28:51 AppVM systemd[2136]: Reached target Timers.
Dez 27 19:28:51 AppVM systemd[2136]: Starting D-Bus User Message Bus Socket.
Dez 27 19:28:51 AppVM systemd[2136]: Listening on debconf communication socket.
Dez 27 19:28:51 AppVM systemd[2136]: Condition check resulted in Sound System being skipped.
Dez 27 19:28:51 AppVM systemd[2136]: Listening on D-Bus User Message Bus Socket.
Dez 27 19:28:51 AppVM systemd[2136]: Reached target Sockets.
Dez 27 19:28:51 AppVM systemd[2136]: Reached target Basic System.
Dez 27 19:28:51 AppVM systemd[2136]: Condition check resulted in Sound Service being skipped.
Dez 27 19:28:51 AppVM systemd[2136]: Condition check resulted in Tracker metadata extractor being skipped.
Dez 27 19:28:51 AppVM systemd[2136]: Condition check resulted in Tracker file system data miner being skipped.
Dez 27 19:28:51 AppVM systemd[2136]: Reached target Main User Target.
Dez 27 19:28:51 AppVM systemd[2136]: Startup finished in 93ms.
Dez 27 19:28:51 AppVM systemd[1]: Started User Manager for UID 0.
Dez 27 19:28:51 AppVM systemd[1]: Started Session c6 of user root.
Dez 27 19:28:52 AppVM kernel: vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(0)
Dez 27 19:28:52 AppVM kernel: vhci_hcd vhci_hcd.0: devid(327682) speed(5) speed_str(super-speed)
Dez 27 19:28:52 AppVM kernel: vhci_hcd vhci_hcd.0: Device attached
Dez 27 19:28:52 AppVM kernel: usb 2-1: SetAddress Request (3) to port 0
Dez 27 19:28:52 AppVM kernel: usb 2-1: new SuperSpeed USB device number 3 using vhci_hcd
Dez 27 19:28:52 AppVM kernel: usb 2-1: New USB device found, idVendor=XXXa, idProduct=0XXX, bcdDevice= 3.01
Dez 27 19:28:52 AppVM kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dez 27 19:28:52 AppVM kernel: usb 2-1: Product: USB 3.0 Device
Dez 27 19:28:52 AppVM kernel: usb 2-1: Manufacturer: USB 3.0 Device
Dez 27 19:28:52 AppVM kernel: usb 2-1: SerialNumber: 00000000XXXX
Dez 27 19:28:52 AppVM kernel: usb 2-1: USB controller vhci_hcd.0 does not support streams, which are required by the UAS driver.
Dez 27 19:28:52 AppVM kernel: usb 2-1: Please try an other USB controller if you wish to use UAS.
Dez 27 19:28:52 AppVM kernel: usb-storage 2-1:1.0: USB Mass Storage device detected
Dez 27 19:28:52 AppVM kernel: usb-storage 2-1:1.0: Quirks match for vid XXXa pid 0XXX: 1000000
Dez 27 19:28:52 AppVM kernel: scsi host0: usb-storage 2-1:1.0
Dez 27 19:28:52 AppVM mtp-probe[2180]: checking bus 2, device 3: "/sys/devices/platform/vhci_hcd.0/usb2/2-1"
Dez 27 19:28:52 AppVM mtp-probe[2180]: bus: 2, device: 3 was not an MTP device
Dez 27 19:28:52 AppVM mtp-probe[2200]: checking bus 2, device 3: "/sys/devices/platform/vhci_hcd.0/usb2/2-1"
Dez 27 19:28:52 AppVM mtp-probe[2200]: bus: 2, device: 3 was not an MTP device
Dez 27 19:28:52 AppVM qrexec-agent[2134]: pam_unix(qrexec:session): session closed for user root
Dez 27 19:28:52 AppVM qrexec-agent[2132]: 2023-12-27 19:28:52.738 qrexec-agent[2132]: qrexec-agent-data.c:272:handle_new_process_common: pid 2134 exited with 0
Dez 27 17:29:02 AppVM xdg-desktop-por[2092]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Dez 27 17:29:14 AppVM kernel: vhci_hcd: unlink->seqnum 40
Dez 27 17:29:14 AppVM kernel: vhci_hcd: urb->status -104
Dez 27 17:29:14 AppVM kernel: usb 2-1: SetAddress Request (3) to port 0
Dez 27 17:29:14 AppVM kernel: usb 2-1: reset SuperSpeed USB device number 3 using vhci_hcd

apparatus · December 27, 2023, 4:41pm

apparatus · December 27, 2023, 4:43pm

Maybe it’s possible to disable UAS and it’ll work but it’s just a guess:

apparatus · December 27, 2023, 4:50pm

fsflover · December 27, 2023, 9:16pm

Might be related:

github.com/QubesOS/qubes-issues

External USB drives possibly interrupting backup by going to sleep

opened 09:57AM - 30 Sep 22 UTC

AlbertGoma

T: bug C: core P: critical hardware support C: usb proxy needs diagnosis affects-4.1

### Qubes OS release Upgrade from 4.0 to 4.1.1 ### Brief summary When doing… a backup of relatively large VMs on an external USB drive the motor stops spinning at a certain point and the resulting file contains only a sequential portion of the data. It's already mentioned it in my comment in issue #7567 as this might be a cause for I/O errors and the fix could probably solve both issues. ### Steps to reproduce 1. Attach an external USB hard drive (in this particular scenario, a 3.5" SATA hard drive on a USB 3.0 dock) with a valid partition table, enough space and a healthy filesystem (in this case GPT and ext4). 2. Start a non-networked disposable VM and mount the drive's _block_ device **sys-usb:sda** (not the USB device) on it. 4. Start the _Qubes Backup_ tool and select around 40 VMs with a few of them having a storage use over 200GiB each, exceeding 900GiB in total. Have some of those GiB filled from /dev/zero and some others from /dev/urandom, just in case. 6. Uncheck the _Compress backup_ checkbox and click _Next_. 7. Set the disposable VM as the _Target qube_ and choose a _Backup directory_ in the external hard drive's filesystem. 8. Click _Next_ until the backup starts. 9. Wait until the backup is apparently finished and the hard drive motor has stopped spinning. ### Expected behavior The restored VMs' logical volumes' storage byte count is identical to the original one before starting the backup. ### Actual behavior In the _Qubes Backup Restore_ tool an I/O error popped out and half of the VMs showed 0 bytes of _Disk Usage_ in the _Qube Manager_. When doing an [emergency recovery](https://www.qubes-os.org/doc/backup-emergency-restore-v4/) all of those 0-byte VMs had an **Unexpected EOF** error in all of their chunks when decrypting them with _scrypt_. One of the VMs' chunks were readable until the 490'th.

Singer · December 28, 2023, 10:25am

Okay, here is the same issue:

github.com/QubesOS/qubes-issues

Some USB storage devices cannot be attached to VM because of VHCI controller does not support streams.

opened 11:34AM - 13 Dec 21 UTC

closed 07:19AM - 08 Jan 22 UTC

jevank

T: bug P: default hardware support diagnosed C: storage

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release R4.1 (I guess 4.0 too) ### Brief summary UAS driver in VM tries to init device with streams support but fails with such messages: ``` [ +0.029211] usb 2-1: USB controller vhci_hcd.0 does not support streams, which are required by the UAS driver. [ +0.000029] usb 2-1: Please try an other USB controller if you wish to use UAS. ``` It could be fixed with disabling UAS kernel support and using usb-storage driver instead which leads to performance regression (about 10% as I understand). With linux VM could be used block attaching, but with Windows VMs it is not stable enough. It might be enough to disable UAS in stubdomain kernel. ### Steps to reproduce Attach via qvm-usb USB storage HDD device with USB streams support (usual large than 2Tb) ### Expected behavior Storage available in VM. ### Actual behavior Attaching fails.

But how to solve it?

Singer · December 28, 2023, 10:38am

Here is a guide to disabling UAS for a specific usb device, but it needs a reboot of the VM. How to disable USB Attached Storage (UAS) - Leo's Notes

apparatus · December 28, 2023, 12:18pm

You can add kernel option:

usb-storage.quirks=0bc2:3322:u

To your qube using qvm-prefs in dom0 terminal:

s=$(qvm-prefs -- vmname kernelopts) && qvm-prefs -- vmname kernelopts "usb-storage.quirks=0bc2:3322:u $s"

Singer · December 28, 2023, 1:24pm

Lets say, my AppVM is set to the kernel option “nopat”. If I want to add an option, I have to run qvm-prefs -s AppVM kernelopts "nopat usb-storage.quirks=0bc2:3322:u, thats all?

apparatus · December 28, 2023, 1:47pm

Yes, but you can remove -s since it’s not needed.

Singer · January 2, 2024, 9:35am

There is a simple solution: Attach device to an AppVM, detach and reattach. The device will wake up. Or use a script in dom0:

device=$(qvm-usb | grep -o -P '(?<=).*(?=  begin_of_device_name)' | head -1)
sleep 0.01
qvm-usb attach AppVM ${device}
sleep 1
qvm-usb detach AppVM ${device}
sleep 1
qvm-usb attach AppVM ${device}
notify-send "Lets start"