- Joined
- Dec 8, 2017
- Messages
- 442
One more note. This error only occurs when the drives are already in standby. If I wake them up in between timeout periods, they simply spin down again and there is no error, so my guess is something in your script that executes at end of timeout on drives in standby is causing the error. Is it possible you are searching for data that is unavailable on drives in standby?
Code:
root@nas:/mnt/Main/Files/Software/Scripts # ./spindown_timer.sh -m -t 60 -p 15 -v -i da16 -i da17 -i da18 -i da19 Monitoring drives with a timeout of 60 seconds: da16 da17 da18 da19 I/O check sample period: 15 sec 2019-10-18 15:34:28 Drive timeouts: [da16]=60 [da17]=60 [da18]=60 [da19]=60 2019-10-18 15:34:43 Drive timeouts: [da16]=45 [da17]=45 [da18]=45 [da19]=45 2019-10-18 15:34:58 Drive timeouts: [da16]=30 [da17]=30 [da18]=30 [da19]=30 2019-10-18 15:35:13 Drive timeouts: [da16]=15 [da17]=15 [da18]=15 [da19]=15 2019-10-18 15:35:29 Spun down idle drive: da16 2019-10-18 15:35:30 Spun down idle drive: da17 2019-10-18 15:35:31 Spun down idle drive: da18 2019-10-18 15:35:31 Spun down idle drive: da19 2019-10-18 15:35:31 Drive timeouts: [da16]=60 [da17]=60 [da18]=60 [da19]=60 2019-10-18 15:35:46 Drive timeouts: [da16]=45 [da17]=45 [da18]=45 [da19]=45 2019-10-18 15:36:01 Drive timeouts: [da16]=30 [da17]=30 [da18]=30 [da19]=30 2019-10-18 15:36:17 Drive timeouts: [da16]=15 [da17]=15 [da18]=15 [da19]=15 2019-10-18 15:36:32 Spun down idle drive: da16 2019-10-18 15:36:33 Spun down idle drive: da17 2019-10-18 15:36:34 Spun down idle drive: da18 2019-10-18 15:36:34 Spun down idle drive: da19 2019-10-18 15:36:34 Drive timeouts: [da16]=60 [da17]=60 [da18]=60 [da19]=60