Capture the state before changing anything

Take screenshots of the storage manager, SMART status, event log and drive bay LEDs. Record the exact model, serial number, firmware and bay. Reboots can clear useful evidence and may temporarily make an intermittent problem disappear.

If the array is degraded, verify the backup before any repair operation. Do not create a new volume, initialize the disk or accept a prompt that overwrites partition information.

If the NAS is still serving data from the remaining members, avoid unrelated configuration changes. One controlled change at a time preserves the ability to identify what restored or broke detection.

Confirm the physical installation

After a safe shutdown, check that the drive is mounted correctly in the tray and the tray is fully inserted. Look for bent connectors, loose screws or a latch that has not engaged. In a desktop or HBA setup, inspect SATA data and power connections.

Seagate lists unplugged or faulty data cables, lack of spin-up and a faulty drive among major reasons a SATA disk is not detected. Replace a suspect cable with a known-good cable rather than relying on visual appearance alone.

Inspect the connector with good light but do not scrape contacts or apply household cleaners. Backplanes and trays can be damaged by force even when the drive appears slightly misaligned.

Determine whether the drive spins

A spinning drive usually produces a slight vibration after power-on. Do not touch internal components or move a running NAS. If the drive is silent and does not spin, the power path, backplane, tray or drive electronics may be at fault.

Repeated beeping or attempted spin-up is not a reason to keep cycling power. Shut down and escalate, especially when the data is not backed up.

Some enclosures delay spin-up or sequence power across bays. Compare the missing drive with the normal startup behaviour of its neighbours before deciding that a few seconds of silence is a fault.

Use a known-good bay carefully

A controlled swap can distinguish a drive problem from a bay or backplane problem. Only do this after documenting bay order and following the NAS vendor’s shutdown and migration rules. Never move several RAID members casually.

If the missing drive works in another bay while a known-good drive fails in the original bay, the NAS hardware path becomes the leading suspect. If the IronWolf remains missing everywhere, focus on the drive and its power.

Write down the original bay order before any swap and photograph the front of the chassis. This simple record is valuable when the vendor asks for a controlled cross-test.

Visible to hardware but absent from the pool

When BIOS or the controller sees the model but the storage manager does not show the old pool, the issue may involve partition metadata, filesystem import, unsupported sector format, encryption or software policy. Preserve the disk unchanged while identifying the prior configuration.

Do not format simply because the operating system labels the disk uninitialized. That label may describe missing metadata from the current system, not an empty disk.

Encryption keys, passphrases and pool configuration backups can be as important as the disk itself. Preserve them before attempting import or recovery on another system.

Intermittent detection and host resets

An intermittent drive can point to a tray, cable, backplane, power supply, controller or the drive itself. IHM code 101 reports a connection issue, while code 106 reports excessive host resets. Correlate those codes with NAS logs and power events.

Back up while the drive is accessible. Intermittent detection is not stable enough for normal service or a long unattended test.

An unstable power supply can affect several bays or only the highest-load moment during spin-up. Review UPS and system logs for abrupt shutdowns, undervoltage or repeated restarts.

After updates or compatibility changes

A NAS update can change validation rules, driver behaviour or display status. Check the vendor release notes and compatibility list for the exact drive. Firmware changes should be tied to the exact model and revision, not applied as a generic detection fix.

If the drive disappeared immediately after an update but remains visible to hardware, contact the NAS vendor before altering disk metadata.

Replacement and recovery choices

When the drive fails detection in known-good hardware, does not spin or repeatedly drops, start the warranty or replacement process. If the only copy of important data is on the disk, consider Rescue Data Recovery before returning it, because a warranty replacement does not recover files.

Match the replacement capacity and compatibility requirements. After rebuilding, review the original fault path so a bad bay or power issue does not damage the new disk.