On 11/21/2016 09:20 AM, Matthew Miller wrote:
On Mon, Nov 21, 2016 at 08:21:01AM -0500, Robert Moskowitz wrote:
I have a 1TB drive that is getting I/O errors enough that while I
What is a good way to move the OS and all the data? I used
Clonezilla some many years ago, but that does not seem to be the way
to go when there are bad sections on the source drive?
Not helpful _now_, but consider making sure you have backups once you
start using the new system. Then, next time this happens, forget
worrying about transferring from a failing drive and just restore your
backup.
The data is backed up. In fact it was one of the rsync cron tasks that
wedged the system while I was gone. The I/O did not seem to be in the
data, but perhaps some temp or other storage needed.
The challenge is the OS and software configs. Actually the system is a
ClearOS file server and there are all those config information scattered
around by ClearOS. I back up the whole /var/flexshare, but there is a
lot more to their setup and no 'clear' directions from them. Building a
new server from scratch would be painful. Last year (when I had time
while building up my contract work) I looked into building my own Samba
4 server, but dropped it. Anyway, I have yet to find directions on a
good way to maintain a running backup of the OS for a straight rebuild.
If this is a desktop system with room for it, consider buying *two*
drives and mirroring them. That's not a backup (since errors and
mistakes get propagated instantly, and because it's in the same
physical location), but makes situations like this rare (at least, if
you replace as soon as you start seeing errors instead of waiting for a
double failure).
I could never figure out what mirroring failing sectors meant.
Bob
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
