Bill Hance on 30 Apr 2008 05:45:30 -0700 |
I would only worry about working it to death if it was getting read or write errors. It's spinning at 7-10k rpm all the time anyway. I would copy everything to another server ASAP. If something is irreplaceable, I would copy that off first, then some sort of rsync or copy *.* to get it all. > I have a 200 GB IDE drive that recently stopped being detected by the BIOS. > After I did a dist-upgrade and was forced to reboot, the drive reappeared. The drive had not given me problems prior to disappearing. I still don't trust it and am ordering a replacement. > > Once the replacement arrives I want to copy the contents, mostly audio files, > to the new drive, but don't want to do it in a way that will tax the drive and make it fail during the copy. > > My first thought was rsync, but I am concerned about the effect this (transferring ~180 GB at once) may have on the precarious drive. > > Another thought was to just copy a little at a time, giving it a chance to rest in between, but am reminded that sometimes turning things on and off causes more wear than being left on. > > What are the best practices in this situation? > ___________________________________________________________________________ Philadelphia Linux Users Group -- > http://www.phillylinux.org > Announcements - > http://lists.phillylinux.org/mailman/listinfo/plug-announce > General Discussion -- > http://lists.phillylinux.org/mailman/listinfo/plug > ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|