FreeAgent Drives
« previous entry | next entry »
Jun. 6th, 2007 | 04:28 pm
We got some Seagate FreeAgent pro drives at work, and they have an annoying tendency to spin themselves down under linux, causing linux to give up on the drive and disconnect the device.
bbobbo on neweggs product review had a suggestion to fix this problem.
However I found that the sdparm command would fail if the drive was already idled.
update 2007 Dec 09: I've also used the drive with the eSATA connection, and in that case the linux kernel does appear to be able to restart the drive correctly.
bbobbo on neweggs product review had a suggestion to fix this problem.
However I found that the sdparm command would fail if the drive was already idled.
# the drive reports something like this
$ sudo sdparm -a /dev/sde
/dev/sde: Seagate FreeAgent Pro 400A
Power condition mode page:
IDLE 0 [cha: n, def: 0, sav: 0]
STANDBY 1 [cha: y, def: 1, sav: 1]
ICT 0 [cha: n, def: 0, sav: 0]
SCT 9000 [cha: y, def:9000, sav:9000]
# when the drive was idled I got the following error message.
$ sudo sdparm --clear STANDBY -6 /dev/sde
/dev/sde: Seagate FreeAgent Pro 400A
change_mode_page: failed setting page: Power condition
# this appears to force the drive to start
$ sudo sdparm --command=start /dev/sde
# and now this command works
$ sudo sdparm --clear STANDBY -6 /dev/sde
$ sudo sdparm -a /dev/sde
/dev/sde: Seagate FreeAgent Pro 400A
Power condition mode page:
IDLE 0 [cha: n, def: 0, sav: 0]
STANDBY 0 [cha: n, def: 1, sav: 0]
ICT 0 [cha: n, def: 0, sav: 0]
SCT 0 [cha: n, def:9000, sav: 0]
update 2007 Dec 09: I've also used the drive with the eSATA connection, and in that case the linux kernel does appear to be able to restart the drive correctly.

How annoying
from:
dilinger
date: Jun. 13th, 2007 03:11 pm (UTC)
Link
Reply | Thread
Re: How annoying
from:
alienghic
date: Jul. 12th, 2007 07:57 pm (UTC)
Link
Reply | Parent | Thread
Re: How annoying
from:
theemptied
date: May. 30th, 2008 09:22 pm (UTC)
Link
Heck, mines still shrink-wrapped on the counter- I've learned to pre-google ;)
Reply | Parent | Thread
Thanks. That worked for me!
from:
fptiangco
date: Aug. 1st, 2007 12:36 pm (UTC)
Link
Fedora Core 5
Seagate Freeagent 320GB (as /dev/sdd)
Thanks for that! That worked for me. I thought that the drive is still active because i can list the directories. But it seems that it wasn't because I can't do:
sdparm --clear STANDBY -6 /dev/sddif I hadn't done:
sudo sdparm --command=start /dev/sddas you have suggested. Will wait and see if it won't spin down/become idle again.
Just found this link useful, if you don't have sdparm, you can get the rpm from a post in this link: http://forums.fedoraforum.org/showthrea
Thanks again!
Reply | Thread
Re: Thanks. That worked for me!
from:
alienghic
date: Aug. 7th, 2007 05:51 am (UTC)
Link
The ls probably worked because I suspect the directory contents were still in linux's filesystem cache.
Reply | Parent | Thread
Re: Thanks. That worked for me!
from:
primadd
date: Dec. 9th, 2007 01:12 pm (UTC)
Link
Keep up the good work!
Reply | Parent | Thread
(no subject)
from:
quxi
date: Aug. 16th, 2007 12:25 am (UTC)
Link
for the user who is using the drive on linux who couldn't find a solution for the spindown problem, here is the solution: make sure you have the sdparm package installed. as root, do :
# sdparm -al /dev/sdd /dev/sdd: Seagate FreeAgentDesktop 100D
Direct access device specific parameters: WP=0 DPOFUA=0
Power condition [po] mode page: IDLE 0 [cha: n, def: 0, sav: 0] Idle timer active
STANDBY 1 [cha: y, def: 1, sav: 1] Standby timer active
ICT 0 [cha: n, def: 0, sav: 0] Idle condition timer (100 ms)
SCT 9000 [cha: y, def:9000, sav:9000] Standby condition timer (100 ms)
# sdparm --clear STANDBY -6 /dev/sdd /dev/sdd: Seagate FreeAgentDesktop 100D
# sdparm -al /dev/sdd /dev/sdd: Seagate FreeAgentDesktop 100D Direct access device specific parameters: WP=0 DPOFUA=0
Power condition [po] mode page:
IDLE 0 [cha: n, def: 0, sav: 0] Idle timer active
STANDBY 0 [cha: n, def: 1, sav
Reply | Thread
(no subject)
from:
dysath
date: Oct. 19th, 2007 04:16 pm (UTC)
Link
I bought the drive to use as a full Linux system that I could plug up to a box, boot off USB, and go. Except for the going to sleep thing, it works perfectly in that regard. Now I can fix it when I get home tonight and finally get to play!
Reply | Parent | Thread
You saved me a lot of work.
from:
pronnquist
date: Sep. 27th, 2007 04:55 pm (UTC)
Link
Reply | Thread
FreeAgent spindown problem
from:
marosorio
date: Oct. 31st, 2007 11:16 am (UTC)
Link
http://www.nslu2-linux.org/wiki/FAQ/Dea
Reply | Thread
Do you know...
from:
ptomblin_lj
date: Nov. 1st, 2007 01:45 pm (UTC)
Link
Reply | Thread
Re: Do you know...
from:
marosorio
date: Nov. 1st, 2007 10:55 pm (UTC)
Link
% sdparm -D --page=po -6 DEVICE (/dev/sdb is DEVICE in my case).
Reply | Parent | Thread
Re: Do you know...
from:
ewumnrr
date: Dec. 6th, 2007 07:57 am (UTC)
Link
sdparm --defaults --page=po -6 --save /dev/sdb
/M
Reply | Parent | Thread
Re: Do you know...
from:
rockclimber88
date: Dec. 9th, 2007 11:45 pm (UTC)
Link
but then again, I don't know that much about udev.
Reply | Parent | Thread
Re: Do you know...
from:
alienghic
date: Dec. 10th, 2007 12:40 am (UTC)
Link
Reply | Parent | Thread
Re: Do you know...
from:
ptomblin_lj
date: Dec. 10th, 2007 12:53 am (UTC)
Link
Reply | Parent | Thread
(no subject)
from:
pooloftrees
date: Dec. 9th, 2007 11:29 am (UTC)
Link
P.S. - I haven't got one, but it's very useful to know...
Reply | Thread
Fixed drive issue
from:
kernelrahl
date: Dec. 9th, 2007 04:27 pm (UTC)
Link
Please see my blog entry on the entire process. Ignore the backup stuff, it was my first pass at system backups. I have moved on since then to use some tools that do the job for me, but the drive fix is still required.
Scroll down to the "Beware sleeping drive" section.
http://cliffbenoist.com/blog/index.php?
Reply | Parent | Thread
(no subject)
from:
wxgeek
date: Dec. 9th, 2007 05:29 pm (UTC)
Link
Reply | Thread
Oh do enjoy.
from:
thisonething
date: Dec. 10th, 2007 12:21 am (UTC)
Link
Reply | Parent | Thread
Re: Do you know...
from:
alienghic
date: Dec. 10th, 2007 12:31 am (UTC)
Link
Though I right now I'm really wishing that LJ had integrated google analytics.
Reply | Parent | Thread
Re: Do you know...
from:
sodabrew
date: Dec. 10th, 2007 02:05 am (UTC)
Link
Reply | Parent | Thread
(no subject)
from:
rjray
date: Dec. 10th, 2007 03:14 am (UTC)
Link
Reply | Thread
(no subject)
from:
alienghic
date: Dec. 10th, 2007 06:04 am (UTC)
Link
The Firewire version did seem to work correctly with OS X though
Reply | Parent | Thread
FWIW
from:
neal1138
date: Dec. 10th, 2007 03:44 am (UTC)
Link
For what it's worth Western Digital My Book Premium external drives don't seem to have the spin down problem on Linux (at least on our old Red Hat systems). They work correctly out of the box using FireWire; haven't tried their USB ports. (In our experience FireWire 400 is somewhat faster than USB2 so we prefer it.)
We had originally tried Maxtor externals. The Maxtor "II" series worked fine with FireWire, but the Maxtor "III" series didn't--they exhibited the same problems you described. Since Seagate bought Maxtor, maybe the same technology is being used.
Thanks again for your post.
Reply | Thread
Re: FWIW
from:
alienghic
date: Dec. 10th, 2007 06:08 am (UTC)
Link
I wanted eSATA as I thought it'd be even faster than Firewire, the USB was mostly a backup for when we just needed quick access from on one of the systems that didn't have eSATA.
Reply | Parent | Thread
Re: FWIW
from:
neal1138
date: Jun. 5th, 2008 07:28 am (UTC)
Link
Wanted to post an update to my comment regarding Western Digital. We can no longer recommend them as we have had spontaneous failures of both My Book Premium 500G and My Book Home Edition 1T external FireWire drives, both under 1 year old.
The data on the drives was unrecoverable in both instances, even after we opened up the cases and attached the drives to internal SATA controller cards. Apparently we're not alone in experiencing this issue. Sure wish we had seen this post before purchasing:
http://www.tomrafteryit.net/western-dig
So we're back looking for alternative vendors with good Linux compatibility.
Reply | Parent | Thread
Good Discussion
from:
aaron_maynard
date: Dec. 10th, 2007 03:57 am (UTC)
Link
Reply | Thread
(no subject)
from:
yokozar
date: Mar. 7th, 2008 10:44 pm (UTC)
Link
I would notice erratic behavior when the drive was idle and connected by USB. Sometimes ls would report a folder not found - other times it would show a folder,but then I couldn't show a subfolder. Sometimes I'd get input/output errors and nothing at all would even work.
Reply | Thread
completing the circle...
from:
bbobbo_o
date: Aug. 12th, 2008 08:18 pm (UTC)
Link
Reply | Thread
Re: completing the circle...
from:
neal1138
date: Aug. 12th, 2008 09:40 pm (UTC)
Link
After doing an evaluation of alternatives to our failed WD My Books, we settled on the Maxtor One Touch 4 Plus series. They spin up/down with no problems under Linux (even on old unmodificed RH8 kernels). They have a 5 year warranty (as opposed to 1 year on the My Books).
We've purchased four of the new Maxtor's already in capacities ranging up to 1TB. Another indication of firmware quality: they seem to come up normally if we pull the plug on a server to simulate a severe crash and force an unscheduled cold boot (WD's would mostly come up offline in that scenario requiring lots of manual power cycling to bring them back online.)
Reply | Parent | Thread