Unmount an NVMe Storage Drive
# egrep –H ‘.*’ /sys/bus/pci/slots/*/address
This commands returns output similar to the following:
/sys/bus/pci/slots/10/address:0000:b8:00
/sys/bus/pci/slots/11/address:0000:b6:00
/sys/bus/pci/slots/12/address:0000:b2:00 (instance nvme0, pcie slot 12, drive
label nvme2)
/sys/bus/pci/slots/13/address:0000:b4:00 (instance nvme1, pcie slot 13, drive
label nvme3)
In the above output, the bus addresses for the corresponding NVMe instances are
highlighted in bold text.
Note - In the above output, notice that the instance names for the NVMe drives do not
correspond to the NVMe drive labels on the front of the server, that is, pci/slots/12/address:
0000:b2:00 corresponds to instance nvme0; however, on the front of the server, this drive is
labeled NVMe2. For a table that shows the relationship between the pci/slot# and the NVMe
storage drive label on the front of the server, see “Server Operating System Names for the
NVMe Storage Drives” on page 44.
c.
Disconnect all users of the NVMe drive and back up the NVMe drive data as
needed.
i.
Use the umount command to unmount any file systems that are mounted
on the device.
ii.
Remove the device from any multiple device (md) and Logical Volume
Manager (LVM) volume using it.
If the device is a member of an LVM Volume group, then it might be necessary
to move data off the device using the pvmove command, then use the vgreduce
command to remove the physical volume, and (optionally) pvremove to remove the
LVM metadata from the disk.
iii.
If the device uses multipathing, run multipath -l and note all the paths
to the device. Then, remove the multipathed device using the multipath
-f device command.
iv.
Run the blockdev --flushbufs device command to flush any outstanding
I/O to all paths to the device.
3.
To prepare the NVMe drive for removal, that is, to detach the NVMe device driver
and power off the NVMe drive slot, type:
Servicing Storage Drives (CRU) 75
To Next Page
Loading...
Need help?
General
