Krautmaster
Explorer
- Joined
- Apr 10, 2017
- Messages
- 81
Dear all, currently im trying to rebuild my homeserver rig to have a more energy saving environment.
Its a Xeon D Board with a 16x LSI onboard. ESXI and im passing that LSI 2116 to my Freenas VM.
There are 6x 4TB WD Green inside, I want them to go sleeping if no activity on disk. (the disks where sleeping fine with the LSI 9280 i8 I also have)
My personal goal is to have all VMs running on a 512 GB NVME disk and to have a 6x4TB RaidZ1 + 2 TB Cache via SSD. I want my disks to spin down - and that is the problem. Whatever i try to do, thy dont fell asleep.
With xigamanas it seem slike i could put them manually down by
but no matter what I configure in the Webclient, the disks stay up. There cant be really disk access, as they stay completely unconfigured during time of testing.
I tried 5 min of idle timeout, 127 power level, and i set SMART monitoring to standby. Disk will not stop at all - but anyhow manually with that command above.
In freenas its slightly different.
If I try ataidle i get this:
I cant really remember if i used wdidle to disable anything some years back, but i can hardly imagine that this causes my issue.
Any ideas how to get the atadile running like it should?
First thing I will do at home is to check the jumper as i saw this:
https://support-en.wd.com/app/answers/detail/a_id/20944
Someone experience with that?
Thanks for your help.
Its a Xeon D Board with a 16x LSI onboard. ESXI and im passing that LSI 2116 to my Freenas VM.
There are 6x 4TB WD Green inside, I want them to go sleeping if no activity on disk. (the disks where sleeping fine with the LSI 9280 i8 I also have)
Code:
xigmanas: /home# camcontrol identify da2 pass3: <WDC WD40EZRX-00SPEB0 80.00A80> ACS-2 ATA SATA 3.x device pass3: 600.000MB/s transfers, Command Queueing Enabled protocol ATA/ATAPI-9 SATA 3.x device model WDC WD40EZRX-00SPEB0 firmware revision 80.00A80 serial number WD-WCC4E6HS7PKU WWN 50014ee20b6d870e cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 4096, offset 0 LBA supported 268435455 sectors LBA48 supported 7814037168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM 5400 Zoned-Device Commands no Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags NCQ Queue Management no NCQ Streaming no Receive & Send FPDMA Queued no SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no automatic acoustic management no no media status notification no no power-up in Standby yes no write-read-verify no no unload no no general purpose logging yes yes free-fall no no Data Set Management (DSM/TRIM) no Host Protected Area (HPA) yes no 7814037168/7814037168 HPA - Security no
My personal goal is to have all VMs running on a 512 GB NVME disk and to have a 6x4TB RaidZ1 + 2 TB Cache via SSD. I want my disks to spin down - and that is the problem. Whatever i try to do, thy dont fell asleep.
With xigamanas it seem slike i could put them manually down by
Code:
xigmanas: ~# camcontrol standby da4 -t 10 xigmanas: ~# camcontrol standby da5 -t 10 xigmanas: ~# camcontrol standby da6 -t 10 xigmanas: ~# camcontrol standby da7 -t 10
but no matter what I configure in the Webclient, the disks stay up. There cant be really disk access, as they stay completely unconfigured during time of testing.
I tried 5 min of idle timeout, 127 power level, and i set SMART monitoring to standby. Disk will not stop at all - but anyhow manually with that command above.
In freenas its slightly different.
If I try ataidle i get this:
Code:
root@freenas[~]# ataidle -i /dev/da1 root@freenas[~]# ataidle -i /dev/da2 root@freenas[~]# ataidle -s /dev/da2 root@freenas[~]# ataidle -o /dev/da2 ataidle: the device does not support power management root@freenas[~]# /bin/bash /bin/spindown/spindown.sh How many minutes do you want between spin checks? 1 Monday, Jul 15 pass0 pass1 pass2 pass3 pass4 pass5 pass6 pass7 pass8 Tmax Tmean 02:45:50 Spin /bin/spindown/spindown.sh: line 85: let: Tsum=0+: syntax error: operand expected (error token is "+") Spin /bin/spindown/spindown.sh: line 85: let: Tsum=0+: syntax error: operand expected (error token is "+") Spin /bin/spindown/spindown.sh: line 85: let: Tsum=0+: syntax error: operand expected (error token is "+") Spin 39 Spin 38 Spin 37 Spin 38 Spin 40 Spin 37 ^40 25.44 ERRc= -8.13 02:46:51 Spin /bin/spindown/spindown.sh: line 85: let: Tsum=0+: syntax error: operand expected (error token is "+") Spin /bin/spindown/spindown.sh: line 85: let: Tsum=0+: syntax error: operand expected (error token is "+") Spin /bin/spindown/spindown.sh: line 85: let: Tsum=0+: syntax error: operand expected (error token is "+") Spin 39 Spin 38 Spin 37 Spin 38 Spin 40 Spin 37 ^40 25.44 ERRc= -8.13
I cant really remember if i used wdidle to disable anything some years back, but i can hardly imagine that this causes my issue.
Any ideas how to get the atadile running like it should?
First thing I will do at home is to check the jumper as i saw this:
https://support-en.wd.com/app/answers/detail/a_id/20944
Someone experience with that?
Thanks for your help.