Buffer i o error on dev sda logical block 0 async page read - Исправление ошибок и поиск оптимальных решений проблем

Как правильно задавать вопросы

Правильно сформулированный вопрос и его грамотное оформление способствует высокой вероятности получения достаточно содержательного и по существу ответа. Общая рекомендация по составлению тем: 1. Для начала воспользуйтесь поиском форума. 2. Укажите версию ОС вместе с разрядностью. Пример: LM 19.3 x64, LM Sarah x32 3. DE. Если вопрос касается двух, то через запятую. (xfce, KDE, cinnamon, mate) 4. Какое железо. (достаточно вывод inxi -Fxz в спойлере (как пользоваться спойлером смотрим здесь)) или же дать ссылку на hw-probe 5. Суть. Желательно с выводом консоли, логами. 6. Скрин. Просьба указывать 2, 3 и 4 независимо от того, имеет ли это отношение к вопросу или нет. Так же не забываем об общих правилах Как пример вот

Arman: Сообщения: 3; Зарегистрирован: 07 май 2018, 21:19; Благодарил (а): 1 раз; Контактная информация:

Ошибка Buffer I/O error on dev sda1, logical block 0

07 май 2018, 21:29

Я новичек в Linux. Установил его по началу все работал хорошо без никаких нареканий но потом что то он выдал ошибку buffer I/0 error dev sda1, logical block 0. Перезагружаю и нечего не меняется читал на других форумах там что нужно открыть терминал и что то написать но я не могу открыть терминал т.к. не могу загрузится в линукс. Помогите мне пожалуйста.

di_mok: Сообщения: 5439; Зарегистрирован: 27 авг 2016, 19:06; Решено: 32; Откуда: Арзамас; Благодарил (а): 1569 раз; Поблагодарили: 1262 раза; Контактная информация:

Ошибка Buffer I/O error on dev sda1, logical block 0

07 май 2018, 21:36

Наверное, как раз твой случай Ошибки чтения секторов на HDD А загрузиться можно с LiveUSB. Или подцепить винт к другому компьютеру

Настоящая водка — это не пьянство, а ключ к своей совести, с нее-то и начинается настоящая мудрость. (c)

Arman: Сообщения: 3; Зарегистрирован: 07 май 2018, 21:19; Благодарил (а): 1 раз; Контактная информация:

Ошибка Buffer I/O error on dev sda1, logical block 0

07 май 2018, 21:45

di_mok, я просто перезагрузил ноут и он завис на загрузки где иконка минт .

di_mok: Сообщения: 5439; Зарегистрирован: 27 авг 2016, 19:06; Решено: 32; Откуда: Арзамас; Благодарил (а): 1569 раз; Поблагодарили: 1262 раза; Контактная информация:

Ошибка Buffer I/O error on dev sda1, logical block 0

07 май 2018, 22:14

Не пойму, что мешает загрузится с флешки

Настоящая водка — это не пьянство, а ключ к своей совести, с нее-то и начинается настоящая мудрость. (c)

slant: Сообщения: 4028; Зарегистрирован: 21 июн 2017, 18:09; Решено: 79; Благодарил (а): 50 раз; Поблагодарили: 1762 раза; Контактная информация:

Ошибка Buffer I/O error on dev sda1, logical block 0

07 май 2018, 22:36

С очень большой вероятностью, тут проблемы с диском на аппаратном уровне. В гарантию/ремонт/мусорку. В любом случае, сначала нужно проверять железо.

Arman: Сообщения: 3; Зарегистрирован: 07 май 2018, 21:19; Благодарил (а): 1 раз; Контактная информация:

Ошибка Buffer I/O error on dev sda1, logical block 0

07 май 2018, 22:43

slant, а как его проверить

slant: Сообщения: 4028; Зарегистрирован: 21 июн 2017, 18:09; Решено: 79; Благодарил (а): 50 раз; Поблагодарили: 1762 раза; Контактная информация:

Ошибка Buffer I/O error on dev sda1, logical block 0

08 май 2018, 00:45

Отнести в сервис. Особенно, если на диске есть что-то ценное.

Но если удается загрузится в какую-нить линукс-систему, можно предварительно глянуть SMART:

smatrctl -a /dev/sda

(Вместо /dev/sda — имя диска в системе.) В ответ будет большая простыня из которой, в принципе, можно извлечь много информации о состоянии диска. Но тут в двух словах не расскажешь — оно комплексно анализируется.

slant: Сообщения: 4028; Зарегистрирован: 21 июн 2017, 18:09; Решено: 79; Благодарил (а): 50 раз; Поблагодарили: 1762 раза; Контактная информация:

Ошибка Buffer I/O error on dev sda1, logical block 0

29 мар 2019, 14:09

biker95 писал(а): ↑

29 мар 2019, 08:14

Или запуститься с флешки в live режиме и в консоле выполнить команду: sudo fsck -M -y

Для диска с подозрениями на аппаратные проблемы — совет откровенно вредительский.
Не в коем случае, никогда не пытайтесь лечить структуру файловой системы если нет уверенности что аппаратно диск полностью здоров. А то потом вам данные с такого диска даже в сервисе не спасут.

Источник

Здравствуйте!

Xubuntu 20.04
Внешний жёсткий диск на 500Гб в контейнере на один диск от AGE STAR, подключается через USB.
Мать ASUS возраст 10 лет.

Настроил автомонтирование этого внешнего диска.
Сначала физически включаю диск, потом комп.
Сразу при загрузке стоит работа бэкапа — BackinTime.
Всё нормально работало несколько месяцев (обновления системы за этот период не было).

Теперь (ничего вроде не менялось в системе) диск не монтируется:

— на уровне железа и в БИОСе он виден и нормально на этом этапе подключается при запуске;

— во время загрузки (ещё чёрно-белый экран, но режим монитора уже вроде бы графический) процесс загрузки надолго застревает — что-то с SATA, к внешнему диску идёт непрерывное обращение, после его физического выключения (выключателем) процесс загрузки продолжается нормально;

— если после завершения загрузки системы сразу попытаться снова включить этот (уже выключенный во время проблем с загрузкой — см.выше) внешний диск (выключателем), то он непрерывно работает, но ОС его не видит (диск непрерывно мигает как при обращении к нему, а GParted говорит, что не может получить статус такого устройства, называя конкретное устройство) (подождав, диск выключаем выключателем);

— если, не выключая компа, подождать некоторое время и снова включить выключателем внешний жёсткий диск — то он сам по себе тихо работает, но GParted его не видит вообще и даже не пытается искать;

— если теперь, не выключая компа, выключить выключателем внешний жёсткий диск и перемкнуть его в другой USB-разъём, то при его повторном включении он снова начинает долго мигать, а GParted опять говорит, что не может получить статус такого устройства.

Что это может быть:

1) Железо? Где? Мать, контейнер, диск?
2) ОС? Баг? Настройки?
3) Неудачная конфигруация бэкапа? Но почему это начинается ещё до запуска графической оболочки?

Как это исправить?

Спасибо

Источник

Is «OneDrive — Georgian College» a mountpoint for an external USB-disk ?

No, it’s a local folder, but syncs with OneDrive. I also don’t have OneDrive running, but I run OneDrive at the end of the day just to sync the files to the OneDrive (use it as a backup). I have thought about OneDrive may bre responsible so I make sure that it is not running when I use the VMs. So OneDrive should not be a cause/affect VM disk when the VM is running, and I suddenly see I/O errors in the guest OS randomly without OneDrive being involved as far as I can tell.

> I do take a lot of snapshots, because the darn thing is too unreliable.

It actually is the other way round — the more snapshots the more unreliable a VM becomes !

Yes, but I may just be doing anything and I start getting disk errors, my only option is to restore from snapshot. Unfortunately that is what I have had to resort to in order to keep the VM going, otherwise I’ll have to reinstall the entire thing 3 times a day.

Do you use any aggressive Antivirus-tools that scan vmdks ?

not that I know of. I just use the Windows Defender that comes with Windows 10. I don’t know if Windows defender is scanning these files, and I don’t know how to check (yet). I’ll look into that.

Did you ever tried to expand the VMDK after you started creating snapshots ?

Nope, it’s just a 16GB disk since day 1.

Actually the issue is it happens even when start a new VM. When the issue happens even I start from scratch (creating a new VM) before I get the chance to install Ubuntu server it goes bad in the middle of installation. It might work without issues for a while, so I can install, then suddenly it goes bad again. Right now I upgraded VMware to 15.1 and my old VM started working again after restoring from snapshot.

I have scanned all the physical disk for errors and nothing turned up on both computers. They are both running on Samsung SSDs. The desktop is running 2.5″ Samsung 850 Evo (512 GB) and the laptop is running a Samsung PM981 NVMe 512GB… could this be some sort of compatibility issue with SSDs? I have been using Intel and Crucial SSD’s in my previous systems and never seen this happen before.

Источник

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

Источник

sudo smartctl -a /dev/sdb

Hi thank you for the reply,

1. lsblk ouput

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

fd0 2:0 1 4K 0 disk

sda 8:0 0 135.7G 0 disk

├─sda1 8:1 0 134.7G 0 part /

├─sda2 8:2 0 1K 0 part

└─sda5 8:5 0 976M 0 part [SWAP]

sdb 8:16 0 67.8G 0 disk

sr0 11:0 1 1024M 0 rom

2. sudo smartctl -a /dev/sdb

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-7-amd64] (local build)

/dev/sdb: requires option '-d cciss,N'

Please specify device type with the -d option.

from googling i tried something like this smartctl -a -i -d cciss,0 /dev/sdb

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-7-amd64] (local build)

=== START OF INFORMATION SECTION ===

Vendor: COMPAQ

Product: BD07289BB8

Revision: HPB1

Rotation Rate: 10025 rpm

Logical Unit id: 0x00000e1100d78bf4

Serial number: DAL1P690GR3L0638

Device type: disk

Transport protocol: Parallel SCSI (SPI-4)

Local Time is: Mon Jul 19 08:07:27 2021 +08

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

Temperature Warning: Enabled

=== START OF READ SMART DATA SECTION ===

SMART Health Status: OK

Current Drive Temperature: 23 C

Drive Trip Temperature: 65 C

Manufactured in week 38 of year 2006

Specified cycle count over device lifetime: 10000

Accumulated start-stop cycles: 377

Elements in grown defect list: 0

Error counter log:

Errors Corrected by Total Correction Gigabytes Tot al

ECC rereads/ errors algorithm processed unc orrected

fast | delayed rewrites corrected invocations [10^9 bytes] err ors

read: 0 0 0 0 0 0.000 0

write: 0 0 0 0 0 0.000 0

Non-medium error count: 216

SMART Self-test log

Num Test Status segment LifeTime LBA_first_err [ SK ASC ASQ]

Description number (hours)

# 1 Background short Completed - 63 - [ - - -]

# 2 Background short Completed - 63 - [ - - -]

Long (extended) Self-test duration: 2016 seconds [33.6 minutes]

———————————————————————

im new to linux and debian im not sure on how to really read this data, should i replace the hardisk or ignore the error ?

Источник

Hello.

I don’t think that I have a broken USB drive..since the drive works correctly on other hosts.

I tried another (larger, Seagate) USB drive ..and saw the same type of errors (see listing below).

Also, the drive is not mounted/accessed on the proxmox server host (The proxmox server host
device name../dev/sdc1 disappears..when I run the ‘qm monitor’ ‘device_add’ command..to move
the device into the LinuxVM.)

Error listing from 2nd USB Drive Mount Attempt
—————————————————————-
Dev sda: unable to read RDB block 0
blk_update_request: I/O error, dev sda, sector 1953524992
blk_update_request: I/O error, dev sda, sector 1953524992
Buffer I/O error on dev sda, logical block 1953524992, async page read
blk_update_request: I/O error, dev sda, sector 1953524993
Buffer I/O error on dev sda, logical block 1953524993, async page read
blk_update_request: I/O error, dev sda, sector 1953524994
Buffer I/O error on dev sda, logical block 1953524994, async page read
Buffer I/O error on dev sda, logical block 1953524995, async page read
———————————————————————

Here is a portion of the ‘dmesg’ command output:
——————————————————————
[70425.041492] usb 1-2.3: Product: Backup+ BK
[70425.041493] usb 1-2.3: Manufacturer: Seagate
[70425.041494] usb 1-2.3: SerialNumber: NA51G3Y6
[70425.042687] usb-storage 1-2.3:1.0: USB Mass Storage device detected
[70425.042776] usb-storage 1-2.3:1.0: Quirks match for vid 0bc2 pid a013:
2000000
[70425.042785] scsi host4: usb-storage 1-2.3:1.0
[70426.047194] scsi 4:0:0:0: Direct-Access Seagate Backup+ BK
0409 PQ: 0 ANSI: 6
[70426.048791] sd 4:0:0:0: Attached scsi generic sg1 type 0
[70426.054597] sd 4:0:0:0: [sda] 1953525167 512-byte logical blocks: (1.00
TB/932 GiB)
[70426.059849] sd 4:0:0:0: [sda] Test WP failed, assume Write Enabled
[70426.065011] sd 4:0:0:0: [sda] Cache data unavailable
[70426.065013] sd 4:0:0:0: [sda] Assuming drive cache: write through
[70426.083970] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.083973] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.083975] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.083977] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 00 00
00 01 00
[70426.083987] blk_update_request: critical target error, dev sda, sector
0
[70426.084244] Buffer I/O error on dev sda, logical block 0, async page
read
[70426.087034] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.087036] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.087038] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.087039] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 01 00
00 01 00
[70426.087041] blk_update_request: critical target error, dev sda, sector
1
[70426.087289] Buffer I/O error on dev sda, logical block 1, async page
read
[70426.090277] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.090283] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.090287] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.090291] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 02 00
00 01 00
[70426.090294] blk_update_request: critical target error, dev sda, sector
2
[70426.090651] Buffer I/O error on dev sda, logical block 2, async page
read
[70426.093410] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.093416] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.093421] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.093425] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 03 00
00 01 00
[70426.093428] blk_update_request: critical target error, dev sda, sector
3
[70426.093857] Buffer I/O error on dev sda, logical block 3, async page
read
[70426.096455] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.096457] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.096459] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.096461] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 04 00
00 01 00
[70426.096462] blk_update_request: critical target error, dev sda, sector
4
[70426.096798] Buffer I/O error on dev sda, logical block 4, async page
read
[70426.099621] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.099624] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.099626] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.099627] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 05 00
00 01 00
[70426.099628] blk_update_request: critical target error, dev sda, sector
5
[70426.100000] Buffer I/O error on dev sda, logical block 5, async page
read
[70426.102702] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.102704] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.102710] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.102712] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 06 00
00 01 00
[70426.102713] blk_update_request: critical target error, dev sda, sector
6
[70426.103106] Buffer I/O error on dev sda, logical block 6, async page
read
[70426.106516] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.106519] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.106521] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.106523] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 07 00
00 01 00
[70426.106524] blk_update_request: critical target error, dev sda, sector
7
[70426.107354] Buffer I/O error on dev sda, logical block 7, async page
read
[70426.111861] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.111868] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.111872] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.111876] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 00 00
00 01 00
[70426.111880] blk_update_request: critical target error, dev sda, sector
0
[70426.112454] Buffer I/O error on dev sda, logical block 0, async page
read
[70426.116993] Buffer I/O error on dev sda, logical block 1, async page
read
[70426.161596] ldm_validate_partition_table(): Disk read failed.
[70426.262292] Dev sda: unable to read RDB block 0
[70426.390529] sda: unable to read partition table
[70426.761963] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70427.498033] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70428.630026] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70429.398021] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70430.162023] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70430.926022] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70431.694019] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70432.075590] scsi_io_completion: 87 callbacks suppressed
[70432.075596] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK
[70432.075599] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 70 6d 00 00
00 08 00
[70432.075600] blk_update_request: 87 callbacks suppressed
[70432.075601] blk_update_request: I/O error, dev sda, sector 1953524992
[70432.086912] sd 4:0:0:0: [sda] Attached SCSI disk
[70432.113567] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70432.113574] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70432.113579] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70432.113583] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 70 6d 00 00
00 01 00
[70432.113586] blk_update_request: critical target error, dev sda, sector
1953524992
[70432.114546] buffer_io_error: 86 callbacks suppressed
[70432.114548] Buffer I/O error on dev sda, logical block 1953524992,
async page read
[70432.466022] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70433.234024] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70434.002033] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70434.766002] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70435.530021] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70436.297997] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70436.679903] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK
[70436.679907] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 70 6d 01 00
00 07 00
[70436.679908] blk_update_request: I/O error, dev sda, sector 1953524993
[70436.680842] Buffer I/O error on dev sda, logical block 1953524993,
async page read
[70436.681466] Buffer I/O error on dev sda, logical block 1953524994,
async page read
[70436.682110] Buffer I/O error on dev sda, logical block 1953524995,
async page read
[70436.682741] Buffer I/O error on dev sda, logical block 1953524996,
async page read
[70436.683364] Buffer I/O error on dev sda, logical block 1953524997,
async page read
[70436.684018] Buffer I/O error on dev sda, logical block 1953524998,
async page read
[70436.684657] Buffer I/O error on dev sda, logical block 1953524999,
async page read
[70437.066021] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70437.809977] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70438.549980] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70439.290028] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70440.034027] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70440.774020] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70441.155521] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK
[70441.155524] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 70 6d 00 00
00 01 00
[70441.155525] blk_update_request: I/O error, dev sda, sector 1953524992
[70441.156491] Buffer I/O error on dev sda, logical block 1953524992,
async page read
—————————————————————————————————

Some additional details…
When I used to mount drives successfully into a VM, the device name would
appear as ‘sda1’ (and not ‘sda’)

——————————————————————————————————

*** OK, I think that I’ve figured out the source of the problem… ***

The Linux VM (vmid=750) is only able to detect USB 1.1 USB controller hardware..
but the mounted USB drives are USB 2.0 and USB 3.0 type drives. (which are much
faster than the USB 1.1 interface.)

Here is a portion of the Linux VM’s dmesg output:
——————————————————————
[ 0.851909] PPP generic driver version 2.4.2
[ 0.855959] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 0.856591] ehci-pci: EHCI PCI platform driver
[ 0.857214] ehci-platform: EHCI generic platform driver
[ 0.857832] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 0.858446] ohci-pci: OHCI PCI platform driver
[ 0.859053] ohci-platform: OHCI generic platform driver
[ 0.859663] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.890410] uhci_hcd 0000:00:01.2: UHCI Host Controller
[ 0.891056] uhci_hcd 0000:00:01.2: new USB bus registered, assigned bus
number 1
[ 0.895910] uhci_hcd 0000:00:01.2: detected 2 ports
[ 0.896629] uhci_hcd 0000:00:01.2: irq 11, io base 0x0000e0c0
[ 0.897301] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0001
[ 0.897911] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 0.898514] usb usb1: Product: UHCI Host Controller
[ 0.899103] usb usb1: Manufacturer: Linux 4.4.0-62-generic uhci_hcd
[ 0.899708] usb usb1: SerialNumber: 0000:00:01.2
[ 0.903950] hub 1-0:1.0: USB hub found
[ 0.904552] hub 1-0:1.0: 2 ports detected
[ 0.905249] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at
0x60,0x64 irq 1,12
[ 0.906565] serio: i8042 KBD port at 0x60,0x64 irq 1
——————————————————————————

The ehci-pci drivers (i.e. USB 2.0) are present…but the VM never sees an ehci-pci
USB controller.

The VM ‘does find’ a UHCI (i.e. USB 1.1) USB controller. The following dmesg lines
illustrate this:
[ 0.897301] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.898514] usb usb1: Product: UHCI Host Controller
[ 0.899103] usb usb1: Manufacturer: Linux 4.4.0-62-generic uhci_hcd

—————————————————————————————————————

Now, here’s some ‘dmesg’ output from my proxmox ve server (that manages the Linux
VM:

[ 0.972902] PPP generic driver version 2.4.2
[ 0.972929] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 0.972931] ehci-pci: EHCI PCI platform driver
[ 0.973073] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 0.973079] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 0.973088] ehci-pci 0000:00:1a.0: debug port 2
[ 0.976980] ehci-pci 0000:00:1a.0: cache line size of 32 is not supported
[ 0.976990] ehci-pci 0000:00:1a.0: irq 18, io mem 0x91e13000
[ 0.992058] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 0.992118] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.992121] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.992124] usb usb1: Product: EHCI Host Controller
[ 0.992126] usb usb1: Manufacturer: Linux 4.15.18-9-pve ehci_hcd
[ 0.992128] usb usb1: SerialNumber: 0000:00:1a.0
[ 0.992344] hub 1-0:1.0: USB hub found
[ 0.992348] hub 1-0:1.0: 2 ports detected
[ 0.992569] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 0.992574] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 0.992583] ehci-pci 0000:00:1d.0: debug port 2
[ 0.996481] ehci-pci 0000:00:1d.0: cache line size of 32 is not supported
[ 0.996484] ehci-pci 0000:00:1d.0: irq 18, io mem 0x91e12000
[ 1.012056] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 1.012118] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.012121] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.012124] usb usb2: Product: EHCI Host Controller
[ 1.012126] usb usb2: Manufacturer: Linux 4.15.18-9-pve ehci_hcd
[ 1.012129] usb usb2: SerialNumber: 0000:00:1d.0
[ 1.012305] hub 2-0:1.0: USB hub found
[ 1.012308] hub 2-0:1.0: 2 ports detected
[ 1.012441] ehci-platform: EHCI generic platform driver
[ 1.012447] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 1.012449] ohci-pci: OHCI PCI platform driver
[ 1.012458] ohci-platform: OHCI generic platform driver
[ 1.012464] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.012584] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.012588] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[ 1.013657] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810
[ 1.013661] xhci_hcd 0000:00:14.0: cache line size of 32 is not supported
[ 1.013740] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.013741] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.013742] usb usb3: Product: xHCI Host Controller
[ 1.013743] usb usb3: Manufacturer: Linux 4.15.18-9-pve xhci-hcd
[ 1.013744] usb usb3: SerialNumber: 0000:00:14.0
[ 1.013844] hub 3-0:1.0: USB hub found
[ 1.013859] hub 3-0:1.0: 15 ports detected
[ 1.014998] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.015001] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[ 1.015003] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[ 1.015030] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.015031] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.015032] usb usb4: Product: xHCI Host Controller
[ 1.015033] usb usb4: Manufacturer: Linux 4.15.18-9-pve xhci-hcd
[ 1.015034] usb usb4: SerialNumber: 0000:00:14.0
[ 1.015226] hub 4-0:1.0: USB hub found
[ 1.015237] hub 4-0:1.0: 6 ports detected
[ 1.015881] i8042: PNP: No PS/2 controller found.
[ 1.015955] mousedev: PS/2 mouse device common for all mice
[ 1.016031] rtc_cmos 00:00: RTC can wake from S4
——————————————————————————————————————-

The following USB controllers are found on the proxmox ve server:

[ 0.992124] usb usb1: Product: EHCI Host Controller (i.e. USB 2.0)
[ 1.013742] usb usb3: Product: xHCI Host Controller (i.e. USB 3.0)

—————————————————————————————————

So, what do I have to do…to the Linux VM ..to get it to see
the proxmox server’s EHCI or xHCI Host Controller hardware ?

If the VM could see either of those USB Host Controllers…it could communicate with
the mounted USB 2.0, or USB 3.0 mounted drives.

Thanks!

—Brett R

P.S. I may have created my Linux VM..from a proxmox template .ISO file..for Ubuntu 16.04 LTS
Could some USB controller drivers be missing from that .ISO file?

Источник

I thought I would add the following for those who regularly get this on USB sticks, which you can probably ignore if you see in the «Logs» (Mint menu > Logs (and will be on ‘Important’ tab))…

«Buffer I/O error on dev sde1, logical block *NumberHere*, async page read» (and the like) (NOTE: sde1 is my USB stick on my system)

because I narrowed it down to the ‘eject’ (file manager, right click USB stick, select ‘eject’) as that’s when that occurs as if I ‘unmount’ (in file manager, right click USB stick, select ‘unmount’) it first then ‘eject’ those errors do not come up.

because I can delete and transfer files to the USB stick and no errors are logged in relation to it as it’s only when I do the ‘eject’ is when that I/O Error is logged.

NOTE: I tried a few USB sticks and even different USB ports (front of case and back of case on motherboard) and they react basically the same. I am using Mint v20.3-Xfce with 5.13 kernel (but was on Cinnamon for quite sometime until last month with similar results etc).

basically if you want to avoid having the error logged a simple enough work around, at least on Mint v20.x-Xfce, is to just ‘unmount’ the drive and then physically remove the USB stick instead of using ‘eject’. but either way, it don’t really matter much as your USB stick will still work as expected.

p.s. but in short, file transfers with general eject work as expected on my USB stick(s) ; a bit more detail… but to further test to make sure all is good with basic file transfers and ejecting so there is no data corruption etc I basically put in a USB stick, started a large file 4GB transfer (so it will take time to finish), then I went to the ‘eject’ and a little popup came up asking me if I want to force eject as there is still a file transfer in progress, which of course I said no. so at this point I waited for the file transfer to complete with the on screen file transfer and as soon as it was done I immediately went to the ‘eject’ again to see what happens and this time it just shows that little message at the top right of the screen saying not to remove the USB stick yet as file transfer is still going at which point I just waited, because it stayed there for a while longer as data was still being written, and then disappeared after it was done and processed the eject and then I can remove the USB stick since it was safely ejected like usual.

MainPC: i5-3550 (undervolted by -0.120v (CPU runs 12c cooler) /w stock i3-2120 hs/fan) | 1050 Ti 4GB | 16GB (2x 8GB) DDR3 1600Mhz RAM | Backups: AMD E-300 CPU (8GB RAM) / Athlon X2 3600+ CPU (@2.3GHz@1.35v) (4GB RAM) | All /w Mint 21.x-Xfce

Источник

I have a webserver that have the content in HP MSA2040 Storage (10 tb total storage).

I keep getting error like below

Jul 31 19:06:24 xxxxxxxx*** kernel: blk_update_request: I/O error, dev sda, sector 7094923416
Jul 31 19:06:24 xxxxxxxx*** kernel: buffer_io_error: 1110 callbacks suppressed
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865171, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865172, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865173, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865174, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865175, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865176, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865177, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865178, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865179, lost async page write
Jul 31 19:06:24 xxxxxxxx*** kernel: Buffer I/O error on dev sda, logical block 886865180, lost async page write

I’ve tried to run xfs_repair on /dev/sda which is my MSA2040 storage, this is the report I’ve got

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...

I even tried to run xfs_repaif -L I can reach to my data but it got stuck after some time. I have also checked MSA’s interface, everything seems smooth.

Is there any method to solve this issue?

Thanks in advance.

Edit* This is also smartctl report

=== START OF INFORMATION SECTION ===
Vendor:               HP
Product:              MSA 2040 SAN
Revision:             G210
User Capacity:        10,239,998,951,424 bytes [10.2 TB]
Logical block size:   512 bytes
LU is thin provisioned, LBPRZ=1
Rotation Rate:        15000 rpm
Logical Unit id:      0x600xxxxxxxxxxxxxxxef5701000000
Serial number:        00c0ff27xxxxxxxxxxxx701000000
Device type:          disk
Transport protocol:   Fibre channel (FCP-2)
Local Time is:        Mon Jul 31 19:22:30 2017 +03
SMART support is:     Available - device has SMART capability.
SMART support is:     Disabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Elements in grown defect list: 0

Error Counter logging not supported

Device does not support Self Test logging

Edit2* Requested outputs

[root@xxxxxxxx*** thumbs]# lsblk
NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda               8:0    0  9.3T  0 disk /msa10tb
sdb               8:16   0  1.8T  0 disk
├─sdb1            8:17   0  200M  0 part /boot/efi
├─sdb2            8:18   0  500M  0 part /boot
└─sdb3            8:19   0  1.8T  0 part
  ├─centos-root 253:0    0   50G  0 lvm  /
  ├─centos-swap 253:1    0  7.8G  0 lvm  [SWAP]
  └─centos-home 253:2    0  1.8T  0 lvm  /home
sr0              11:0    1 1024M  0 rom
[root@xxxxxxxx*** thumbs]# pvs
  PV         VG     Fmt  Attr PSize PFree
  /dev/sdb3  centos lvm2 a--  1.82t 64.00m
[root@xxxxxxxx*** thumbs]# vgs
  VG     #PV #LV #SN Attr   VSize VFree
  centos   1   3   0 wz--n- 1.82t 64.00m
[root@xxxxxxxx*** thumbs]# lvs
  LV   VG     Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  home centos -wi-ao----  1.76t
  root centos -wi-ao---- 50.00g
  swap centos -wi-ao----  7.75g
[root@xxxxxxxx*** thumbs]#

Edit*3 — When I check journalctl, now I keep getting these logs;

Jul 31 19:29:46 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1461891501:1461898801 (repaired)
Jul 31 19:29:48 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1461891501:1461898801 (repaired)
Jul 31 19:29:50 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1461891501:1461898801 (repaired)
Jul 31 19:29:54 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1461891501:1461898801 (repaired)
Jul 31 19:30:03 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1461891501:1461898801 (repaired)
Jul 31 19:30:25 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1462932481:1462952921 (repaired)
Jul 31 19:30:27 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1462932481:1462952921 (repaired)
Jul 31 19:30:29 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1462932481:1462952921 (repaired)
Jul 31 19:30:30 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:5e37:2374:63273/443 unexpectedly shrunk window 3861953537:3862015916 (repaired)
Jul 31 19:30:31 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:5e37:2374:63273/443 unexpectedly shrunk window 3861953537:3862015916 (repaired)
Jul 31 19:30:32 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:5e37:2374:63273/443 unexpectedly shrunk window 3861953537:3862015916 (repaired)
Jul 31 19:30:33 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:1885:f5b0:30313/443 unexpectedly shrunk window 1462932481:1462952921 (repaired)
Jul 31 19:30:34 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:5e37:2374:63273/443 unexpectedly shrunk window 3861953537:3862015916 (repaired)
Jul 31 19:30:38 xxxxxxxx*** kernel: Peer 0000:0000:0000:0000:0000:ffff:5e37:2374:63273/443 unexpectedly shrunk window 3861953537:3862015916 (repaired)

Источник