Post by William Schaible
The knoppix version is 8.6.1. The new computer has a UEFI SSD with Win
10. The old computer has a pre-UEFI drive. Currently the SSD has only
Win 10 but I will put Ubuntu on it soon. Before I put Ubuntu on it I
want to do a dd copy of the original SSD to an external drive. My usual
way of doing that is to boot knoppix and run the dd command from
knoppix. Immediately before running the dd command I run fdisk to list
the devices and partitions. What's happening is fdisk does not see the
SSD in the new computer: it says the sda device is the knoppix flash
drive and there's no other device.
All the knoppix flash drives are made using the old pre-UEFI system. One
time I made the knoppix flash drive using a knoppix dvd. All other times
I used MKUSB. I wonder if the knoppix creating software is making the
assumption that the intended target system will be pre-UEFI. Or maybe
the new computer is hiding the drive from knoppix.
TIA. Bill S.
sudo fdisk /dev/sda
sudo gdisk /dev/sda
The second command knows what GPT is (a partitioning method).
You can also use gnome-disks to display partition setups
if you want. Or
to survey the situation.
Installation materials are "boot sensitive"
If you download Ubuntu 20.04 and say to yourself,
"I'd really like to do an install on storage now",
you boot the DVD in UEFI mode, if you expect to do a
UEFI installation. You boot the DVD in legacy mode
(UEFI+CSM) if you want a legacy installation (MSDOS
The only place I can see the difference here, is when
I press the F8 "popup boot menu" hotkey on my computer.
Then the two choices for booting from the DVD drive
are presented to me.
You need to learn about popup boot, to get all the
options presented at boot time.
But so far, the things you've been talking about, the
"reviewing of disks", that does not require special
precautions. The OS function does not change based
on how it's booted. It's only the "virtue signaling"
of booting UEFI mode, causing a UEFI installation to
happen, that depends on how you booted the DVD.
I'm not going to address your usage of "dd".
I hope you know what you're doing. "dd" is dangerous
(amongst other things). "dd" does not respect the needs
of boot identifiers either. It can make an awful mess,
requiring "some learning" to fix.
At least, do not try "sudo update-grub" with the
two cloned drives still plugged in. Be careful what
disk can "see" what other disk, at inopportune moments.
While doing your disk surgery, unplug the network cable.
Why ? This prevents any sort of OS upgrade/update from
buggering what you're doing.