- Closed
I have been using hddtemp in a docker to read drive temperatures and have noticed that when I spin down drives and then let the hddtemp try to read it's temperature it knocks a drive out of the array (it will show up in assigned devices).
I have replicated it this a few times, and to stop it from occuring now I check if the drive is on standby (with smartmontools) before using hddtemp to read the temp. Drive is a 10TB Seagate, but note it won't happen with all Seagate drives, just appears to be this one (so far).
Steps to cause issue:
Spin down drive via unRAID interface
Use 'hddtemp -n /dev/sdX' on drive
-- Drive shows still spun down on interface and appears with new sdX assignment in Unassigned Devices --
Steps to fix/restore:
Stop array (if possible, if not reboot)
New config
Start array