idle power consumption

ryecoaaron · 4. März 2015

If the value for Wake-on is 'g', then WOL is supported. You have a 'g'.

C0mmanda · 4. März 2015

Q1900-ITX definitely supports WOL out-of-the-box!
You have to activate "PCIe is allowed to wake up" or similar. Dont know the exact syntax now.

I'm waking my OMV with a RasPi via Cron. wakeonlan does not work, etherwake does! (apt-get install etherwake). Don't know why...
Maybe it helps to try another tool if WOL does not work.

Is there any Risk to go on Backport-Kernel?

I would like to see your results of testing the Q1900-ITX with Pico-PSU. Maybe it is worth to change my PSU...

ryecoaaron · 4. März 2015

Zitat von C0mmanda

I'm waking my OMV with a RasPi via Cron. wakeonlan does not work, etherwake does! (apt-get install etherwake). Don't know why...

The openmediavault-wol plugin uses etherwake.

Zitat von C0mmanda

Is there any Risk to go on Backport-Kernel?

No. I run it on all of my systems and it usually runs better.

Zitat von C0mmanda

QI would like to see your results of testing the Q1900-ITX with Pico-PSU. Maybe it is worth to change my PSU...

I don't believe the efficiency numbers they publish. Those things get very hot which is wasted power. You also have the 12v psu's efficiency to add. I haven't had good luck with long life with them either.

Don · 4. März 2015

When you shut down OMV, is the green LED on the NIC on or OFF?

schpongo · 4. März 2015

Zitat von ryecoaaron

I don't believe the efficiency numbers they publish. Those things get very hot which is wasted power. You also have the 12v psu's efficiency to add. I haven't had good luck with long life with them either.

That was a user report and it was very detailed and specific so I didn't think it was created by the manufacturer.
I would still like to know if the consumption is lower. At the moment 1 Watt at idle will cost me 2,13 euros over the period of a year.
Reliability is most certainly something to be considered.

Zitat von Don

When you shut down OMV, is the green LED on the NIC on or OFF?

At the moment no. I will look into the bios again for the pci thing C0mmanda mentioned.

Don · 4. März 2015

You can find it in
UEFI, Advanced, ACPI Configuration
PCIE Device Power On

Handbook S.41

schpongo · 4. März 2015

Small update:
For all my tests I unplugged all the data drives from the system so I don't have to wait until they are spun down.

1. I tried the backport kernel 3.16 and the system consumed about 0.5 Watts more. So I selected the 3.20 kernel again the system consumed 0.5Watts less again

2. I got wol to work

At the moment I'm cloning the system to a usb stick.

ryecoaaron · 4. März 2015

I wouldn't leave it on a usb stick...

C0mmanda · 4. März 2015

Zitat von ryecoaaron

OpenMediavault-wol plugin uses etherwake.

Nice to know. Thanks!

Zitat

No. I run it on all of my systems and it usually runs better.

Just installed 3.16 Backports-Kernel, my Digital-Devices CineS2 Card was not detected.
Any idea why?
Switched directly back to 3.2.0...

Zitat

I don't believe the efficiency numbers they publish. Those things get very hot which is wasted power. You also have the 12v psu's efficiency to add. I haven't had good luck with long life with them either.

That's new to me, if the Pico dies quickly every power-saving is ridiculous.
I will bet a good PSU, like my beQuiet! will live 10years or more.
Never had a PSU which died, and I had a few really cheap and old ones.. (aged 10years, still living)

ryecoaaron · 4. März 2015

Did you compile the driver? If you did, you need to compile it for each kernel.

C0mmanda · 4. März 2015

Zitat von ryecoaaron

Did you compile the driver? If you did, you need to compile it for each kernel.

Yes, I did.
Makes sense, thank you!
Will give it another try this weekend!

schpongo · 4. März 2015

So I failed to copy the os drive to my usb stick.
I never do get along with clonezilla .

I'll maybe retry running on a usb stick at a later point in time.

Zitat von ryecoaaron

I wouldn't leave it on a usb stick...

I wasn't planning to. I would have just like to know the power difference.

ryecoaaron · 4. März 2015

If the usb stick is smaller than the drive, you need to enable ICDS in advanced options of clonezilla.

schpongo · 4. März 2015

Zitat von ryecoaaron

If the usb stick is smaller than the drive, you need to enable ICDS in advanced options of clonezilla.

I tried that but I still got an error. That time not the "disk too small" error but it still didn't work.

ryecoaaron · 4. März 2015

Resize the partitions to be smaller than the usb stick -or-

Create partitions on stick, rsync files to stick, and run some kind of grub rescue.

schpongo · 5. März 2015

Zitat von ryecoaaron

Resize the partitions to be smaller than the usb stick -or-

Create partitions on stick, rsync files to stick, and run some kind of grub rescue.

I'll maybe try an make the partition smaller.

Yesterday I also noticed that the case fan uses more than 1 Watt.
I knew one could set a target cpu temperature in the bios but I have quite understood how the system works.
I set my target cpu temp to 50C so that my hdd don't get too warm.

But the fan was spinning constantly at the entered speed even if the cpu only was at 35C.
I would have tought that the fan would only start spinning if the cpu temperature went over 50C.

C0mmanda · 5. März 2015

Target temp x, fan speed 1 = fan spins with speed 1 until target temp is reached
is the temp above target, fan speeds up to max if temp
cool down below target, fan slows down to speed 1

schpongo · 5. März 2015

Zitat von C0mmanda

Target temp x, fan speed 1 = fan spins with speed 1 until target temp is reached
is the temp above target, fan speeds up to max if temp
cool down below target, fan slows down to speed 1

Ahhh thank you.
So if I were to set the fan speed to "0" using the custom mode and set the cpu temp target to 50C the fan would only spin up if the cpu temp is above 50C and then it would also spin at max speed?

C0mmanda · 5. März 2015

Yes, it should
but keep an eye on it, I've never tested with Speed 0

C0mmanda · 6. März 2015

Zitat von davidh2k

30 is too high from our experience. You have to be below that. We don't know where this bug comes from, but values >=30 mins do not spindown hard disks for some people.

Greetings
David

I've set spindown-time to 20mins.
As it seems, without success...

Code

@C0mmanda-Server:~# hdparm -C /dev/sdd
/dev/sdd:
drive state is:  active/idle
@C0mmanda-Server:~# hdparm -C /dev/sda
/dev/sda:
drive state is:  active/idle
@C0mmanda-Server:~# hdparm -C /dev/sdb
/dev/sdb:
drive state is:  active/idle

All disks weren't touched for at least 40mins.
Checked even after hours of idle, same result

Any suggestions how to get these damn WD Greens into sleep?

Jetzt mitmachen!