NSLU2-Linux
view · edit · print · history

HowTo.SetSpinDownTimeOnMaxtorOneTouch History

Hide minor edits - Show changes to markup

November 04, 2008, at 10:55 AM by Andreas Lundblad -- note by Andreas Lundblad
Added lines 187-188:

Note by Andreas Lundblad: I'm using Debian and a WD Mybook 320 gb Essential without a flash-stick. It will spin down after 10 minutes UNMOUNTED (out of the box). However after a clean Debian installation the system accessed the disk. (Logs said kjournald, sysklogd and pdflush). I resolved this by editing /etc/fstab and adding noatime on the sda lines and killing sysklogd and cron with rc-update -f remove sysklogd (and then for cron).

April 01, 2008, at 06:43 AM by Jean-Bernard --
Added line 190:
April 01, 2008, at 06:42 AM by Jean-Bernard --
Changed lines 190-192 from:
to:

[Solved] After checking, the hard drive spindown well, the indicator remains lit but the disc is well stopped after 10 '. I applied all the modifications suggested by Markus. Thank you with you all!

March 28, 2008, at 08:56 AM by Jean-Bernard --
Changed lines 187-192 from:
to:

Note by Jean-Bernard: Hello with all! I have myself a disc "My book essential edition 2 - 500GB" connected on my NSLU2 (firmware unslung 6.10 beta mounted on /dev/sdb1) and I applied all the various modifications suggested well above, but the disc never spin-down! However I checked well, the folders /dev and /var are well mounted in ramdisk and the disc indicates to me well that it there not access during more than 10 '!!! But nothing made there, he don't want to spin-down…. The only means of putting it in spin-down is to stop the NSLU2. Would you have a hint to give me? Somebody has the same problem?

Thank you for help !!

August 04, 2007, at 03:33 AM by David Cain -- Maxtor OneTouch III spins down only when the Slug is up
Added lines 9-10:

The Maxtor utility v4.1.0.12 will also change spindown time on my ext3fs OneTouch III. However, in testing I tried to wait for it to spin down with the drive plugged into the SLUG (running Debian Etch from a keychain disk) while the SLUG was powered off. This just didn't work. Solution: Boot up the slug, once booted, wait for the established spindown time - the drive spins down fine with the SLUG booted.

July 23, 2007, at 09:17 PM by fcarolo -- removed false wikilinks
Changed line 33 from:
  • I have a old Maxtor OneTouch drive and the original Maxtor driver really messed up my USB devices. This is how I fixed it (ONLY DO IF NECESSARY. NO GUARANTEES WITH THE FOLLOWING. TRY AT YOUR OWN RISK). Under WinXP? (SP2?) I deleted all the items under "Universal Serial Bus Controllers" in the device manager (a little trial and error is necessary as they need to deleted in the right order). OBVIOUSLY DON'T DO THIS IF YOU HAVE A USB KEYBOARD, as the USB devices will stop working (mouse can be an issue too, but you can usually get around it by using the keyboard)!!!! Upon rebooting XP will reinstall the USB controllers, and the necessary drivers for the USB items connected (usually without you needing the disks). Everything worked great after that.
to:
  • I have a old Maxtor OneTouch drive and the original Maxtor driver really messed up my USB devices. This is how I fixed it (ONLY DO IF NECESSARY. NO GUARANTEES WITH THE FOLLOWING. TRY AT YOUR OWN RISK). Under WinXP (SP2) I deleted all the items under "Universal Serial Bus Controllers" in the device manager (a little trial and error is necessary as they need to deleted in the right order). OBVIOUSLY DON'T DO THIS IF YOU HAVE A USB KEYBOARD, as the USB devices will stop working (mouse can be an issue too, but you can usually get around it by using the keyboard)!!!! Upon rebooting XP will reinstall the USB controllers, and the necessary drivers for the USB items connected (usually without you needing the disks). Everything worked great after that.
July 23, 2007, at 09:15 PM by fcarolo -- removed false wikilinks
Changed line 33 from:
  • I have a old Maxtor OneTouch? drive and the original Maxtor driver really messed up my USB devices. This is how I fixed it (ONLY DO IF NECESSARY. NO GUARANTEES WITH THE FOLLOWING. TRY AT YOUR OWN RISK). Under WinXP? (SP2?) I deleted all the items under "Universal Serial Bus Controllers" in the device manager (a little trial and error is necessary as they need to deleted in the right order). OBVIOUSLY DON'T DO THIS IF YOU HAVE A USB KEYBOARD, as the USB devices will stop working (mouse can be an issue too, but you can usually get around it by using the keyboard)!!!! Upon rebooting XP will reinstall the USB controllers, and the necessary drivers for the USB items connected (usually without you needing the disks). Everything worked great after that.
to:
  • I have a old Maxtor OneTouch drive and the original Maxtor driver really messed up my USB devices. This is how I fixed it (ONLY DO IF NECESSARY. NO GUARANTEES WITH THE FOLLOWING. TRY AT YOUR OWN RISK). Under WinXP? (SP2?) I deleted all the items under "Universal Serial Bus Controllers" in the device manager (a little trial and error is necessary as they need to deleted in the right order). OBVIOUSLY DON'T DO THIS IF YOU HAVE A USB KEYBOARD, as the USB devices will stop working (mouse can be an issue too, but you can usually get around it by using the keyboard)!!!! Upon rebooting XP will reinstall the USB controllers, and the necessary drivers for the USB items connected (usually without you needing the disks). Everything worked great after that.
Changed line 36 from:
  • experiment with ext2fsd mount command in a dos box (you need to guess the magic disk number) - just start from 0 and work up you'll find the ext drive eventually (you'll notice it can mount NTFS, FAT as well as EXT2?/3). You do not need to unmount a drive letter before trying another mount command (in fact it is a bit bugging in that it won't let you unmount unless you have successfully mounted). Check the mounted drive when you are successful (especially try a sub directory) - the ext2fsd driver seems a little sensitive, so if necessary give your PC a reboot, and try again.
to:
  • experiment with ext2fsd mount command in a dos box (you need to guess the magic disk number) - just start from 0 and work up you'll find the ext drive eventually (you'll notice it can mount NTFS, FAT as well as EXT2/3). You do not need to unmount a drive letter before trying another mount command (in fact it is a bit bugging in that it won't let you unmount unless you have successfully mounted). Check the mounted drive when you are successful (especially try a sub directory) - the ext2fsd driver seems a little sensitive, so if necessary give your PC a reboot, and try again.
Changed lines 165-168 from:

Note by Anguel Stankov: The rc.bootbin and rc.local scripts given above seem to make my WD MyBook? 500GB spin down with Unslung 5.5 only. I cannot make spindown work with Unslung 6.8 or original Linksys firmware v23RA5. This spin-down problem is also reported in the "nslu2-general" newsgroup.

Note by Oli Wright: I too had this problem with a WD MyBook? and Unlsung 6.8. It seems to be a process called 'onetouch_detect' that causes the problem. Killing it has made my WD MyBook? spin down properly after 10 minutes. If you add the following to the middle of the /unslung/rc.local script then the offending process will be killed on startup.

to:

Note by Anguel Stankov: The rc.bootbin and rc.local scripts given above seem to make my WD MyBook 500GB spin down with Unslung 5.5 only. I cannot make spindown work with Unslung 6.8 or original Linksys firmware v23RA5. This spin-down problem is also reported in the "nslu2-general" newsgroup.

Note by Oli Wright: I too had this problem with a WD MyBook and Unlsung 6.8. It seems to be a process called 'onetouch_detect' that causes the problem. Killing it has made my WD MyBook spin down properly after 10 minutes. If you add the following to the middle of the /unslung/rc.local script then the offending process will be killed on startup.

Changed line 177 from:

Note by Alexander Lorz: The combination of the additional rc.local, rc.bootbin and a modified crontab worked fine for letting my MyBook? 250 GB spin down on Unslung 6.8. The Downside of this solution is that I cannot power of the slug anymore by pressing the power switch. Reboot from the console works. If I remove or rename the new rc.local powering of the slug works fine again.

to:

Note by Alexander Lorz: The combination of the additional rc.local, rc.bootbin and a modified crontab worked fine for letting my MyBook 250 GB spin down on Unslung 6.8. The Downside of this solution is that I cannot power of the slug anymore by pressing the power switch. Reboot from the console works. If I remove or rename the new rc.local powering of the slug works fine again.

Changed line 198 from:

and modify all lines which mount a partition on your MaxtorOneTouch? to contain the noatime parameter like the following line:

to:

and modify all lines which mount a partition on your MaxtorOneTouch to contain the noatime parameter like the following line:

Changed line 205 from:

This will set the time till spin down (SCT = Standby ConditionTimer?) to 6 minutes (= 3600 tenth of a second).

to:

This will set the time till spin down (SCT = Standby ConditionTimer) to 6 minutes (= 3600 tenth of a second).

July 22, 2007, at 01:15 PM by itsmi -- exim4 settings
Added lines 201-202:

Beside that you have to change the exim4 settings in /etc/default/exim4. Either you must set a higher value for QUEUEINTERVAL (default = 30 minutes) to prevent exim from starting the disk every half hour, or you simply can stop the exim4 server if you don't need it.

July 21, 2007, at 05:53 PM by anonymous -- added kernel 2.4 and upwards solution
Added lines 193-203:

Solution for kernel 2.4 and upwards

Add to /etc/fstab the line

 tmpfs           /var/run        tmpfs   defaults,size=512k      0       0

and modify all lines which mount a partition on your MaxtorOneTouch? to contain the noatime parameter like the following line:

 /dev/sda1       /               ext3    defaults,noatime,errors=remount-ro 0       1

Additionally you can shorten the time after which the drive spins down using sdparm in the following way:

 sdparm --set=SCT=3600 /dev/sda

This will set the time till spin down (SCT = Standby ConditionTimer?) to 6 minutes (= 3600 tenth of a second).

June 15, 2007, at 10:41 PM by mwester -- Revert question; questions go to the mailing list and answers end up in the wiki!
Changed lines 185-187 from:

Note by Mekondelta: I have Unslung 6.8 beta and I don't have the various files above. My /unslung folder is empty. I do have a /etc/rc.d folder though. Using a Seagate FreeAgent 500GB and no spin down. Help!

to:
June 12, 2007, at 08:43 PM by mekondelta -- Added question about file locations
Changed lines 185-187 from:
to:

Note by Mekondelta: I have Unslung 6.8 beta and I don't have the various files above. My /unslung folder is empty. I do have a /etc/rc.d folder though. Using a Seagate FreeAgent 500GB and no spin down. Help!

March 23, 2007, at 09:57 AM by Mathis -- Slug power down issues with disk spin down
Added lines 180-182:

Note by Mathis: Uncommenting the return 1 line in /unslung/rc.local also fixes the issues with halting. Not returning 1 from any /unslung/rc.* script causes the calling /etc/rc.d/rc.* script to abort.

January 29, 2007, at 07:04 AM by Markus --
Added lines 180-182:

Note by Markus: I'm using Unslung 6.8 and a WD Mybook 320 gb Essential Edition without a flash-stick and it will spin down after about 10 minutes of inactivity IF the two scripts rc.local and rc.bootbin are used as described above together with edits of the crontab. I figured out that my disk was not called sda1 but sdb1, a hint to new users when editing rc.local. In the crontab I removed the line about checking disk space and changed the watchdog and time set function to run once a week.

January 27, 2007, at 08:13 PM by Oli Wright -- Added note about WD MyBook with Unslung 6.8
Added lines 167-176:

Note by Oli Wright: I too had this problem with a WD MyBook? and Unlsung 6.8. It seems to be a process called 'onetouch_detect' that causes the problem. Killing it has made my WD MyBook? spin down properly after 10 minutes. If you add the following to the middle of the /unslung/rc.local script then the offending process will be killed on startup.

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
# Kill the onetouch_detect processes so that the WD MyBook drive can spin down
/bin/killall onetouch_detect

(:tableend:)

January 15, 2007, at 12:45 PM by Alexander Lorz -- ... some typos
Changed lines 168-169 from:

Addendum: FIXED - just look at the old /etc/rc.d/rc.local and add the startup commands for the processes checking for reset and power-off to the new and all the other stuff after the re-mount of the drives in your new /unslung/rc.local

to:

Addendum: FIXED - just look at the old /etc/rc.d/rc.local and add the startup commands for the processes checking for reset and power-off and all the other stuff after the re-mount of the drives in your new /unslung/rc.local

January 15, 2007, at 12:44 PM by Alexander Lorz -- Spindown of MyBook works now ...
Changed lines 168-169 from:
to:

Addendum: FIXED - just look at the old /etc/rc.d/rc.local and add the startup commands for the processes checking for reset and power-off to the new and all the other stuff after the re-mount of the drives in your new /unslung/rc.local

January 10, 2007, at 11:21 PM by Alexander Lorz -- Spin down works, but slug doesnt power off
Added lines 167-168:

Note by Alexander Lorz: The combination of the additional rc.local, rc.bootbin and a modified crontab worked fine for letting my MyBook? 250 GB spin down on Unslung 6.8. The Downside of this solution is that I cannot power of the slug anymore by pressing the power switch. Reboot from the console works. If I remove or rename the new rc.local powering of the slug works fine again.

January 08, 2007, at 01:26 PM by Anguel Stankov -- Spindown problems with Unslung 6.8
Added lines 165-166:

Note by Anguel Stankov: The rc.bootbin and rc.local scripts given above seem to make my WD MyBook? 500GB spin down with Unslung 5.5 only. I cannot make spindown work with Unslung 6.8 or original Linksys firmware v23RA5. This spin-down problem is also reported in the "nslu2-general" newsgroup.

November 24, 2006, at 02:47 PM by Peter November 2006 -- Default Spindown 1 h
Added lines 168-171:

Default Spindown 1 hour Just checked my new One-Touch III - factory default appears to be 1hr to spindown. So it's highly likely that there is no need to mess with the Maxtor at all, all that is needed is to eliminate dynamic access to the disk as shown in scripts above.

October 22, 2006, at 01:48 PM by matthias --
Added lines 6-8:

The Maxtor utility v4.0.4.0 discovers my already formated OneTouch III without any problem. Setting the spindown time via energy options works as expected.

August 08, 2006, at 07:25 PM by Frank Heepmann -- just deleted some unnecessary spaces in rc.bootbin script for better copy&paste
Changed lines 134-141 from:

/bin/echo "Creating ramfs for /dev:" /bin/mount -t ramfs ramfs /mnt/tmpmnt /bin/cp -rp /dev/* /mnt/tmpmnt/ /bin/mkdir -p /dev.state /bin/mount -o bind /dev /dev.state /bin/mount -o bind /mnt/tmpmnt /dev /bin/umount /mnt/tmpmnt /bin/echo "Creating ramfs for /var:"

to:

/bin/echo "Creating ramfs for /dev:" /bin/mount -t ramfs ramfs /mnt/tmpmnt /bin/cp -rp /dev/* /mnt/tmpmnt/ /bin/mkdir -p /dev.state /bin/mount -o bind /dev /dev.state /bin/mount -o bind /mnt/tmpmnt /dev /bin/umount /mnt/tmpmnt /bin/echo "Creating ramfs for /var:"

Changed lines 143-148 from:

/bin/cp -rp /var/* /mnt/tmpmnt/ /bin/mkdir -p /var.state /bin/mount -o bind /var /var.state /bin/mount -o bind /mnt/tmpmnt /var /bin/umount /mnt/tmpmnt

to:

/bin/cp -rp /var/* /mnt/tmpmnt/ /bin/mkdir -p /var.state /bin/mount -o bind /var /var.state /bin/mount -o bind /mnt/tmpmnt /var /bin/umount /mnt/tmpmnt

Changed line 150 from:

/bin/killall syslogd

to:

/bin/killall syslogd

July 30, 2006, at 08:32 AM by RobHam -- minor update to noatime and linksys clock fix sections
Changed lines 92-93 from:

Using a unix style text editor, copy the following script section into a new file called rc.local, you need to locate this file in the /unslung/ folder. Remember to chmod the file with permissions 755, and while you are at it, it is worth checking you've typed it in correctly :-

to:

Script to re-mount your discs with noatime. Using a unix style text editor, copy the following script section into a new file called rc.local, you need to locate this file in the /unslung/ folder. Remember to chmod the file with permissions 755, and while you are at it, it is worth checking you've typed it in correctly :-

July 30, 2006, at 08:24 AM by RobHam -- minor update to noatime and linksys clock fix sections
Added lines 84-89:

Note that the hourly linksys fix for the clock is easily changed to update only once per day at midnight by changing the relevant line in the /etc/crontab file to :-

0 0 * * * root /usr/sbin/hwclock -s &>/dev/null

Then re-boot your slug.

Changed lines 92-93 from:

Using a unix style text editor, copy the following script section into a new file called S00remount, you need to locate this file in the /opt/etc/init.d/ folder usually used for startup scripts for packages. Remember to chmod the file with permissions 755, and while you are at it, it is worth checking you've typed it in correctly :-p

to:

Using a unix style text editor, copy the following script section into a new file called rc.local, you need to locate this file in the /unslung/ folder. Remember to chmod the file with permissions 755, and while you are at it, it is worth checking you've typed it in correctly :-

Changed line 98 from:
  1. /opt/etc/init.d/S00remount
to:
  1. /unslung/rc.local
Added line 110:
  1. return 1
Changed lines 115-120 from:

This is very similar to what happens in /etc/rc.d/rc.1 when /.ext3flash exists. The main difference being that the swap is left as is. Re-boot your slug for the script to run. Then check that /dev/sda1 has the option noatime set, by typing mount. Putting it in the package startup scripts directory is probably not the best place for it, but there is no obvious /unslung/rc script to put it in.

JamesCC October 2005

Regarding a suitable /unslung/rc script - /unslung/rc.local is commonly used to mount fat32 partitions so would also make a good place for this script section. Note that /unslung/rc scripts normally needs to end with return 1 to function correctly.

to:

This is very similar to what happens in /etc/rc.d/rc.1 when /.ext3flash exists. The main difference being that the swap is left as is. Re-boot your slug for the script to run. Then check that /dev/sda1 has the option noatime set, by typing mount.

JamesCC October 2005 - (modified for rc.local unslung diversion script)

Changed line 164 from:

I had no problem setting the spindown time with sdparm, see http://www.joachim-breitner.de/blog/archives/130-Silencing-my-Slug.html

to:

I had no problem setting the spindown time with sdparm, see http://www.joachim-breitner.de/blog/archives/130-Silencing-my-Slug.html

April 26, 2006, at 02:16 PM by emm_is -- added organising links
Changed lines 4-5 from:

But, if you formated your drive with the NSLU2, you can't chose your drive with that tool.

to:

But, if you formated your drive with the NSLU2, you can't chose your drive with that tool.

Even after you set the master discs spin-down the drive will not spin down because of regular accesses to /dev and /var. Instructions below describe how you can place /dev and /var on a ramdisc.

Added lines 84-85:

Added lines 114-115:

Added lines 153-155:

Do not forget you will also have to set 'noatime' for /dev/sda1, a script above describes how.

March 12, 2006, at 11:35 AM by nomeata -- sdparm works
Changed lines 145-149 from:

(:tableend:)

to:

(:tableend:)

The Non-Problem

I had no problem setting the spindown time with sdparm, see http://www.joachim-breitner.de/blog/archives/130-Silencing-my-Slug.html

January 20, 2006, at 01:38 PM by Andreas --
Added lines 110-145:

Better /unslung/rc.bootbin with /dev and /var ramdisk and working syslog

(Andreas, Jan 2006)

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#!/bin/sh
# /unslung/rc.bootbin
# Tested with unslung firmware 5.5
# create ramdisk for /var and /dev

/bin/echo "Creating ramfs for /dev:"                                          
/bin/mount -t ramfs ramfs /mnt/tmpmnt                                         
/bin/cp -rp /dev/* /mnt/tmpmnt/                                               
/bin/mkdir -p /dev.state                                                      
/bin/mount -o bind /dev /dev.state                                            
/bin/mount -o bind /mnt/tmpmnt /dev                                           
/bin/umount /mnt/tmpmnt              
/bin/echo "Creating ramfs for /var:" 
/bin/mount -t ramfs ramfs /mnt/tmpmnt -o maxsize=256
/bin/cp -rp /var/* /mnt/tmpmnt/                     
/bin/mkdir -p /var.state                            
/bin/mount -o bind /var /var.state                  
/bin/mount -o bind /mnt/tmpmnt /var                 
/bin/umount /mnt/tmpmnt                             

# restart logging daemons
/bin/killall syslogd                                
/bin/killall klogd

# Return and continue execution of system rc.
return 1
# [EOF]

(:tableend:)

October 02, 2005, at 10:40 PM by RobHam -- Note added to bottom, regarding suitable rc script
Changed lines 74-75 from:

The above worked for me, with 5.5 Beta, but only when I had repeated the ramfs process for the /dev dir. Repeat the main section of script and replace var with dev. I reduced the maxsize down to 126 for the /dev ram disk. After inactivity the disk spun down in time with the setting entered using the Maxtor utility.

to:

The above worked for me, with 5.5 Beta, but only when I had repeated the ramfs process for the /dev dir. Repeat the main section of script and replace var with dev. I reduced the maxsize down to 128 for the /dev ram disk. After inactivity the disk spun down in time with the setting entered using the Maxtor utility.

Changed line 95 from:

/bin/echo "Remounting /dev/sda1 with noatime"

to:

/bin/echo "Remounting /dev/sda1 with noatime"

Added lines 107-109:

Regarding a suitable /unslung/rc script - /unslung/rc.local is commonly used to mount fat32 partitions so would also make a good place for this script section. Note that /unslung/rc scripts normally needs to end with return 1 to function correctly.

October 02, 2005, at 06:58 PM by JamesCC --
Changed lines 80-83 from:

Unslung 5.5. I also needed the ramfs process for the /dev dir. It is also worth pointing out that you need to mount the HDD /dev/sda1 with noatime. This prevents the writes (modification to access time) during reads (common issue is when a crontab is being read by crond - every hour if using the linksys fix for the clock). The reads are cached, but the writes get done immediately taking the drive out of standby.

Using a unix style text editor, copy the following script section into a new file called S00remount, you need to locate this file in the /opt/etc/init.d/ folder usually used for startup scripts for packages. Remember to chmod the file with permissions 755, and while you are at it, it is worth checking you you've typed it in correctly :-p

to:

Unslung 5.5. I also needed the ramfs process for the /dev dir. It is also worth pointing out that you need to mount the HDD /dev/sda1 with noatime. This prevents writes (modification to access time) during reads (common issue is when a crontab is being read by crond - every hour if using the linksys fix for the clock). The reads can be cached (and so the disk is not read), but the writes (for the access time) get done immediately taking the drive out of standby.

Using a unix style text editor, copy the following script section into a new file called S00remount, you need to locate this file in the /opt/etc/init.d/ folder usually used for startup scripts for packages. Remember to chmod the file with permissions 755, and while you are at it, it is worth checking you've typed it in correctly :-p

October 02, 2005, at 06:51 PM by JamesCC -- Using ext2fsd - my hassles
Added lines 26-34:

JamesCC October 2005 - This seemed the safest option, however I had considerable hassles with this, but got there in the end! Here are some suggestions...

  • Make sure you have the latest Maxtor drivers/utility (go to http://www.maxtor.com and click on software downloads).
  • I have a old Maxtor OneTouch? drive and the original Maxtor driver really messed up my USB devices. This is how I fixed it (ONLY DO IF NECESSARY. NO GUARANTEES WITH THE FOLLOWING. TRY AT YOUR OWN RISK). Under WinXP? (SP2?) I deleted all the items under "Universal Serial Bus Controllers" in the device manager (a little trial and error is necessary as they need to deleted in the right order). OBVIOUSLY DON'T DO THIS IF YOU HAVE A USB KEYBOARD, as the USB devices will stop working (mouse can be an issue too, but you can usually get around it by using the keyboard)!!!! Upon rebooting XP will reinstall the USB controllers, and the necessary drivers for the USB items connected (usually without you needing the disks). Everything worked great after that.
  • Install ext2fsd as mentioned above (I got an error message when installing, but that didn't seem to matter). Disable writing (it is not reliable and could mess up your disk).
  • Shutdown and start the PC with the NSLU2 drive attached (and powered!) - i.e. don't connect after windows starts.
  • experiment with ext2fsd mount command in a dos box (you need to guess the magic disk number) - just start from 0 and work up you'll find the ext drive eventually (you'll notice it can mount NTFS, FAT as well as EXT2?/3). You do not need to unmount a drive letter before trying another mount command (in fact it is a bit bugging in that it won't let you unmount unless you have successfully mounted). Check the mounted drive when you are successful (especially try a sub directory) - the ext2fsd driver seems a little sensitive, so if necessary give your PC a reboot, and try again.
  • Once your mounted drive looks good. Run the Maxtor OneTouch utility if you want to set the Spin Down Time.
October 02, 2005, at 06:09 PM by JamesCC -- Clarifying that you need noatime for spin down on maxstor.
Changed lines 69-70 from:
to:

Another Additional Note on the above:

Unslung 5.5. I also needed the ramfs process for the /dev dir. It is also worth pointing out that you need to mount the HDD /dev/sda1 with noatime. This prevents the writes (modification to access time) during reads (common issue is when a crontab is being read by crond - every hour if using the linksys fix for the clock). The reads are cached, but the writes get done immediately taking the drive out of standby.

Using a unix style text editor, copy the following script section into a new file called S00remount, you need to locate this file in the /opt/etc/init.d/ folder usually used for startup scripts for packages. Remember to chmod the file with permissions 755, and while you are at it, it is worth checking you you've typed it in correctly :-p

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#!/bin/sh
# /opt/etc/init.d/S00remount
# A diversion script to remount the drive(s) without access
# times being recorded (the update of access times can
# prevent drives sleeping)

# Usually it is enough just to do /sda1 as this is the usually
# the one that holds the system.
/bin/echo  "Remounting /dev/sda1 with noatime"
/bin/mount -o remount,rw,noatime /dev/sda1
#/bin/echo  "Remounting /dev/sda2 with noatime"
#/bin/mount -o remount,rw,noatime /dev/sda2

# EOF - include this line

(:tableend:)

This is very similar to what happens in /etc/rc.d/rc.1 when /.ext3flash exists. The main difference being that the swap is left as is. Re-boot your slug for the script to run. Then check that /dev/sda1 has the option noatime set, by typing mount. Putting it in the package startup scripts directory is probably not the best place for it, but there is no obvious /unslung/rc script to put it in.

JamesCC October 2005

August 22, 2005, at 04:45 PM by Nigel Gerdes -- Comment on solution when using Unslung 5.5 Beta
Changed lines 63-64 from:

to:

Additional Note on the above:

The above worked for me, with 5.5 Beta, but only when I had repeated the ramfs process for the /dev dir. Repeat the main section of script and replace var with dev. I reduced the maxsize down to 126 for the /dev ram disk. After inactivity the disk spun down in time with the setting entered using the Maxtor utility.

Nigel Gerdes Aug 2005

June 26, 2005, at 07:23 PM by RobHam -- cat /proc/mounts ram disk check added
Changed lines 59-60 from:

Use the 'mount' command to check that /var is running in a ram disk. With my NSLU2 and Maxtor drive, the drive does seem to power down for extended periods.

to:

Use cat /proc/mounts to check that /var is running in a ram disk.

June 22, 2005, at 10:54 PM by RobHam -- Removed ambiguous reference to /mnt/sda1/unslung
Changed lines 32-33 from:

Using a unix style text editor, copy the following script section into a new file called rc.bootbin, you need to locate this file in the /unslung folder located on the disk drive and not the one located in the flash ram. To locate the correct folder does depend if you are running off of the hd rootfs or not. The best way to guarantee the correct unslung folder is to follow /mnt/sda1/unslung (note - may be sdb1 or another folder depending upon partition and USB socket used for rootfs).

to:

Using a unix style text editor, copy the following script section into a new file called rc.bootbin, you need to locate this file in the /unslung folder located on the disk drive rootfs.

Changed lines 59-62 from:

Interestingly this ram disk does not show up when using the df command, but does show when using the mount command. The slug disk drive does seem to power down for extended periods so the above script seem to work for most configurations.

to:

Use the 'mount' command to check that /var is running in a ram disk. With my NSLU2 and Maxtor drive, the drive does seem to power down for extended periods.

June 16, 2005, at 10:20 PM by RobHam -- Minor amendment to Ramdisk instruction
Changed lines 26-39 from:

Still wont spin down? Here is another possible solution

With unslung firmwares 4.x or 5.x, the complete root filing system is located on the disk. The One Touch drive will never spin down because linux will regularly access log files located in /var. One possible fix for this is to move the /var folder tree to a ramdisk (or possibly to a flash ram stick).

Instructions to create and move /var to a ramdisk -

Copy the following script section into a new file called rc.bootbin, you need to locate this file in the /unslung folder located on the disk drive and not the one located in the flash ram. To locate the correct folder does depend if you are running off of the hd rootfs or not. The best way to guarantee the correct unslung folder is to follow /mnt/sda1/unslung (note - may be sdb1 or another folder depending upon USB socket used for disk drive). chmod the file with permissions 755.

to:

A solution when using unslung firmware 4.x or 5.x

With unslung firmwares 4.x or 5.x, the complete root filing system is located on a disk partition. The One Touch drive will never spin down because linux will regularly access log files located in /var. One possible fix for this is to move the /var folder tree to a ramdisk (or possibly to a flash ram stick).

Instructions to create and move /var to a ramdisk -

Using a unix style text editor, copy the following script section into a new file called rc.bootbin, you need to locate this file in the /unslung folder located on the disk drive and not the one located in the flash ram. To locate the correct folder does depend if you are running off of the hd rootfs or not. The best way to guarantee the correct unslung folder is to follow /mnt/sda1/unslung (note - may be sdb1 or another folder depending upon partition and USB socket used for rootfs). chmod the file with permissions 755.

Changed lines 62-63 from:

seem to power down for extended periods so does seem to be working.

to:

seem to power down for extended periods so the above script seem to work for most configurations.

June 16, 2005, at 05:59 PM by RobHam -- Minor amendment to Ramdisk instruction
Changed lines 26-32 from:

Still wont spin down? Here is the solution

Robert Hammond noticed that if the One Touch drive is the one supporting Unslung that it will never spin down because linux is always accessing the log files in /var. He developed a fix for this by moving /var to a ramdisk so that the drive would be accessed. Then the One Touch drive does to sleep properly.

Instructions-

Copy the following script section into a new file called rc.sysinit,

to:

Still wont spin down? Here is another possible solution

With unslung firmwares 4.x or 5.x, the complete root filing system is located on the disk. The One Touch drive will never spin down because linux will regularly access log files located in /var. One possible fix for this is to move the /var folder tree to a ramdisk (or possibly to a flash ram stick).

Instructions to create and move /var to a ramdisk -

Copy the following script section into a new file called rc.bootbin,

Changed lines 37-38 from:

/mnt/sda1/unslung (note - may be sda2 depending upon USB socket used for disk drive).

to:

/mnt/sda1/unslung (note - may be sdb1 or another folder depending upon USB socket used for disk drive).

Added lines 40-69:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#!/bin/sh
# /unslung/rc.bootbin
# Tested with unslung firmware 4.20 and 5.5
# Script section to create ramdisk for /var

/bin/echo "Creating ramfs for /var:"
/bin/mount -t ramfs ramfs /mnt/tmpmnt -o maxsize=256
/bin/cp -rp /var/* /mnt/tmpmnt/
/bin/mkdir -p /var.state
/bin/mount -o bind /var /var.state
/bin/mount -o bind /mnt/tmpmnt /var
/bin/umount /mnt/tmpmnt

# Return and continue execution of system rc.
return 1
# [EOF]

(:tableend:)

Re-boot your slug

Interestingly this ram disk does not show up when using the df command, but does show when using the mount command. The slug disk drive does seem to power down for extended periods so does seem to be working.

RobHam June 2005

Changed lines 71-101 from:

#!/bin/sh
# Intended for unslung firmware 4.x only
# Script section to create ramdisk for /var
mkdir -p /var/lock/samba >/dev/null
/bin/echo "Creating ramfs for /var:"
/bin/mount -t ramfs ramfs /mnt/tmpmnt -o maxsize=256
/bin/cp -rp /var/* /mnt/tmpmnt/
/bin/mkdir -p /var.state
/bin/mount -o bind /var /var.state
/bin/mount -o bind /mnt/tmpmnt /var
/bin/umount /mnt/tmpmnt
/bin/killall syslogd
/bin/killall klogd
# Return and continue execution of system rc.sysinit
return 1
# [EOF]


Re-boot your slug

Interestingly this ram disk does not show up when using the df command, but does show when using the mount command. The slug disk drive does seem to power down for extended periods so does seem to be working.

-- Robert Hammond PGP:0x154144DA

to:
June 16, 2005, at 01:36 PM by Maurice --
Changed lines 28-29 from:

Robert Hammond noticed that if the One Touch drive is the one supporting Unslung that it will never spin down because linux is always accessing the log files in /var. He developed a fix for this by moving /var to a ramdisk so that the drive would be accessed. Then the One Touch drive does to sleep properly.

to:

Robert Hammond noticed that if the One Touch drive is the one supporting Unslung that it will never spin down because linux is always accessing the log files in /var. He developed a fix for this by moving /var to a ramdisk so that the drive would be accessed. Then the One Touch drive does to sleep properly.

Changed line 41 from:
to:

Changed line 60 from:
to:

June 16, 2005, at 01:34 PM by Maurice -- Still wont spin down? Here is the solution
Added lines 25-72:

Still wont spin down? Here is the solution

Robert Hammond noticed that if the One Touch drive is the one supporting Unslung that it will never spin down because linux is always accessing the log files in /var. He developed a fix for this by moving /var to a ramdisk so that the drive would be accessed. Then the One Touch drive does to sleep properly.

Instructions-

Copy the following script section into a new file called rc.sysinit, you need to locate this file in the /unslung folder located on the disk drive and not the one located in the flash ram. To locate the correct folder does depend if you are running off of the hd rootfs or not. The best way to guarantee the correct unslung folder is to follow /mnt/sda1/unslung (note - may be sda2 depending upon USB socket used for disk drive). chmod the file with permissions 755.

#!/bin/sh
# Intended for unslung firmware 4.x only
# Script section to create ramdisk for /var
mkdir -p /var/lock/samba >/dev/null
/bin/echo "Creating ramfs for /var:"
/bin/mount -t ramfs ramfs /mnt/tmpmnt -o maxsize=256
/bin/cp -rp /var/* /mnt/tmpmnt/
/bin/mkdir -p /var.state
/bin/mount -o bind /var /var.state
/bin/mount -o bind /mnt/tmpmnt /var
/bin/umount /mnt/tmpmnt
/bin/killall syslogd
/bin/killall klogd
# Return and continue execution of system rc.sysinit
return 1
# [EOF]

Re-boot your slug

Interestingly this ram disk does not show up when using the df command, but does show when using the mount command. The slug disk drive does seem to power down for extended periods so does seem to be working.

-- Robert Hammond PGP:0x154144DA

June 11, 2005, at 08:25 PM by tman --
Changed lines 10-13 from:

I suggest doing this before storing your only copy of your Britney CDs? because something could go wrong; Windows may decide to write disk signatures and other useful information all over your most vital data. Although this has been tested and is reasonably safe, there are no guarantees. Backup your important data.

If (like me) you don't run Linux at home then download Knoppix, a LiveCD? distribution. Burn a CD with it on, then boot from the CD and you'll have access to Linux for the period of time you need. Remove the CD, and you reboot back to Windows.

to:

I suggest doing this before storing your only copy of your Britney CDs because something could go wrong; Windows may decide to write disk signatures and other useful information all over your most vital data. Although this has been tested and is reasonably safe, there are no guarantees. Backup your important data.

If (like me) you don't run Linux at home then download Knoppix, a LiveCD distribution. Burn a CD with it on, then boot from the CD and you'll have access to Linux for the period of time you need. Remove the CD, and you reboot back to Windows.

Changed lines 16-17 from:

Attach your disk to a XP box and run Partition Magic. Create a small (I did 15Meg) NTFS partition. Now XP recognize the disk and you can change the spindown time.

to:

Attach your disk to a XP box and run PartitionMagic. Create a small (I did 15MB) NTFS partition. Now XP will recognize the disk and you can change the spindown time.

Changed lines 20-21 from:

Instead of changing the conf (sda1) or data (sda2) partitions, change the swap partition (sda3). This way if windows messes it up, you haven't lost any data. Just make a note of the partition type before you make the change and set it back when you are done.

to:

Instead of changing the conf (sda1) or data (sda2) partitions, change the swap partition (sda3). This way if Windows messes it up, you haven't lost any data. Just make a note of the partition type before you make the change and set it back when you are done.

Changed line 24 from:

Attach the (ext3 formatted) disk to your Windows PC, install EXT2FSD? (from Sourceforge), and use the included MOUNT.EXE to mount the drive. It will then have a drive letter, and you'll be able to read its contents. Then run the Maxtor Onetouch II utility and set the spin down time as you wish. Then put the drive back on the NSLU2. Having EXT2FSD? installed will allow you to read the disk directly on your PC whenever necessary!

to:

Attach the (ext3 formatted) disk to your Windows PC, install Ext2fsd, and use the included MOUNT.EXE to mount the drive. It will then have a drive letter, and you'll be able to read its contents. Then run the Maxtor OneTouch II utility and set the spin down time as you wish. Then put the drive back on the NSLU2. Having Ext2fsd installed will allow you to read the disk directly on your PC whenever necessary!

June 11, 2005, at 03:57 PM by Gert Van Heghe -- Install EXT2FSD
Changed lines 20-24 from:

Instead of changing the conf (sda1) or data (sda2) partitions, change the swap partition (sda3). This way if windows messes it up, you haven't lost any data. Just make a note of the partition type before you make the change and set it back when you are done.

to:

Instead of changing the conf (sda1) or data (sda2) partitions, change the swap partition (sda3). This way if windows messes it up, you haven't lost any data. Just make a note of the partition type before you make the change and set it back when you are done.

Still another solution

Attach the (ext3 formatted) disk to your Windows PC, install EXT2FSD? (from Sourceforge), and use the included MOUNT.EXE to mount the drive. It will then have a drive letter, and you'll be able to read its contents. Then run the Maxtor Onetouch II utility and set the spin down time as you wish. Then put the drive back on the NSLU2. Having EXT2FSD? installed will allow you to read the disk directly on your PC whenever necessary!

April 04, 2005, at 07:24 PM by ChezDude2010 --
Changed line 14 from:

An other solution

to:

Another solution

Added lines 17-20:

One Modification to "The Solution"

Instead of changing the conf (sda1) or data (sda2) partitions, change the swap partition (sda3). This way if windows messes it up, you haven't lost any data. Just make a note of the partition type before you make the change and set it back when you are done.

March 18, 2005, at 10:24 PM by teobald --
Changed line 16 from:

Attach your disk to a XP box and run Partition Magic. Create a small (I did 15Meg) NTFS partition. Now WP recognize the disk and you can change the spindown time.

to:

Attach your disk to a XP box and run Partition Magic. Create a small (I did 15Meg) NTFS partition. Now XP recognize the disk and you can change the spindown time.

March 18, 2005, at 10:23 PM by teobald --
Changed lines 12-16 from:

If (like me) you don't run Linux at home then download http://www.knoppix.net/ Knoppix, a LiveCD? distribution. Burn a CD with it on, then boot from the CD and you'll have access to Linux for the period of time you need. Remove the CD, and you reboot back to Windows.

to:

If (like me) you don't run Linux at home then download http://www.knoppix.net/ Knoppix, a LiveCD? distribution. Burn a CD with it on, then boot from the CD and you'll have access to Linux for the period of time you need. Remove the CD, and you reboot back to Windows.

An other solution

Attach your disk to a XP box and run Partition Magic. Create a small (I did 15Meg) NTFS partition. Now WP recognize the disk and you can change the spindown time.

January 16, 2005, at 01:04 PM by uSURPER --
Changed line 8 from:

Attach your disk to a Linux box and use fdisk to set the partition type to Windows (I set the first partiton to 0x0C). Now attach your drive to Windows-box or reboot to Windows. The partition will now be assigned a drive letter (like H:) and you can select the drive from within the Maxtor utility and change the spin-down timeout. Afterwards restore the partition type back to Linux.

to:

Attach your disk to a Linux box and use fdisk to set the partition type to Windows (I set the first partiton to 0x0C). Now attach your drive to Windows-box or reboot to Windows. The partition will now automatically be assigned a drive letter (like H:) and you can select the drive from within the Maxtor utility and change the spin-down timeout. Afterwards back into Linux to restore the partition type back to a type the NSLU2 supports (probaby 0x83).

January 08, 2005, at 06:17 PM by tman --
Changed line 3 from:

If you have a Maxtor OneTouch? and want to set the spin-down on idle timeout, you can use a tool provided by Maxtor on the CD that comes with the drive. This tool runs only on Windows so ideally do this before connecting it for the first time to your NSLU2.

to:

If you have a Maxtor OneTouch and want to set the spin-down on idle timeout, you can use a tool provided by Maxtor on the CD that comes with the drive. This tool runs only on Windows so ideally do this before connecting it for the first time to your NSLU2.

Deleted line 6:

Attach your disk to a Linux box and use fdisk to set the partition-type to Windows (I set the first partiton to 0x0C). Now attach your drive to Windows-box or reboot to Windows. The Partition will now get a Letter (like H:) and you can chose the drive with the Maxtor Tool and do your changes. Afterwards I restored the Partitiontype back to Linux.

Changed lines 8-10 from:

I suggest doing this before storing your only copy of your Britney cds because something could go wrong; Windows may decide to write disk signatures and other useful information all over your most vital data. Although this has been tested and is reasonably safe, there are no guarantees. Backup your important data.

to:

Attach your disk to a Linux box and use fdisk to set the partition type to Windows (I set the first partiton to 0x0C). Now attach your drive to Windows-box or reboot to Windows. The partition will now be assigned a drive letter (like H:) and you can select the drive from within the Maxtor utility and change the spin-down timeout. Afterwards restore the partition type back to Linux.

I suggest doing this before storing your only copy of your Britney CDs? because something could go wrong; Windows may decide to write disk signatures and other useful information all over your most vital data. Although this has been tested and is reasonably safe, there are no guarantees. Backup your important data.

January 08, 2005, at 06:10 PM by uSURPER --
Changed line 3 from:

If you have a Maxtor OneTouch? and want to set the spin-down on idle timeout, you can use a tool provided by Maxtor on the CD that comes with the drive. This tool runs only on Windows.

to:

If you have a Maxtor OneTouch? and want to set the spin-down on idle timeout, you can use a tool provided by Maxtor on the CD that comes with the drive. This tool runs only on Windows so ideally do this before connecting it for the first time to your NSLU2.

Changed line 9 from:

I suggest doing this before storing your only copy of your Britney cds because something could go wrong; Windows may decide to write disk signatures and other useful information all over your most vital data. Although this has been tested and is reasonably safe, there are no guarantees.

to:

I suggest doing this before storing your only copy of your Britney cds because something could go wrong; Windows may decide to write disk signatures and other useful information all over your most vital data. Although this has been tested and is reasonably safe, there are no guarantees. Backup your important data.

January 06, 2005, at 10:22 AM by uSURPER --
Added lines 8-11:

I suggest doing this before storing your only copy of your Britney cds because something could go wrong; Windows may decide to write disk signatures and other useful information all over your most vital data. Although this has been tested and is reasonably safe, there are no guarantees.

If (like me) you don't run Linux at home then download http://www.knoppix.net/ Knoppix, a LiveCD? distribution. Burn a CD with it on, then boot from the CD and you'll have access to Linux for the period of time you need. Remove the CD, and you reboot back to Windows.

December 01, 2004, at 06:55 PM by smartin --
Changed lines 1-8 from:
to:

The Problem

If you have a Maxtor OneTouch? and want to set the spin-down on idle timeout, you can use a tool provided by Maxtor on the CD that comes with the drive. This tool runs only on Windows. But, if you formated your drive with the NSLU2, you can't chose your drive with that tool.

The Solution

Attach your disk to a Linux box and use fdisk to set the partition-type to Windows (I set the first partiton to 0x0C). Now attach your drive to Windows-box or reboot to Windows. The Partition will now get a Letter (like H:) and you can chose the drive with the Maxtor Tool and do your changes. Afterwards I restored the Partitiontype back to Linux.