My new Crucial MX500 1TB 3D NAND SDD 2.5" drive should arrive
by Thursday.

In the past, I have generally either cloned a same-size hdd to
another hdd or used images.

But what is the procedure y'all would recommend for cloning an
HDD that has two partions (C and H) to a larger SSD?

The original system is XP.

I'm reading that perhaps Macrium Reflect 8 could do it.

Another product called AOMEI claims to do the same, but
expanding a partition requires a pay version of the program.
But it sounds to be the easiest to use.

But there are caveats in both wrt to "bootable" partitions.

What experiences have y'all had doing this? And what tools
have you used for cloning an XP OS?

I'm somewhat familiar with some linux rescue disk software that
I could probably use for prepping the destination SSD prior to
the cloning. But I would rather like to stick to one tool that
can do all necessary steps.


--- OpenXP 5.0.51
* Origin: (618:500/23.10)

My new Crucial MX500 1TB 3D NAND SDD 2.5" drive should arrive
by Thursday.

Ooops. I meant that my SATA/USB cable will arrive on Thursday.
Then, I'll be able to begin the cloning process.


--- OpenXP 5.0.51
* Origin: (618:500/23.10)

August Abolins wrote to All <=-

But what is the procedure y'all would recommend for cloning an
HDD that has two partions (C and H) to a larger SSD?

Clonezilla.

-- Sean


... Only adults have difficulty with child-proof bottles.
--- MultiMail/Win
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

To: Sean Dennis
Re: Re: hdd to larger sdd
By: Sean Dennis to August Abolins on Sun Jan 08 2023 05:56 pm

From Newsgroup: Micronet.MIN_COMP

August Abolins wrote to All <=-

But what is the procedure y'all would recommend for cloning an
HDD that has two partions (C and H) to a larger SSD?

Clonezilla.

i tried that before and it just made bad images.
--- Synchronet 3.19b-Win32 NewsLink 1.113
* bbses.info - http://bbses.info - telnet://bbses.info
* Origin: Star Frontiers starfron.synchronetbbs.org (618:200/44)

But what is the procedure y'all would recommend for cloning an
HDD that has two partions (C and H) to a larger SSD?

Clonezilla.

I remember trying Clonezilla years ago. I found it not very
inuitive. Might be worth another look.

--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

Jas Hud wrote to Sean Dennis <=-

But what is the procedure y'all would recommend for cloning an
HDD that has two partions (C and H) to a larger SSD?

Clonezilla.

i tried that before and it just made bad images.

Well then, you did it wrong.



... He does the work of 3 Men...Moe, Larry & Curly
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24)

On 09 Jan 2023, August Abolins said the following...

I remember trying Clonezilla years ago. I found it not very
inuitive. Might be worth another look.

https://www.macrium.com/reflectfree

Reflect 8 Free
Backup and recovery software for home PCs

- Perfect for limited backups and cloning. Capable of basic backup scheduling. - Removable media imaging and cloning
- Create images of running Windows OS
- Restore non-booting systems
- Scalable and navigable log view interface
- Instantly boot backups in Hyper-V / Oracle VirtualBox VM
- Direct disk cloning
- WinPE 11 rescue media


Jay

... Electricity is really just organized lightning.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Northern Realms | bbs.nrbbs.net | 289-424-5180 (618:500/23)

To: August Abolins
Re: hdd to larger sdd
By: August Abolins to Sean Dennis on Mon Jan 09 2023 08:18 am

From Newsgroup: Micronet.MIN_COMP

But what is the procedure y'all would recommend for cloning an
HDD that has two partions (C and H) to a larger SSD?

Clonezilla.

I remember trying Clonezilla years ago. I found it not very
inuitive. Might be worth another look.

I had a real simple setup to clone. there wasn't really anything I could have done wrong. the image it made was bad.

this was over 5 years ago so maybe it's better. i think cloning partitians and resizing shit is too much work.

i'd rather backup files and install an OS fresh and make partitians then.
for me it's less tinkering and faster.
--- Synchronet 3.19b-Win32 NewsLink 1.113
* bbses.info - http://bbses.info - telnet://bbses.info
* Origin: Star Frontiers starfron.synchronetbbs.org (618:200/44)

Hello Warpslide!

https://www.macrium.com/reflectfree

Reflect 8 Free
Backup and recovery software for home PCs

[...]

Yup.. I'm leaning towards that one at this time. But I am going
to try my EaseUS that I have planted on my XP from some years
ago. It seems to be a "Trial" edition, but I think it's an
earlier "Trial" that is full featured. Will see.

--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

Re: Re: hdd to larger sdd
By: Sean Dennis to August Abolins on Sun Jan 08 2023 05:56 pm

August Abolins wrote to All <=-

But what is the procedure y'all would recommend for cloning an
HDD that has two partions (C and H) to a larger SSD?

Clonezilla.

-- Sean

... Only adults have difficulty with child-proof bottles.
--- MultiMail/Win
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

You beat me to it. BUrn the image to DVD and boot from it, then use the wizzard to clone the drives and you are done.

--
gopher://gopher.richardfalken.com/1/richardfalken
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24)

Jas Hud wrote to Sean Dennis <=-

i tried that before and it just made bad images.

That's operator error then. I've used it since it came out and it works
great both personally and professionally.

-- Sean
--- MMail/FreeBSD
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

August Abolins wrote to Sean Dennis <=-

I remember trying Clonezilla years ago. I found it not very
inuitive. Might be worth another look.

If you do use it, use the beginner mode. Another program you might try that
I recommend is Acronis True Image.

-- Sean
--- MMail/FreeBSD
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

Hello Arelor!

** On Monday 09.01.23 - 13:51, Arelor wrote to Sean Dennis:

Clonezilla.

You beat me to it. BUrn the image to DVD and boot from it, then use the wizzard to clone the drives and you are done.

But can it resize (enlarge) a bootable WinXP partition?


--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

To: Sean Dennis
Re: Re: hdd to larger sdd
By: Sean Dennis to Jas Hud on Mon Jan 09 2023 03:59 pm

From Newsgroup: Micronet.MIN_COMP

Jas Hud wrote to Sean Dennis <=-

i tried that before and it just made bad images.

That's operator error then. I've used it since it came out and it works great both personally and professionally.

-- Sean

what do you mean operator error? it's so easy there's nothing a person could screw up.
i used it years ago so maybe it improved.

most people who talk about having images are full of shit anyways and end up losing "everything in a crash."

--- Synchronet 3.19b-Win32 NewsLink 1.113
* bbses.info - http://bbses.info - telnet://bbses.info
* Origin: Star Frontiers starfron.synchronetbbs.org (618:200/44)

That's operator error then. I've used it since it came out
and it works great both personally and professionally.

what do you mean operator error? it's so easy there's nothing a person could screw up. i used it years ago so maybe it improved.

Right.. I don't know what could go wrong. Most of these
programs steer the user to the "next" necessary step (and
warnings if necessary), so that there is really no way to mess
up.

most people who talk about having images are full of shit anyways and end up losing "everything in a crash."

I've used DriveImageXML in the past to make images of my own
drives (most under 200GB at the time) and for other people.
Restorations to a new HDD went without a hitch when a suspect
HDD needed to be replaced. The images could even be searched
for a particular file if necessary - which I have done for
people's backups.

BUT.. now, I see that the same product has a "Disk to Disk"
option! So.. I might give that a go. All that is required is
to establish the destination partions in advance, and I can
probably do that with Windows Disk Management.

The SATA cable arrives tomorrow.
--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

Hello Arelor!

** On Wednesday 11.01.23 - 13:52, you wrote to me:

It's off to a bad start. :(

https://kolico.ca/tmp/ccc.jpg

Now what?

Well, the disk is having a bad day and nearing demise.

CHKDSK only reported a total of 14KB of "bad". I doubt that
it's an indication of growing doom.

I'd copy the disk over using dd_rescue (which skips bad
sectors) and then run some filesystem check utility on the
transfered filesystems in the destination drive. YOu may
find some file resided in a damaged sector and it is lost
or damaged, though.

I did it another way. I had a friend on Telegram who aided me
in using dd. Apparently, dd performs a byte-by-byte copy.

The end result maintained the "bad" areas, but at only 14KB,
I'm not worried about space implications on a 1TB SSD. :D

This is the whole story:

I tried Macrium, but I failed to understand where to look to
create the boot version. I did not realize that it was laying
under "Other Tasks". I also did NOT like how Macrium seemed to
hijack the pc by remaining resident in memory after killing its
processes manually; it simply kept reloading on its own! And
then there was the blasted "30 day Trial" bubble that kept
popping up on the task bar at random intervals.

Anyway, the whole Macrium process is now moot. I uninstalled it
when I noticed that it preferred to be always running at bootup
and in memory as a couple of processes and popping up with the
"30 day Trial.." bubble on my taskbar.

I did the migration with Clonezilla's Partclone thru the
default (novice) settings with the "auto expand partions
proportionally".

It failed to do my C partion after it encountered some bad
blocks, but it proceeded with H successfully.

Then.. with the help of a friend live on Telegram, I got help
with using the plain old "dd" command from the command line
boot to do a byte by byte copy of the C partition.

Then.. it was a simple matter to use the ntfsresize command to
get the original 35GB C partion to expand to the already
allocated 139GB space that was established when I selected the
"expand proportionally" option when I ran clonezilla.

Then, upon installing the SSD into the T60, Windows did NOT
originally report the C partition as the expanded size of
139GB, but another linux (debian) boot to the command line with
the Clonezilla program, and running ntfsresize -f -b /dev/sda1
FIXED the problem. That process automatically scheduled a
Windows chkdsk at the next reboot, and *then* I got the
official 139GB size of the C partition.

I have decided not to recover the few small sectors that are
still marked bad. The bad sectors aren't really real now that
I have migrated C onto the SSD.

In other research, I was reading that ntfstruncate is the
better tool to recover the marked bad sectors on my newly
migrated C partition on the SSD since there are no bad memory
locations on a new SSD. But chkdsk's report that they only
total up to 14KB, I'm not going to fuss over that.

This whole process was quite a journey.

I *don't* really notice a SIGNIFICANTLY faster boot time in XP,
but [1] maybe coming out of hibernate, the system loads a bit
faster, [2] the fan is running at a slower speed, and [3] there
is NO fan-speed test at boot up on my T60, [4] some web
browsing performance is a tad smoother and faster as the cache
previous content gets reused, I guess.


--../|ug




--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

This whole process was quite a journey.

I *don't* really notice a SIGNIFICANTLY faster boot time in XP,
but [1] maybe coming out of hibernate, the system loads a bit
faster, [2] the fan is running at a slower speed, and [3] there
is NO fan-speed test at boot up on my T60, [4] some web
browsing performance is a tad smoother and faster as the cache
previous content gets reused, I guess.

There was just one surprise that frustrated me for a little
while.

When I booted with the SSD in place, [1] many desktop icons
lost their associations. Consequently, [2] the same programs
could not find their installation locations.

The origianl HDD was divided as C and H. Since C was a piddly
35GB maximum size (and getting used up pretty fast) and H was
the remaining 200GB, I had gotten into the habit of installing
future programs on H over the years.

But the SSD process created an E partition in place of the H
partition.

I could simply go through all the shortcuts and change E to H,
and the associations. That worked on a couple of them. But I
still remained discouraged since I had numerous programs and
references to H in various places! Even my Tables in MS Access
had numerous references to H, and I was *not* interested in
reprogramming those in my various databases!

I was still discouraged when I learned that XP did not support
an ASSIGN command!

However.. after calming down, and having a look at the
partitions with XP's Disk Management tool, I realized that all
I had to do was right-click over the E partition, and it
provided the option to change the letter.

--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

==================================================================<

** Original area : "/MICRO/MIN_COMP"
** Original message from : August Abolins@618:250/1.9
** Original message to : Arelor
** Original date/time : 13 Jan 23, 08:09 >==================================================================<

Hello Arelor!

** On Wednesday 11.01.23 - 13:52, you wrote to me:

It's off to a bad start. :(

https://kolico.ca/tmp/ccc.jpg

Now what?

Well, the disk is having a bad day and nearing demise.

CHKDSK only reported a total of 14KB of "bad". I doubt that
it's an indication of growing doom.

I'd copy the disk over using dd_rescue (which skips bad
sectors) and then run some filesystem check utility on the
transfered filesystems in the destination drive. YOu may
find some file resided in a damaged sector and it is lost
or damaged, though.

I did it another way. I had a friend on Telegram who aided me
in using dd. Apparently, dd performs a byte-by-byte copy.

The end result maintained the "bad" areas, but at only 14KB,
I'm not worried about space implications on a 1TB SSD. :D

This is the whole story:

I tried Macrium, but I failed to understand where to look to
create the boot version. I did not realize that it was laying
under "Other Tasks". I also did NOT like how Macrium seemed to
hijack the pc by remaining resident in memory after killing its
processes manually; it simply kept reloading on its own! And
then there was the blasted "30 day Trial" bubble that kept
popping up on the task bar at random intervals.

Anyway, the whole Macrium process is now moot. I uninstalled it
when I noticed that it preferred to be always running at bootup
and in memory as a couple of processes and popping up with the
"30 day Trial.." bubble on my taskbar.

I did the migration with Clonezilla's Partclone thru the
default (novice) settings with the "auto expand partions
proportionally".

It failed to do my C partion after it encountered some bad
blocks, but it proceeded with H successfully.

Then.. with the help of a friend live on Telegram, I got help
with using the plain old "dd" command from the command line
boot to do a byte by byte copy of the C partition.

Then.. it was a simple matter to use the ntfsresize command to
get the original 35GB C partion to expand to the already
allocated 139GB space that was established when I selected the
"expand proportionally" option when I ran clonezilla.

Then, upon installing the SSD into the T60, Windows did NOT
originally report the C partition as the expanded size of
139GB, but another linux (debian) boot to the command line with
the Clonezilla program, and running ntfsresize -f -b /dev/sda1
FIXED the problem. That process automatically scheduled a
Windows chkdsk at the next reboot, and *then* I got the
official 139GB size of the C partition.

I have decided not to recover the few small sectors that are
still marked bad. The bad sectors aren't really real now that
I have migrated C onto the SSD.

In other research, I was reading that ntfstruncate is the
better tool to recover the marked bad sectors on my newly
migrated C partition on the SSD since there are no bad memory
locations on a new SSD. But chkdsk's report that they only
total up to 14KB, I'm not going to fuss over that.

This whole process was quite a journey.

I *don't* really notice a SIGNIFICANTLY faster boot time in XP,
but [1] maybe coming out of hibernate, the system loads a bit
faster, [2] the fan is running at a slower speed, and [3] there
is NO fan-speed test at boot up on my T60, [4] some web
browsing performance is a tad smoother and faster as the cache
previous content gets reused, I guess.


--../|ug




--
../|ug

-+- OpenXP 5.0.51
+ Origin: (} Pointy McPointface (618:250/1.9)

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

Hello Arelor!

I'd copy the disk over using dd_rescue (which skips bad sectors)..

dd_rescue is on the Clonezilla environment?

--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

Hello Arelor!

** On Wednesday 11.01.23 - 13:46, Arelor wrote to August Abolins:

I don t know, but in any case, what I would do is to copy everything over with Clonezilla, then boot from the new drive, and use WIndow s own tools for enlarging the partition if need be. Afaik WIndows supports online resizing.

I was working with a HDD drive that had TWO partitions. :(

--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

Re: hdd to larger sdd
By: August Abolins to Arelor on Fri Jan 13 2023 08:35 pm

Hello Arelor!

I'd copy the disk over using dd_rescue (which skips bad sectors)..

dd_rescue is on the Clonezilla environment?

--

Probably, but if not, it is in the System Rescue DVD and many other live environments.

Anyway, I see you didn prety much the same thing with dd + clonezilla, so...

--
gopher://gopher.richardfalken.com/1/richardfalken
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24)

Hello Arelor!

Anyway, I see you didn prety much the same thing with dd + clonezilla, so...

It was more like: Clonezilla (ie. Partclone) + dd + ntfsresize

--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

Hello Arelor!

** On Monday 09.01.23 - 13:51, Arelor wrote to Sean Dennis:

Clonezilla.

You beat me to it. BUrn the image to DVD and boot from it, then use the wizzard to clone the drives and you are done.

It's off to a bad start. :(

https://kolico.ca/tmp/ccc.jpg

Now what?

--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

Re: hdd to larger sdd
By: August Abolins to Arelor on Mon Jan 09 2023 04:20 pm

Hello Arelor!

** On Monday 09.01.23 - 13:51, Arelor wrote to Sean Dennis:

Clonezilla.

You beat me to it. BUrn the image to DVD and boot from it, then use the wizzard to clone the drives and you are done.

But can it resize (enlarge) a bootable WinXP partition?

--
../|ug

--- OpenXP 5.0.51
* Origin: (} Pointy McPointface (618:250/1.9)

I don t know, but in any case, what I would do is to copy everything over with Clonezilla, then boot from the new drive, and use WIndow s own tools for enlarging the partition if need be. Afaik WIndows supports online resizing.

--
gopher://gopher.richardfalken.com/1/richardfalken
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24)

Re: hdd to larger sdd
By: August Abolins to Arelor on Tue Jan 10 2023 10:49 pm

You beat me to it. BUrn the image to DVD and boot from it, then use the wizzard to clone the drives and you are done.

It's off to a bad start. :(

https://kolico.ca/tmp/ccc.jpg

Now what?

Well, the disk is having a bad day and nearing demise.

I'd copy the disk over using dd_rescue (which skips bad sectors) and then run some filesystem check utility on the transfered filesystems in the destination drive. YOu may find some file resided in a damaged sector and it is lost or damaged, though.

--
gopher://gopher.richardfalken.com/1/richardfalken
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24)