HDD Standby

Th-Hahn

New Member
Nov 12, 2012
4
0
1
Hi all,

I have set up a Proxmox 2.2 with 3 HDD's.
The Proxmox OS and the related VM's are stored only on the first HDD.
The other two disks contains only some independent data which are not relevant for Proxmox operation.

These HDD's don't reach the standby mode. They don't spin down.
After manually hdparm -Y /dev/sdX the device will going in "standby" but after few seconds it switched back to "active/idle".

Can you give me a hint where the problem is ?

Thanks in advance!

Mit freundlichen Grüßen/Best regards

Thomas
 
Hi all,

the problem still exists -.-

So I checked the kernel.log and found a hint....

The following lines will appear immediately after executing of hdparm -Y /dev/sdX

Nov 13 22:32:30 BO01 kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6
Nov 13 22:32:30 BO01 kernel: ata4.00: waking up from sleep
Nov 13 22:32:30 BO01 kernel: ata4: hard resetting link
Nov 13 22:32:30 BO01 kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 13 22:32:30 BO01 kernel: ata4.00: configured for UDMA/133
Nov 13 22:32:30 BO01 kernel: ata4: EH complete

Nov 13 22:44:39 BO01 kernel: ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6
Nov 13 22:44:39 BO01 kernel: ata5.00: waking up from sleep
Nov 13 22:44:39 BO01 kernel: ata5: hard resetting link
Nov 13 22:44:40 BO01 kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 13 22:44:40 BO01 kernel: ata5.00: configured for UDMA/133
Nov 13 22:44:40 BO01 kernel: ata5: EH complete


Did some one have a idea how I can solve these exception ?

Thomas
 
Hi again,

I found out that the daemon pvestatd will wake up the normally unused hdd's.

If I stop it and send the hdd's via hdparm -y /dev/... into standby they remains in standby and only wake up if I access.

Can someone tell me what these daemon does ?
And if it is necessary, it possible to configure these hdd scans ?

Thomas
 
Hi Dietmar,

thanks for your response.
I had a deeper look in the coding and found that the sub update_storage_status {} will responsible.
If I comment the whole sub the hdd's will sleep well ;)

I think in these sub the line 272 my $info = PVE::Storage::storage_info($cfg); will be the bad guy.

But I think this will not the best practice to solve the problem.... -.-
Also I'm not expert in Perl so I don't found the (package or class ??) PVE::Storage::storage_info.

Did some one have an information where I can found the sub storage_info ?

Thomas
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!