by UberSlackr » Sun Feb 10, 2013 9:46 pm
$this->bbcode_second_pass_quote('Socaltom', 'T')here are a couple of tools that can help. hdidle is in the repos, and its easy to use, but.... if you have a swap file or logging, then the drive gets accessed routinely and it rarely powers down. I had some sucess by mounting a thumbdrive as var/log and let the logging get done there, but i still couldn't get my root drive to power down as often as my data drive.
Tom
Thanks for your response.
I shouldn't have any Swap or logging being performed on the Hard Drives. The root/linux is run off an inexpensive 16GB thumb drive, plus its flash memory so the risk of damage with constant power, or removal when powered is very very minimal. I'm just concerned about the 2 1TB Hard Disk Drives. It seems you were able to get your "data" drives to "power down" unfortunately I've had No success at this. The drives have been running constantly for 4-5 days (were only down for a short time 4-5 days while I updated alARM and did some testing.)
The only thing running within alARM is miniDLNA and Samba. I stopped both services, thinking maybe one of them was keeping the drives "alive" but had no success with that. Just been unable to finger out why they are not going to "sleep"/"powering down"... Thought it was a feature built into Arch, but maybe it was removed with the build of alARM.
I will definitely check into "hdiddle" for the "sleep" problem, thank you for the suggestion.
Update: I'm not finding anything in repos or package list by the name "hiddle"Also, Issuing the "poweroff" command does not seem to power off the drives for safe removal... so that's my major concern really. The poweroff seems to shutdown alARM, at least it breaks any SSH and Samba Connection I have open. But if I place my hand on the STAT or USB HHD I can feel the discs spinning. (Had a barebone (no cover/shell) drive in the top SATA port before I replaced it with the GoFlex, and after issuing the poweroff command, I grabbed a hold of the SATA Drive (a little to hard, and not knowing it was still spinning) and caused the discs inside the grind (so that drive is toaste.) Any thoughts on why the poweroff (or even halt) command is not working properly?