How to Resolve a Missing DO_NOT_WIPE Label After Rebooting into the OL6 OS Post the BDA OL6 to OL7 Migration Reboot Step Being Stuck in the Dracut Emergency Shell
(Doc ID 2761416.1)
Last updated on MARCH 02, 2023
Applies to:
Big Data Appliance Integrated Software - Version 4.12.0 and laterLinux x86-64
Goal
Introduction
The five notes below apply to BDA 4.13 and higher when an OL6 to OL7 migration boots into the Dracut Emergency Shell are:
1. Migrating Oracle Linux 6 (OL6) to Oracle Linux 7 (OL7) Post ./bdareimagenode.sh Reboot Step Boots into the Dracut Emergency Shell (Doc ID 2794999.1).
2. How to Boot into the OL6 OS When BDA OL6 to OL7 Migration Reboot Step Remains Stuck in the Dracut Emergency Shell (Doc ID 2792691.1).
3. Confirming the State of the OL6 OS After Rebooting into that OS Post the BDA OL6 to OL7 Migration Reboot Step Being Stuck in the Dracut Emergency Shell (Doc ID 2761414.1).
4. How to Resolve a Missing DO_NOT_WIPE Label After Rebooting into the OL6 OS Post the BDA OL6 to OL7 Migration Reboot Step Being Stuck in the Dracut Emergency Shell (Doc ID 2761416.1).
5. How to Correct syslinux.cfg After Rebooting into the OL6 OS Post the BDA OL6 to OL7 Migration Reboot Step Being Stuck in the Dracut Emergency Shell (Doc ID 2675334.1).
The steps here apply if following Confirming the State of the OL6 OS After Rebooting into that OS Post the BDA OL6 to OL7 Migration Reboot Step Being Stuck in the Dracut Emergency Shell (Doc ID 2761414.1) and HDFS/Data partitions are found to be missing.
Background
When following, Confirming the State of the OL6 OS After Rebooting into that OS Post the BDA OL6 to OL7 Migration Reboot Step Being Stuck in the Dracut Emergency Shell (Doc ID 2761414.1), if "blkid" or "lsblk -o NAME,LABEL,MOUNTPOINT" indicates that an HDFS/Data partition is missing the "DO_NOT_WIPE" label, it needs to be added. This must be done before continuing with the rest of the checks in that note.
In the example here the HDFS/Data partition sda4 is missing the label DO_NOT_WIPE. That needs to be added back.
Solution
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
Goal |
Introduction |
Background |
Solution |
References |