On 2017-01-25 07:02, Felix Miata wrote:
Carlos E. R. composed on 2017-01-25 04:20 (UTC+0100):
george from the tribe wrote:
On my new work desktop, I have dual boot with Windows 7 and openSUSE 42.2. It works great.
My main concern is the windows partition. I don't normally use windows, but every once in a while, like once every couple of weeks, I will probably have to boot into windows for something.
If I use clonezilla, doesn't it also clone the UUID of the drive and partitions?
Yes, I think so.
If it doesn't, it's not cloning. I don't use Clonezilla, but I suppose it must have some option to alter UUIDs, and maybe filesystem LABELs too; that or it expects its users to be sophisticated enough to deal with the duplication.
There may be tools that change the uuid, or have an option to do so.
If so, how will that effect my ability to boot from windows? I have heard that windows does some funny things with verifying the UUID of drives when it boots. I want to keep this drive plugged in regularly so that when I feel like it I can just back things up.
Not only the partition uuid, but the "Disk identifier". You can see it and set it up with fdisk. They have to be the same or Windows will cry "Pirates!"
# ls -l /dev/disk/by-id/ | grep -v part | grep ata lrwxrwxrwx 1 root root 9 Jan 23 17:39 ata-Optiarc_DVD_RW_AD-7200S -> ../../sr0 lrwxrwxrwx 1 root root 9 Jan 23 00:49 ata-ST1000DM003-1CH162_S1DFA2TD -> ../../sda lrwxrwxrwx 1 root root 9 Jan 23 00:49 ata-ST1000DM003-1CH162_Z1DCJZ8N -> ../../sdb
What you see are uniques from the manufacturers that are immutable, based on disk model number and serial number.
No, I mean this: Telcontar:~ # fdisk /dev/sda Welcome to fdisk (util-linux 2.28). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x000e9888 <========== Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 25167871 25165824 12G 83 Linux /dev/sda2 25167872 33556479 8388608 4G 82 Linux swap / Solaris /dev/sda3 33556480 3907028991 3873472512 1.8T 83 Linux Command (m for help): Windows 7 looks at that identifier, but it can be changed from fdisk: Help (expert commands): DOS (MBR) b move beginning of data in a partition i change the disk identifier <=======
The problem is that both disks being connected and both having the same uuids and labels is also a problem for Linux when mounting the partitions, because it will confuse them. It won't confuse disks because of the uniques, but duplicate UUIDs and LABELs do need to be dealt with expeditiously after clone operations.
The only way to work is to change the uuids (and labels if they exist) on the second disk, and then also to change the references in fstab and grub.
You could simply remove the first disk temporarily, try to boot the second disk, and correct the problems as they arise.
I do a _lot_ of cloning, but never of the booted OS from the booted OS, and never anything mounted except by forgetting to first check and
My reasoning is to find out if it works, and if not, correct it, using rescue media to boot instead. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)