I have two laptops with WD Green 931.52GB SSD's. I wanted to make clones of them so I
purchased two more WD Green 1TB SSD's. However those have a size of 931.51GB !!
Clonezilla won't do it. The difference if .02GB. Will G4L do it? Thanks.
Forgot to mention I am running Ubuntu 22.04.
Last edit: KenUnix 2023-06-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have two laptops with WD Green 931.52GB SSD's. I wanted to make clones
of them so I
purchased two more WD Green 1TB SSD's. However those have a size of
931.51GB !!
Clonezilla won't do it. The difference if .02GB. Will G4L do it? Thanks.
Imageing from 931.52 SSD to 931.51 SSD possible?
Generally, the direct process with a bit level copy will not directly
copy a larger disk to a smaller disk. But one can use a process to
reduce the used space on the original drive and then the process
works.You don't mention anything about the disk setup in way of
format or partitions or OS(s).
Example: Of how it might be done.
Years ago I had a classroom with 20 identical computers. The were
identical except for 1 computers hard disk reported disk size as
being 32M smaller than the other 19? Don't know why, all drives
were exact same drives. Assume must have been some bad sectors
that were mapped out?
Would not copy the larger disk to the smaller one.
Solution was to use gparted to reduce the size of partition on disk
to make the used space on disk fit.
The disks had multiple OSs, so had to slightly reduce the size of
the last partition in the extended partition, and then reduce the
size of the extended partitions.
Afterwards, could copy the disk image between disks, since none
were using space larger than the smallest. Extra space was just not
used on any disk.
The origina GHOST program that was later purchase by Norton,
did have the ability to resize partitions on the fly but a site license
for it was like $2,000 from original company. So, not a feature that
I've been able to reproduce.
That was with regular disk partitions.
If disk is setup using GPT partitions might have an issue with that
since it put a copy of partition info at exact end of disk?
With the G4L I create a 64M image file using GPT that can be
copied to an USB, but since it has the GPT partition at the end of
the 64M, have to fix the process after copying with:
echo -e "Fix" | parted -l ---pretend-input-tty
That will then correctly create the copy of GPT info at end of USB,
and then other space can be used.
If OS is windows, might be able to reduce size of last partition, and
then do copy. Windows doesn't seem to report the GPT error, but
does seem to fix it if putting an uncorrect flash in machine.
I have bought the extact same brand of SSD drives for my
machines, and have been able to clone the old regular disks to the
new SDD disks with no problems. Did have my mom's computer
that had a disk that was slightly larger, so bought a 2TB SSD, and
copied the 1TB disk to the 2TB drive. It worked fine, and then just
created another partition with the extra space.
Wish I had a better answer.. But perhaps that will help.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply. I thought I had good quality SSD's Western Digital Green 1.tb then to discover some are 931.51 and some are 931.52!
Clonezilla had the -r flag set and kept running until it was 99% done then said it was having write errors. And the clone was aborted. Tried with two different drives. So I got a Samsung 2tb SSD and cloned the laptop to it. As a test I attempted to clone the Samsung 2tb that had 1tb on it back to the laptop with the 1tb drive and clonezilla said the destination was too small...
Maybe I'll just create one way images. In other words if drive acts up in the laptop replace it with a backup.
Guam ! WOW. I started with Unix in 1974 at Bell Telephone (AT&T).
Ken
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Michael,
Thanks for the reply. I thought I had good quality SSD's Western Digital
Green 1.tb then to discover some are 931.51 and some are 931.52!
Clonezilla had the -r flag set and kept running until it was 99% done then
said it was having write errors. And the clone was aborted. Tried with two
different drives. So I got a Samsung 2tb SSD and cloned the laptop to it. As a
test I attempted to clone the Samsung 2tb that had 1tb on it back to the
laptop with the 1tb drive and clonezilla said the destination was too small...
Maybe I'll just create one way images. In other words if drive acts up in the
laptop replace it with a backup.
Guam ! WOW. I started with Unix in 1974 at Bell Telephone (AT&T).
Ken
Been in Guam since 1974, was in 8th grade then.
First Unix was UnixWare, but had Novell 2.x servers at College.
386 26Mhz servers with 650M SCSI disks. Later had Novell 4
server with duplex SCSI disk. Machine had 2 1G duplexed SCSI
with System and 2 9G SCSI disks for Data partition, then two other
9G SCSI disk that were not duplexed for additional storage.
That was an AMD K6-2 350Mhz machine with 192M of Ram with
Novell 4.x.
Just to note, you could make disk image files of disks for backups
to an ftp server or external drive. That could then be restored to
the disk if it was corrupted with no issue, since it would be
restoring to the same exact sized disk. When I was still teaching, I
would generally update 1 machine an create an image of it, and
then use the udpcast option to broadcast image to the other 19
machines.
Since retiring I don't have the setup to do lots of testing. Still
make my own images. I genereally have use WD Blue SSD drives.
Think I've got one Green in a machine, but have had no issues.
Good Luck.
One note: if you make image file, it is best to clear all unused
space to nulls. Once did a clean install of Fedora core 8 on on 80G
disk. Did an image and it created a 12G image file. Then cleared
all the space and redid image, and it created a 2.5G image. So, the
random stuff in unused space took up 9.5G of compress space
versus the almost no space if all cleared.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have two laptops with WD Green 931.52GB SSD's. I wanted to make clones of them so I
purchased two more WD Green 1TB SSD's. However those have a size of 931.51GB !!
Clonezilla won't do it. The difference if .02GB. Will G4L do it? Thanks.
Forgot to mention I am running Ubuntu 22.04.
Last edit: KenUnix 2023-06-18
On 18 Jun 2023 at 18:39, KenUnix wrote:
To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net
From: "KenUnix" kenmartin@users.sourceforge.net
Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net
Subject: [g4l:discussion] Imageing from 931.52 SSD to 931.51 SSD possible?
Date sent: Sun, 18 Jun 2023 18:39:04 -0000
Generally, the direct process with a bit level copy will not directly
copy a larger disk to a smaller disk. But one can use a process to
reduce the used space on the original drive and then the process
works.You don't mention anything about the disk setup in way of
format or partitions or OS(s).
Example: Of how it might be done.
Years ago I had a classroom with 20 identical computers. The were
identical except for 1 computers hard disk reported disk size as
being 32M smaller than the other 19? Don't know why, all drives
were exact same drives. Assume must have been some bad sectors
that were mapped out?
Would not copy the larger disk to the smaller one.
Solution was to use gparted to reduce the size of partition on disk
to make the used space on disk fit.
The disks had multiple OSs, so had to slightly reduce the size of
the last partition in the extended partition, and then reduce the
size of the extended partitions.
Afterwards, could copy the disk image between disks, since none
were using space larger than the smallest. Extra space was just not
used on any disk.
The origina GHOST program that was later purchase by Norton,
did have the ability to resize partitions on the fly but a site license
for it was like $2,000 from original company. So, not a feature that
I've been able to reproduce.
That was with regular disk partitions.
If disk is setup using GPT partitions might have an issue with that
since it put a copy of partition info at exact end of disk?
With the G4L I create a 64M image file using GPT that can be
copied to an USB, but since it has the GPT partition at the end of
the 64M, have to fix the process after copying with:
echo -e "Fix" | parted -l ---pretend-input-tty
That will then correctly create the copy of GPT info at end of USB,
and then other space can be used.
If OS is windows, might be able to reduce size of last partition, and
then do copy. Windows doesn't seem to report the GPT error, but
does seem to fix it if putting an uncorrect flash in machine.
I have bought the extact same brand of SSD drives for my
machines, and have been able to clone the old regular disks to the
new SDD disks with no problems. Did have my mom's computer
that had a disk that was slightly larger, so bought a 2TB SSD, and
copied the 1TB disk to the 2TB drive. It worked fine, and then just
created another partition with the extra space.
Wish I had a better answer.. But perhaps that will help.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
Michael,
Thanks for the reply. I thought I had good quality SSD's Western Digital Green 1.tb then to discover some are 931.51 and some are 931.52!
Clonezilla had the -r flag set and kept running until it was 99% done then said it was having write errors. And the clone was aborted. Tried with two different drives. So I got a Samsung 2tb SSD and cloned the laptop to it. As a test I attempted to clone the Samsung 2tb that had 1tb on it back to the laptop with the 1tb drive and clonezilla said the destination was too small...
Maybe I'll just create one way images. In other words if drive acts up in the laptop replace it with a backup.
Guam ! WOW. I started with Unix in 1974 at Bell Telephone (AT&T).
Ken
On 18 Jun 2023 at 23:13, KenUnix wrote:
To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net
From: "KenUnix" kenmartin@users.sourceforge.net
Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net
Subject: [g4l:discussion] Imageing from 931.52 SSD to 931.51 SSD possible?
Date sent: Sun, 18 Jun 2023 23:13:16 -0000
Been in Guam since 1974, was in 8th grade then.
First Unix was UnixWare, but had Novell 2.x servers at College.
386 26Mhz servers with 650M SCSI disks. Later had Novell 4
server with duplex SCSI disk. Machine had 2 1G duplexed SCSI
with System and 2 9G SCSI disks for Data partition, then two other
9G SCSI disk that were not duplexed for additional storage.
That was an AMD K6-2 350Mhz machine with 192M of Ram with
Novell 4.x.
Just to note, you could make disk image files of disks for backups
to an ftp server or external drive. That could then be restored to
the disk if it was corrupted with no issue, since it would be
restoring to the same exact sized disk. When I was still teaching, I
would generally update 1 machine an create an image of it, and
then use the udpcast option to broadcast image to the other 19
machines.
Since retiring I don't have the setup to do lots of testing. Still
make my own images. I genereally have use WD Blue SSD drives.
Think I've got one Green in a machine, but have had no issues.
Good Luck.
One note: if you make image file, it is best to clear all unused
space to nulls. Once did a clean install of Fedora core 8 on on 80G
disk. Did an image and it created a 12G image file. Then cleared
all the space and redid image, and it created a 2.5G image. So, the
random stuff in unused space took up 9.5G of compress space
versus the almost no space if all cleared.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+