[SOLVED] Buffer I/O error logical block async page read

Message

4joeyirosh1 · #1 Post by **4joeyirosh1** » 2021-06-11 09:42

Hi!I have Debian 11 64 bit installed on my machine.

When I booted my machine today,I got the errors below during boot.Please see the attached screenshot of the boot errors.Sorry the picture isnt that clear but one can still read the content

I have run ,Please find output

Code: Select all

# smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-7-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01ABD...
Device Model:     TOSHIBA MQ01ABD100
Serial Number:    87PSPGCKT
LU WWN Device Id: 5 000039 7f2f0a12f
Firmware Version: AX1R4C
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Jun 11 13:08:25 2021 EAT
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:  (0x80)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  120) 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: 	 ( 199) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0027   100   100   050    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   100   100   002    Pre-fail  Always       -       1777
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       3075
  5 Reallocated_Sector_Ct   0x0033   099   099   010    Pre-fail  Always       -       320
  7 Seek_Error_Rate         0x002f   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   058   058   000    Old_age   Always       -       17000
 10 Spin_Retry_Count        0x0033   161   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2915
183 Runtime_Bad_Block       0x0032   100   100   001    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
185 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       65535
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       1435
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   001    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   061   052   040    Old_age   Always       -       39 (Min/Max 36/39)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       213
192 Power-Off_Retract_Count 0x0022   100   100   000    Old_age   Always       -       5308497
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       5727
194 Temperature_Celsius     0x0022   061   052   040    Old_age   Always       -       39 (Min/Max 36/39)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       36
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1435 (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 1435 occurred at disk power-on lifetime: 17000 hours (708 days + 8 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
  -- -- -- -- -- -- --
  40 41 30 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 02 30 06 f6 7f 40 00      00:07:39.916  READ FPDMA QUEUED
  60 02 10 08 f6 7f 40 00      00:07:39.896  READ FPDMA QUEUED
  60 02 08 0c f6 7f 40 00      00:07:39.896  READ FPDMA QUEUED
  60 10 00 99 ba d1 40 00      00:07:39.896  READ FPDMA QUEUED
  60 08 f8 80 67 70 40 00      00:07:39.896  READ FPDMA QUEUED

Error 1434 occurred at disk power-on lifetime: 17000 hours (708 days + 8 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
  -- -- -- -- -- -- --
  40 41 10 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 10 28 99 ba d1 40 00      00:07:39.397  READ FPDMA QUEUED
  60 02 20 0c f6 7f 40 00      00:07:39.380  READ FPDMA QUEUED
  60 02 b0 0a f6 7f 40 00      00:07:39.380  READ FPDMA QUEUED
  60 02 18 08 f6 7f 40 00      00:07:39.380  READ FPDMA QUEUED
  60 02 10 06 f6 7f 40 00      00:07:39.380  READ FPDMA QUEUED

Error 1433 occurred at disk power-on lifetime: 17000 hours (708 days + 8 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
  -- -- -- -- -- -- --
  40 41 f0 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 08 18 e8 3f 40 00      00:07:38.839  READ FPDMA QUEUED
  60 08 80 00 28 00 40 00      00:07:38.828  READ FPDMA QUEUED
  60 08 78 00 18 00 40 00      00:07:38.818  READ FPDMA QUEUED
  60 08 70 18 90 10 40 00      00:07:38.815  READ FPDMA QUEUED
  60 20 f8 79 ba d1 40 00      00:07:38.807  READ FPDMA QUEUED

Error 1432 occurred at disk power-on lifetime: 17000 hours (708 days + 8 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
  -- -- -- -- -- -- --
  40 41 38 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 02 38 06 f6 7f 40 00      00:07:24.791  READ FPDMA QUEUED
  60 06 a0 08 f6 7f 40 00      00:07:24.769  READ FPDMA QUEUED
  60 f8 98 86 f6 7f 40 00      00:07:24.769  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:07:24.767  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 00      00:07:24.766  IDENTIFY DEVICE

Error 1431 occurred at disk power-on lifetime: 17000 hours (708 days + 8 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
  -- -- -- -- -- -- --
  40 41 70 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 f8 80 86 f6 7f 40 00      00:07:24.635  READ FPDMA QUEUED
  60 06 78 08 f6 7f 40 00      00:07:24.635  READ FPDMA QUEUED
  60 02 70 06 f6 7f 40 00      00:07:24.635  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:07:24.634  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 00      00:07:24.633  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      6747         -
# 2  Short offline       Completed without error       00%      6747         -
# 3  Short offline       Completed without error       00%      6747         -
# 4  Extended offline    Aborted by host               90%      6747         -

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.

From output above I can see errors as example below

Code: Select all

Error 1432 occurred at disk power-on lifetime: 17000 hours (708 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

What do these errors mean and how can I resolve them.Seems there is a disk I/O error and I hope I dont have to replace the disk. /dev/sda6 is my /home partition and I have manged to boot my OS and reach the gnome desktop and somehow I am able to work normally but the disk I/O issues concern me.

Please help

#2 Post by **sunrat** » 2021-06-11 10:16

Looks like a hardware error, maybe the disk or something connected to it. Could even be a bad cable connection.
Make sure you have your data backed up.

steve_v · #3 Post by **steve_v** » 2021-06-11 10:47

4joeyirosh1 wrote:5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 320
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 36

Reallocated sectors generally indicate the drive has media defect(s), i.e. unreadable sectors. If the count is not increasing the drive may run many years yet, but it has still failed in it's singular job - not eating your data. It's also valid grounds for RMA with most manufacturers.
Personally I wouldn't trust it as far as I could throw it, and I suggest you back up anything important immediately.

4joeyirosh1 wrote:I am able to work normally but the disk I/O issues concern me.

They'd concern me too.

Bloom · #4 Post by **Bloom** » 2021-06-11 10:49

This specific error message means that the system tried to wake your hard disk up when it was powered down and failed.
That can mean two things: either it tried to wake up a hard disk that was already spinning (and you can ignore that), or it failed to get a hard disk to spin up when it was not spinning. The latter probably means that your power management system isn't working properly with your specific hardware. If you don't absolutely need power management, you should probably switch it off.

I/O errors can be due a powered-down hard disk which can't be accessed. If the error occurs on a normal spinning and working hard disk, there's possibly a surface defect. In that case, try to backup your data and replace the hard disk.

p.H · #5 Post by **p.H** » 2021-06-11 17:13

OP : you could have got the messages in text form with dmesg instead of posting a picture.

sunrat wrote:Looks like a hardware error, maybe the disk

Yes.

sunrat wrote:Could even be a bad cable connection.

No. "UNC" means uncorrectable media error during read or write. In short, bad sectors.
As steve_v pointed out, SMART reports that many bad sectors were already reallocated by the embedded disk controller. It does not report pending (currently unreadable but not yet reallocated) sectors, but I would not trust that too much. I have seen many drives with the pending count not matching the real sector status tested with badblocks.

Bloom wrote:This specific error message means that the system tried to wake your hard disk up when it was powered down and failed.

Which specific error message ?

4joeyirosh1 · #6 Post by **4joeyirosh1** » 2021-06-11 18:53

p.H wrote:OP : you could have got the messages in text form with dmesg instead of posting a picture.

My output of dmesg is extemely long and I cant post all of it here but generally error message looks as below

Code: Select all

# dmesg
[ 8431.341307] sd 0:0:0:0: [sda] tag#13 Sense Key : Medium Error [current] 
[ 8431.341316] sd 0:0:0:0: [sda] tag#13 Add. Sense: Unrecovered read error - auto reallocate failed
[ 8431.341327] sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 0c 7f f6 06 00 00 08 00
[ 8431.341340] blk_update_request: I/O error, dev sda, sector 209712646 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 8431.341358] Buffer I/O error on dev sda6, logical block 17, async page read
[ 8431.341415] ata1: EH complete
[ 8432.438648] ata1.00: exception Emask 0x0 SAct 0x8000000 SErr 0x40000 action 0x0
[ 8432.438653] ata1.00: irq_stat 0x40000008
[ 8432.438656] ata1: SError: { CommWake }
[ 8432.438659] ata1.00: failed command: READ FPDMA QUEUED
[ 8432.438664] ata1.00: cmd 60/08:d8:00:f6:7f/00:00:0c:00:00/40 tag 27 ncq dma 4096 in
                        res 41/40:00:06:f6:7f/00:00:0c:00:00/40 Emask 0x409 (media error) <F>
[ 8432.438666] ata1.00: status: { DRDY ERR }
[ 8432.438668] ata1.00: error: { UNC }
[ 8432.441244] ata1.00: configured for UDMA/100
[ 8432.441258] sd 0:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 8432.441260] sd 0:0:0:0: [sda] tag#27 Sense Key : Medium Error [current] 
[ 8432.441262] sd 0:0:0:0: [sda] tag#27 Add. Sense: Unrecovered read error - auto reallocate failed
[ 8432.441264] sd 0:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 0c 7f f6 00 00 00 08 00

Anyway I have backed up all my critical data just incase the disk fails

#7 Post by **sunrat** » 2021-06-11 22:01

p.H wrote:OP : you could have got the messages in text form with dmesg instead of posting a picture.

sunrat wrote:Looks like a hardware error, maybe the disk
Yes.
sunrat wrote:Could even be a bad cable connection.
No. "UNC" means uncorrectable media error during read or write. In short, bad sectors.

Thank you for the clarification. I had difficulty reading the image and saw the { DRDY ERR } which I recall having for a bad connection previously. IIRC it means "disk ready" which relates to the previous mention above of a failed access or wake attempt.

p.H · #8 Post by **p.H** » 2021-06-12 08:54

{ DRDY ERR } seems to be a general error status that you will see with different error types. The actual error type is mentionned in the following line.

4joeyirosh1 · #9 Post by **4joeyirosh1** » 2021-06-14 06:15

I have solved it.I copied all the contents of the troublesome /dev/sda6 partition to another partition,formatted and recreated the filesystem on the /sda6 partition with gparted then copied back all the contents to /sda6 and the error messages are now gone.

Debian User Forums

[SOLVED] Buffer I/O error logical block async page read

[SOLVED] Buffer I/O error logical block async page read

Re: Buffer I/O error logical block async page read

Re: Buffer I/O error logical block async page read

Re: Buffer I/O error logical block async page read

Re: Buffer I/O error logical block async page read

Re: Buffer I/O error logical block async page read

Re: Buffer I/O error logical block async page read

Re: Buffer I/O error logical block async page read

Re: Buffer I/O error logical block async page read