I backed up 2 folders (containing .py files) from my Ubuntu 20 OS to the external hard drive. While trying to see the files on the external hard drive from Windows 10, I can't find those. Please advise

I'm relatively new to linux mint(4-5 months in [loving it!]) and I have a 2TB USB 3.0 HDD connected (WD Drive in the photo) I'm trying to shrink the main NTFS Partition on said drive, and it says max and min size are the same, therefore i cant change it if you need more info drop a comment

I have an external drive with Linux Mint 18 on it. It boots to my desktop, which is where I used the live CD to install the OS onto the external drive. However, when I try to boot this external drive from my laptop, it will not boot. Now, I changed the boot menu, made sure I set "Secure Boot" to disabled, and verified that "UEFI boot" is set to enabled, and I still cannot get the drive to boot. I used EasyBCD to install a grub, but that also puts me into the grub menu upon boot. I am not able to see the drive in windows explorer, but it is in the Manage Disks. I tried all of the EasyBCD grub options to no avail. Am I missing something? I do not want to take a chance and install the grub from the command when it first boots, (I get this message: Minimal BASH-like line editing is supported. For the first word. TAB lists possible command completions. Anywhere else TAB Lists possible device or file complete) because I do not want to take that chance and wipe out my windows boot, or more. When I boot it to my desktop, I get the options from grub asking whether to boot to Linux or Windows. What am I missing? Can I just add a grub through EasyBCD and if so, which procedure is it? I would like to get this grub on my laptop so that when it boots, I get the option to boot to either Linux or Windows when the drive is plugged in. I want to be able to install this drive to any computer and be able to boot into the Linux OS on this external drive. Even if I have to change the BOIS setting upon boot. That does not bother me. I was also thinking of just reinstalling the live CD again, only this time, use my laptop to perform the install to "the same" external drive I have Linux Mint 18 on right now. Basically overwriting the OS to the same OS. This way, the grub is on my laptop as well. However, when I do this, I was thinking about removing the two drives I have in the laptop before installing. My question about this is, "if I do remove the drives, will this work, because I didn't remove the drive from my desktop when I installed the initial OS on the external drive. Does this grub play a role within the C:/? Any help would be greatly appreciated.

I have Ubuntu 24+ (6.11.0-26-generic) installed on a PC with a Asus Prime Z690-P D4 motherboard, Intel CPU and so on. I have a WD MyBook 24 TB HDD USB which is always connected to the motherboard, by using the USB-C port. But I only power it on, by using the AC adapter, when I want to use it. The problem starts here. Most of times, after plugging in the AC adapter, the WD USB/SATA converter negotiates a 480 Mbit/s speed. Calling the usbreset command does not make it to go to 5 Gbit/s. In order to get the correct speed, I need to manually detach one end of the USB connector and attach it again. Is there any other command which gets the job done? I do not have this issue on another PC with a Asus WS motherboard (Intel 8th core gen), running Debian 12+. Thanks in advance. The console log: REDACTED@REDACTED:~$ lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 001: Dev 008, If 0, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 002: Dev 002, If 0, Class=Vendor Specific Class, Driver=[none], 12M |__ Port 002: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 011: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 011: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 012: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 002: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 003: Dev 007, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 003: Dev 007, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 013: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2 /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M REDACTED@REDACTED:~$ usbreset Usage: usbreset PPPP:VVVV - reset by product and vendor id usbreset BBB/DDD - reset by bus and device number usbreset "Product" - reset by product name Devices: Number 001/007 ID 045e:07f8 Wired Keyboard 600 Number 001/004 ID 1a40:0101 USB 2.0 Hub Number 001/008 ID 1058:25ed My Book 25ED Number 001/006 ID 1c4f:0051 Usb Mouse Number 001/005 ID 058f:6254 Number 001/003 ID 062a:4101 2.4G Keyboard Mouse Number 001/002 ID 0b05:19af AURA LED Controller REDACTED@REDACTED:~$ sudo usbreset 001/008 Resetting My Book 25ED ... ok REDACTED@REDACTED:~$ lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 001: Dev 008, If 0, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 002: Dev 002, If 0, Class=Vendor Specific Class, Driver=[none], 12M |__ Port 002: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 011: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 011: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 012: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 002: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 003: Dev 007, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 003: Dev 007, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 013: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2 /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M REDACTED@REDACTED:~$ sudo usbreset Usage: usbreset PPPP:VVVV - reset by product and vendor id usbreset BBB/DDD - reset by bus and device number usbreset "Product" - reset by product name Devices: Number 001/007 ID 045e:07f8 Wired Keyboard 600 Number 001/004 ID 1a40:0101 USB 2.0 Hub Number 001/008 ID 1058:25ed My Book 25ED Number 001/006 ID 1c4f:0051 Usb Mouse Number 001/005 ID 058f:6254 Number 001/003 ID 062a:4101 2.4G Keyboard Mouse Number 001/002 ID 0b05:19af AURA LED Controller REDACTED@REDACTED:~$ sudo usbreset 001/008 Resetting My Book 25ED ... ok REDACTED@REDACTED:~$ lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 001: Dev 008, If 0, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 002: Dev 002, If 0, Class=Vendor Specific Class, Driver=[none], 12M |__ Port 002: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 011: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 011: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 012: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 002: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 003: Dev 007, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 003: Dev 007, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 013: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2 /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M +++++++++++++++ detached USB cable and attached it again ++++++++++++++++++++++++++++++ REDACTED@REDACTED:~$ lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 002: Dev 002, If 0, Class=Vendor Specific Class, Driver=[none], 12M |__ Port 002: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 011: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 011: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 012: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 002: Dev 009, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 003: Dev 010, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 003: Dev 010, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 013: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2 |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M

I have noticed that when I mount my external HDD NTFS partition with the sync option, the write performance is terrible (1MB/s max). But when I use async the system finishes the operation very quickly (yes I know it is filled in the write cache), but according to htop I can see over 100MB/s writes to the external HDD. Why is this happening? Isn't sync immediately applying writes instead of caching? Why would it perform so poorly (x100 less than the max speed of the drive) I am Running Debian unstable (equivalent to 13 - trixie)

I have a old DVD/HDD recorder (Panasonic DMR-EH58) with RCA inputs & outputs etc. I want to recover all the recordings off its HDD. The HDD is a 2008 ATA/IDE 7200RPM Hitachi deskstar Model no:HDP725025GLAT80 250 GB has a DVD drive. It has been used at a conference center for many years recording camera RCA input. It is in good condition but it is outdated so I am trying to copy the recordings to a computer. I also would like to recover the deleted files if possible as they would not have been overwritten yet. I have borrowed a universal drive adapter and tried to mount it on both Windows 8.1 and ChaletOS Linux (Ubuntu based XFCE type distro). Windows showed it as a grayed F: drive and Linux did not auto mount it either. GParted shows it as "/dev/sdb: unrecognised disk label": Command line attempts follow: joel@joel-laptop:~$ mount dev/sdb mount: dev/sdb: No such file or directory joel@joel-laptop:~$ sudo mount /dev/sdb /mnt/usbdisk [sudo] password for joel: mount: special device /dev/sdb does not exist joel@joel-laptop:~$ mount dev/sdb mount: dev/sdb: No such file or directory joel@joel-laptop:~$ ls -alh /dev/disk/by-path/ total 0 drwxr-xr-x 2 root root 160 Apr 30 22:05 . drwxr-xr-x 6 root root 120 Apr 30 18:41 .. lrwxrwxrwx 1 root root 9 Apr 30 21:31 pci-0000:00:1f.2-ata-1 -> ../../sda lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 Apr 30 21:31 pci-0000:00:1f.2-ata-1-part6 -> ../../sda6 - Root directory is dev/sda5 - Swap is dev/sda6 - Windows is dev/sda1 - Spare data partition is dev/sda2 Looks like an unsupported file system error...

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?

I'm trying to see if there's a possibility to disable the power saving on my external Seagate Expansion Drive that is connected through USB to my NUC running Ubuntu Server. I had problems using hdparm as it gave me an error message, so I instead found sdparm that seemed to work for my particular drive according to this post . I run sudo sdparm -l -a /dev/sda and get the following output: /dev/sda: Seagate Expansion Desk 0915 Direct access device specific parameters: WP=0 DPOFUA=0 Caching (SBC) [ca] mode page: IC 0 [cha: n, def: 0, sav: 0] Initiator control ABPF 0 [cha: n, def: 0, sav: 0] Abort pre-fetch CAP 0 [cha: n, def: 0, sav: 0] Caching analysis permitted DISC 1 [cha: n, def: 1, sav: 1] Discontinuity SIZE 0 [cha: n, def: 0, sav: 0] Size enable WCE 1 [cha: y, def: 1, sav: 1] Write cache enable MF 0 [cha: n, def: 0, sav: 0] Multiplication factor RCD 0 [cha: n, def: 0, sav: 0] Read cache disable DRRP 0 [cha: n, def: 0, sav: 0] Demand read retention priority WRP 0 [cha: n, def: 0, sav: 0] Write retention priority DPTL -1 [cha: n, def: -1, sav: -1] Disable pre-fetch transfer length MIPF 0 [cha: n, def: 0, sav: 0] Minimum pre-fetch MAPF -1 [cha: n, def: -1, sav: -1] Maximum pre-fetch MAPFC -1 [cha: n, def: -1, sav: -1] Maximum pre-fetch ceiling FSW 0 [cha: n, def: 0, sav: 0] Force sequential write LBCSS 0 [cha: n, def: 0, sav: 0] Logical block cache segment size DRA 0 [cha: n, def: 0, sav: 0] Disable read ahead SYNC_PROG 0 [cha: n, def: 0, sav: 0] Synchronous cache progress indication NV_DIS 0 [cha: n, def: 0, sav: 0] Non-volatile cache disable NCS 255 [cha: n, def:255, sav:255] Number of cache segments CSS 0 [cha: n, def: 0, sav: 0] Cache segment size Control [co] mode page: TST 0 [cha: n, def: 0, sav: 0] Task set type TMF_ONLY 0 [cha: n, def: 0, sav: 0] Task management functions only DPICZ 0 [cha: n, def: 0, sav: 0] Disable protection information check if protect field zero D_SENSE 0 [cha: n, def: 0, sav: 0] Descriptor format sense data GLTSD 0 [cha: n, def: 0, sav: 0] Global logging target save disable RLEC 0 [cha: n, def: 0, sav: 0] Report log exception condition QAM 1 [cha: n, def: 1, sav: 1] Queue algorithm modifier NUAR 0 [cha: n, def: 0, sav: 0] No unit attention on release QERR 0 [cha: n, def: 0, sav: 0] Queue error management RAC 0 [cha: n, def: 0, sav: 0] Report a check UA_INTLCK 0 [cha: n, def: 0, sav: 0] Unit attention interlocks control SWP 0 [cha: n, def: 0, sav: 0] Software write protect ATO 0 [cha: n, def: 0, sav: 0] Application tag owner TAS 0 [cha: n, def: 0, sav: 0] Task aborted status ATMPE 0 [cha: n, def: 0, sav: 0] Application tag mode page enabled RWWP 0 [cha: n, def: 0, sav: 0] Reject write without protection SBLP 0 [cha: n, def: 0, sav: 0] Supported block lengths and protection information AUTOLOAD 0 [cha: n, def: 0, sav: 0] Autoload mode BTP 0 [cha: n, def: 0, sav: 0] Busy timeout period (100us) ESTCT 0 [cha: n, def: 0, sav: 0] Extended self test completion time (sec) Power condition [po] mode page: PM_BG 0 [cha: n, def: 0, sav: 0] Power management, background functions, precedence STANDBY_Y 0 [cha: n, def: 0, sav: 0] Standby_y timer enable IDLE_C 0 [cha: n, def: 0, sav: 0] Idle_c timer enable IDLE_B 0 [cha: n, def: 0, sav: 0] Idle_b timer enable IDLE 0 [cha: n, def: 0, sav: 0] Idle_a timer enable STANDBY 0 [cha: y, def: 1, sav: 0] Standby_z timer enable ICT 0 [cha: n, def: 0, sav: 0] Idle_a condition timer (100 ms) SCT 4294967286 [cha: y, def:9000, sav:4294967286] Standby_z condition timer (100 ms) IBCT 0 [cha: n, def: 0, sav: 0] Idle_b condition timer (100 ms) ICCT 0 [cha: n, def: 0, sav: 0] Idle_c condition timer (100 ms) SYCT 0 [cha: n, def: 0, sav: 0] Standby_y condition timer (100 ms) CCF_IDLE 0 [cha: n, def: 0, sav: 0] check condition on transition from idle CCF_STAND 0 [cha: n, def: 0, sav: 0] check condition on transition from standby CCF_STOPP 0 [cha: n, def: 0, sav: 0] check condition on transition from stopped I'm very novice to the terminology around HDD's, but my guess is that STANDBY would be a boolean for if the drive should run in standby-mode? Would turning this to 1 instead of 0 tell the disk to not "fall asleep" or is it the opposite? Are there any other settings in the list that I should take a look at or am I doing this completely wrong?

I got Pi4 4Gb running rasbian (similar to Debian) and Orico 4bay HDD rack connected with USB3. Earlier with same host and one HDD in separate enclosure I was able to power off disk using: sudo udisksctl power-off -b /dev/sda But now, for this four disks enclosure rack I got errors like this: pi@raspberrypi:~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk └─sda1 8:1 0 931.5G 0 part └─md0 9:0 0 931.4G 0 raid1 /mnt/raid sdb 8:16 0 931.5G 0 disk └─sdb1 8:17 0 931.5G 0 part └─md0 9:0 0 931.4G 0 raid1 /mnt/raid sdc 8:32 0 2.7T 0 disk └─sdc1 8:33 0 2.7T 0 part /mnt/wdred sdd 8:48 0 1.8T 0 disk └─sdd1 8:49 0 1.8T 0 part mmcblk0 179:0 0 14.8G 0 disk ├─mmcblk0p1 179:1 0 256M 0 part /boot └─mmcblk0p2 179:2 0 14.6G 0 part / pi@raspberrypi:~ $ sudo umount /mnt/raid pi@raspberrypi:~ $ sudo umount /mnt/wdred pi@raspberrypi:~ $ sudo udisksctl power-off -b /dev/sdc Error powering off drive: Error opening /dev/sdb for fsync: Device or resource busy (udisks-error-quark, 0) pi@raspberrypi:~ $ sudo udisksctl power-off -b /dev/sda Error powering off drive: Error opening /dev/sdb for fsync: Device or resource busy (udisks-error-quark, 0) pi@raspberrypi:~ $ sudo udisksctl power-off -b /dev/sdb Error powering off drive: Error opening /dev/sdb for fsync: Device or resource busy (udisks-error-quark, 0) pi@raspberrypi:~ $ sudo udisksctl power-off -b /dev/sdd Error powering off drive: Error opening /dev/sdb for fsync: Device or resource busy (udisks-error-quark, 0) pi@raspberrypi:~ $ If I shutdown pi and the turn off this rack with power button on it I see increment of Power-Off_Retract_Count attribute in HDD Smart (so this is not graceful power off, but emergency retract). How can I properly power off drives in this rack?

I have a problematic HDD (/dev/sdb) 1. Causes complete system during boot and freeze (on windows) drive listing 2. Appear in *lsblk* but shown as unreadable 3. Fail all standard repair attempts *fsck*, *wipefs* Symptoms: 1. System boots normally only when HDD unplugged 2. dmesg shows buffer I/O errors 3. SMART test failed or timeout ``` sudo wipefs -a /dev/sdb -> No such device sudo badblocks -sv /dev/sdb -> I/O errors sudo dd if=/dev/zero of=/dev/sdb bs=1M -> Hangs system What I need to know: - Last-resort methods to force-wipe the disk. - Is there any chance to revive this HDD? - Can you confirm if this is a hardware failure? - Is this definitely a hardware issue?

How can I keep my external hard drive connected to the USB port but in an unmounted state to preserve it? Is it possible to remount it at any time? I would like to keep it on for just an hour a day for writing and turn it off for the rest of the time. Can hdparm help? I don’t know how to use it.

I'v recently bought some old hard drives from a company that barely used them and wanted to use them to create a RAID 1 array. When I connect them to my linux desktop it doesn't reconise the drives at all and at start up I get the following errors: Now before you jump to the conclusion they are just dead hard drives (like me at first). The drives seem to work perfectly fine on Windows. I can partition them, add them to storage spaces, etc. The only thing I cannot do is do a SMART scan with the seagate tool but that might be because it doesn't have it (old drives). It is vital that the drives work on linux to be the start of my NAS. Update: The answers to the quesions asked in the comments: - 1. The drives do not have delayed jumper settings - 2. Yes both drives (identical) have the same issue when connected individually - 3. The kernel version is 6.1.0-11amd64 - 4. Software raid mdadm - 5. USB Micro-B (3.0) connector If it helps, the drives are both LaCie Rugged USB 3.0 FW 800. I also got the following error at start up (not shown on screenshot): ima: Error Communicating to TPM (x6)

Lately when I write to an external drive formatted as NTFS* and then eject it, and wait a full minute before un-powering, then upon re-powering it won't auto-mount and manual mount attempts give an error. It wasn't like this before as it started around 2 months ago. An Ext4-formatted drive doesn't have this problem, and can even be hot-unplugged without issues (discovered by having a bad dock). Log excerpt: (Important point: $MFTMirr does not match $MFT)

Mar 10 14:42:39 confucius kernel: usb 4-1.1: new SuperSpeed USB device number 10 using xhci_hcd
Mar 10 14:42:39 confucius kernel: usb 4-1.1: New USB device found, idVendor=1058, idProduct=107c, bcdDevice=10.42
Mar 10 14:42:39 confucius kernel: usb 4-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Mar 10 14:42:39 confucius kernel: usb 4-1.1: Product: Elements 107C
Mar 10 14:42:39 confucius kernel: usb 4-1.1: Manufacturer: Western Digital
Mar 10 14:42:39 confucius kernel: usb 4-1.1: SerialNumber: 574343344E30353730323533
Mar 10 14:42:39 confucius kernel: usb-storage 4-1.1:1.0: USB Mass Storage device detected
Mar 10 14:42:39 confucius kernel: scsi host5: usb-storage 4-1.1:1.0
Mar 10 14:42:39 confucius mtp-probe: checking bus 4, device 10: "/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/usb4/4-1/4-1.1"
Mar 10 14:42:39 confucius mtp-probe: bus: 4, device: 10 was not an MTP device
Mar 10 14:42:39 confucius mtp-probe: checking bus 4, device 10: "/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/usb4/4-1/4-1.1"
Mar 10 14:42:39 confucius mtp-probe: bus: 4, device: 10 was not an MTP device
Mar 10 14:42:40 confucius kernel: scsi 5:0:0:0: Direct-Access     WD       Elements 107C    1042 PQ: 0 ANSI: 6
Mar 10 14:42:40 confucius kernel: sd 5:0:0:0: Attached scsi generic sg4 type 0
Mar 10 14:42:40 confucius kernel: sd 5:0:0:0: [sdd] Spinning up disk...
Mar 10 14:42:49 confucius kernel: .........ready
Mar 10 14:42:49 confucius kernel: sd 5:0:0:0: [sdd] 732558336 4096-byte logical blocks: (3.00 TB/2.73 TiB)
Mar 10 14:42:49 confucius kernel: sd 5:0:0:0: [sdd] Write Protect is off
Mar 10 14:42:49 confucius kernel: sd 5:0:0:0: [sdd] No Caching mode page found
Mar 10 14:42:49 confucius kernel: sd 5:0:0:0: [sdd] Assuming drive cache: write through
Mar 10 14:42:49 confucius kernel: sdd: sdd1
Mar 10 14:42:49 confucius kernel: sd 5:0:0:0: [sdd] Attached SCSI disk
Mar 10 14:42:50 confucius kernel: ntfs3: Max link count 4000
Mar 10 14:42:50 confucius kernel: ntfs3: Enabled Linux POSIX ACLs support
Mar 10 14:42:50 confucius kernel: ntfs3: Read-only LZX/Xpress compression included
Mar 10 14:43:05 confucius kernel: ntfs3: sdd1: volume is dirty and "force" flag is not set!
Mar 10 14:43:05 confucius udisksd: $MFTMirr does not match $MFT (record 3).
Mar 10 14:43:05 confucius udisksd: Failed to mount '/dev/sdd1': Input/output error
Mar 10 14:43:05 confucius udisksd: NTFS is either inconsistent, or there is a hardware fault, or it's a
Mar 10 14:43:05 confucius udisksd: SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
Mar 10 14:43:05 confucius udisksd: then reboot into Windows twice. The usage of the /f parameter is very
Mar 10 14:43:05 confucius udisksd: important! If the device is a SoftRAID/FakeRAID then first activate
Mar 10 14:43:05 confucius udisksd: it and mount a different device under the /dev/mapper/ directory, (e.g.
Mar 10 14:43:05 confucius udisksd: /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
Mar 10 14:43:05 confucius udisksd: for more details.

Doing a disk check in Windows takes very long, I think in the order of 5 hours. This isn't a workable situation for us. Is there a way that I can troubleshoot this error in a reasonable manner (not taking 5 hours each time), or a way to just fix this by discarding/ignoring one of the $MFT? * drive shares data with Windows PCs --- Nemo has auto-mounting enabled. I eject with the eject button in Nemo (i.e. not umount)

I can't mount my HDD anymore. After the last time I used it, I clicked "**Remove safely**" in my file browser, and now I can't read data on it anymore. Here are some diagnostic commands I executed:

`
# fdisk -l
Disk /dev/sdb: 465.73 GiB, 500074283008 bytes, 976707584 sectors
Disk model: Elements 10A8
Units: sectors of 1 × 512 = 512 bytes
Sector size (logical / physical): 512 bytes / 512 bytes
I/O size (minimum / optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xf2c19c1e

Device     Boot Start       End   Sectors   Size  Id Type
/dev/sdb1        256  976707583  976707328  465.7G  7 HPFS/NTFS/exFAT

` # fsck.exfat /dev/sdb1 exfatprogs version : 1.2.2 too long label. 139 failed to read volume label invalid start cluster of allocate bitmap. 0x34c04c90 failed to read bitmap failed to verify root directory. /dev/sdb1: clean. directories 1, files 0 --- # mount /dev/sdb1 /media/myself/Medias/ mount: /media/myself/Medias: can't read superblock at address /dev/sdb1. dmesg(1) may have more information after failed mount system call. --- Here are the messages seen in dmesg when attempting the previous mount command:

`
[ 1439.474346] exFAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 1439.516358] exFAT-fs (sdb1): failed to read sector(0xd57a397000)
[ 1439.516365] exFAT-fs (sdb1): failed to load upcase table
[ 1439.516367] exFAT-fs (sdb1): failed to recognize exfat type

` I'm trying TestDisk to analyze/repair my HDD, but how can I repair my HDD? I have no issues booting into my system, this question is about **repairing an external drive**, used for data storage.

On Windows and other Linux distros, I simply go to Steam Storage Settings and add that external harddrive as a library storage device from here: When I try to do it via the "Add Drive" option, then I get an error popup that says the following: > Failed to add Steam library folder --- Why am I getting that error? How can I use my external harddrive and install games onto it? The Drive itself is in perfect condition. I tested installing Steam games onto it with other operating systems. I tested on Windows 11, Linux Mint and Ubuntu. It worked on all of them, but on SteamOS, it doesn't want to work. --- Does anyone know why it doesn't work or how I can get it to work?

One the directories in my machine has a high turn-over of very large files, so as I was snapshotting the file-system, those files began to fill-up my hard-drive. I transformed it into a btrfs subvolume so that the snapshots wouldn't contain them. I used something like the following commands:

mv $DIR $DIR.old
btrfs subvolume create $DIR
cp --reflink=always $DIR.old/. $DIR
rm -r $DIR.old

But now btrfs receive throws an error when I try to send the snapshots to my backup HD. The relevant lines when running it with --log debug are these:

unlink o822875-724-0/$FILE
rmdir o822875-724-0
ERROR: rmdir o822875-724-0 failed: Directory not empty

where $FILE is a file that was added to the directory just before the snapshot that is being sent. The question: how do I fix this? I don't care about preserving the contents of that directory across snapshots in my main HD or the backup one. I'd like to avoid doing a complete backup from scratch, both because I'd like to keep the current history, and because that takes time. Notes: I'm using btrbk for backups, but I managed to isolate the faulty command to the btrfs receive on the backup HD side. I know that directories with names such as o822875-724-0 have something to do with btrfs internals, even more so because I have no such directory in my filesystem, but I don't quite understand how that works.

I've got a Western Digital Technologies, Inc. Elements 25A2. This is the way it introduces itself through the lsusb command. Unfortunately, I cannot format it. Through Gnome Disk Utility the command refuses to run and returns: “Error wiping device: Failed to probe the device ‘/dev/sdd’ (udisks-error-quark, 0)”. I tried various commands but they all failed: - sudo fsck /dev/sdd - sudo e2fsck -b 8193 /dev/sdd - sudo e2fsck -b 32768 /dev/sdd I want to recreate a file system because we can consider that the device is totally empty (and notice I haven't got any image copy). (base) avy@machine:~$ sudo parted -l Erreur: /dev/sdd : étiquette de disque inconnue #unknown disk's label Modèle : WD Elements 25A2 (scsi) Disque /dev/sdd : 2000GB Taille des secteurs (logiques/physiques) : 512B/512B #block's size (logical/physical) Table de partitions : unknown #partition table Drapeaux de disque : #disk's flags As far as I know, solutions like DDRescue are based on existing image of a file system (e.g. sudo ddrescue .img ), so I can’t use them. The hard drive itself seems "healthy" after SMART control: - sudo smartctl --health /dev/sdd → SMART overall-health self-assessment test result: PASSED - sudo smartctl --log=error /dev/sdd → SMART Error Log Version: 1 \n No Errors Logged So, I have a little hope to avoid throwing it in the trash. Here are the kernel messages relating to the drive: sudo dmesg --follow [ 444.527131] usb 2-4: Product: Elements 25A2 [ 444.527134] usb 2-4: Manufacturer: Western Digital [ 444.527138] usb 2-4: SerialNumber: 575855314533383859304150 [ 444.528739] usb-storage 2-4:1.0: USB Mass Storage device detected [ 444.529073] scsi host6: usb-storage 2-4:1.0 [ 445.546672] scsi 6:0:0:0: Direct-Access WD Elements 25A2 1021 PQ: 0 ANSI: 6 [ 445.546937] sd 6:0:0:0: Attached scsi generic sg3 type 0 [ 445.547812] sd 6:0:0:0: [sdd] Spinning up disk... [ 446.570416] ........ready [ 453.738963] sd 6:0:0:0: [sdd] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB) [ 453.739246] sd 6:0:0:0: [sdd] Write Protect is off [ 453.739251] sd 6:0:0:0: [sdd] Mode Sense: 47 00 10 08 [ 453.739479] sd 6:0:0:0: [sdd] No Caching mode page found [ 453.739487] sd 6:0:0:0: [sdd] Assuming drive cache: write through [ 456.492061] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 456.492069] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 456.492074] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 456.492080] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 456.492087] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 456.492096] Buffer I/O error on dev sdd, logical block 0, async page read [ 459.561974] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 459.561982] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 459.561988] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 459.561994] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 459.562001] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 459.562010] Buffer I/O error on dev sdd, logical block 0, async page read [ 462.747978] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 462.747986] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 462.747991] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 462.747997] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 462.748004] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 462.748012] Buffer I/O error on dev sdd, logical block 0, async page read [ 462.748032] ldm_validate_partition_table(): Disk read failed. [ 465.948181] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 465.948188] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 465.948192] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 465.948197] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 465.948202] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 465.948210] Buffer I/O error on dev sdd, logical block 0, async page read [ 469.216369] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 469.216371] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 469.216372] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 469.216374] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 469.216375] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 469.216378] Buffer I/O error on dev sdd, logical block 0, async page read [ 472.382131] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 472.382139] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 472.382145] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 472.382151] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 472.382157] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 472.382166] Buffer I/O error on dev sdd, logical block 0, async page read [ 475.548568] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 475.548570] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 475.548571] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 475.548573] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 475.548574] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 475.548577] Buffer I/O error on dev sdd, logical block 0, async page read [ 475.548611] Dev sdd: unable to read RDB block 0 [ 478.628200] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 478.628208] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 478.628213] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 478.628220] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 478.628227] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 478.628236] Buffer I/O error on dev sdd, logical block 0, async page read [ 481.707768] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 481.707776] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 481.707782] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 481.707788] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 481.707795] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 481.707804] Buffer I/O error on dev sdd, logical block 0, async page read [ 484.864341] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 484.864349] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 484.864355] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 484.864361] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 18 00 00 08 00 [ 484.864368] blk_update_request: critical medium error, dev sdd, sector 24 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 484.864377] Buffer I/O error on dev sdd, logical block 3, async page read [ 487.982899] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 487.982907] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 487.982912] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 487.982919] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 487.982925] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 487.982935] Buffer I/O error on dev sdd, logical block 0, async page read [ 491.116325] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 491.116333] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 491.116339] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 491.116345] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 491.116351] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 491.116361] Buffer I/O error on dev sdd, logical block 0, async page read [ 491.116432] sdd: unable to read partition table [ 491.504986] sd 6:0:0:0: [sdd] Attached SCSI disk [ 494.284826] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 494.284834] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 494.284840] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 494.284846] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 494.284853] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 497.472400] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 497.472408] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] [ 497.472413] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error [ 497.472419] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 497.472426] blk_update_request: critical medium error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 497.472435] Buffer I/O error on dev sdd, logical block 0, async page read ---------- Disclaimer: I won't accept answers such as "Buy a new hard-drive", "Use warranty" (all examples given are true stories). There's nothing of value in this hard-drive, I want to improve my IT skills and bring added value to Stack Exchange platforms.

I have a RasPi 4 connected to a 12TB EXT4 hard drive in a Sabrent cage hub which I use for an OpenMediaVault NAS. The drive worked fine for about a month until its file system started to go missing in OMV, either completely or visible and unmounted with the status "missing." I've tried automatically rebooting every 12 hours or manual restarts (the Pi and cage have separate power buttons) and cannot tell which method is more reliable. I've noticed the block device sometimes changes between sda(1) and sdb(1) and other times no partitions are listed in fdisk or df. Sometimes the drive is SMART compatible (and passes), other times it says it isn't. I've had error messages after the following commands:

**(1) [2024-11-02] sudo smartctl -a /dev/sda | less**

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status:  (0x80) Offline data collection activity
                                        was never started.
                                        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:                (   87) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        (   1) minutes.
SCT capabilities:              (0x003d) 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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   132   132   054    Pre-fail  Offline      -       96
  3 Spin_Up_Time            0x0007   155   155   024    Pre-fail  Always       -       425 (Average 425)

**(2) [2024-11-02] dmesg**

[ 1197.499680] critical target error, dev sda, sector 23437770624 op 0x0:(READ)                                                                                                                                                                                                                                              flags 0x0 phys_seg 1 prio class 2

[ 1197.499692] Buffer I/O error on dev sda, logical block 2929721328, async page                                                                                                                                                                                                                                              read

[Note: no errors in dmesg as of 2024-12-02]

**(3) [2024-12-01] sudo fdisk -l /dev/sda**

fdisk: cannot open /dev/sda: Input/output error

**(4) [2024-12-01] sudo fsck /dev/sda**

fsck.ext2: Input/output error while trying to open /dev/sda

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193  [Note: this option timed out]
 or
    e2fsck -b 32768  [Note: this option timed out]

**(5) [2024-12-01] sudo smartctl -i /dev/sda**

Read Device Identity failed: scsi error medium or hardware error (serious)

**(6) [2024-12-01] sudo smartctl --all /dev/sda1 --test=short -T permissive**

SMART support is:     Unavailable - device lacks SMART capability

Error Counter logging not supported

No Self-tests have been logged

It appears most likely to unmount after I'm away from home and don't perform updates for awhile (I have not set up a reverse proxy for the RasPi in general, only for a Plex server). I can't tell if the hard drive is about to fail or if this is all just an issue with booting.

I am trying to back up data (230 GB, 160k files), over USB3.0 to a newly bought external Seagate Expansion Portable Drive of 4 TB, formatted as NTFS. I am running Ubuntu 18.04.3 LTS. I first tried using a simple cp command in the terminal, but after only copying a few percent, the copying started stuttering and became slow. After some time the disk became unresponsive. Remounting the disk did not work. I tried connecting the disk to another computer, and was first unable to mount it, and then after a few attempts, it would mount but read/write would be very slow. Once the cp starts failing, I get the following errors in dmesg (all these messages are repeating multiple times but with some different numbers): [67598.098118] sd 4:0:0:0: [sdb] tag#18 uas_zap_pending 0 uas-tag 19 inflight: CMD [67598.098122] sd 4:0:0:0: [sdb] tag#18 CDB: Write(16) 8a 00 00 00 00 01 1c 75 24 18 00 00 04 00 00 00 [67598.225621] usb 1-9: reset high-speed USB device number 5 using xhci_hcd [67598.378202] scsi host4: uas_eh_device_reset_handler success [67598.378466] sd 4:0:0:0: [sdb] tag#14 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK [67598.378468] sd 4:0:0:0: [sdb] tag#14 CDB: Write(16) 8a 00 00 00 00 01 1c 74 d0 18 00 00 04 00 00 00 [67598.378470] blk_update_request: I/O error, dev sdb, sector 4772384792 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0 [67598.378473] buffer_io_error: 246 callbacks suppressed [67598.378474] Buffer I/O error on dev sdb2, logical block 596515075, lost async page write [67635.212662] scsi host4: uas_eh_device_reset_handler start [67635.213657] sd 4:0:0:0: [sdb] tag#28 uas_zap_pending 0 uas-tag 10 inflight: CMD [67635.213658] sd 4:0:0:0: [sdb] tag#28 CDB: Write(16) 8a 00 00 00 00 01 1c 75 e8 18 00 00 04 00 00 00 [67635.340988] usb 1-9: reset high-speed USB device number 5 using xhci_hcd [67635.490335] scsi host4: uas_eh_device_reset_handler success I left the disk for a week, and then did a SMART scan using the Seagate Bootable Tool, which showed no issues. Thus, I attempted copying the data again. The disk would mount properly now and I could read/write without issues, so I started an rsync command. First I did rsync -avh source dest It worked, albeit slowly, for about 20 % of the data, then it started stuttering so I stopped the transfer. I restarted the transfer using rsync -avhW source dest --inplace to try and make it faster. It ran great, much faster than the first attempt, but after a few minutes, I received errors: rsync: recv_generator: failed to stat "..." : Input/output error (5) rsync: write failed on "...": Input/output error (5) rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2] In dmesg I see the following: [ 6772.890553] buffer_io_error: 1092735 callbacks suppressed [ 6772.890556] Buffer I/O error on dev sdb2, logical block 874428, async page read Once this happened, the disk became unresponsive. After a few minutes I could remount it, and checking the folder to which I was copying data it is completely empty, including the files that were properly copied during my first rsync attempt. I did not try to restore any data to see if the data was still intact, I suppose that it is only the file table that has been corrupted. The files that were being copied at the time of failure are of type .mat.gz, on the order of 1 MB each. As a sidenote, an old external Seagate disk recently broke when I was copying small amounts of data from it, on this computer (the infamous click of death...), which was also my first HDD ever to die. I have no idea what to make of this, if the problem lies with how I am copying data (can copying data destroy disks?), if the problem lies with hardware (computer, HDD, USB-SATA converter, ...) or if it has to do with Ubuntu... Normally I only run Manjaro and I never experienced this kind of issues.

I want to know the speed of data transfer between a HDD or SSD and the mainboard. It through a command. If is possible through a GUI, it is accepted too **Goal**: I want to do a comparison of speeds against * Thunderbolt 3/4/5 if is connected through a docking station with a M.2 NvME PCIe versus * SSD (HDD) and the mainboard Thus I want to know how viable would be install Linux in a secondary SSD through a docking station with Thunderbolt. How similar would be the time of response of Linux running with that approach? I know thunderbolt has the following values about speed * Thunderbolt 1: 10 Gbit/s per channel, or 20 Gbit/s total * Thunderbolt 2: 20 Gbit/s total * Thunderbolt 3 and 4: 40 Gbit/s bidirectional * Thunderbolt 5: 80 Gbit/s bidirectional So, *If the difference is really huge* against the _mobo/SSD_ thus I must consider use dual boot but it takes space in the primary disk.