Understanding the 'Buffer I/O error' Message During CentOS 7.9 Boot-Up#

Understanding the 'Buffer I/O error' Message During CentOS 7.9 Boot-Up#

Environment

RAID Model: all Graid card
Host Hardware: every platform
Operating System: Linux CentOS 7

Issue

When booting up a CentOS 7.9 system, users may encounter an error message that reads "Buffer I/O error on dev [gpdXn1], logical block 0, async page read". This document will explain the cause of this error message and provide some guidance for users on how to proceed.

Example of the IO error message during CentOS 7.9 booting.

[ 24.240854] Buffer I/O error on dev gpd0n1, logical block 0, async page read [ 24.240868] blk_update_request: I/O error, dev gpd0n1, sector 0 [ 24.240871] Buffer I/O error on dev gpd0n1, logical block 0, async page read [ 24.240960] blk_update_request: I/O error, dev gpd0n1, sector 0 [ 24.240966] Buffer I/O error on dev gpd0n1, logical block 0, async page read [ 24.240987] blk_update_request: I/O error, dev gpd0n1, sector 0 [ 24.240989] Buffer I/O error on dev gpd0n1, logical block 0, async page read [ 24.241018] blk_update_request: I/O error, dev gpd0n1, sector 0 [ 24.241023] Buffer I/O error on dev gpd0n1, logical block 0, async page read [ 24.241094] blk_update_request: I/O error, dev gpd0n1, sector 0 [ 24.241100] Buffer I/O error on dev gpd0n1, logical block 0, async page read [ 24.241164] blk_update_request: I/O error, dev gpd0n1, sector 0 [ 24.241167] Buffer I/O error on dev gpd0n1, logical block 0, async page read

Cause of the Error

The error message indicates that the system is attempting to read from or write to a device during boot-up, and is encountering an error due to a restriction placed on the device. 

Resolution

The /dev/gpdXn1 is the NVMe drive which is already controlled by graid, and it is graid's physical drive path, not the virtual drive device, so graid would restrict user/applications to access those physical drives.

Hence, the "Buffer I/O error" message that users encounter during CentOS 7.9 boot-up is caused by the system attempting to access restricted devices, because those devices are controlled by graid driver and graid driver would restrict assess for safety reasons. While it may be disconcerting to see an error message during boot-up, the error is unlikely to cause any serious issues with the performance or stability of the system. As such, most users can safely ignore the error messages


    • Related Articles

    • Enabling Secure Boot with SupremeRAID™ on Ubuntu

      Environment RAID Model: SR1000 or SR1010 etc Host Hardware: AMD/Intel/Supermicro model etc Operating System: Linux Ubuntu etc Issue Setting up Secure Boot with SupremeRAID™ requires proper key enrollment for loading both the SupremeRAID and NVIDIA ...

    • Offline install SupremeRAID driver#

      Environment RAID Model: SR1000 or SR1010, SR1001 Host Hardware: Intel, AMD Operating System: Linux RPM base(Alamlinux, CentOS, RHEL, Oracle Linux) Issue When users need to install the SupremRAID driver but cannot connect to the external network. ...

    • How to get basic information from Graid log collection tool(Linux)?#

      Environment RAID Model: All Host Hardware: All Operating System: Linux Issue This script collects config and logs information that graid support requires to troubleshoot issues effectively. Resolution 1. Download the log collection script and make it ...

    • License not expired but when you apply fail show [Apply license failed : License expired]#

      Environment RAID Model: All Supreme RAID model Host Hardware: AMD/Intel Operating System: Linux SupremeRAID driver: 1.3.x or later Description If you check the license product expiry date not expired, but when you apply license still failed and show ...

    • Offline install SupremeRAID driver(Ubuntu)#

      Environment RAID Model: SR1000 or SR1010, SR1001 Host Hardware: Intel, AMD Operating System: Linux Deb base(Ubuntu) Issue When users need to install the SupremRAID driver but cannot connect to the external network. Resolution Prepare an environment ...