Does anyone know if there is an elegant way to tell an external usb drive not to spin down after a period of inactivity? I've seen cron based solutions that write a file every minute, but nothing that smells of nice unixey elegance. There must be a hdparm, or scsi command that I can issue (usb drives are accessed via the sd driver in OpenBSD) to the drive to tell it to not sleep. I'm afraid that this is probably a *feature* built into the controller in the enclosure, and as such not much can change it aside from ripping the drive out of it's enclosure and plopping it directly in the machine, but I figured I would ask, on the off chance. Ideally, I'm looking for an OpenBSD solution, but I know there are others out there w/the same problem so any solutions will be considered for the answer.

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.

I have added a new disk to the server: [root@ns1 tgt]# lsblk |grep sdh sdh 8:112 0 600M 0 disk Also, I have created a new entry for /dev/sdh in /etc/tgt/targets.conf [root@ns1 tgt]# cat /etc/tgt/targets.conf |grep /dev/ direct-store /dev/sdb direct-store /dev/sdc direct-store /dev/sdd direct-store /dev/sde direct-store /dev/sdf direct-store /dev/sdg direct-store /dev/sdh [root@ns1 tgt]# How can I reload the new configuration and make available the new lun? I have tried systemctl reload tgtd, tgt-admin -e and tgt-admin --ready ALL, but none has worked. Bellow we can see there is no /dev/sdh yet. [root@ns1 tgt]# tgtadm --mode target --op show|grep /dev/ Backing store path: /dev/sdb Backing store path: /dev/sdc Backing store path: /dev/sdd Backing store path: /dev/sde Backing store path: /dev/sdf Backing store path: /dev/sdg [root@ns1 tgt]# I have tested with systemctl restart tgtd and it has worked, but it affect the initiator hosts. ie after restart tgtd (log from some initiator host): Jun 6 18:20:41 rac1 kernel: connection1:0: detected conn error (1020) Jun 6 18:20:41 rac1 iscsid: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) Jun 6 18:20:43 rac1 iscsid: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (2) Jun 6 18:20:43 rac1 kernel: connection1:0: detected conn error (1020) Jun 6 18:20:45 rac1 kernel: connection1:0: detected conn error (1020) Jun 6 18:20:45 rac1 iscsid: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (2) Jun 6 18:20:46 rac1 kernel: session1: session recovery timed out after 5 secs Jun 6 18:20:47 rac1 multipathd: checker failed path 8:112 in map data1 Jun 6 18:20:47 rac1 multipathd: data1: remaining active paths: 0 Jun 6 18:20:47 rac1 kernel: device-mapper: multipath: Failing path 8:112. Jun 6 18:20:47 rac1 kernel: device-mapper: multipath: Failing path 8:80. Jun 6 18:20:47 rac1 kernel: device-mapper: multipath: Failing path 8:96. Jun 6 18:20:47 rac1 multipathd: checker failed path 8:80 in map fra2 Jun 6 18:20:47 rac1 multipathd: fra2: remaining active paths: 0 Jun 6 18:20:47 rac1 multipathd: checker failed path 8:96 in map fra3 Jun 6 18:20:47 rac1 multipathd: fra3: remaining active paths: 0 Jun 6 18:20:47 rac1 iscsid: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (2) Jun 6 18:20:47 rac1 kernel: connection1:0: detected conn error (1020) Jun 6 18:20:49 rac1 iscsid: iscsid: connection1:0 is operational after recovery (4 attempts)

When a disk starts to die slowly multipath starts to Failing & Reinstating paths and this keeps forever.. (I'm using LSI-3008HBA card with SAS-JBOD not FC-Network) Dmesg; Sep 13 11:20:17 DEV2 kernel: sd 0:0:190:0: attempting task abort! scmd(ffff88110e632948) Sep 13 11:20:17 DEV2 kernel: sd 0:0:190:0: [sdft] tag#3 CDB: opcode=0x0 00 00 00 00 00 00 Sep 13 11:20:17 DEV2 kernel: scsi target0:0:190: handle(0x0037), sas_address(0x5000c50093d4e7c6), phy(38) Sep 13 11:20:17 DEV2 kernel: scsi target0:0:190: enclosure_logical_id(0x500304800929ec7f), slot(37) Sep 13 11:20:17 DEV2 kernel: scsi target0:0:190: enclosure level(0x0001),connector name(1 ) Sep 13 11:20:17 DEV2 kernel: sd 0:0:190:0: task abort: SUCCESS scmd(ffff88110e632948) Sep 13 11:20:18 DEV2 kernel: device-mapper: multipath: Failing path 130:240. Sep 13 11:25:34 DEV2 kernel: device-mapper: multipath: Reinstating path 130:240. As you can see kernel aborted the mission and after that multipath failed. So I want to get rid of this problem via telling Multipath "do not Reinstate the path". This method will keep dead the zombie disk. How can I do that?

Similar question was asked here . I have a SATA disk connected to a SAS2308 HBA and there is backplane. Is there any way i can make the linux system ignore the disk at boot.

# lsscsi -v

[0:0:3:0]    disk    ATA      WDC WD10EFRX-68J 1A01  /dev/sda 
  dir: /sys/bus/scsi/devices/0:0:3:0  [/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:09.0/0000:04:00.0/host0/port-0:3/end_device-0:3/target0:0:3/0:0:3:0]

The HBA is this,

# lspci -nn -v -s 04:00.0
04:00.0 Serial Attached SCSI controller : Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0087] (rev 05)
        Subsystem: Hewlett Packard Enterprise H220i [1590:0041]
        Flags: bus master, fast devsel, latency 0, IRQ 17
        I/O ports at c000 [size=256]
        Memory at dd540000 (64-bit, non-prefetchable) [size=64K]
        Memory at dd500000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at dd400000 [disabled] [size=1M]
        Capabilities:  Power Management version 3
        Capabilities:  Express Endpoint, IntMsgNum 0
        Capabilities: [d0] Vital Product Data
        Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [c0] MSI-X: Enable+ Count=16 Masked-
        Capabilities:  Advanced Error Reporting
        Capabilities: [1e0] Secondary PCI Express
        Capabilities: [1c0] Power Budgeting 
        Capabilities:  Dynamic Power Allocation 
        Capabilities:  Alternative Routing-ID Interpretation (ARI)
        Kernel driver in use: mpt3sas
        Kernel modules: mpt3sas

The error in dmesg is like so,

[  235.126718] mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00)
[  235.126738] sd 0:0:3:0: [sda] tag#4233 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=3s
[  235.126751] sd 0:0:3:0: [sda] tag#4233 CDB: Read(10) 28 00 00 44 d0 00 00 00 08 00
[  235.126757] I/O error, dev sda, sector 4509696 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[  235.126787] sd 0:0:3:0: [sda] tag#4227 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=3s
[  235.129288] sd 0:0:3:0: [sda] tag#4227 CDB: Read(10) 28 00 1c 6d 3a 00 00 00 08 00
[  235.129293] I/O error, dev sda, sector 476920320 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[  235.474711] sd 0:0:3:0: Power-on or device reset occurred
[  238.716033] mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00)

Environment: Debian Bullseye, up to date at the time of writing, nvme-cli 1.12 I am totally new to NVMe and currently try to configure an NVMe SSD correctly. As far as I can tell, I don't need metadata, but **I would like to use the T10-PI protection information.** I have got two questions regarding this subject: **First, I'd like to know how to find out whether that protection has been enabled for a certain device or namespace at all.** I know that I can enable or disable the T10-PI when formatting the device or namespace, but I can't figure out how to get its current status. I have read a good part of the manual pages of the various nvme commands, and also have tried to make sense of the NVMe specification to a certain level, but to no avail. I just seem to be unable to spot it. I am having that problem only with that specific setting; with other settings that are of interest to me, it didn't take too long to find out how to read their current status or value. **Second, I am not sure how to enable that protection.** Theoretically, and from reading man nvme-format, it is clear. I just have to add the -i parameter to the format command to have something like that: nvme format /dev/nvme0 -l 3 -i 1 The disk in question provides 6 LBA modes, mode 3 being the one I want: 4096 bytes per sector, no metadata; hence the -l 3 parameter. -i 1 turns on the T10-PI. When I issue the command above, it gets executed without error message. Afterwards, smartctl -x /dev/nvme0 shows that the current LBA size is now 4096; nvme id-ns /dev/nvme0n1 confirms that mode 3 is in use as expected. So far, so good. But the following is very suspicious: root@gaia ~/scripts # nvme list Node SN Model Namespace Usage Format FW Rev ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 PHFT640100G7800CGN INTEL SSDPEDMD800G4 1 800.17 GB / 800.17 GB 4 KiB + 0 B 8DV10171 Under Format, it shows 4 KiB + 0 B. Why? As far as I have understood, the T10-PI needs at least 8 bytes of metadata per LBA. Therefore, I am unsure what actually happens. Does nvme format /dev/nvme0 -l 3 -i 1 just leave the PI disabled (because there is no metadata, and therefore no space for it)? Or is the PI enabled, but nvme list shows only the "real" metadata size (not including the "implicit" bytes which are needed for the PI)? Do I need to use -l 4 instead of -l 3 with nvme format? -l 4 means 4096 bytes LBA size + 8 bytes metadata. If I need to use -l 4, why does nvme format -l 3 -i 1 not throw an error due to wrong command line parameters (we can't turn on T10-PI if we don't have metadata)?

I'm attempting to do raw reads of an old magneto-optical disk in Debian 10 (I can do this in Windows without issues) I was expecting linux to add the disk as /dev/hd*n* or /dev/sd*n*, but it appears to be seeing it as a cdrom (/dev/sr*n*). Here's the relevant lines from dmesg: [ 22.112062] scsi host33: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs [ 37.472036] scsi host36: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs [ 38.764112] scsi 36:0:5:0: WORM LMS LD 1200E SCSI 0183 PQ: 0 ANSI: 1 [ 38.780029] scsi target36:0:5: Beginning Domain Validation [ 38.801822] scsi target36:0:5: Ending Domain Validation [ 41.134286] sr 36:0:5:0: [sr1] scsi-1 drive [ 41.134456] sr 36:0:5:0: Attached scsi CD-ROM sr1 [ 41.134516] sr 36:0:5:0: Attached scsi generic sg2 type 4 [ 41.178402] sr 36:0:5:0: [sr1] unsupported sector size 1024. [ 41.312627] PM: Image not found (code -22) when I attempt to read from /dev/sr1 using dd bs=1024 if=/dev/sr1 I get 0 records; presumably because /dev/sr1 doesn't accept a 1024 byte block size, but I know that is what the M/O disk is using. Incidentally, cat /proc/scsi/scsi results in: Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 2.0 Type: Direct-Access ANSI SCSI revision: 06 Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: NECVMWar Model: VMware SATA CD00 Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 05 Host: scsi36 Channel: 00 Id: 05 Lun: 00 Vendor: LMS Model: LD 1200E SCSI Rev: 0183 Type: WORM ANSI SCSI revision: 01 is there a way to make linux create a /dev/sd*n* device file for it rather than a /dev/sr*n*?

I'm getting timeouts on inquiry while a write buffer is active because the device cannot respond to the inquiry until the write buffer is complete. See errors . Dec 10 16:04:39 soul kernel: sd 0:0:34:0: [sdai] tag#2540 CDB: Inquiry 12 01 83 00 fe 00 Done: TIMEOUT_ERROR Dec 10 16:04:39 soul kernel: sd 0:0:34:0: attempting task abort!scmd(0x000000005af3d755), outstanding for 7050 ms & timeout 7000 ms Dec 10 16:04:39 soul kernel: sd 0:0:34:0: task abort: SUCCESS scmd(0x000000005af3d755) it appears that inquiry has a 7 sec timeout; I was only aware of a single timeout control of /sys/block/sdac/device/timeout 44 Is there a way to change the timeout for inquiry ?

[This is on Debian 12] To fully access my DVD drive, I need to also know its SCSI generic path (/dev/sgX) in addition to its expected CDROM-/dev/srX path. The specific device is important, though, and I need to access the device even if the system re-shuffles the /dev/srXs and /dev/sgXs.

sudo lsscsi -g
[3:0:0:0]    cd/dvd  HL-DT-ST BD-RE  WH16NS60  1.05  /dev/sr0   /dev/sg3

sudo blkid /dev/sr0
/dev/sr0: UUID="035bbeef20202020" LABEL="WALDEINSAMKEIT" BLOCK_SIZE="2048" TYPE="udf"

sudo blkid /dev/sg3

/dev/sr0 is set with a /dev/disk/by-uuid/035bbeef20202020 but if /dev/sg3 doesn't actually have a UUID (I'm guessing it's not seen as a block device), I could go for the full controller/system path, per this Linus rant I found https://yarchive.net/comp/linux/scsi_ids.html

sudo udevadm info -q path -n /dev/sr0
/devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/block/sr0

sudo udevadm info -q path -n /dev/sg3
/devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/scsi_generic/sg3

This does not seem like a solution either, as the path includes sr0 or sg3 which will change order. /sys/devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0 seems to be a directory the device is referencing but I can't find anything more than the folders block/sr0 and scsi_generic/sg3 which again revert to the original problem of sr0 and sg3 changing if the system cables are reordered or something. How can I get a consistent identifier for /dev/sg3? I have searched hard, but I must be missing a command.

I use Rocky Linux and have to change my hard disk bus type but then my booting failed. However, it runs normally when i select the bus type NVMe. Boot failed How do i solve this? Should i make a new VM and choose SCSI from the start?

I am working on an iMX6ULL board running a Debian-based OS with suspend capabilities. A USB hub (USB2514) is connected to the USB bus. When a single device or two devices with different VID and PID are connected to the USB hub (and consequently to the USB bus) the system resumes from suspend almost immediately. However, the system resume is much slower when I have two devices connected to the USB hub with the same VID and PID. After digging, I found that the OS resets the USB devices after wake-up from suspend and before resuming (see code blocks below). **How can I prevent the OS from resetting the USB devices on wake-up to speed up the resume process when two devices with the same VID and PID are connected to the same bus?** ___ ###### Logs - Single Device (*Normal*) Wake-up

bash
>>>>>>>>>>>>>> SYSTEM WAKE-UP REQUEST
[ 9217.484783] ieee80211 phy6: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[ 9217.484817] ieee80211 phy6: brcmf_cfg80211_get_tx_power: error (-5)
[ 9218.076812] PM: suspend devices took 1.640 seconds
[ 9218.082099] Disabling non-boot CPUs ...
[ 9218.330490] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 9218.399775] usb 2-1.1: reset high-speed USB device number 19 using ci_hdrc
[ 9218.476006] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Jun 13 2018 23:24:39 version 7.45.98.52 (r691997 CY) FWID 01-8b9f8ef5
[ 9218.552328] PM: resume devices took 0.470 seconds
[ 9218.608394] OOM killer enabled.
[ 9218.611611] Restarting tasks ... done.
[ 9218.714350] random: crng reseeded on system resumption
[ 9218.771424] PM: suspend exit
>>>>>>>>>>>>>> SYSTEM RESUME

- Two Devices Same VID and PID Wake-up

bash
>>>>>>>>>>>>>> SYSTEM WAKE-UP REQUEST
[ 8907.844493] ieee80211 phy0: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[ 8907.844524] ieee80211 phy0: brcmf_cfg80211_get_tx_power: error (-5)
[ 8908.436812] PM: suspend devices took 1.670 seconds
[ 8908.442572] Disabling non-boot CPUs ...
[ 8908.681128] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 8908.749956] usb 2-1.3: reset high-speed USB device number 13 using ci_hdrc
[ 8908.826696] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Jun 13 2018 23:24:39 version 7.45.98.52 (r691997 CY) FWID 01-8b9f8ef5
[ 8908.859973] usb 2-1.3: device no response, device descriptor read/64, error -71
[ 8909.089935] usb 2-1.3: device no response, device descriptor read/64, error -71
[ 8909.309918] usb 2-1.3: reset high-speed USB device number 13 using ci_hdrc
[ 8909.419914] usb 2-1.3: device no response, device descriptor read/64, error -71
[ 8909.649893] usb 2-1.3: device no response, device descriptor read/64, error -71
[ 8909.869896] usb 2-1.3: reset high-speed USB device number 13 using ci_hdrc
[ 8910.309878] usb 2-1.3: device not accepting address 13, error -71
[ 8910.409859] usb 2-1.3: reset high-speed USB device number 13 using ci_hdrc
[ 8910.849852] usb 2-1.3: device not accepting address 13, error -71
[ 8910.949853] usb 2-1.1: reset high-speed USB device number 14 using ci_hdrc
[ 8911.102358] PM: resume devices took 2.660 seconds
[ 8911.227343] OOM killer enabled.
[ 8911.230543] Restarting tasks ...
[ 8911.281057] usb 2-1.3: USB disconnect, device number 13
[ 8911.292238] done.
[ 8911.294268] random: crng reseeded on system resumption
[ 8911.351833] PM: suspend exit
>>>>>>>>>>>>>> SYSTEM RESUME

___ So far, I have attempted the following (*without success*): - Applied udev rules to set the removable attribute to fixed or 0. - Configured the USB hub's NON_REM pins, causing /sys/bus/usb/devices/2-1.1/removable to report as fixed. - Modified /sys/bus/usb/devices/2-1.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/removable by writing 0 or fixed, but this did not resolve the issue. - Loaded the SCSI Generic (sg) kernel module, exposing the devices at /dev/sg*, but they remained listed under /dev/sd* as well. - Blacklisted the usb-storage module, which caused the SCSI Generic module to stop functioning.

I am trying to boot Solaris 8 from external scsi CD-ROM drive Yamaha 8/8/24 on a Sun blade 150 through Open Boot. Its scsi ID is set to 6. probe-scsi-all reports that the CD drive is at: /pci@1f,0/pci@5/scsi@1 target 6, unit 0. So I am trying to boot with this command: boot /pci@1f,0/pci@5/scsi@1/disk@6,0 But it just halts until I switch off the external scsi CD drive. Then it fails with an error. The CD drive does not give any read indication during the entire time. The Solaris cd and the CD drive are OK I think, I only have some doubts about the scsi cable. Is this the correct command to boot in my case? Maybe the Yamaha is not compatible with the Sun hardware?

I'm having a little issue. I have a live system which run on RHEL 6.7 (VM) and have VMware 6.5 (which is not managed by our group). The issue is, the other group tried to extend the capacity of an existing disk on a VM. After that, I ran a scan command to detect new disk as usual with echo "- - -" > /sys/class/scsi_host/host0/scan, but nothing happened. They added 40G on sdb disk which should be 100G and I saw that is changed on VM but not on Linux. So where is the problem ? As I said, this is a live system, so I don't want to reboot it. Here is the system :

# df -h /dev/mapper/itsmvg-bmclv
59G   47G  9.1G  84% /opt/bmc

# lsblk sdb
  8:16   0   60G  0 disk  └─itsmvg-bmclv (dm-2)
253:2    0   60G  0 lvm  /opt/bmc

# vgs
  VG       #PV #LV #SN Attr   VSize  VFree
  itsmvg     1   1   0 wz--n- 59.94g     0

# pwd
/sys/class/scsi_host

# ll 
lrwxrwxrwx 1 root root 0 Nov 13 16:18 host0 -> ../../devices/pci0000:00/0000:00:07.1/host0/scsi_host/host0 
lrwxrwxrwx 1 root root 0 Nov 13 16:19 host1 -> ../../devices/pci0000:00/0000:00:07.1/host1/scsi_host/host1 
lrwxrwxrwx 1 root root 0 Nov 13 16:19 host2 -> ../../devices/pci0000:00/0000:00:15.0/0000:03:00.0/host2/scsi_host/host2

I am currently trying to back up data onto an LTO-4 tape using mt-st and gnu tar 1.32, but I want to make sure I stop trying to copy things before the tape runs out! LTO-4 nominally has a capacity of 800G or 1.6T compressed. tapeinfo -f /dev/nst0 | grep Comp returns DataCompEnabled: yes DataCompCapable: yes DataDeCompEnabled: yes CompType: 0x1 DeCompType: 0x1 which I think means that compression is enabled ? Then again, I am adding archives to the tape with mt-st -f /dev/nst0 eod ; tar -czf /dev/nst0 directoryname, so I am also compressing that archive with gzip. In short, I don't know how to visualize how much data the archives on the tape are taking up, they are measured in blocks and I don't know how much data a block consists of. I have copied about 200G of data to the tape already and mt-st -f /dev/nst0 eod ; mt-st -f /dev/nst0 status ; echo -e "\n" ; mt-st -f /dev/nst0 tell returns: SCSI 2 tape drive: File number=1, block number=-1, partition=0. Tape block size 0 bytes. Density code 0x46 (LTO-4). Soft error count since last status=0 General status bits on (9010000): EOD ONLINE IM_REP_EN At block 18763534. But tapeinfo -f | grep MaxBlock returns MaxBlock: 16777215. So it appears I am already passed the maximum block? But mt-st -f /dev/nst0 rewind ; tar -tzvf /dev/nst0 does return a list of all of the files I copied into that archive and moves the tape to the end of data, so I shouldn't have ran out of any space. From looking at the mt manual, I cannot find a way to go to the end of the tape without first writing it. Here is the rest given by tapeinfo if that helps: Vendor ID: 'HP ' Product ID: 'Ultrium 4-SCSI ' Revision: 'U57D' Attached Changer API: No SerialNumber: 'HU1104ERC3' MinBlock: 1 MaxBlock: 16777215 SCSI ID: 0 SCSI LUN: 0 Ready: yes BufferedMode: yes Medium Type: Not Loaded Density Code: 0x46 BlockSize: 0 Block Position: 18763534 Partition 0 Remaining Kbytes: 800226 Partition 0 Size in Kbytes: 800226 ActivePartition: 0 EarlyWarningSize: 0 NumPartitions: 0 MaxPartitions: 0

When trying to sudo dd if=/dev/sda of=dump.dd conv=noerror,sync on my Kingston SSD (SA400S37/120G, SBFK71E0) the dmesg log shows the following:

usb 4-4: new SuperSpeed USB device number 8 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 scsi host0: uas
 scsi 0:0:0:0: Direct-Access     SATAFIRM    S11           0    PQ: 0 ANSI: 6
 sd 0:0:0:0: Attached scsi generic sg0 type 0
 sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
 sd 0:0:0:0: [sda] Write Protect is off
 sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
 sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
 sd 0:0:0:0: [sda] Attached SCSI disk
 
...

 sd 0:0:0:0: [sda] tag#29 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 
 sd 0:0:0:0: [sda] tag#29 CDB: Read(10) 28 00 00 00 6e a0 00 04 00 00
 sd 0:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
 sd 0:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 00 00 e2 a0 00 04 00 00
 sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 30 inflight: CMD IN 
 ...
 scsi host0: uas_eh_device_reset_handler start
 usb 4-4: reset SuperSpeed USB device number 8 using xhci_hcd
 usb 4-4: device firmware changed
 scsi host0: uas_eh_device_reset_handler FAILED err -19
 sd 0:0:0:0: Device offlined - not ready after error recovery
 sd 0:0:0:0: Device offlined - not ready after error recovery
 ...
 sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=31s
 sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 ce a0 00 04 00 00
 I/O error, dev sda, sector 52896 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 2
 ...
 sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=31s
 sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 00 7a a0 00 04 00 00
 I/O error, dev sda, sector 31392 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 2
 sd 0:0:0:0: rejecting I/O to offline device
 usb 4-4: USB disconnect, device number 8
 Buffer I/O error on dev sda, logical block 3412, async page read
 Buffer I/O error on dev sda, logical block 3412, async page read
 ...
 sd 0:0:0:0: [sda] Synchronizing SCSI cache
 sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
 usb 4-4: new SuperSpeed USB device number 9 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb-storage 4-4:1.0: USB Mass Storage device detected
 scsi host0: usb-storage 4-4:1.0
 usb 4-4: reset SuperSpeed USB device number 9 using xhci_hcd

I disabled UAS since "uas_eh_abort_handler" implies some issue related to it. After dd again I got the following:

usb 4-4: new SuperSpeed USB device number 11 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb 4-4: UAS is ignored for this device, using usb-storage instead
 usb-storage 4-4:1.0: USB Mass Storage device detected
 usb-storage 4-4:1.0: Quirks match for vid 174c pid 1153: 800000
 scsi host0: usb-storage 4-4:1.0
 scsi 0:0:0:0: Direct-Access     SATAFIRM    S11           0    PQ: 0 ANSI: 6
 sd 0:0:0:0: Attached scsi generic sg0 type 0
 sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
 sd 0:0:0:0: [sda] Write Protect is off
 sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sd 0:0:0:0: [sda] Attached SCSI disk
 usb 3-1.4.1: reset high-speed USB device number 7 using xhci_hcd
 usb 4-4: reset SuperSpeed USB device number 6 using xhci_hcd
 usb 4-4: device firmware changed
 usb 4-4: USB disconnect, device number 6
 sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=31s
 sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 4f fb 28 00 01 00 00
 I/O error, dev sda, sector 5241640 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
 sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
 sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 4f fc 28 00 01 00 00
 I/O error, dev sda, sector 5241896 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
 sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
 sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 4f fb 28 00 00 08 00
 I/O error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 Buffer I/O error on dev sda, logical block 655206, async page read
 Buffer I/O error on dev sda, logical block 655206, async page read
 sd 0:0:0:0: [sda] Synchronizing SCSI cache
 sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
 usb 4-4: new SuperSpeed USB device number 7 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb-storage 4-4:1.0: USB Mass Storage device detected
 usb-storage 4-4:1.0: Quirks match for vid 174c pid 1153: 800000
 scsi host0: usb-storage 4-4:1.0
 usb 4-4: reset SuperSpeed USB device number 7 using xhci_hcd
 usb 4-4: USB disconnect, device number 7
 usb 4-4: new SuperSpeed USB device number 8 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb 4-4: UAS is ignored for this device, using usb-storage instead
 usb-storage 4-4:1.0: USB Mass Storage device detected
 usb-storage 4-4:1.0: Quirks match for vid 174c pid 1153: 800000
 scsi host0: usb-storage 4-4:1.0
 scsi 0:0:0:0: Direct-Access     SATAFIRM    S11           0    PQ: 0 ANSI: 6
 sd 0:0:0:0: Attached scsi generic sg0 type 0
 sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
 sd 0:0:0:0: [sda] Write Protect is off
 sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sd 0:0:0:0: [sda] Attached SCSI disk
 usb 4-4: reset SuperSpeed USB device number 8 using xhci_hcd
 usb 4-4: device firmware changed
 usb 4-4: USB disconnect, device number 8
 sd 0:0:0:0: [sda] Synchronizing SCSI cache
 sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
 usb 4-4: new SuperSpeed USB device number 9 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb-storage 4-4:1.0: USB Mass Storage device detected
 usb-storage 4-4:1.0: Quirks match for vid 174c pid 1153: 800000
 scsi host0: usb-storage 4-4:1.0
 usb 4-4: reset SuperSpeed USB device number 9 using xhci_hcd

So the problem still remains. Someone has an idea what's going on and can help me? Also I'm interested why actually UAS is used and in the log it says about Attached SCSI even though it is a SATA.

I will keep it short, I am trying to better understand the different standards of storage type interfaces, but the output of smartctl is confusing me a little. Is this an actual problem in my system (like a saw on another post where some firmware was outdated) or am I misunderstanding the output of smartctl. Observe:

> sudo smartctl --scan
/dev/sda -d scsi # /dev/sda, SCSI device
/dev/nvme0 -d nvme # /dev/nvme0, NVMe device

I have an HDD and an NVMe, but the HDD isn't SCSI as far as I know, unless it is "[Why do my SATA devices show up under /proc/scsi/scsi?](https://unix.stackexchange.com/questions/3901/why-do-my-sata-devices-show-up-under-proc-scsi-scsi) ". But if it is, why can I use both -d ata and -d scsi to get information on it:

> sudo smartctl -d ata --info /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.10.5] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Scorpio Black (AF)
Device Model:     WDC WD5000BPKT-75PK4T0
Serial Number:    WD-WX11EC114329
LU WWN Device Id: 5 0014ee 6ad29b3f3
Firmware Version: 01.01A01
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database 7.3/5387
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Thu Aug 29 14:09:19 2024 WEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

> sudo smartctl -d scsi --info /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.10.5] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

User Capacity:        500,107,862,016 bytes [500 GB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Logical Unit id:      0x50014ee6ad29b3f3
Serial number:        WD-WX11EC114329
Device type:          disk
Local Time is:        Thu Aug 29 14:09:35 2024 WEST
SMART support is:     Unavailable - device lacks SMART capability.

According to the output of both, ata is clearly the "correct" type, but sudo smartctl -d ata --scan returns nothing, (unlike sudo smartctl -d scsi --scan). Why does it seem that I can use both ata and scsi to access information, and why is it detected as scsi by --scan?

udisks exists for regular users, root must (and is) able to live without it, I need help figuring out how. The goal is to do exactly what

udisks power-off /dev/sdX

does without udisks. hdparm is out of question, as it is assumed that UAS (https://linux-sunxi.org/USB/UAS) is in use and ATA pass-through is broken, which is the case for many external drives (i.e. all Seagate enclosures, see https://www.smartmontools.org/wiki/SAT-with-UAS-Linux) . To physically stop the drive from spinning I have successfully employed

scsi_stop /dev/sdX

which is a part of the sg3-utils (Debian and derivatives) package. Then, to remove the drive from the system, I used

echo 1 > /sys/block/sdX/device/delete

These two steps do most of, but not all the work. The block device itself is removed and is not visible anymore, however, the drive is still visible as a USB device through lsusb, which is not the case with udisks power-off. So how do I finish it?

Here is the problem: My usb storage device has a 64kB (limited by hardware) buffer used to cache reads/writes which means it can only cache up to 128 blocks(512B) of memory. The SCSI Write-10 command has a total-blocks field that can be up to 256 blocks (128kB). When originally testing the product on Windows 11 it never writes more than 128 blocks at a time but when tested on Linux it sometimes writes more than 128 blocks, which causes the microcontroller to crash. Is there a way to tell the host OS not to request more than 128 blocks? I have implemented block limit VPD page, and it works well on Windows 10/11. I even set the block limit to be 64 blocks, it's OK! However, on Linux or MacOS, the host does not appear to be running the block limits command. So the write/read blocks number beyond the buffer size.

I am using a couple SAS SSDs. A while ago I started a "background long test" on one of them, unfortunately there was a blackout and the test was therefore interrupted. After the power was back again, I re-run the background long test, and this time, it succeeded. However, I have now in my SCSI LOG PAGE a nasty entry like the following (entry #3 in the self test log) SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background long Completed - 48721 - [- - -] # 2 Background long Completed - 48253 - [- - -] # 3 Background long Self test in progress ... 8 48251 - [- - -] it is clearly a wrong entry and it irritates me a lot, because this test is definitely aborted due to the power cut. I know it is possible with the sg_utils package to manipulate certain log pages. For instance, with sg_logs -R /dev/sda one can reset the statistical counters on how many gigabytes were read/written. So I wonder, is it somehow possible to clear the self test log as well? According to the sg_utils manual I think yes, but I don't understand yet how. I just want to clear this self test log as it annoys me a lot when looking at my disks - I regularly run the tests and from time to time, I scroll through the test results and then this one is always standing out a bit. Can I probably clear all this by a FORMAT UNIT command?

When one uses SATA SSDs or HDDs under Linux, they can be addressed in numerous ways, like for example: /dev/sda /dev/disk/by-id/ata-TOSHIBA_MG05ACA800E_78LBK8P7FUUD /dev/disk/by-id/wwn-0x50000398abc0251c which, on my system, all refer to the same disk. I recently started to use a couple SAS disks of different make and model, and I noticed that these SAS disks seem to behave a bit different. For example /dev/sdb /dev/disk/by-id/scsi-35000cca01337732c /dev/disk/by-id/wwn-0x5000cca01337732c are also all the same disk. But I would have expected that there would also be a device file like, for example /dev/disk/by-id/scsi-HGST_HUSSL4040BSS600_XWVZGT1A so the format would be similar to the SATA disk, -__. I would find this much more convenient. So I wonder, why are the SAS disks treated differently in this regard from other disks? even NVME disks have a similar device file with the manufacturer, model and serial number in its name, but not the SAS disks. Bonus question: is it possible (with the aid of some udev rule?) to have these more informative device files also for the SAS disks?