I have a cool powered enclosure for an external HDD that I like (LaCie Blade Runner) and I wanted to shift to Linux Mint but there is a big problem. When I use linux it takes a full ten minutes to mount the drive, and it doesn't matter which actual HDD is inside the enclosure nor what kind of a file system it is (I've tried all the options already). I have also other low-cost simple enclosures and they work perfectly with linux and automatically mounts within a second. Under macOS or Win10 everything is fine and fast. So it’s an enclosure/linux thing.
HDD isn't even present in any of the folders like /mount, /mnt, /dev, or /usb before mounting. You can’t see the file system. But, I have tried one informational command (I totally forgot which one because I was playing with all kinds of stuff to fix the issue, perhaps if was dmesg or lsusb) that can see the enclosure within seconds as usb attacked thing (same as a mouse or a keyboard) but not as a HDD with a file system.
So you need to wait for a 10 minutes until the system figures it out and then everything seams normal — file system is present, files and folders open normally, although erasing the partitions in gparted is very, very slow as making new one too. I haven’t check the overall disk speed under linux.
So, is there a fix for it? How to make it work as same as on macOS or Win10?
Ext HDD mounts after 10 minutes :/
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Ext HDD mounts after 10 minutes :/
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Ext HDD mounts after 10 minutes :/
Hi Vleyd ,
welcome to our forum.
can you tell us about your hardware:
viewtopic.php?f=90&t=318644
copy the result of that, back here, on your reply.
is your ext drive connected via usb 2 or with usb 3 ?.
NB: the LinuxMint System is Not iMac / Windows comparable,
and thus you cannot expect the same results . . .
welcome to our forum.
can you tell us about your hardware:
viewtopic.php?f=90&t=318644
copy the result of that, back here, on your reply.
is your ext drive connected via usb 2 or with usb 3 ?.
NB: the LinuxMint System is Not iMac / Windows comparable,
and thus you cannot expect the same results . . .
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.
Re: Ext HDD mounts after 10 minutes :/
Thanks Pierre
Log of a USB 3.0 HDD from plug-in to USB 3.0 port and mounting — https://termbin.com/g0ny
SYS INFO — https://termbin.com/sq3f
Hope this helps
Log of a USB 3.0 HDD from plug-in to USB 3.0 port and mounting — https://termbin.com/g0ny
Code: Select all
[ 393.527959] usb 2-3: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 393.548606] usb 2-3: New USB device found, idVendor=059f, idProduct=1043, bcdDevice= 0.06
[ 393.548613] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 393.548616] usb 2-3: Product: Blade Runner
[ 393.548619] usb 2-3: Manufacturer: LaCie
[ 393.548622] usb 2-3: SerialNumber: 0000000035e88c611084
[ 393.553426] scsi host2: uas
[ 393.554122] scsi 2:0:0:0: Direct-Access LaCie Blade Runner 051E PQ: 0 ANSI: 6
[ 393.555077] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 425.015111] sd 2:0:0:0: tag#3 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[ 425.015121] sd 2:0:0:0: tag#3 CDB: Read capacity(16) 9e 10 00 00 00 00 00 00 00 00 00 00 00 20 00 00
[ 425.031110] scsi host2: uas_eh_device_reset_handler start
[ 425.159499] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 425.182142] scsi host2: uas_eh_device_reset_handler success
[ 425.199592] sd 2:0:0:0: [sdc] 976754646 4096-byte logical blocks: (4.00 TB/3.64 TiB)
[ 425.199700] sd 2:0:0:0: [sdc] Write Protect is off
[ 425.199704] sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 425.199882] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 455.734404] sd 2:0:0:0: tag#2 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[ 455.734414] sd 2:0:0:0: tag#2 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 455.750416] scsi host2: uas_eh_device_reset_handler start
[ 455.878733] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 455.900592] scsi host2: uas_eh_device_reset_handler success
[ 486.457735] scsi host2: uas_eh_device_reset_handler start
[ 486.457796] sd 2:0:0:0: tag#2 uas_zap_pending 0 uas-tag 1 inflight:
[ 486.457803] sd 2:0:0:0: tag#2 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 486.586082] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 486.608036] scsi host2: uas_eh_device_reset_handler success
[ 517.177123] scsi host2: uas_eh_device_reset_handler start
[ 517.177186] sd 2:0:0:0: tag#2 uas_zap_pending 0 uas-tag 1 inflight:
[ 517.177193] sd 2:0:0:0: tag#2 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 517.305460] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 517.327352] scsi host2: uas_eh_device_reset_handler success
[ 547.895378] scsi host2: uas_eh_device_reset_handler start
[ 547.895445] sd 2:0:0:0: tag#2 uas_zap_pending 0 uas-tag 1 inflight:
[ 547.895453] sd 2:0:0:0: tag#2 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 548.023739] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 548.045553] scsi host2: uas_eh_device_reset_handler success
[ 578.609635] sd 2:0:0:0: tag#3 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[ 578.609645] sd 2:0:0:0: tag#3 CDB: Report supported operation codes a3 0c 01 93 00 00 00 00 02 00 00 00
[ 578.625627] scsi host2: uas_eh_device_reset_handler start
[ 578.753980] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 578.775988] scsi host2: uas_eh_device_reset_handler success
[ 609.332085] scsi host2: uas_eh_device_reset_handler start
[ 609.332147] sd 2:0:0:0: tag#3 uas_zap_pending 0 uas-tag 1 inflight:
[ 609.332153] sd 2:0:0:0: tag#3 CDB: Report supported operation codes a3 0c 01 93 00 00 00 00 02 00 00 00
[ 609.460438] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 609.482352] scsi host2: uas_eh_device_reset_handler success
[ 640.050715] scsi host2: uas_eh_device_reset_handler start
[ 640.050775] sd 2:0:0:0: tag#3 uas_zap_pending 0 uas-tag 1 inflight:
[ 640.050782] sd 2:0:0:0: tag#3 CDB: Report supported operation codes a3 0c 01 93 00 00 00 00 02 00 00 00
[ 640.179077] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 640.201145] scsi host2: uas_eh_device_reset_handler success
[ 670.769482] scsi host2: uas_eh_device_reset_handler start
[ 670.769542] sd 2:0:0:0: tag#3 uas_zap_pending 0 uas-tag 1 inflight:
[ 670.769549] sd 2:0:0:0: tag#3 CDB: Report supported operation codes a3 0c 01 93 00 00 00 00 02 00 00 00
[ 670.897844] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 670.919778] scsi host2: uas_eh_device_reset_handler success
[ 701.484389] sd 2:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[ 701.484398] sd 2:0:0:0: tag#0 CDB: Report supported operation codes a3 0c 01 41 00 00 00 00 02 00 00 00
[ 701.504361] scsi host2: uas_eh_device_reset_handler start
[ 701.632726] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 701.654777] scsi host2: uas_eh_device_reset_handler success
[ 732.207315] scsi host2: uas_eh_device_reset_handler start
[ 732.207374] sd 2:0:0:0: tag#0 uas_zap_pending 0 uas-tag 1 inflight:
[ 732.207380] sd 2:0:0:0: tag#0 CDB: Report supported operation codes a3 0c 01 41 00 00 00 00 02 00 00 00
[ 732.335701] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 732.358129] scsi host2: uas_eh_device_reset_handler success
[ 762.930336] scsi host2: uas_eh_device_reset_handler start
[ 762.930450] sd 2:0:0:0: tag#0 uas_zap_pending 0 uas-tag 1 inflight:
[ 762.930458] sd 2:0:0:0: tag#0 CDB: Report supported operation codes a3 0c 01 41 00 00 00 00 02 00 00 00
[ 763.058692] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 763.081084] scsi host2: uas_eh_device_reset_handler success
[ 793.645410] scsi host2: uas_eh_device_reset_handler start
[ 793.645537] sd 2:0:0:0: tag#0 uas_zap_pending 0 uas-tag 1 inflight:
[ 793.645545] sd 2:0:0:0: tag#0 CDB: Report supported operation codes a3 0c 01 41 00 00 00 00 02 00 00 00
[ 793.773776] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 793.796151] scsi host2: uas_eh_device_reset_handler success
[ 793.796260] sd 2:0:0:0: [sdc] Optimal transfer size 268431360 bytes
[ 824.360557] sd 2:0:0:0: tag#1 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[ 824.360567] sd 2:0:0:0: tag#1 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 824.376540] scsi host2: uas_eh_device_reset_handler start
[ 824.504974] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 824.527537] scsi host2: uas_eh_device_reset_handler success
[ 855.083682] scsi host2: uas_eh_device_reset_handler start
[ 855.083812] sd 2:0:0:0: tag#20 uas_zap_pending 0 uas-tag 1 inflight:
[ 855.083820] sd 2:0:0:0: tag#20 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 855.212113] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 855.234481] scsi host2: uas_eh_device_reset_handler success
[ 885.802850] scsi host2: uas_eh_device_reset_handler start
[ 885.802979] sd 2:0:0:0: tag#28 uas_zap_pending 0 uas-tag 1 inflight:
[ 885.802987] sd 2:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 885.931284] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 885.953245] scsi host2: uas_eh_device_reset_handler success
[ 916.526046] scsi host2: uas_eh_device_reset_handler start
[ 916.526125] sd 2:0:0:0: tag#29 uas_zap_pending 0 uas-tag 1 inflight:
[ 916.526132] sd 2:0:0:0: tag#29 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 916.654409] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 916.676693] scsi host2: uas_eh_device_reset_handler success
[ 947.237255] sd 2:0:0:0: tag#2 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[ 947.237271] sd 2:0:0:0: tag#2 CDB: Report supported operation codes a3 0c 01 93 00 00 00 00 02 00 00 00
[ 947.261255] scsi host2: uas_eh_device_reset_handler start
[ 947.389610] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 947.411797] scsi host2: uas_eh_device_reset_handler success
[ 977.960458] scsi host2: uas_eh_device_reset_handler start
[ 977.960537] sd 2:0:0:0: tag#28 uas_zap_pending 0 uas-tag 1 inflight:
[ 977.960545] sd 2:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 93 00 00 00 00 02 00 00 00
[ 978.088822] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 978.110946] scsi host2: uas_eh_device_reset_handler success
[ 1008.679700] scsi host2: uas_eh_device_reset_handler start
[ 1008.679776] sd 2:0:0:0: tag#29 uas_zap_pending 0 uas-tag 1 inflight:
[ 1008.679783] sd 2:0:0:0: tag#29 CDB: Report supported operation codes a3 0c 01 93 00 00 00 00 02 00 00 00
[ 1008.808065] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1008.830230] scsi host2: uas_eh_device_reset_handler success
[ 1039.398751] scsi host2: uas_eh_device_reset_handler start
[ 1039.398833] sd 2:0:0:0: tag#3 uas_zap_pending 0 uas-tag 1 inflight:
[ 1039.398841] sd 2:0:0:0: tag#3 CDB: Report supported operation codes a3 0c 01 93 00 00 00 00 02 00 00 00
[ 1039.527126] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1039.549315] scsi host2: uas_eh_device_reset_handler success
[ 1070.112821] sd 2:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[ 1070.112830] sd 2:0:0:0: tag#0 CDB: Report supported operation codes a3 0c 01 41 00 00 00 00 02 00 00 00
[ 1070.128829] scsi host2: uas_eh_device_reset_handler start
[ 1070.257191] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1070.279336] scsi host2: uas_eh_device_reset_handler success
[ 1100.835009] scsi host2: uas_eh_device_reset_handler start
[ 1100.835093] sd 2:0:0:0: tag#1 uas_zap_pending 0 uas-tag 1 inflight:
[ 1100.835101] sd 2:0:0:0: tag#1 CDB: Report supported operation codes a3 0c 01 41 00 00 00 00 02 00 00 00
[ 1100.963382] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1100.985539] scsi host2: uas_eh_device_reset_handler success
[ 1131.553299] scsi host2: uas_eh_device_reset_handler start
[ 1131.553384] sd 2:0:0:0: tag#2 uas_zap_pending 0 uas-tag 1 inflight:
[ 1131.553391] sd 2:0:0:0: tag#2 CDB: Report supported operation codes a3 0c 01 41 00 00 00 00 02 00 00 00
[ 1131.681670] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1131.703799] scsi host2: uas_eh_device_reset_handler success
[ 1162.271692] scsi host2: uas_eh_device_reset_handler start
[ 1162.271777] sd 2:0:0:0: tag#3 uas_zap_pending 0 uas-tag 1 inflight:
[ 1162.271784] sd 2:0:0:0: tag#3 CDB: Report supported operation codes a3 0c 01 41 00 00 00 00 02 00 00 00
[ 1162.400064] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1162.422233] scsi host2: uas_eh_device_reset_handler success
[ 1162.475776] sdc: sdc1
[ 1192.986156] sd 2:0:0:0: tag#3 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[ 1192.986162] sd 2:0:0:0: tag#3 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 1192.986297] sd 2:0:0:0: [sdc] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[ 1192.986301] sd 2:0:0:0: [sdc] tag#1 CDB: ATA command pass through(12)/Blank a1 08 2e 00 01 00 00 00 00 ec 00 00
[ 1193.002205] scsi host2: uas_eh_device_reset_handler start
[ 1193.130517] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1193.153517] scsi host2: uas_eh_device_reset_handler success
[ 1193.477403] hfsplus: write access to a journaled filesystem is not supported, use the force option at your own risk, mounting read-only.
[ 1223.712701] scsi host2: uas_eh_device_reset_handler start
[ 1223.712826] sd 2:0:0:0: tag#21 uas_zap_pending 0 uas-tag 1 inflight:
[ 1223.712834] sd 2:0:0:0: tag#21 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
[ 1223.841150] usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1223.863542] scsi host2: uas_eh_device_reset_handler success
Code: Select all
System: Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.8.5
wm: muffin dm: LightDM Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal
Machine: Type: Laptop System: Apple product: Macmini7,1 v: 1.0 serial: <filter> Chassis:
type: 10 v: Mac-35C5E08120C7EEAF serial: <filter>
Mobo: Apple model: Mac-35C5E08120C7EEAF v: Macmini7,1 serial: <filter> UEFI: Apple
v: 431.0.0.0.0 date: 02/22/2021
CPU: Topology: Dual Core model: Intel Core i5-4278U bits: 64 type: MT MCP arch: Haswell
rev: 1 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20801
Speed: 3101 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 2648 2: 2951 3: 3073
4: 3085
Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Apple driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:0a2e
Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel Iris Graphics 5100 (HSW GT3) v: 4.5 Mesa 20.0.8
compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Apple driver: snd_hda_intel v: kernel
bus ID: 00:03.0 chip ID: 8086:0a0c
Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:9c20
Sound Server: ALSA v: k5.4.0-58-generic
Network: Device-1: Broadcom and subsidiaries BCM4360 802.11ac Wireless Network Adapter
vendor: Apple driver: bcma-pci-bridge v: N/A port: efa0 bus ID: 02:00.0
chip ID: 14e4:43a0
Device-2: Broadcom and subsidiaries NetXtreme BCM57766 Gigabit Ethernet PCIe
driver: tg3 v: 3.137 port: efa0 bus ID: 03:00.0 chip ID: 14e4:1686
IF: enp3s0f0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 4.56 TiB used: 1.13 GiB (0.0%)
ID-1: /dev/sda vendor: Apple model: HDD HTS541010A9E662 size: 931.51 GiB
speed: 3.0 Gb/s serial: <filter> temp: 34 C
ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra USB 3.0 size: 14.32 GiB
speed: 3.0 Gb/s serial: <filter>
ID-3: /dev/sdc type: USB vendor: Lacie model: Blade Runner size: 3.64 TiB
serial: <filter>
Partition: ID-1: / size: 3.83 GiB used: 66.4 MiB (1.7%) fs: overlay source: ERR-102
ID-2: /var/log size: 12.17 GiB used: 40.5 MiB (0.3%) fs: ext4 dev: /dev/sdb3
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 9 rev: 2.0 chip ID: 1d6b:0002
Device-1: 1-2:2 info: Logitech RX 250 Optical Mouse type: Mouse
driver: hid-generic,usbhid rev: 2.0 chip ID: 046d:c050
Hub: 1-3:3 info: Broadcom BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) ports: 3
rev: 2.0 chip ID: 0a5c:4500
Device-2: 1-3.3:8 info: Apple BRCM20702 Hub type: <vendor specific> driver: btusb
rev: 2.0 chip ID: 05ac:8289
Device-3: 1-4:4 info: Apple Built-in IR Receiver type: HID driver: appleir,usbhid
rev: 2.0 chip ID: 05ac:8242
Device-4: 1-8:6 info: Holtek USB-HID Keyboard type: Keyboard,HID
driver: hid-generic,usbhid rev: 1.1 chip ID: 04d9:0192
Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 chip ID: 1d6b:0003
Device-5: 2-1:2 info: SanDisk Ultra Flair type: Mass Storage driver: usb-storage
rev: 3.0 chip ID: 0781:5591
Device-6: 2-3:3 info: LaCie Blade Runner type: Mass Storage driver: uas rev: 3.0
chip ID: 059f:1043
Sensors: System Temperatures: cpu: 45.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list
1: deb cdrom:[Linux Mint 20.1 _Ulyssa_ - Release amd64 20210103]/ focal contrib main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http: //archive.canonical.com/ubuntu/ focal partner
Info: Processes: 198 Uptime: 21m Memory: 7.65 GiB used: 735.9 MiB (9.4%) Init: systemd v: 245
runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client inxi: 3.0.38
Re: Ext HDD mounts after 10 minutes :/
Code: Select all
idVendor=059f, idProduct=1043
Here is a simple test. Mount it in USB 2 port. If the mount is instant, the problem is the USB3-SATA chip not fully supporting USB 3. I call those chips USB 2.5 because they are only half way from USB 2 to USB 3. Windows is full of special code to work around those hardware design shortcuts.
Re: Ext HDD mounts after 10 minutes :/
Long time no see. Ok, this thing below worked in a sense that the drive was mounted instantly. I copied that from some online help since my terminal skills are non-existing.
Then I reformatted the drive with ext4, which went OK without any errors in a few seconds. But, when I mounted the newly formatted drive it started to constantly work on something. I can see the blinking lights on my drive when it's working, but there's nothing there — not a single file. When I unmount it (powered on) it's idle, but when I mount it back the "mysterious work" gets back.
Is this normal, like if the filesystem making 'rows' of ext4 on my blank 10TB external drive? Shouldn't that be on-the-fly while writing files? Or is it something else?
This is the log after 2 minutes. I don't know what last three lines are, maybe that's it.
Btw, some guy on Reddit told me that I haven't completely blocked UAS, the mounting part is fixed but UAS is somehow alive.
EDIT: adding log link/txt and adding another info.
Code: Select all
sudo su
cat > /etc/modprobe.d/disable-uas.conf
options usb-storage quirks=059f:1043:u
update-initramfs -u
reboot
Is this normal, like if the filesystem making 'rows' of ext4 on my blank 10TB external drive? Shouldn't that be on-the-fly while writing files? Or is it something else?
This is the log after 2 minutes. I don't know what last three lines are, maybe that's it.
Code: Select all
[ 853.082047] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 853.102759] usb 2-1: New USB device found, idVendor=059f, idProduct=1043, bcdDevice= 0.06
[ 853.102765] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 853.102768] usb 2-1: Product: Blade Runner
[ 853.102771] usb 2-1: Manufacturer: LaCie
[ 853.102774] usb 2-1: SerialNumber: 0000000015d52aa80000
[ 853.160330] usb 2-1: UAS is blacklisted for this device, using usb-storage instead
[ 853.160333] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 853.160415] usb-storage 2-1:1.0: Quirks match for vid 059f pid 1043: 800000
[ 853.160443] scsi host1: usb-storage 2-1:1.0
[ 853.160518] usbcore: registered new interface driver usb-storage
[ 853.183431] usbcore: registered new interface driver uas
[ 854.162485] scsi 1:0:0:0: Direct-Access LaCie Blade Runner 051E PQ: 0 ANSI: 6
[ 854.163140] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 854.164009] sd 1:0:0:0: [sdb] Spinning up disk...
[ 855.185883] ..................ready
[ 872.980904] sd 1:0:0:0: [sdb] 2441609216 4096-byte logical blocks: (10.0 TB/9.10 TiB)
[ 872.981181] sd 1:0:0:0: [sdb] Write Protect is off
[ 872.981185] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 872.981512] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 873.039199] sdb: sdb1
[ 873.054945] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 873.719937] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 952.431263] [UFW BLOCK] IN=enp3s0f0 OUT= MAC=01:00:5e:00:00:01:b0:c2:87:e0:a2:3e:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
[ 952.431413] [UFW BLOCK] IN=enp3s0f0 OUT= MAC=01:00:5e:00:00:01:b0:c2:87:e0:a2:3e:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
[ 955.010891] [UFW BLOCK] IN=enp3s0f0 OUT= MAC=01:00:5e:00:00:fb:4e:3c:2f:02:ba:70:08:00 SRC=192.168.0.29 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39900 PROTO=2
EDIT: adding log link/txt and adding another info.
Re: Ext HDD mounts after 10 minutes :/
Ext4 can format part of a partition then leave the rest of the formatting for idle time later. https://ext4.wiki.kernel.org/index.php/ ... allocation
It is annoying on magnetic disks because it looks the same as some types of errors.
It is annoying on magnetic disks because it looks the same as some types of errors.
Re: Ext HDD mounts after 10 minutes :/
Some other guys said that it's actually so-called lazy init that's zeroing the partition table, and that's normal thing for ext4 after formatting. I never experienced anything like that on Windows or Mac. Most Win/Mac filesystems do that while writing files on-the-fly. This ext4 thing looks something in between old, log full format and those of Win and Mac.Petermint wrote: ⤴Mon Sep 20, 2021 6:15 pm Ext4 can format part of a partition then leave the rest of the formatting for idle time later. https://ext4.wiki.kernel.org/index.php/ ... allocation
It is annoying on magnetic disks because it looks the same as some types of errors.
How long does it take to finish lazyinit on 10TB drive?