Comments on: What UUIDs Are and How To Use Them in Ubuntu

By: etnadamoc

etnadamoc — Fri, 29 Apr 2011 06:56:21 +0000

Anon is right! what good does uuid if you can not make any backups/clones from harddisks anymore without starting to "code" before. Linux should try to be more userfriendly if it want to spread itself

By: anonymoose

anonymoose — Fri, 07 May 2010 12:12:37 +0000

If you clone a partition's filesystem, the UUID of the original partition will be tacked on to the new partition as the cloned filesystem is copied over.

You can then generate a new UUID for an Ext2 or Ext3 partition using

tune2fs -U random /dev/sdax

(where /dev/sdax is the number of the new partition)

Be sure to copy the new UUID, as displayed by
sudo blkid

to the GRUB (Legacy) /boot/grub/menu.lst and to /etc/fstab

Alternatively, you could generate a new UUID with
uuidgen

and copy it to the menu.lst and fstab files and to the partition with

tune2fs -U xxxxxx-xxxx /dev/sdax

where xxxxx-xxxx stands for the newly generated UUID.

By: Keith A

Keith A — Fri, 22 Jan 2010 13:33:41 +0000

Wim, it looks to me as if your sfd1 is a partition within the sde1 partition (using the same mounting point)

I could be mistaken but that's my take on it.
Try looking at your partitions with a LiveCD's graphical partition tool, it may help to visualize it.

By: Ubuntu Karmic Koala: Upgrading Jaunty Jackalope « Curly Braces

Ubuntu Karmic Koala: Upgrading Jaunty Jackalope « Curly Braces — Sun, 01 Nov 2009 09:28:56 +0000

[...] 1.What is UUID ? | Unix Tutorial [...]

By: electronico

electronico — Tue, 20 Oct 2009 08:15:41 +0000

@Wim
Might your devices /dev/sde1 and /dev/sdf1 have been in a RAID1 or cloned ?
This happened to me …

By: Mike Christianson

Mike Christianson — Mon, 02 Mar 2009 07:05:20 +0000

Thanks for the info. It came in handy after repartitioning my two drives.

By: Wim

Wim — Wed, 28 Jan 2009 20:07:14 +0000

If these UUIDS are considered unique then why the heck do I get the same UUID all of a sudden. For some weird reason some of the UUIDs got screwed up.

sudo blkid
/dev/sda1: UUID="cde9bfc0-4c4f-405d-8729-95c0624cd3b3"
/dev/sda2: TYPE="swap" UUID="19233dcb-6ae3-4b5f-a926-39e1909689c6"
/dev/sdb1: UUID="cd79f6ab-6770-4e6c-a4ad-15db909abe02"
/dev/sdc1: UUID="e7041c14-3952-4af6-8d98-fddc8e9313b9"
/dev/sdd1: UUID="7bfd287a-9bab-4ef0-9e35-8931dba74f91"
/dev/sde1: UUID="740b0350-af69-4d23-83ec-31b6f6e8b4ce"
/dev/sdf1: UUID="740b0350-af69-4d23-83ec-31b6f6e8b4ce"

Why oh why are these id's NOT unique?
Reason #1 is not a correct argument if I look at this

By: Anon

Anon — Fri, 28 Nov 2008 17:37:11 +0000

UUIDs suck big time. They are hard to find out, keep changing all the time and GRUB doesn't use them. Linux developers are just insane to have introduced this.

By: Embedded

Embedded — Sat, 07 Jun 2008 19:52:23 +0000

Speaking of UUID and Grub on SuSE the Grub boot knows about UUID as does /etc/fstab.

If you clone a Hard Drive better edit these for the new one because they will NOT be right on it eg. Toshiba 100GB hard drive to Toshiba 320GB hard drive. Best to rename all to sda0-whatever from UUID. (you can do that on the original too)

Been There done that.

By: Gleb Reys

Gleb Reys — Sat, 24 May 2008 00:53:24 +0000

Thanks for a really useful comment – good to know, especially BEFORE adding new drive to one's PC