I read here, once, that installing a Debian 9 on a pendrive (well, in my case it's a SDCard adapter) directly would work, and it did. The problem came up, though, after i unplugged the adapter from the computer; when i wanted to boot into linux, all i had to do was to choose the boot device labelled 'UEFI: debian' on the bios setup, but as soon as i removed the adapter, that option disappeared. I don't want to lose the debian installation, I want it working again. I need to get it booting again.

I have a USB drive, encrypted with LUKS [cryptsetup](https://gitlab.com/cryptsetup/cryptsetup) , that I use for regular backups. When I plug in the drive, I am prompted for a password, just as expected. But then the drive gets mounted, an icon appears on my desktop, and a second password dialogue is shown. The message in the dialogue – “A passphrase is needed to access …” is wrong. I can ignore the second dialogue, or cancel it, and I am able to access the drive. See the screen-shot, which shows the drive icon (unlocked), files on it in Nemo, and the second password dialogue. It gets weirder: if I enter my password again, it is rejected and the dialogue reappears. This seems to happen infinitely, until I Cancel the dialogue. Is this a bug, or am I doing something wrong? Here is the lsblk output (sda is the USB drive): NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 233G 0 disk └─sda1 8:1 1 233G 0 part └─luks-4c8f9d1b-f967-4257-91d5-c32db662e482 252:0 0 233G 0 crypt /media/ME/BackupRed nvme0n1 259:0 0 931.5G 0 disk ├─nvme0n1p1 259:1 0 512M 0 part /boot/efi └─nvme0n1p2 259:2 0 931G 0 part / I am using Linux Mint 22.1 Cinnamon. There are similar questions but they refer to boot problems. e.g. https://askubuntu.com/questions/1106136/prompted-for-luks-password-twice-on-boot-despite-separate-unencrypted-boot-part . **Edit - Answers to early comments.** I don’t have KDE, it’s not even in the Mint distro. I tried running ps -fu ME at various stages: • No new processes when USB plugged in • No new processes when first dialogue cancelled • No new processes when first dialogue completed All of which leads me to assume the dialogues are part of Cinnamon, and not a separate process. ** Edit - Answers to @waltinator ** No output at all from sudo journalctl --follow |tail -f. It was started before the drive was plugged in, and left running through both dialogues. Here are my notes from when the drive was encrypted. It was brand-new so had nothing to save. > To use the GUI: Launch Disks to get access to the encryption utility. > Plug in your memory stick and look for it in the list of available > disks. Create a temporary folder and copy out all of the files you > have on the stick. Next, you choose to format the external drive, > specifying the encryption option. Remember, this action will mean > that you will only be able to access the files on Linux computers > that also have cryptsetup installed. If you don’t want to encrypt the > entire memory stick, partition it first. This action can also be > performed in the Disks utility. > > You specify a password when the > Format procedure launches. The formatting process offers you the > option to not overwrite existing data. However, this doesn’t work and > you will lose all of your files on the memory stick during the > formatting process. That’s why you need to copy them over to a > temporary folder before you start the encryption process. Once the > formatting finishes, copy your files back over. > > A drive that has been > protected by encryption is flagged in the Disks display by a padlock > icon. Henceforth, when you click on that drive to access it, a popup > window will appear to prompt you for the password. Options in the > popup specify whether the computer should store the password for > future access, whether it should forget the password immediately, or > whether it should forget the password once the USB stick is removed > from the computer.

What is the meaning of these error messages in the system log, when I plug in [a 2.5" spinning-disk SATA drive](https://www.seagate.com/files/staticfiles/support/docs/samsung-ds/100698122c.pdf) that I _know_ works, using a [USB-to-SATA adapter](https://web.archive.org/web/20230401071626/https://sabrent.com/products/ec-ss31) ? Jun 25 16:08:07 hostname kernel: [181603.928983] scsi 6:0:0:0: Direct-Access SABRENT 2210 PQ: 0 ANSI: 6 Jun 25 16:08:07 hostname kernel: [181603.931640] sd 6:0:0:0: Attached scsi generic sg1 type 0 Jun 25 16:08:07 hostname kernel: [181603.938380] sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK Jun 25 16:08:07 hostname kernel: [181603.938391] sd 6:0:0:0: [sdb] Sense Key : Illegal Request [current] Jun 25 16:08:07 hostname kernel: [181603.938398] sd 6:0:0:0: [sdb] Add. Sense: Invalid command operation code Jun 25 16:08:07 hostname kernel: [181603.939443] sd 6:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B) Jun 25 16:08:07 hostname kernel: [181603.939449] sd 6:0:0:0: [sdb] 0-byte physical blocks Jun 25 16:08:07 hostname kernel: [181603.942357] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled Jun 25 16:08:07 hostname kernel: [181603.943386] sd 6:0:0:0: [sdb] Asking for cache data failed Jun 25 16:08:07 hostname kernel: [181603.943393] sd 6:0:0:0: [sdb] Assuming drive cache: write through Jun 25 16:08:07 hostname kernel: [181603.944506] sd 6:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes) Jun 25 16:08:07 hostname kernel: [181603.948248] sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK Jun 25 16:08:07 hostname kernel: [181603.948255] sd 6:0:0:0: [sdb] Sense Key : Illegal Request [current] Jun 25 16:08:07 hostname kernel: [181603.948257] sd 6:0:0:0: [sdb] Add. Sense: Invalid command operation code Jun 25 16:08:07 hostname kernel: [181603.960998] sd 6:0:0:0: [sdb] Attached SCSI disk Specifically: […] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK […] Sense Key : Illegal Request [current] […] Add. Sense: Invalid command operation code The device spins up fine mechanically with no unusual noises, but none of the partitions are being detected, and as a result, they don't show up in the file manager. I don't think this matters much, but just to provide some context, it's an Ubuntu 20.04-based distribution (elementary OS 6.1 Jólnir) running on a Samsung Series 9.

I have two USB Drives. I created partitions and formatted them to ext4. Running fdisk -l shows that I have /dev/sda1 and /dev/sdb1 Device Boot Start End Sectors Size Id Type /dev/sda1 /dev/sdb1 Then I mounted both on boot by running sudo nano /etc/fstab I use Samba to access them from the different computer and most of the time it is working fine, but sometime I can't access the files via samba and running fdisk -l shows the the device for my drives changed to for example /dev/sdc1. Sometimes it changes only per one drive and sometimes it changes both. I have no idea why this is happening. Any help is much appreciated.

On Debian, when automounted, all files and directories in USB drives have 777 permissions. I don't like it very much. I know a bit of udev rules, and I think I could write a rule of mine to override the default behaviour. But I also would like to know which system rules are involved in this mechanism, can you help me?

Both systems are Arch Linux with the latest rsync. Connected via 1Gbit/s ethernet. Still rsyncing to a USB drive is slow, it's just 1-2MB/s

rsync -Pavh --stats --rsh="ssh -T -c aes128-gcm@openssh.com -o Compression=no" ~/Downloads/googleTakeout/takeout-202* plex:/media/usb-4tb/backup/google
sending incremental file list
takeout-20250428T071344Z-040.zip
          2.14G 100%    2.82MB/s    0:12:04 (xfr#1, to-chk=21/61)
takeout-20250428T071344Z-041.zip
          2.15G 100%    1.24MB/s    0:27:30 (xfr#2, to-chk=20/61)
takeout-20250428T071344Z-042.zip
          2.15G 100%    1.31MB/s    0:26:04 (xfr#3, to-chk=19/61)
takeout-20250428T071344Z-043.zip
          2.15G 100%    1.02MB/s    0:33:28 (xfr#4, to-chk=18/61)

Tested USB speed and it's much higher

1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 14.0448 s, 76.5 MB/s

sudo hdparm -Tt /dev/sdc 
/dev/sdc:
 Timing cached reads:   6186 MB in  2.00 seconds = 3097.42 MB/sec
 Timing buffered disk reads:  28 MB in  3.03 seconds =   9.24 MB/sec

Tried speed between endpoints

yes | pv | ssh plex "cat > /dev/null"                                                                                                                                                                      
944MiB 0:00:10 26.8MiB/s

yes | pv | ssh plex "cat > /media/usb-4tb"
1.06MiB 0:00:00 6.99MiB/s

scp is much faster, but it can't do partial copy as rsync

scp Downloads/googleTakeout/takeout-20250428T071344Z-001.zip plex:/media/usb-4tb/backup/google/takeout-20250428T071344Z-001.zip
takeout-20250428T071344Z-001.zip   13%  275MB  28.7MB/s   01:01 ETA

Any ideas how to fix/improve rsync speed?

I'm using U-Boot 2020.10. In U-Boot, out of two USB drives, one is recognized and the other is not. Once Debian 12 is running, I have my two USB drives that are recognized and use the same driver xhci-hcd. Here are the dmesg logs for the unrecognized USB drive [ 2.460318] usb 1-1.2: new high-speed USB device number 4 using xhci-hcd [ 2.597067] usb 1-1.2: New USB device found, idVendor=058f, idProduct=6387 [ 2.597073] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.597077] usb 1-1.2: Product: Mass Storage [ 2.597081] usb 1-1.2: SerialNumber: F2611EC0 [ 2.597845] usb-storage 1-1.2:1.0: USB Mass Storage device detected [ 2.612148] scsi host1: usb-storage 1-1.2:1.0 Here is the output of the command fdisk -l /dev/sdb1 Disk /dev/sdb1: 7.5 GiB, 8052015104 bytes, 15726592 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0a0dff65 Device Boot Start End Sectors Size Id Type /dev/sdb1p1 * 1869881445 3571221465 1701340021 811.3G 7a unknown /dev/sdb1p2 * 1634566756 3553817813 1919251058 915.2G 72 unknown /dev/sdb1p3 0 0 0 0B 0 Empty /dev/sdb1p4 * 28049408 28049849 442 221K 0 Empty Partition table entries are not in disk order. The detected size is also incorrect with the USB drive recognized by U-Boot Disk /dev/sdb1: 1.9 GiB, 2013233664 bytes, 3932097 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x73696420 Device Boot Start End Sectors Size Id Type /dev/sdb1p1 1936286752 6221126032 4284839281 2T 45 unknown /dev/sdb1p2 1853169786 3723051230 1869881445 891.6G 65 Novell Netware 386 /dev/sdb1p3 1701978226 3336544981 1634566756 779.4G 20 unknown /dev/sdb1p4 0 3468733439 3468733440 1.6T d unknown When I run usb start in U-Boot, the following error message appears. Starting the controller USB XHCI 1.00 scanning bus usb@2f00000 for devices... Device not responding to set address. USB device not accepting new address (error=80000000) The error seems to be a timeout to me, but I don't know why the USB drive doesn't respond in U-Boot. Why is one of the USB drives not recognized in U-Boot?

I'm endeavoring to put Kali linux onto a USB stick - I know it's already written up , but I'd like to use only a portion of the total space (the aforementioned link will use the entire drive space). Let's have my 16GB usb stick mounted as sdb ... the goal is: 16 GB total, split like this... ---------------------------- | 11 | 01 | 04 | (GB) ---------------------------- sdb1 sdb2 sdb3 (partition ID) FAT32 FAT32 FAT32 (format) storage fatdog kalipart (label) - sdb1 is FAT32 and the main storage area (so that [windows can see it] along with any other OSes) - sdb2 is bootable and has Fatdog64 (6.3.0) and Precise Puppy (5.7.1) installed (multi-booting from one syslinux menu) - sdb3 is the target partition for Kali to use The objective is to multi-boot Fatdog64, Puppy, and Kali linux. Currently, sdb2 is bootable (syslinux) and successfully passes to Fatdog and Puppy, both on sdb2. Next I'd like to add chainloading to Kali on sdb3. It seems to me that the best way to do that is to load GRUB4DOS from syslinux (both on sdb2), map sdb3 and chainload to sdb3 from GRUB4DOS. So I ask: How do I install Kali onto an existing partition on this USB stick? Other options: - Install live Kali onto the USB stick/partition from the Kali distro itself - but this doesn't seem to be an option the same way it is with Fatdog/Puppy/Ubuntu - Boot direclty to sdb3, chainloading to sdb2 if necessary (not preferred, but an option) >Update: > >1. I have tried copying the files from a mounted iso to sdb3 using Fatdog64 and noticed several errors, mostly in copying the firmware files. Here's two examples: > Copying /mnt/+mnt+sda1+isos+kali-linux-1+0+6-i286+kali-linux-1+0+6-i286+iso/firmware/amd64/microcode_1.20120910-2_i386.deb as /mnt/sda3/firmware/amd64-microcode_1.20120910-2_i286.deb > ERROR: Operation not permitted > Copying /mnt/+mnt+sda1+isos+kali-linux-1+0+6-i286+kali-linux-1+0+6-i286+iso/debian as /mnt/sda3/debian > ERROR: Operation not permitted > These errors look like permissions errors, but I can't tell if they affect booting or not (I can troubleshoot other errors later, I'd prefer to keep this question to just multi-boot). > >2. I'm chainloading GRUB4DOS from the SYSLINUX installed by default via Fatdog64 ... > > label grub4dos > menu label grub4dos > boot /boot/grub/grldr > text help > Load grub4dos via grldr (in /boot/grub) > endtext > > ... and then once in GRUB4DOS, I have successfully chainloaded GRUB2 (on the kali partition) ... > > title Load GRUB2 inside of kali > find --set-root /g2ldr.mbr > chainloader /g2ldr.mbr > > ... but all this gives me is a grub> prompt, and I haven't figured out any proper combinations of GRUB4DOS commands to load GRUB2 with a GRUB2 config file - and to add to the confusion, I thought the live CD iso of Kali ran on syslinux. (@jasonwryan @user63921)

I want to create a bootable USB and to put drivers folder beside my .iso image. Firstly, I wrote zeroes on my USB drive using this command:

dd if=/dev/zero of=/dev/sda bs=4096 conv=fsync oflag=direct status=progress

, got this output:

1907201+0 records in

1907200+0 records out

7811891200 bytes (7.8 GB, 7.3 GiB) copied, 2188.11 s, 3.6 MB/s

then I unmounted and formatted it:

sudo umount /dev/sda

sudo mkfs.vfat /dev/sda

Then I created a partition on it using

, and got this output in

:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

sda 8:0 1 7.3G 0 disk

└─sda1 8:1 1 7.3G 0 part

Then I wrote an .iso file into my USB using

dd bs=4M if=/home/alex/Downloads/Win10_22H2_EnglishInternational_x64v1.iso of=/dev/sda conv=fsync oflag=direct status=progress

command and got this output:

1462+1 records in

1462+1 records out

6135633920 bytes (6.1 GB, 5.7 GiB) copied, 1396.19 s, 4.4 MB/s

As I understood later,

command overwrites partition table, so now my partition is gone. I'm still need to put a folder with drivers on to my USB drive beside

.iso

image. I don't know how to do it, because I can't copy my folder into USB drive, or create a new folder inside it. My partition

is disappeared, and when I try to mount

itself, it says

"source write-protected, mounted read-only"

. I heard I can use

for this kind of things, but is there any other way? I don't know what to do now and where is the problem. Would be thankful for your help.

So Dolphin is behaving funny. I can't tell you if this is new or not. System Info: Arch Linux 64 bit up to date, standalone startx with i3. The devices in question are fat32 and exfat (stupid windows support...). I haven't tried formatting them to ext4 because that just isn't an option for me. 1) Open Dolphin, instert USB, device recognized! 2) Insert USB, open Dolphin, device not listed :( I can run a mount /dev/sdc1 /mount/xxx no problem. fdisk -l out: Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 6EEBD8E6-6C6B-415F-8DF2-5E635871C1E1 Device Start End Sectors Size Type /dev/sda1 2048 976895 974848 476M EFI System /dev/sda2 976896 59570175 58593280 28G Linux filesystem /dev/sda3 59570176 387002367 327432192 156.1G Linux filesystem /dev/sda4 387002368 468860927 81858560 39G Microsoft basic data Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xcf4dbac4 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT /dev/sdb2 206848 738678783 738471936 352.1G 7 HPFS/NTFS/exFAT /dev/sdb3 738678784 972658687 233979904 111.6G 83 Linux /dev/sdb4 972658688 976773167 4114480 2G 82 Linux swap / Solaris Disk /dev/sdc: 7.5 GiB, 8029470208 bytes, 15682559 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x56604413 Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 15681535 15679488 7.5G b W95 FAT32 Dolphin recognized all of the partitions on my SSD and HDD, it is just USBs that are the problem. Any ideas? Thanks!

_OS community, I’m experiencing persistent USB issues on my Acer Aspire 3 running Pop!_OS 22.04, and I’d appreciate some guidance. The problem involves frequent USB controller failures and device disconnections, which don’t occur when I use the same peripherals on Windows 11. I’ve tried multiple troubleshooting steps, including updating the kernel, disabling the touchpad, and using a new mouse with a lower polling rate, but the issue persists. **Background** Hardware: Acer Aspire 3 notebook. OS: Pop!_OS 22.04 (based on Ubuntu 22.04). Peripherals: Previously used a Corsair Harpoon RGB PRO (1000Hz polling) and now a YSPRINGTECH USB OPTICAL MOUSE (lower polling rate), plus an internal ELAN050A touchpad. Observation: On Windows 11 (dual-boot), there are no USB problems with the same setup, suggesting a Linux-specific driver or configuration issue. **Symptoms** USB devices disconnect or require resets. The xHCI controller reports errors, especially during resume from suspend. Additional issues with power management, Acer WMI, and SATA links are present, which might be related. **Troubleshooting Attempted** Updated the kernel to the latest HWE version (e.g., 5.15.0-107). Disabled the touchpad (ID 17) using xinput disable 17 to rule out its interference. Switched to a mouse with a lower polling rate (10000us 4 times, consider switching to WQ_UNBOUND [Jun 28 12:35:03] workqueue: power_supply_changed_work hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [Jun 29 20:39:47] workqueue: power_supply_changed_work hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [Jun 29 20:39:56] workqueue: power_supply_changed_work hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [Jun 29 20:40:04] workqueue: power_supply_changed_work hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND [Jun 29 20:40:54] workqueue: power_supply_changed_work hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND [Jun 28 12:28:18] acer_wmi: Unknown function number - 8 - 0 [Jun 28 12:38:51] acer_wmi: Unknown function number - 8 - 0 [Jun 28 12:38:56] acer_wmi: Unknown function number - 8 - 1 [Jun 29 20:32:37] acer_wmi: Unknown function number - 8 - 0 [Jun 29 20:39:32] acer_wmi: Unknown function number - 8 - 0 [Jun 29 20:39:34] acer_wmi: Unknown function number - 8 - 1 [Jun 29 20:41:03] acer_wmi: Unknown function number - 8 - 0 [Jun 29 20:41:08] acer_wmi: Unknown function number - 8 - 1 [Jun 28 12:38:57] ata1: SATA link down (SStatus 0 SControl 300) [Jun 29 20:39:09] ata1: SATA link down (SStatus 0 SControl 300) [Jun 29 20:41:09] ata1: SATA link down (SStatus 0 SControl 300) [2247.818144] ACPI BIOS Error [13.652880] TSC found unstable ``` I’d love to get advice from the community on how to stabilize the USB subsystem. Could this be a driver issue, a BIOS incompatibility, or a power management problem? Any suggestions on further diagnostics or fixes would be greatly appreciated. I’m hesitant to update the BIOS without confirmation, given the risks. Thanks in advance for your support!

I got this Python script that reads media files from USB stick. It used to run fine, today it keeps giving me OS Error: [Errno 13] Permission denied: media/myName/usbName when the script runs the command os.listdir(). os.listdir() simply checks what folders and files are in the main folder. It doesn't write anything, so why is there a permission error? I can use the USB stick just fine, open, add and delete files in it myself. I'm not very experienced with Linux, what might be the issue? Some kind of permission, etc. setting for the script file or the usb drive that somehow magically changed without me doing anything? Using Lubuntu 14.04.

I have a usb disk and I have format it to ExFAT on Mac. Then I run the command to create a bootable windows on Mac: sudo dd if=Win11_24H2_EnglishInternational_x64.iso of=/dev/disk4 bs=8m status=progress The command finishes successfully but the disk format is changed to UDF (Universal Disk Format) which is not recognised by windows installation. How can I keep the disk format no change? I want it to be stay as ExFAT.

I am trying to get qemu-kvm to boot from my live usb stick. Is this possible?

After my PC won't start again (my first guess was the power switch to turn it on was dead), I removed the HDD to extract my data. When I set the HDD (a 640 GB WD) into an external case (USB 2.0), the drive simply won't mount. I am using Fedora 21. Debug output: **SmartControl** smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.1.5-100.fc21.x86_64] (local build) Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green Device Model: WDC WD6400AACS-00G8B1 Serial Number: WD-WCAUF3310323 LU WWN Device Id: 5 0014ee 101fa1ac5 Firmware Version: 05.04C05 User Capacity: 640,135,028,736 bytes [640 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.5, 3.0 Gb/s Local Time is: Tue Sep 15 15:43:46 2015 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART Status command failed: scsi error medium or hardware error (serious) SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (15600) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 181) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 142 137 021 Pre-fail Always - 5883 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1796 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 6180 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1766 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 75 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1796 194 Temperature_Celsius 0x0022 121 099 000 Old_age Always - 26 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. **dmesg** [ 6908.519756] usb 1-2: new high-speed USB device number 7 using xhci_hcd [ 6908.684848] usb 1-2: New USB device found, idVendor=1058, idProduct=1021 [ 6908.684865] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 6908.684867] usb 1-2: Product: Ext HDD 1021 [ 6908.684870] usb 1-2: Manufacturer: Western Digital [ 6908.684872] usb 1-2: SerialNumber: 574341554633333130333233 [ 6908.685583] usb-storage 1-2:1.0: USB Mass Storage device detected [ 6908.687976] scsi host13: usb-storage 1-2:1.0 [ 6909.694176] scsi 13:0:0:0: Direct-Access WD Ext HDD 1021 2021 PQ: 0 ANSI: 4 [ 6909.695222] sd 13:0:0:0: Attached scsi generic sg4 type 0 [ 6909.695275] sd 13:0:0:0: [sdd] 1250258944 512-byte logical blocks: (640 GB/596 GiB) [ 6909.696846] sd 13:0:0:0: [sdd] Write Protect is off [ 6909.696863] sd 13:0:0:0: [sdd] Mode Sense: 17 00 10 08 [ 6909.698417] sd 13:0:0:0: [sdd] No Caching mode page found [ 6909.698424] sd 13:0:0:0: [sdd] Assuming drive cache: write through [ 6909.703411] scsi_io_completion: 1 callbacks suppressed [ 6909.703419] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.703423] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.703428] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.703432] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.703433] blk_update_request: 1 callbacks suppressed [ 6909.703435] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.703439] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.704014] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.704020] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.704024] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.704028] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.704031] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.704034] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.704596] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.704603] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.704607] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.704610] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.704613] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.704616] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.704630] ldm_validate_partition_table(): Disk read failed. [ 6909.705046] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.705050] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.705053] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.705056] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.705058] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.705060] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.705525] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.705527] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.705533] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.705535] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.705537] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.705539] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.705986] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.705989] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.705993] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.705995] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.705997] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.705999] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.706421] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.706424] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.706427] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.706430] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.706431] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.706433] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.706442] Dev sdd: unable to read RDB block 0 [ 6909.706861] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.706864] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.706867] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.706869] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.706871] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.706873] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.707296] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.707299] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.707302] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.707305] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.707307] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.707308] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.707318] sdd: unable to read partition table [ 6909.711258] sd 13:0:0:0: [sdd] Attached SCSI disk [ 6909.831440] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.831449] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.831456] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.831461] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 4a 85 6f 80 00 00 08 00 [ 6909.831465] blk_update_request: critical target error, dev sdd, sector 1250258816 [ 6909.831980] Buffer I/O error on dev sdd, logical block 156282352, async page read [ 6908.519756] usb 1-2: new high-speed USB device number 7 using xhci_hcd [ 6908.684848] usb 1-2: New USB device found, idVendor=1058, idProduct=1021 [ 6908.684865] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 6908.684867] usb 1-2: Product: Ext HDD 1021 [ 6908.684870] usb 1-2: Manufacturer: Western Digital [ 6908.684872] usb 1-2: SerialNumber: 574341554633333130333233 [ 6908.685583] usb-storage 1-2:1.0: USB Mass Storage device detected [ 6908.687976] scsi host13: usb-storage 1-2:1.0 [ 6909.694176] scsi 13:0:0:0: Direct-Access WD Ext HDD 1021 2021 PQ: 0 ANSI: 4 [ 6909.695222] sd 13:0:0:0: Attached scsi generic sg4 type 0 [ 6909.695275] sd 13:0:0:0: [sdd] 1250258944 512-byte logical blocks: (640 GB/596 GiB) [ 6909.696846] sd 13:0:0:0: [sdd] Write Protect is off [ 6909.696863] sd 13:0:0:0: [sdd] Mode Sense: 17 00 10 08 [ 6909.698417] sd 13:0:0:0: [sdd] No Caching mode page found [ 6909.698424] sd 13:0:0:0: [sdd] Assuming drive cache: write through [ 6909.703411] scsi_io_completion: 1 callbacks suppressed [ 6909.703419] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.703423] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.703428] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.703432] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.703433] blk_update_request: 1 callbacks suppressed [ 6909.703435] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.703439] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.704014] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.704020] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.704024] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.704028] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.704031] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.704034] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.704596] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.704603] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.704607] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.704610] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.704613] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.704616] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.704630] ldm_validate_partition_table(): Disk read failed. [ 6909.705046] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.705050] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.705053] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.705056] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.705058] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.705060] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.705525] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.705527] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.705533] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.705535] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.705537] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.705539] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.705986] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.705989] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.705993] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.705995] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.705997] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.705999] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.706421] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.706424] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.706427] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.706430] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.706431] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.706433] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.706442] Dev sdd: unable to read RDB block 0 [ 6909.706861] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.706864] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.706867] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.706869] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.706871] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.706873] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.707296] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.707299] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.707302] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.707305] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 6909.707307] blk_update_request: critical target error, dev sdd, sector 0 [ 6909.707308] Buffer I/O error on dev sdd, logical block 0, async page read [ 6909.707318] sdd: unable to read partition table [ 6909.711258] sd 13:0:0:0: [sdd] Attached SCSI disk [ 6909.831440] sd 13:0:0:0: [sdd] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6909.831449] sd 13:0:0:0: [sdd] Sense Key : Data Protect [current] [ 6909.831456] sd 13:0:0:0: [sdd] Add. Sense: Logical unit access not authorized [ 6909.831461] sd 13:0:0:0: [sdd] CDB: Read(10) 28 00 4a 85 6f 80 00 00 08 00 [ 6909.831465] blk_update_request: critical target error, dev sdd, sector 1250258816 [ 6909.831980] Buffer I/O error on dev sdd, logical block 156282352, async page read I don't know if this is the right place to ask this question, but I am out of ideas. Is the drive itself dead? Is there any way to repair it to get access to the data on it? Any help or suggestions whatsoever are appreciated.

TLDR: How do I troubleshoot a slow usb 3.1 device plugged into a laptop. ISSUE: When I copy (tried GUI and terminal) the first few .iso files copy almost instantly 300mb/s+, but then the 3rd/4th start to slow to below 12mb/s (even if copying one at a time). HARDWARE: - Dell XPS 15 9520 (Fedora Linux 37 - Workstation) - Sandisk Extreme GO USB 3.1 64GB (using Ventoy) - Dell USB-C to USB-A/HDMI Adapter - Anker PowerExpand+ 7-in-1 USB-C PD Hub TRIED: - Reformatting usb (gparted - exfat). - Using USB with and without Ventoy installed. - Using different ports, different adapters/hubs. - Copying lots of .iso files in one go vs copying one file at a time - waiting until each file fully copied. Either way after a few files (around 4GB) the USB drive becomes very slow. Ejecting the USB (via GUI or terminal) can take a long time but after remounting fast speeds return. When ejecting using GUI I get message device busy - so now use terminal and wait until command has completed. DRIVER | PORT DETAILS:

$ udevadm info -q path -n /dev/sdc

/devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1.1/4-1.1:1.0/host1/target1:0:0/1:0:0:0/block/sdc


$ lsusb -t

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/1p, 5000M
        |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 5: Dev 6, If 0, Class=, Driver=, 480M
    |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 4: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 3: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
            |__ Port 3: Dev 11, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
            |__ Port 4: Dev 12, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 4: Dev 13, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 3: Dev 15, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 16, If 0, Class=, Driver=, 12M
    |__ Port 6: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 6: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 6: Dev 4, If 2, Class=Video, Driver=uvcvideo, 480M
    |__ Port 6: Dev 4, If 3, Class=Video, Driver=uvcvideo, 480M
    |__ Port 9: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 10: Dev 10, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 10: Dev 10, If 1, Class=Wireless, Driver=btusb, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 20000M/x2
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
        |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
        |__ Port 3: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M

I have an external hard disk with a ZFS pool on it. The data is accessed very infrequently so I would like to drive to go to sleep after some inactivity, which I set to 10min: hdparm -S 120 /dev/disk/by-id/usb-Seagate_Expansion_Desk_NAABDT6W-0\:0 With a cron script I check the status of the drive over time: hdparm -C /dev/disk/by-id/usb-Seagate_Expansion_Desk_NAABDT6W-0\:0 This works sometimes but most of the time, the drive remains in "active/idle" all the time, even if no access occurs. The ZFS pool is not performing scrubs. There are no zvols. All datasets (some of them encrypted) are mounted to under /zpseagate8tb/ (and /zpseagate8tb_bind/ for use in LXC containers). I confirmed no file descriptors to any of the datasets are open: # lsof -w | grep zpseagate8tb # What else could be preventing the drive from going to sleep?

This question is mostly about USB performance on Linux, but more specifically performance issues when running virtualbox images off of my USB. I posted this on the virtualbox forum, but so far no one has helped me. **Details** I bought a new Kingston HyperX Savage 512 GB 3.1 USB stick. I copied a 150 GB file on it, verified the hash and it passed. I also verified the speed using: time $(sudo dd if=/dev/zero of=/home/host/mnt/testfile2 bs=1M count=1000 & sync) 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB, 1000 MiB) copied, 3.69425 s, 284 MB/s real 0m3.883s user 0m0.002s sys 0m0.002s Other time it would be around 110 MB/s, but still I think performance is good enough for VirtualBox to run Ubuntu instance on it. Another benchmark shows the following: sudo hdparm -Tt /dev/sdd1 /dev/sdd1: Timing cached reads: 21882 MB in 1.99 seconds = 10973.39 MB/sec Timing buffered disk reads: 1204 MB in 3.00 seconds = 400.74 MB/sec What happens is that when I start the VirtualBox, there are pauses or lags happening. A virtual box log of a fresh start and shutdown is located at: https://pastebin.com/iC7kQ54J (cut beginning part out because it was too long). Based on my research, whenever there is lagging there are a lot of the following messages in VBox.log: 00:07:10.988753 AsyncCompletion: Task 0x007f65495ff9c0 completed after 16 seconds 00:07:17.981513 AsyncCompletion: Task 0x007f65495ffe80 completed after 23 seconds 00:07:17.989714 AsyncCompletion: Task 0x007f65495ff7c0 completed after 23 seconds 00:07:18.004043 AsyncCompletion: Task 0x007f65495ffec0 completed after 23 seconds 00:07:18.009427 AsyncCompletion: Task 0x007f65495fffc0 completed after 23 seconds 00:07:18.065390 AsyncCompletion: Task 0x007f65495ffd80 completed after 23 seconds 00:07:18.065474 AsyncCompletion: Task 0x007f65495ff840 completed after 23 seconds After googling around, it seems people are saying this has to do with I/O on the drive, but how can that be the case if I get a good performance on the drive during benchmarks? Am I bench marking wrong? Can you suggest a better method? Are there any other parameters which might be disabled which are causing virtual-box to have performance issues with my USB? There are no errors in dmesg on the host during a run of this virtual machine. Here is sudo lshw | grep -A26 -B10 Kingston for my USB: *-usb:1 description: Mass storage device product: HyperX Savage vendor: Kingston physical id: 6 bus info: usb@4:6 logical name: scsi8 version: 1.00 capabilities: usb-3.10 scsi emulated scsi-host configuration: driver=usb-storage maxpower=896mA speed=5000Mbit/s *-disk description: SCSI Disk product: HyperX Savage vendor: Kingston physical id: 0.0.0 bus info: scsi@8:0.0.0 logical name: /dev/sdd version: PMAP size: 468GiB (503GB) capabilities: removable configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 *-medium physical id: 0 logical name: /dev/sdd size: 468GiB (503GB) capabilities: partitioned partitioned:dos configuration: signature=6e13cd5d *-volume description: EXT4 volume vendor: Linux physical id: 1 logical name: /dev/sdd1 logical name: /home/host/mnt version: 1.0 serial: e953210a-43c2-4ba9-87ec-55ed8ab3c6ff size: 468GiB capacity: 468GiB capabilities: primary journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized configuration: created=2018-09-01 00:55:53 filesystem=ext4 label=datapartition lastmountpoint=/home/host/mnt modified=2018-09-01 12:50:22 mount.fstype=ext4 mount.options=rw,relatime,data=ordered mounted=2018-09-01 12:50:22 state=mounted Can anyone tell what could be the problem?

I unmounted my 2TB Samsung SSD, before I went on holiday (meaning to bring it with me but I forgot). I have remote SSH access but I can't find a way that will work for an up-to-date kernel (OpenSuse Tumbleweed, as of May 2025) to remotely remount an unmounted but plugged in USB drive. lsusb -t /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2 |__ Port 008: Dev 003, If 0, Class=Mass Storage, Driver=uas, 5000M |__ Port 009: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M

The [Axagon EE35-GTR USB-C 5Gbps RIBBED box](https://axagon.eu/en/produkty/ee35-gtr) HDD enclosure claims to be compatible with Linux and any capacity. I need to use it with a 20TB Seagate HDD on a desktop PC with AMD A88X chipset, running Fedora Linux 41 (currently Linux 6.14), which only has USB-A ports. Will it work?