-
Notifications
You must be signed in to change notification settings - Fork 32
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
No log file despite -l /path/to/file.log #17
Comments
Hi @agcmartins Could you please share the result of the command Thank you |
Hi, Mar 31 23:47:30 raspberrypi systemd[1]: Started hd-idle - spin down idle hard disks. |
Sadly the log doesn't show long lines :/ |
Sure, but sorry, before I saw you message I had to reboot it. Apr 1 11:07:53 raspberrypi hd-idle[371]: sda spinup |
I can't tell why your log file is always empty. But not all is lost for you. You can use This is a sample of how the log file looks like:
Hope this helps. |
Thank you very much, I'll use that information. Do you have any advice about spin up events and hardware durability for external usb HD? |
I had to re-test the scenario that you describe and I can confirm that the log file does get created if it doesn't previously exits. Sorry that I can't help you further with this topic, but at least you got the data you were looking for. |
Hi all,
no log file:
hd-idle configuration file:
Anything I can do to help you track down the issue? |
Have you seen my reply to #63? |
All right. |
Hi,
Fist congratulation for the project I'm really enjoying the program and it works for me. I'm trying to use the log file to track how many times the disk spin up and down during a normal day. I need this to find the best sleep time to balance between disk durability/performance, by reducing the number of spinning up events per day and not allowing the disk to stay up 24/7. I'm using a raspberry 4 and a external HD as a backup centre for my other computers.
I've changed the last line of /etc/default/hd-idle to:
HD_IDLE_OPTS="-i 600 -l /home/USER/hd-idle.log"
I've also enabled and started it in systemctl and I can see that it is working and includes the log option using htop. However after I watched the disk spin up and down for a while, there is no log file in the directory.
Best
The text was updated successfully, but these errors were encountered: