I connected my usb drive to one of my vms and wanted to simply transfer several files from the vm to the usb drive, around 90gb. I started the transfer and just went off the desk so it will finish, but apparently it just printed an error somewhere in the 1/3 of the process. As I figured out later, my sys-usb went completely off.
Could that be timeout issue of sort? Cause I have this in my log:
urb completion with non-zero status -121
just now something very similar happen.
I noticed that my usb drive (it’s actually another one this time) is unresponsive. I tried to safe remove it but it didn’t respond. sys-usb didn’t shut down, but I have a feeling it’s something deeper than broken disk or something like that, because of 2 things:
- the qui-devices was unresponsive until system reboot.
- the cpu on dom0 was 30% and my cpu was getting hot. I couldn’t do a thing. the qubesd process was taking the most of it, but wait it’s not all. now after a reboot I don’t have the same silent dom0 anymore, it constantly doing some jobs and takes huge amount of cpu, like 5-30%… this is huge, I know for sure before that incident it was max 7-10% at most intense work. And it’s not like some specific process takes cpu now, it’s some xorg and other normal kind of processes all together combined, except the “qubes-qube-mana” that gets spikes, I have no idea what the heck is that thing.