Security Compliance

Buffer I/O error on device sdaX logical block XXXXXX

SEM displays the following error when booting and drops to an initramfs(.busybox) prompt: Buffer I/O error on device sdaX, logical block XXXXXX The issue still persists even after SEM is rebooted and the root login prompt is not displayed. The only way to access SEM is through the Console directly from VMware/Hyper-V.

First published date

10/29/2018 8:05 PM

Last published date

10/29/2018 8:05 PM

Overview

Security Event Manager (formerly Log & Event Manager) displays the following error when booting and drops to an initramfs(.busybox) prompt:

Buffer I/O error on device sdaX, logical block XXXXXX

The issue still persists even after SEM is rebooted and the root login prompt is not displayed. The only way to access SEM is through the Console directly from VMware/Hyper-V.

Product section

Security Event Manager

Cause

This issue occurs when one of the physical disks develop bad sectors.

Resolution

  • If rebooting SEM does not prompt you to log in as root to manually run fsck, reboot the host and run a disk check. Refer to your Hyper-V or VMware documentation on how to monitor failing disks.
  • Refer to Boot drops to a (initramfs) prompts/busybox (© 2017 Stack Exchange Inc, available at https://askubuntu.com/, obtained on June 23, 2017.) to identify and repair the bad superblock or sector.

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.