Extended root LV using DASD disk and getting IO error after reboot

Solution Verified - Updated -

Issue

  • Can a DASD Disk be used for Root LV or root file system?

  • The root LV was extended using a DASD disk but it's getting activated in partial mode and LVM reports these error(s):

/dev/root: read failed after 0 of 4096 at 16554852352: Input/output error
  • Boot-time error(s):
dracut: Scanning devices sda2  for LVM logical volumes rootvg/rootlv
dracut: Couldn't find device with uuid WPJ2JE-300V-dmTc-uhq0-Qp0X-l5ov-qwWcEN.
dracut: inactive '/dev/rootvg/rootlv' <DD>15.42 GiB<A8> inherit
dracut: PARTIAL MODE. Incomplete logical volumes will be processed.
dracut: Couldn't find device with uuid WPJ2JE-300V-dmTc-uhq0-Qp0X-l5ov-qwWcEN.
Buffer I/O error on device dm-1, logical block 4041712
Buffer I/O error on device dm-1, logical block 4041726
Buffer I/O error on device dm-1, logical block 4041727

Environment

  • Red Hat Enterprise Linux
  • Direct Access Storage Device (DASD)
  • IBM System z

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content