Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drives not waking up #122

Open
Craigp23 opened this issue Nov 20, 2024 · 2 comments
Open

Drives not waking up #122

Craigp23 opened this issue Nov 20, 2024 · 2 comments

Comments

@Craigp23
Copy link

Hello :)

Running hd-idle with defaults on an OMV7/Debian system with several Exos SAS drives connected via an LSI HBA (IT mode) card.

hd-idle is successfully spinning down the disks after 10 minutes or so but the disks aren't waking up.

The OS gives an I/O error (or read/only error) when I run fdisk, etc to attempt to wake them up.

If the system is rebooted all okay... for 10 minutes ;o)

TIA

@adelolmo
Copy link
Owner

Hi @Craigp23
I can only suggest to use a different -c command_type option.
Please check the documentation here.

@Craigp23
Copy link
Author

Craigp23 commented Nov 20, 2024

Hi @Craigp23
I can only suggest to use a different -c command_type option.
Please check the documentation here.

Thanks, I'll try & post back🤞

I assumed the default (scsi) was the right method for this setup.

Edit : Thanks for the link to the documentation. I noticed this about the -p option :

"The default value of 0 works fine for disks accessible via the SCSI layer (USB, IEEE1394, ...), but it will NOT work as intended with real SCSI / SAS disks. A stopped SAS disk will not start up automatically on access, but requires a startup command for reactivation. Useful values for SAS disks are 2 for idle and 3 for standby."

I'll try setting -p to 2 or 3...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants