SCOUG-HELP Mailing List Archives
Return to [ 29 |
August |
2005 ]
>> Next Message >>
Content Type: text/plain
Hi Jordan
Peter is correct in recommending a backup BEFORE cloning !!!
I just lost 2 HDD's with cloning from one to another !!
Stacked at 11.8% and many more hours the cloning process showed no further
activities and I aborted ...
... assuming that I can repeat again from the source to another target:
Unfortunately both HDD's (the source too) had gotten: Boot Sector Read Erro=
r !
Now, all the data gone and lost ...
... only a very expensive hard recovery may bring it back
but chances seem to be very very little ;-(
This info to you to be forewarned and surely make your backup !!!
Good luck & cheers, svob=EF
Quoting J R FOX :
> --- Peter Skye wrote:
>
>> I'm not trying to tell you how to do your job, but
>> resizing a partition
>> can be a high blood pressure experience if you get
>> any kind of failure
>> while it's running. Aren't you better off by
>> copying/cloning the
>> partition, deleting the old partition and recreating
>> it in the desired
>> size, and then XCOPYing the files from the
>> copy/clone to the new
>> partition?
>
> No, not really Peter. I don't think you're following
> what I planned to do. Nothing will happen to the
> source drive -- it will be kept just the way it is
> until I'm certain that it is no longer needed, perhaps
> much longer than that. All operations will be
> performed on the freshly cloned larger drive. This is
> akin to working on a copy of a file, rather than on
> the original, just on a much larger scale. If the
> copy gets mucked up, you still have the original, and
> can try again *on another copy*, probably in a
> different way. (Hopefully any failure is clear in the
> early going, so not too much time or effort will have
> been invested. In this case, that means booting each
> Target boot partition, and running a representative
> selection of app.s. Also, DFSEE has gotten quite good
> about reporting things not right with the drive
> setup.) And I do use a UPS.
>
>
> Jordan
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "postmaster@scoug.com".
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>
>
>
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
>> Next Message >>
Return to [ 29 |
August |
2005 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|