RASR (Rapid Appliance Self Recovery) can return a Dell EMC VxRail 4.7 node to its factory image. A factory reset is data-destructive: treat the node’s existing ESXi configuration and node-resident data as lost, and do not assume that the reset updates firmware. Use this historical VxRail 4.7 walkthrough only after generating the procedure for the exact node and software version in Dell SolVe Online or working with Dell Support.
Stop before you begin: VxRail 4.x is end of life. Do not reuse this 2019 screen sequence for VxRail 7.x, 8.x, 9.x, or VCF on VxRail. Do not continue until workloads are evacuated, cluster resiliency is verified, backups are confirmed, and the exact RASR image and procedure are approved.
What a VxRail RASR factory reset changes
RASR is a bare-metal recovery path, not a routine reboot or a general troubleshooting shortcut. For a factory reset, plan for these outcomes:
- The node boots from its RASR recovery media and restores the factory image to the boot device.
- The previous ESXi configuration and node-resident data must not be treated as recoverable after the reset.
- The RASR image determines the software level restored to the node. Confirm that image before selecting Factory Reset.
- A factory reset does not by itself guarantee the required firmware baseline. Validate firmware and software compatibility separately.
- The node must be reconfigured, reintroduced to the cluster, and validated after recovery.
Dell’s current documentation says to use SolVe Online for VxRail procedures to avoid potential data loss. The Dell VxRail documentation list also identifies the 4.x series as end of life.
Use this legacy guide only when all conditions are true
- The target really is a Dell EMC VxRail 4.7 node with the IDSDM-based recovery path shown below.
- The reset is part of an approved rebuild, repurpose, or support-directed recovery plan.
- The node has been safely removed from service and the cluster can tolerate its absence.
- No required workload, vSAN object, log, key, or configuration exists only on this node.
- You have the version- and model-specific Dell procedure and a tested post-reset reintegration plan.
Go/no-go checklist before selecting Factory Reset
| Control | Evidence required before “go” | Why it matters |
|---|---|---|
| Change authorization | Approved change or Dell support plan names the exact node and purpose | Prevents an irreversible action on the wrong system |
| Node identity | Service tag, model, cluster, and current VxRail version match the plan | RASR paths and media differ across generations |
| RASR image | Image source and code level are verified for this hardware | The recovery image controls the restored software level |
| Workload evacuation | No production VM or required local workload remains on the host | Factory reset is destructive |
| Cluster and vSAN health | Capacity, fault tolerance, object health, and resynchronization state are acceptable | A second failure can turn maintenance into an outage |
| Recovery data | Backups, encryption material, credentials, licenses, and required logs are available | Do not rely on the reset node as the recovery source |
| Configuration capture | Management addressing, DNS, NTP, VLANs, vmnics, vDS membership, and host-specific settings are recorded | Speeds accurate reintegration |
| Out-of-band access | Working iDRAC console and power control are confirmed | The host will reboot outside normal ESXi management |
| Reintegration plan | Owner, maintenance window, cluster-add procedure, networking steps, and validation criteria are assigned | A successful reset is only the midpoint of recovery |
Legacy VxRail 4.7 RASR workflow
The screenshots below document a 2019 VxRail 4.7 node. Menu names, boot devices, and recovery behavior can differ by model, image, and release. Use them as orientation; the generated Dell procedure for your exact system remains authoritative.
1. Identify and isolate the correct node
Match the service tag and hardware identity to the approved change. Confirm that evacuation, maintenance mode, and cluster-health checks are complete before restarting anything.
2. Restart through controlled out-of-band access
Use the approved iDRAC or local-console method to restart the node. Keep the console open so you can enter Boot Manager during POST.
3. Open Boot Manager
During POST, press F11 to open Boot Manager. If the console misses the keypress, allow the system to boot and restart cleanly; do not interrupt power repeatedly.
4. Select the verified one-shot recovery device
Choose the one-shot UEFI boot menu, then select the internal SD/IDSDM recovery device shown in the generated procedure. Stop if the device name or expected image does not match.
5. Validate the RASR menu before choosing Factory Reset
Allow the recovery application to load. Compare the menu, node identity, and recovery-image information with the approved Dell procedure. In this historical interface, option 1 begins the factory-reset path.
6. Read the destructive warning and obtain the final go-ahead
The confirmation screen is the final stop point. Read it in full. Confirm again that the service tag, image, backups, workload evacuation, and cluster condition match the plan. Select Y only after the designated operator or change owner gives the final go-ahead.
7. Allow reinitialization to finish, then reboot as directed
Do not interrupt power or close the recovery path while the node is being reinitialized. Follow the generated procedure for returning to the menu and rebooting. The original lab run took roughly 30–45 minutes, but that is not a service-level target; hardware, media, and image differences can change the duration.
Post-reset recovery and validation
A successful RASR screen does not mean the node is ready for workloads. Complete and record the following checks:
- Confirm the node boots normally and record the restored VxRail, ESXi, driver, and firmware levels.
- Compare the restored levels with the applicable VxRail support matrix and the approved cluster baseline.
- Restore management networking, DNS, NTP, credentials, and any required host-specific settings through the supported workflow.
- Add or discover the node only through the version-specific Dell procedure.
- Restore distributed-switch membership and validate vmnic-to-uplink mapping. See the VxRail 4.7 distributed-switch re-add walkthrough for the legacy context.
- Verify vSAN health, object accessibility, resynchronization, disk-group state, and cluster alarms before restoring normal operations.
- Validate lifecycle-management compliance and complete any approved upgrade or firmware sequence.
- Record the result, exceptions, and final evidence in the change or support case.
When to stop and open a Dell support case
| Condition | Safe next action | Reference |
|---|---|---|
| The node repeatedly reports “trying to mount RASR” or returns to the recovery menu | Stop repeated reset attempts and validate the model-specific boot order | Dell KB 000051702 |
RASR fails at 15_setup_node.sh | Preserve logs and follow Dell’s failure-specific diagnosis rather than improvising | Dell KB 000050335 |
| The recovery image, code level, menu, or boot device differs from the plan | Exit without confirming Factory Reset and regenerate the procedure | SolVe guidance |
| vSAN objects are inaccessible, resynchronizing unexpectedly, or the cluster has lost required fault tolerance | Do not reset another node; stabilize the cluster first | Dell support case and your approved recovery plan |
| The target runs VxRail 7.x, 8.x, 9.x, or VCF on VxRail | Do not use this 4.7 sequence; generate the current procedure | Current VxRail manuals |
VxRail RASR factory reset FAQ
Does a RASR factory reset update firmware?
Do not assume it does. Treat the factory reset, software/image level, and firmware-compliance workflow as separate controls. Verify the resulting versions against the support matrix and approved lifecycle plan.
Can I use these VxRail 4.7 screenshots on a newer node?
No. They document one legacy 4.7 interface and recovery device. Generate a current SolVe procedure for the exact VxRail model, software version, and task.
Which RASR image should I use?
Use only the image identified by the approved Dell procedure for the target hardware and intended code level. If the media cannot be positively verified, stop before Factory Reset.
How long does a VxRail RASR reset take?
The original 4.7 lab run took about 30–45 minutes for the reset and reboot. Plan a longer maintenance window for preparation, failures, configuration, cluster reintroduction, vSAN resynchronization, and full validation.
Is a successful reset the end of the maintenance?
No. The node is not complete until networking, cluster membership, vSAN health, lifecycle compliance, alarms, and workload readiness have all passed the documented acceptance criteria.