On 8/7/26 15:34, mick.crane wrote:
I've never done this disk cloning.
I've a ~102GB SSD that has the OS trixie on it and I've got spare ~250GB
SSDs
Thought to put the OS on the twice as big drive as it's as I like it and
I might install stuff and get pushed for space.
All my data is on a 3TB drive mounted in a directory in ~/home via fstab
I booted from Debian live on a USB stick.
This "shouldn't" know anything about the 3TB drive except that it exists?
Connect the 250Gb to USB via a power supply and SATA USB connection thingy.
lsblk tells me which is which.
"dd if=/dev/disk_to_copy of=/dev/disk_to_copy_to bs=64M status=progress
conv=fsync"
With the intention to use fdisk to expand the partition with the OS on
it and resize2fs to make more usable space on the partition.
There is an issue that the debian live OS blanks the monitor after a while.
"Ctrl+Shift" brings back the display but the 3rd time "Ctrl+Shift"
didn't do anything.
Before the last screen blanking, progress was showing 99% so I wait a
while then turn off PC.
Booting from new clone of OS disk there is kernel panic and fsck says
it's a bit messed up.
Perhaps I didn't wait long enough.
Perhaps Debian Live is not the best thing to use for this single purpose.
I suppose question is what's best way to ensure original disk integrity
before cloning (if that's an issue).
How in Debian live to turn off for good any screensaver, power saving
settings.
Is there any more surefire way to do this move OS to a bigger disk and
have it boot.
mick
Connect both the 104 GB SSD and the 250 GB SSD to internal SATA ports.
RTFM busybox(1) says busybox includes dd(1). You might want to try the
Debian installer rescue shell.
The "conv" is for data munging, which means "corruption" when you are
doing imaging/ cloning. Instead, use:
iflag=fullblock
oflag=sync
David
