[SATLUG] UUID gone wrong

mark mayfield mayfield_mark at att.net
Fri Apr 9 20:35:40 CDT 2010

have a look at this page

Steps you must take for each and EVERY partition on the cloned drive:
1. Generate a new UUID

At the terminal prompt type:
Code: uuidgen

(a unique number you can use as a UUID will appear - copy to paste into
next command)

Code: sudo tune2fs /dev/sdb? -U paste_above_number_here

(replace sdb? with whatever your drive designation actually is - e.g.
sdb2, hdb3, etc)

You can check the UUID associated with a partition with this command at
a terminal:

Code: vol_id /dev/sdb?

Repeat the above for each partition and now you will have a "clone"
drive that at least has 
unique UUIDs for each partition and wont cause problems due to
duplicated UUIDs caused by the cloning process.

You will need to adjust the grub menu.lst (or if you use grub2 the grub
custom file). Or just reinstall grub (I would just reinstall grub on the
new drive0.

On Fri, 2010-04-09 at 18:53 -0600, Howard Haradon wrote:
> Hi,  another tale of user error: OK, I add a nice new
> drive to my system and then clone the old main partition
> to a bigger partition on the new drive.  Now the new
> SATA partition-1 is a clone of the old ide partition-1, and
> I also tell Clonezilla to clone over the MBR of the old drive to the
> new SATA drive.  BTW, Clonezilla worked great.
> On the first boot after cloning I adjust the BIOS to boot
> from the new SATA drive, but find that it just stalls
> with no GRUB screen.  Now I reset the BIOS to boot
> from the old ide drive, and the boot goes just fine with
> not system problems.  Later I shut down and reboot
> using the same old setup.  Now I notice some clicking
> sounds that tell me that the new SATA drive is active.
> I play around with some disk tools and find that there
> are 2 schools of thought regarding what is what with
> my 2 drives.  The new drive is active and is really
> accessible as sda1.
> fdisk-l
> Disk /dev/sda: 80.0 GB, 80026361856 bytes (old drive)
> Disk /dev/sdb: 640.1 GB, 640135028736 bytes
> df -h
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/sda1             126G   17G  103G  15% /  (new drive)
> mount
> /dev/sda1 on / type ext2 (rw,relatime,errors=remount-ro)
> Nothing for /dev/sdb1 so it's not mounted, right?
> Not according to fsck:
> sudo fsck -y /dev/sdb1
> /dev/sdb1 is mounted.
> WARNING!!!  Running e2fsck on a mounted filesystem may cause
> SEVERE filesystem damage.
> Do you really want to continue (y/n)? no
> So with this confusion I shut down cleanly and reboot
> with a Puppy CD.
> Booting with a Puppy CD, here is what blockid finds:
> # blkid
> /dev/loop0: TYPE="squashfs"
> /dev/loop1: UUID="b4ff483a-013a-4b4c-bdc9-d0766a447287" TYPE="ext2"
> /dev/sda1: UUID="8f467a7b-4aa0-42e0-899c-59d240badee8" TYPE="ext2"
> /dev/sda2: TYPE="swap"
> /dev/sdb1: UUID="8f467a7b-4aa0-42e0-899c-59d240badee8" TYPE="ext2"
> /dev/sdb2: TYPE="swap" UUID="10facf90-dc05-4ce8-aa28-af68a3f32ef8"
> /dev/sdb3: UUID="1c86c0ea-9382-4c4b-8e7f-452bbf7b150c" TYPE="ext2"
> /dev/sdb4: UUID="4b2d938a-650c-4a47-af1e-931311979027" TYPE="ext2"
> Note that the UUIDs for sda1 and sdb1 are the same, and they
> match just what is in /etc/fstab for /dev/sda1.
> I am hoping that some one can help me straighten this out.
> I am grateful for your help,  Howard
> -- 
> Howard Haradon
> San Antonio, TX  USA

More information about the SATLUG mailing list