[opensuse] clonezilla and windows dual boot
On my new work desktop, I have dual boot with Windows 7 and openSUSE 42.2. It works great. The hard drive is 1TB, partitioned as an MBR, not GPT drive, in accordance with the school policies where I volunteer. The partitions I have set up are about 156GB total for Windows partitions, 16GB of swap, followed by the extended partition, which then has 2 30GB separate root partitions (1 is for a future upgrade), and the rest is my data/home partition. I have a separate, new, unpartitioned 1TB drive that I have just connected inside the desktop, and I am looking to set it up to backup my first drive, in case the first drive fails. My idea is to use clonezilla to clone the entire drive the first time, which will set up all the partitions and everything, as well as back up the data. After that I will do regular synchronizing of the data and root partitions. 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? 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. For the linux side, how will using clonezilla effect things? In my fstab file, I mount based on drive label, not UUID, so I figured that after using clonezilla, I would go in on a restore configuration and change the blkid of the new drives, so that the system doesn't get confused when trying to boot up. But what about grub2? Do I need to do something about the UUIDs of the partitions on the new drive before booting again, so that it doesn't present a problem? George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-25 01:40, 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 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!" 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. 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. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Wed, 25 Jan 2017, Carlos E. R. wrote:
On 2017-01-25 01:40, 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 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!"
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. 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.
Depending on the kernel's ordering of the disks involved, the confusion may be immediate. Once the duplicate filesystem uuid pops into existance the running system may report the wrong/new filesystem as being mounted instead of the existing one. The confusion will prevent relabelling. I think if you shutdown, remove one of the disks, and then change the uuid's you' should be OK. A more safe procedure would be to use dd/clonezilla with a rescue disk. It's interesting the advent of labels and uuid's has crept up on these tools and undermined their use in a running system. Cheers, Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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.
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.
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 umount when necessary. As all my machines are multiboot, it is is no big deal to boot anything else unless there is a (rare) shortage of boot media options and a full disk clone is desired. Usually if that would happen I remove the source and target to a different machine. As soon as I finish a clone operation, I use blkid to verify duplicates, then eliminate the duplication, usually using tune2fs -U -L, following up with adjusting the fstabs and boot menus where necessary. As I only use Grub as a GNU bootloader, it's a simple matter to fix clone target booting with the Grub shell's setup command, which doesn't require filesystem mounting, script version matching, or complicated script parameters. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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)
On 01/25/2017 10:36 PM, Carlos E. R. wrote:
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:
Ok, that was excellent. Thank you all for the help. There is nothing like working hard at something, setting it up, running it, and having it work PERFECTLY THE FIRST TIME! Thank you! (or as we used to say at my former job, I think somebody forgot to tell the devil what I was planning to do) In essence, after studying through your emails, I realized that this was what I had to do. The drive has NTFS partitions, a swap partition, and ext4 partitions, so after cloning, I had to change the labels and UUIDs on all of these, with different sets of tools. The 4 things that had to be changed, with the tools used to change them: 1. disk unique identifier - fdisk in expert mode 2. labels - e2label, swaplabel, and ntfslabel 3. UUIDs - tune2fs, swaplabel, and ntfslabel 4. Windows serial numbers - ntfslabel After changing all those (and making a record of what they are supposed to be if I ever have to change them back), and booting up again in both windows and linux, and the system runs great. So thanks again for your help! George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R. -
Felix Miata -
george from the tribe -
Michael Hamilton