Do I have a bad drive?

October 28, 2025Oct 28

Hi,

I have a disk that is giving the error below. I tried switching the SATA cable and due to the way the motherboard is layed out I had to connect the SATA cable to a different port on the motherboard. I restarted and I'm still getting this error. I checked SMART data and there doesn't appear to be anything flagged in there. I did not replace the SATA power. Would that be the next step?

Oct 28 10:05:18 server kernel: I/O error, dev sdc, sector 3911194184 op 0x0:(READ) flags 0x0 phys_seg 168 prio class 0

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194120

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194128

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194136

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194144

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194152

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194160

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194168

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194176

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194184

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194192

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194200

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194208

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194216

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194224

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194232

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194240

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194248

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194256

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194264

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194272

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194280

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194288

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194296

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194304

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194312

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194320

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194328

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194336

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194344

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194352

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194360

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194368

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194376

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194384

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194392

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194400

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194408

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194416

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194424

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194432

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194440

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194448

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194456

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194464

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194472

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194480

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194488

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194496

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194504

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194512

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194520

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194528

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194536

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194544

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194552

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194560

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194568

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194576

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194584

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194592

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194600

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194608

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194616

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194624

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194632

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194640

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194648

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194656

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194664

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194672

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194680

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194688

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194696

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194704

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194712

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194720

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194728

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194736

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194744

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194752

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194760

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194768

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194776

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194784

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194792

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194800

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194808

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194816

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194824

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194832

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194840

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194848

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194856

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194864

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194872

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194880

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194888

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194896

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194904

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194912

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194920

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194928

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194936

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194944

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194952

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194960

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194968

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194976

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194984

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911194992

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195000

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195008

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195016

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195024

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195032

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195040

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195048

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195056

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195064

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195072

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195080

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195088

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195096

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195104

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195112

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195120

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195128

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195136

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195144

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195152

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195160

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195168

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195176

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195184

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195192

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195200

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195208

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195216

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195224

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195232

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195240

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195248

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195256

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195264

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195272

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195280

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195288

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195296

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195304

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195312

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195320

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195328

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195336

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195344

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195352

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195360

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195368

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195376

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195384

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195392

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195400

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195408

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195416

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195424

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195432

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195440

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195448

Oct 28 10:05:18 server kernel: md: disk2 read error, sector=3911195456

Quote

October 28, 2025Oct 28

Community Expert

Please post the diagnostics.

Quote

October 28, 2025Oct 28

Author

Hi Jorge,

Thank you for the reply. I have included the diagnostic archive below.

kms2-diagnostics-20251028-1542.zip

Quote

October 29, 2025Oct 29

Community Expert

It's logged as a disk problem, but SMART looks OK, run an extended SMART test on that disk.

Quote

October 30, 2025Oct 30

Author

I ran an extended SMART test and it returned with no error.

Warning: ATA error count 38528 inconsistent with error log pointer 2

ATA Error Count: 38528 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
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 38528 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 02 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 10 02 00 00 00 a0 08      11:47:40.284  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      11:47:40.284  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      11:47:40.284  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 08      11:47:40.284  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      11:47:40.283  IDENTIFY DEVICE

Error 38527 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      11:47:40.284  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 08      11:47:40.284  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      11:47:40.283  IDENTIFY DEVICE
  c8 00 08 b0 d0 05 ef 08      11:47:40.272  READ DMA
  ef 10 02 00 00 00 a0 08      11:47:40.271  SET FEATURES [Enable SATA feature]

Error 38526 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 02 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 10 02 00 00 00 a0 08      11:47:40.284  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      11:47:40.283  IDENTIFY DEVICE
  c8 00 08 b0 d0 05 ef 08      11:47:40.272  READ DMA
  ef 10 02 00 00 00 a0 08      11:47:40.271  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      11:47:40.270  IDENTIFY DEVICE

Error 38525 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 08 b0 d0 05 ef  Device Fault; Error: ABRT 8 sectors at LBA = 0x0f05d0b0 = 252039344

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 b0 d0 05 ef 08      11:47:40.272  READ DMA
  ef 10 02 00 00 00 a0 08      11:47:40.271  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      11:47:40.270  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      11:47:40.270  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 08      11:47:40.270  SET FEATURES [Enable SATA feature]

Error 38524 occurred at disk power-on lifetime: 60877 hours (2536 days + 13 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 02 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 10 02 00 00 00 a0 08      11:47:40.271  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      11:47:40.270  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      11:47:40.270  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 08      11:47:40.270  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      11:47:40.269  IDENTIFY DEVICE

Edited October 30, 2025Oct 30 by kernelpaniced

Quote

October 30, 2025Oct 30

Community Expert
Solution

You can give a 2nd chance; this type of error can be intermittent, but any more logged like a disk problem, I would replace it.

Quote

October 30, 2025Oct 30

Author

28 minutes ago, JorgeB said:
You can give a 2nd chance; this type of error can be intermittent, but any more logged like a disk problem, I would replace it.

Thanks Jorge! I'll keep an eye on it and see what happens.

Quote

1

Do I have a bad drive?

Featured Replies

Solved by JorgeB

Join the conversation

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)