You are not logged in.

#1 2026-11-17 21:18:54

SeagullFish
Member
Registered: 2023-08-10
Posts: 82

External HDD with encrypted partitions running slow

Hello.

I have an external HDD type Western Digital WDBS4B0020BYL-0B, as shown at this website.

This is a hard disk model that is no longer for sale, but I believe that I bought it at approximately the summer of 2022.

Back then, I partitioned the HDD like this:

Part 1: 	/dev/sda1	Cleartext	exFAT
(Part 2):	none		N/A		empty space
Part 3:		/dev/sda3	Veracrypt	exFAT
Part 4:		/dev/sda2	LUKS		Ext4

I am not sure why the partitions are always sorted as Part 3 = sda3 and Part 4 = sda2, it’s just been that way since I first set up the partitions.

Anyway: My use case is simply backing up regular files.

The first partition only contains files and software from WD that came with the HDD. I don’t think that I really need these files, since the software requires MS Windows, but I kept them just in case. And I also thought this partition could be useful if I should ever need to transfer non-sensitive files from one computer to another.

As for the other partitions, I assumed that encrypted partitions would be wise, so that my data would be protected in case the HDD would ever get stolen:

  • Part 3 was intended for files that could perhaps be relevant to open on several devices running different operating systems. Thus, I assumed that Veracrypt and exFAT would be portable choices.

  • Part 4 was intended for files that are only relevant on Linux systems, for example system/user settings, symbolic links, files where owner and access data needs to be preserved, etc. Thus, I assumed that LUKS and Ext4 would be suitable choices.

As for the backup task itself, I have been running rsync manually from a homemade shell script. The command passed from the script is:

ionice -c 2 -n 7 rsync -aAXUHE --delete --info=stats2,progress2 --modify-window=1 --log-file=partX.log /path/to/source_folder/ /path/to/target_folder

This has been working fine these years, up until now. But lately, the HDD has suddenly started to work very slow. When connecting the device to the computer, it takes 1-2 minuts to get all the partitions unlocked and mounted. This used to take only 15-30 seconds. Even mounting only Part 1 takes a long time. And both reading from the HDD and wrting to the HDD feels like it takes ages, compared to the time it used to take.

After searching the web for this issue, I have learned that the technology Shingled Magnetic Recording (SMR) could be to blame for this. I believe it is too early to draw that conclusion too definitively at this time, but I would really like to look deeper into this.

My questions:
1. Does my HDD actually use the SMR technology? I am not entirely sure about this, I only assume that it does since it seems to be the most common technology for external HDD’s these days.
2. If SMR is to blame, how can I find a suitable replacement for my HDD (USB-connected HDD, and not SSD) that does not use SMR? At product pages in online stores, it seems that specifications regarding this is usually not provided.

Offline

#2 2026-11-17 22:00:54

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,958

Re: External HDD with encrypted partitions running slow

Even mounting only Part 1 takes a long time.

Can you quantify "long time"?
Is it accompanied by errors in "dmesg -W" (run before attaching and mounting)?
Did you check https://wiki.archlinux.org/title/SMART "smartctl -a /dev/sda" ?
Is it the same when mounting the drive from some live distro like https://grml.org ?

It's hard to find hard specs (from WD) for the drive ID but it looks like it uses SMR (and also AES 256 hardware encryption)
Finding reliable information on SMR usage is hard in general because the drive manufacturers lie, https://en.wikipedia.org/wiki/Shingled_ … #Criticism

Offline

#3 Yesterday 21:43:34

SeagullFish
Member
Registered: 2023-08-10
Posts: 82

Re: External HDD with encrypted partitions running slow

seth wrote:

Is it accompanied by errors in "dmesg -W" (run before attaching and mounting)?

My output (after reboot, but without connecting the device):

$ dmesg -W
dmesg: read kernel buffer failed: Operation not allowed
$ sudo dmesg -W
(Non-responsive. Have to hit Ctrl + C to abort.)
seth wrote:

Even mounting only Part 1 takes a long time.

Can you quantify "long time"?

I measured this with a stopwatch now. From connecting the device, it took approximately 20-25 seconds before it appeared in the system. (Back in the days, this used to take maximum 5 seconds.) On the other hand, for some unknown reason, mounting Part 1 was done very fast today (only 1-2 seconds). For the last 3-4 weeks, this has taken another 20-30 seconds for each try.

seth wrote:

Did you check https://wiki.archlinux.org/title/SMART "smartctl -a /dev/sda" ?

Negative. I didn't know about smartmontools, but I installed it now. My output (not sure what you'll get out of this information):

$ sudo smartctl -a /dev/sda
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.3.4-zen2-2-zen] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD20SDZW-11Z3CS0
Serial Number:    WD-WXR1E68DS3YE
LU WWN Device Id: 5 0014ee 65e6276a5
Firmware Version: 01.01A01
User Capacity:    2000365379584 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic
Device is:        Not in smartctl database 7.5/5706
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Nov 18 22:21:38 2026 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		(22800) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 351) minutes.
SCT capabilities: 	       (0x7035)	SCT Status 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   138   138   051    Pre-fail  Always       -       3435
  3 Spin_Up_Time            0x0027   193   182   021    Pre-fail  Always       -       3316
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       -       2378
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       372
 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   100   100   000    Old_age   Always       -       312
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       39
193 Load_Cycle_Count        0x0032   199   199   000    Old_age   Always       -       5507
194 Temperature_Celsius     0x0022   116   097   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       16
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   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.

The above only provides legacy SMART information - try 'smartctl -x' for more

For the record, here is more extensive output:

$ sudo smartctl -x /dev/sda
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.3.4-zen2-2-zen] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD20SDZW-11Z3CS0
Serial Number:    WD-WXR1E68DS3YE
LU WWN Device Id: 5 0014ee 65e6276a5
Firmware Version: 01.01A01
User Capacity:    2000365379584 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic
Device is:        Not in smartctl database 7.5/5706
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Nov 18 22:38:06 2026 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1], Master PW ID: 0xbbbb

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		(22800) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 351) minutes.
SCT capabilities: 	       (0x7035)	SCT Status 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   138   138   051    -    3435
  3 Spin_Up_Time            POS--K   193   182   021    -    3316
  4 Start_Stop_Count        -O--CK   098   098   000    -    2378
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   100   100   000    -    372
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    312
192 Power-Off_Retract_Count -O--CK   200   200   000    -    39
193 Load_Cycle_Count        -O--CK   199   199   000    -    5507
194 Temperature_Celsius     -O---K   110   097   000    -    37
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    16
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   100   253   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x24       GPL     R/O    288  Current Device Internal Status Data log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS       1  Device vendor specific log
0xb7       GPL,SL  VS      76  Device vendor specific log
0xb9       GPL,SL  VS       4  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xcf       GPL     VS   65535  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 48 (device log contains only the most recent 24 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 48 [23] occurred at disk power-on lifetime: 371 hours (15 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 40 00 00 9d df 88 10 40 00  Error: UNC 64 sectors at LBA = 0x9ddf8810 = 2648672272

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 40 00 00 9d df 88 00 40 00     00:00:01.798  READ DMA EXT
  25 00 00 00 40 00 00 00 00 08 00 40 00     00:00:01.798  READ DMA EXT
  25 00 00 00 40 00 00 6b df 88 00 40 00     00:00:01.790  READ DMA EXT
  25 00 00 00 08 00 00 00 00 02 00 40 00     00:00:01.784  READ DMA EXT
  25 00 00 00 80 00 00 e8 df 86 78 40 00     00:00:01.783  READ DMA EXT

Error 47 [22] occurred at disk power-on lifetime: 371 hours (15 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 80 00 00 c1 a0 08 30 40 00  Error: UNC 128 sectors at LBA = 0xc1a00830 = 3248490544

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 80 00 00 c1 a0 08 00 40 00     02:00:53.444  READ DMA EXT
  25 00 00 00 80 00 00 c1 60 08 00 40 00     02:00:46.291  READ DMA EXT
  25 00 00 00 80 00 00 c1 20 08 00 40 00     02:00:40.298  READ DMA EXT
  35 00 00 00 10 00 00 c3 37 19 80 40 00     02:00:40.297  WRITE DMA EXT
  25 00 00 00 80 00 00 c0 e0 08 00 40 00     02:00:34.534  READ DMA EXT

Error 46 [21] occurred at disk power-on lifetime: 371 hours (15 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 80 00 00 c1 60 08 38 40 00  Error: UNC 128 sectors at LBA = 0xc1600838 = 3244296248

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 80 00 00 c1 60 08 00 40 00     02:00:46.291  READ DMA EXT
  25 00 00 00 80 00 00 c1 20 08 00 40 00     02:00:40.298  READ DMA EXT
  35 00 00 00 10 00 00 c3 37 19 80 40 00     02:00:40.297  WRITE DMA EXT
  25 00 00 00 80 00 00 c0 e0 08 00 40 00     02:00:34.534  READ DMA EXT
  25 00 00 00 80 00 00 c0 a0 08 00 40 00     02:00:31.834  READ DMA EXT

Error 45 [20] occurred at disk power-on lifetime: 371 hours (15 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 bf a0 08 68 40 00  Error: UNC 8 sectors at LBA = 0xbfa00868 = 3214936168

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 08 00 00 bf a0 08 68 40 00     02:00:14.180  READ DMA EXT
  25 00 00 00 08 00 00 bf a0 08 70 40 00     02:00:13.558  READ DMA EXT
  25 00 00 00 08 00 00 bf a0 08 78 40 00     02:00:12.716  READ DMA EXT
  25 00 00 00 80 00 00 bf a0 08 00 40 00     02:00:02.766  READ DMA EXT
  25 00 00 00 80 00 00 bf 60 08 00 40 00     01:59:59.568  READ DMA EXT

Error 44 [19] occurred at disk power-on lifetime: 371 hours (15 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 80 00 00 bf a0 08 68 40 00  Error: UNC 128 sectors at LBA = 0xbfa00868 = 3214936168

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 80 00 00 bf a0 08 00 40 00     02:00:02.766  READ DMA EXT
  25 00 00 00 80 00 00 bf 60 08 00 40 00     01:59:59.568  READ DMA EXT
  25 00 00 00 80 00 00 bf 20 08 00 40 00     01:59:57.457  READ DMA EXT
  25 00 00 00 80 00 00 be e0 08 00 40 00     01:59:54.192  READ DMA EXT
  25 00 00 00 80 00 00 be a0 08 00 40 00     01:59:48.485  READ DMA EXT

Error 43 [18] occurred at disk power-on lifetime: 370 hours (15 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 80 00 00 cc 60 08 10 40 00  Error: UNC 128 sectors at LBA = 0xcc600810 = 3428845584

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 80 00 00 cc 60 08 00 40 00     00:39:14.731  READ DMA EXT
  25 00 00 00 80 00 00 cc 20 08 00 40 00     00:39:14.716  READ DMA EXT
  25 00 00 00 80 00 00 cb e0 08 00 40 00     00:39:10.809  READ DMA EXT
  25 00 00 00 80 00 00 cb a0 08 00 40 00     00:39:10.758  READ DMA EXT
  25 00 00 00 80 00 00 cb 60 08 00 40 00     00:39:10.736  READ DMA EXT

Error 42 [17] occurred at disk power-on lifetime: 370 hours (15 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 bf a0 08 68 40 00  Error: UNC 8 sectors at LBA = 0xbfa00868 = 3214936168

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 08 00 00 bf a0 08 68 40 00     00:37:17.280  READ DMA EXT
  25 00 00 00 08 00 00 bf a0 08 70 40 00     00:37:16.659  READ DMA EXT
  25 00 00 00 08 00 00 bf a0 08 78 40 00     00:37:15.827  READ DMA EXT
  25 00 00 00 80 00 00 bf a0 08 00 40 00     00:37:08.452  READ DMA EXT
  25 00 00 00 80 00 00 bf 60 08 00 40 00     00:37:06.053  READ DMA EXT

Error 41 [16] occurred at disk power-on lifetime: 370 hours (15 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 80 00 00 bf a0 08 68 40 00  Error: UNC 128 sectors at LBA = 0xbfa00868 = 3214936168

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 80 00 00 bf a0 08 00 40 00     00:37:08.452  READ DMA EXT
  25 00 00 00 80 00 00 bf 60 08 00 40 00     00:37:06.053  READ DMA EXT
  25 00 00 00 80 00 00 bf 20 08 00 40 00     00:37:04.356  READ DMA EXT
  25 00 00 00 80 00 00 be e0 08 00 40 00     00:37:00.489  READ DMA EXT
  25 00 00 00 80 00 00 be a0 08 00 40 00     00:36:55.714  READ DMA EXT

SMART Extended Self-test Log Version: 1 (1 sectors)
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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
Device State:                        Active (0)
Current Temperature:                    37 Celsius
Power Cycle Min/Max Temperature:     26/37 Celsius
Lifetime    Min/Max Temperature:     19/50 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    128 (46)

Index    Estimated Time   Temperature Celsius
  47    2026-11-18 20:31    37  ******************
  48    2026-11-18 20:32    37  ******************
  49    2026-11-18 20:33    37  ******************
  50    2026-11-18 20:34    38  *******************
 ...    ..(  4 skipped).    ..  *******************
  55    2026-11-18 20:39    38  *******************
  56    2026-11-18 20:40    39  ********************
 ...    ..(  5 skipped).    ..  ********************
  62    2026-11-18 20:46    39  ********************
  63    2026-11-18 20:47    40  *********************
 ...    ..(  8 skipped).    ..  *********************
  72    2026-11-18 20:56    40  *********************
  73    2026-11-18 20:57    41  **********************
 ...    ..( 19 skipped).    ..  **********************
  93    2026-11-18 21:17    41  **********************
  94    2026-11-18 21:18    40  *********************
  95    2026-11-18 21:19    38  *******************
  96    2026-11-18 21:20    37  ******************
  97    2026-11-18 21:21    36  *****************
  98    2026-11-18 21:22    36  *****************
  99    2026-11-18 21:23    35  ****************
 100    2026-11-18 21:24    34  ***************
 101    2026-11-18 21:25    34  ***************
 102    2026-11-18 21:26    33  **************
 103    2026-11-18 21:27    33  **************
 104    2026-11-18 21:28    33  **************
 105    2026-11-18 21:29    32  *************
 106    2026-11-18 21:30    32  *************
 107    2026-11-18 21:31    32  *************
 108    2026-11-18 21:32    31  ************
 109    2026-11-18 21:33    31  ************
 110    2026-11-18 21:34    31  ************
 111    2026-11-18 21:35    30  ***********
 ...    ..(  2 skipped).    ..  ***********
 114    2026-11-18 21:38    30  ***********
 115    2026-11-18 21:39    29  **********
 ...    ..(  4 skipped).    ..  **********
 120    2026-11-18 21:44    29  **********
 121    2026-11-18 21:45    28  *********
 ...    ..(  6 skipped).    ..  *********
   0    2026-11-18 21:52    28  *********
   1    2026-11-18 21:53    27  ********
 ...    ..(  9 skipped).    ..  ********
  11    2026-11-18 22:03    27  ********
  12    2026-11-18 22:04     ?  -
  13    2026-11-18 22:05    27  ********
  14    2026-11-18 22:06    28  *********
  15    2026-11-18 22:07    29  **********
  16    2026-11-18 22:08    30  ***********
  17    2026-11-18 22:09     ?  -
  18    2026-11-18 22:10    23  ****
  19    2026-11-18 22:11     ?  -
  20    2026-11-18 22:12    24  *****
  21    2026-11-18 22:13     ?  -
  22    2026-11-18 22:14    22  ***
  23    2026-11-18 22:15     ?  -
  24    2026-11-18 22:16    26  *******
  25    2026-11-18 22:17    26  *******
  26    2026-11-18 22:18    27  ********
  27    2026-11-18 22:19    28  *********
  28    2026-11-18 22:20    30  ***********
  29    2026-11-18 22:21    30  ***********
  30    2026-11-18 22:22    31  ************
  31    2026-11-18 22:23    31  ************
  32    2026-11-18 22:24    32  *************
  33    2026-11-18 22:25    33  **************
  34    2026-11-18 22:26    33  **************
  35    2026-11-18 22:27    34  ***************
  36    2026-11-18 22:28    34  ***************
  37    2026-11-18 22:29    35  ****************
 ...    ..(  2 skipped).    ..  ****************
  40    2026-11-18 22:32    35  ****************
  41    2026-11-18 22:33    36  *****************
  42    2026-11-18 22:34    36  *****************
  43    2026-11-18 22:35    37  ******************
 ...    ..(  2 skipped).    ..  ******************
  46    2026-11-18 22:38    37  ******************

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            1  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            2  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4         1356  Vendor specific
seth wrote:

Is it the same when mounting the drive from some live distro like https://grml.org ?

Sorry, I don't have a live distro available for booting right now. I have to get back to this later. Please stay tuned.

seth wrote:

It's hard to find hard specs (from WD) for the drive ID but it looks like it uses SMR (and also AES 256 hardware encryption)
Finding reliable information on SMR usage is hard in general because the drive manufacturers lie, https://en.wikipedia.org/wiki/Shingled_ … #Criticism

That's disappointing. Who can one really trust these days?

Offline

#4 Yesterday 22:05:10

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,958

Re: External HDD with encrypted partitions running slow

(Non-responsive. Have to hit Ctrl + C to abort.)

The process will follow the ringbuffer and only print anything once new kernel messages arrive (which will happen for sure when you eg. attach a drive)

it took approximately 20-25 seconds before it appeared in the system

That's a dbus timeout - what exactly is "appeared in the system"? What happens in "dmesg -W" during this?

197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       16

Ewww…

3 Spin_Up_Time            0x0027   193   182   021    Pre-fail  Always       -       3316

the drive isn't very old, though.
Run a self test or https://wiki.archlinux.org/title/Badblocks - see what that does to pending and reallocated sectors and monitor the values afterwards.
Until then make sure that this isn't the only storage of valuable data (valuable data is anything you can't easily regenerate or replace or re-download, family pictures, your dissertation, NOT Hollywood movies or porn… ok, maybe also porn)

Fwi

192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       39

Avoid yanking the spinning drive from the system, use eg.

udisksctl power-off -b /dev/sda

or so to power it down first.

Offline

Board footer

Powered by FluxBB