[Arm-dev] UUID for partitions

[Robert Moskowitz]

On 12/24/2015 10:12 AM, Robert Moskowitz wrote:
>
>
> On 12/23/2015 08:20 AM, Robert Moskowitz wrote:
>>
>>
>> On 12/23/2015 07:59 AM, Karanbir Singh wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 22/12/15 02:10, Mandar Joshi wrote:
>>>>> So every installation from an image will have the same UUIDs.
>>>> Yes
>>> this is a bad idea, it means you cant ( or will haveto do some work )
>>> if you ever intend to share media. onprem, lesser issue ( likely only
>>> when disaster recovery is involved ), but this is a much bigger issue
>>> in offprem, where block device mobility is part of the larger picture
>>> and taken for granted.
>>>
>>> so, we should fix it.
>>
>> This simple answer is to add to the, yet to be provided, 
>> centos-arm-installer a step that relabels the partitions.  I don't 
>> see this as an option in parted, but I suspect there is SOME tool 
>> that will change a partition's UUID.
>>
>> Thing is what to do with /etc/fstab.  Edit it with SED?  Use 
>> /dev/device rather than UUID= ?  But the <device> varies by board.
>
> I did a basic google search and found that something like:
>
> uuidgen
>
> along with
>
> sudo tune2fs /dev/sd__ -U ______
>
> Of course you have to provide the device and uuidgen output.
>

Problems with changing the UUID for the swap partition:

# tune2fs /dev/sdb2 -U 4446599f-6dd5-4093-b39a-92ae44aadbb2
tune2fs 1.42.12 (29-Aug-2014)
tune2fs: Bad magic number in super-block while trying to open /dev/sdb2
Couldn't find valid filesystem superblock.

But maybe we don't need to change the swap partition's UUID...

......

Tried this for firstboot, along with switching to enforcing and resizing.

It failed.

Either I typoed, which I don't think, or these three items as the are 
cannot be done at once.  I would not be supprised if autoresize was the 
problem.  But maybe not.

Someone with more inside knowledge than I will have to put all this 
together...