From your description, the behaviour youβre seeing is very commonly related to power draw, not faulty drives.
The ZimaBlade NAS Kit with the 60W power adapter can usually run:
- 1 Γ 3.5" HDD reliably
- 2 Γ 3.5" HDD only if the spin-up current stays within limits
However, WD Red Plus 12TB (WD120EFGX) drives typically draw around 1.75β2A during spin-up. When both drives spin up at the same time, the startup current can exceed what the board and the 60W power brick can supply.
When that happens the system will repeatedly power-cycle the drive, which matches the behaviour you described and why:
- One drive works normally
- Two drives cause the drive to reset repeatedly
lsblk only shows one disk
Things you can check
Boot with one drive connected and confirm it appears:
lsblk
Then power off and swap the drives, confirming both disks work individually.
If each disk works by itself but the reboot behaviour starts when both are connected, it strongly suggests a power limit during HDD spin-up.
Check kernel messages
When both drives are connected you can also check the system logs:
dmesg | tail -n 50
Typical power-related messages include:
- SATA link resets
- drive disconnect / reconnect loops
- controller resets
Common solutions
Most users solve this in one of these ways:
1. Use a higher wattage PSU
A 90W or 120W adapter gives enough headroom for two 3.5" drives to spin up.
2. Use an externally powered enclosure
This removes the startup load from the ZimaBlade.
3. Use lower spin-up current drives
Some HDD models draw less current during startup.