My Oracle Support Banner

Unknown Device In VG. "vgreduce --removemissing" Failed with Error "/dev/xxx: write failed after 0 of xxxx at xxxx: Input/output error" (Doc ID 2536133.1)

Last updated on JUNE 01, 2020

Applies to:

Linux OS - Version Oracle Linux 5.0 and later
Linux x86-64

Symptoms

• Unknown device in VG . 

Couldn't find device with uuid 1h3D1f-NsJB-3wjs-geiu-McbQ-XXXX-KitqOu.
--- Physical volume ---
PV Name unknown device <====
VG Name grid_vg
PV Size 12.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 3071
Free PE 0
Allocated PE 3071
PV UUID 1h3D1f-NsJB-3wjs-geiu-McbQ-XXXX-KitqOu



• vgreduce failed with error "write failed after 0 of xxxx at xxxx: Input/output error"

# vgreduce --removemissing --verbose --force grid_vg
Finding volume group "grid_vg"
Couldn't find device with uuid 1h3D1f-NsJB-3wjs-geiu-McbQ-XXXX-KitqOu.
There are 1 physical volumes missing.
There are 1 physical volumes missing.
Trying to open VG grid_vg for recovery...
Couldn't find device with uuid 1h3D1f-NsJB-3wjs-geiu-McbQ-XXXX-KitqOu.
There are 1 physical volumes missing.
There are 1 physical volumes missing.
Archiving volume group "grid_vg" metadata (seqno 8).
Removing partial LV lv_grid.
Releasing logical volume "lv_grid"
/dev/mapper/LVM_HDS_398_XXXX: write failed after 0 of 8192 at 12288: Input/output error <===
WARNING: Failed to write an MDA of VG grid_vg.
/dev/mapper/mpathez: write failed after 0 of 4096 at 8192: Input/output error <===
WARNING: Failed to write an MDA of VG grid_vg.
Failed to write VG grid_vg.
Failed to write metadata area header
Failed to write metadata area header


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.