What must be verified before replacing a drive in a dedicated server?
Drive replacement is a coordinated storage operation, not simply removal of the device that looks suspicious. Verify the physical target, array health and supported replacement procedure first. A hot-swap chassis does not mean every mounted drive or degraded-array state can safely tolerate an immediate removal.
Before you start
- Authorised access to the dedicated server and the named inspection tools.
Instructions
1. Verify identity and the remaining redundancy
Collect the selected drive’s stable identifiers and the current array state. Hardware RAID or ZFS requires its corresponding supported reporting tools.
lsblk -d -o NAME,SIZE,MODEL,SERIAL,WWN
cat /proc/mdstatMap the selected device to the provider’s bay and serial record, and confirm whether any other members are failed or rebuilding.
2. Agree the exact replacement plan
Confirm compatible capacity, sector format, interface, firmware and endurance. The ticket should name the old and replacement serials, authorised bay, maintenance impact and the expected rebuild or restore procedure. Verify recovery arrangements before physical work.
Check the result
- After replacement, the correct drive is present, the intended array returns to a healthy state and application data and performance pass the agreed checks.
Troubleshooting
- The replacement is nominally the same size but cannot join
- Actual sector count or format may differ. Use the controller/filesystem vendor’s compatibility requirements.
- There is uncertainty about which drive failed
- Stop physical removal until serial and bay identity are independently reconciled.
- Multiple members are unhealthy
- Escalate the recovery plan; a routine one-drive replacement sequence may no longer apply.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.