It looks like the UUIDs for the partitions are set. This only makes sense.
cat /etc/fstab
#Generated by RootFS Build Factory UUID=fa926fa0-ddcb-47ea-9731-ea5c92d9f959 /boot ext3 noatime 0 0 UUID=6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 swap swap noatime 0 0 UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 / ext4 noatime 0 0
Does this matter? Should some script change the UUIDs for each installation?
#Generated by RootFS Build Factory UUID=fa926fa0-ddcb-47ea-9731-ea5c92d9f959 /boot ext3 noatime 0 0 UUID=6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 swap swap noatime 0 0 UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 / ext4 noatime 0 0
Does this matter? Should some script change the UUIDs for each installation?
Every time a new image is generated by RootFS Build Factory, these UUIDs will change. But If you just to dd the image to a microSD, UUIDs will stay the same as the one in the image.
-Mandar Joshi
On 12/21/2015 08:30 PM, Mandar Joshi wrote:
#Generated by RootFS Build Factory UUID=fa926fa0-ddcb-47ea-9731-ea5c92d9f959 /boot ext3 noatime 0 0 UUID=6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 swap swap noatime 0 0 UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 / ext4 noatime 0 0
Does this matter? Should some script change the UUIDs for each installation?
Every time a new image is generated by RootFS Build Factory, these UUIDs will change. But If you just to dd the image to a microSD, UUIDs will stay the same as the one in the image.
So every installation from an image will have the same UUIDs. Is this a problem? Is there some security/privacy consideration here? Should there be some step in the centos-arm-installer script that changes the UUID and /etc/fstab?
So every installation from an image will have the same UUIDs.
Yes
Is this a problem? Is there some security/privacy consideration here? Should there be some step in the centos-arm-installer script that changes the UUID and /etc/fstab?
Off the top of my head, I don't see any security issues. Do you?
On 12/21/2015 09:10 PM, Mandar Joshi wrote:
So every installation from an image will have the same UUIDs.
Yes
Is this a problem? Is there some security/privacy consideration here? Should there be some step in the centos-arm-installer script that changes the UUID and /etc/fstab?
Off the top of my head, I don't see any security issues. Do you?
No, and I am the security guy. But then I am security protocols, like chairing IPsec in the IETF back in '98. Or working on IEEE 802.11i (WiFi WPA) and stuff like that.
But I do know someone over at Mitre that is 'well connected' to ask...
-----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.
- - KB
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
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 should point out that Fedora-arm has the same issue, and I will can this point over to them. From Fedora-23-Xfce image:
/etc/fstab: UUID=5c922e06-bb74-402c-9d65-65feee4516b5 / ext4 defaults,noatime 0 0 UUID=3cc330d2-84bb-46ff-9501-3a1776ed09c5 /boot ext3 defaults,noatime 0 0 UUID=01aee4b3-d3bb-4e17-8d30-3005596f2861 swap swap defaults,noatime 0 0
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.
would do the trick. Should be a way to piple uuidgen output into tune2fs.
Still how to programatically edit /etc/fstab.
And I should point out that this can be done on a live system (with careful editting of fstab!).
sudo blkid
will give you what you currently have so you can correctly do this.
And there might be better ways...
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...
On 24 decembrie 2015 20:02:27 EET, Robert Moskowitz rgm@htt-consult.com wrote:
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...
You cannot use tune2fs on anything but ext2/3/4fs Just run again mkswap on the swap partition,,while it is not in use.
On 12/24/2015 01:06 PM, Manuel Wolfshant wrote:
On 24 decembrie 2015 20:02:27 EET, Robert Moskowitz rgm@htt-consult.com wrote:
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...
You cannot use tune2fs on anything but ext2/3/4fs Just run again mkswap on the swap partition,,while it is not in use.
Ah.
I hope someone is taking notes for all that needs to go into the centos-arm-installer script...
:)
I got my system to boot with new UUIDs. Here is what I had to do.
run
uuidgen
Twice to get two UUIDs. then use
tune2fs /dev/<partition> -U <UUID>
to change the boot and root partitions UUID
mkswap /dev/<partition>
Changed the swap UUID, but one can argue about so what if all the swaps have the same UUID. But since you can change it, do it. Then on the root partition you have edit fstab with these new UUIDs.
Finally, the step I previously missed was, on the boot partition, you also have to edit the root partition UUID in extlinux/extlinux.conf
I made these changes, staged the selinux enforcing switch, and autoresize. Put the card in and did firstboot. It all took.
Now someone skilled needs to take my hacks and put them into a centos-arm-installer script!
Enjoy your holidays!
On 12/24/2015 01:06 PM, Manuel Wolfshant wrote:
On 24 decembrie 2015 20:02:27 EET, Robert Moskowitz rgm@htt-consult.com wrote:
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...
You cannot use tune2fs on anything but ext2/3/4fs Just run again mkswap on the swap partition,,while it is not in use.
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
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.
- KB
I just finished writing a script to change UUIDs and LABELs. It's changeuuid.py in https://github.com/mndar/rbf/tree/master/commonscripts It doesn't depend on anything else in the repo, so you can just download that script.
Sample Usage:
# just show what is going to change ./changeuuid.py pretend /dev/sdb /tmp/temp/
# actually change ./changeuuid.py change /dev/sdb /tmp/temp/
Refer the README for more details. Let me know if you have any issues.
-Mandar Joshi
I will give this a try on Monday.
On 12/25/2015 03:30 PM, 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.
- KB
I just finished writing a script to change UUIDs and LABELs. It's changeuuid.py in https://github.com/mndar/rbf/tree/master/commonscripts It doesn't depend on anything else in the repo, so you can just download that script.
Sample Usage:
# just show what is going to change ./changeuuid.py pretend /dev/sdb /tmp/temp/
# actually change ./changeuuid.py change /dev/sdb /tmp/temp/
Refer the README for more details. Let me know if you have any issues.
-Mandar Joshi _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On 12/25/2015 03:30 PM, 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.
- KB
I just finished writing a script to change UUIDs and LABELs. It's changeuuid.py in https://github.com/mndar/rbf/tree/master/commonscripts It doesn't depend on anything else in the repo, so you can just download that script.
Sample Usage:
# just show what is going to change ./changeuuid.py pretend /dev/sdb /tmp/temp/
# actually change ./changeuuid.py change /dev/sdb /tmp/temp/
Refer the README for more details. Let me know if you have any issues.
Worked fine after I figured out a way to get the script. I clicked on 'raw' and saved, then chmod +x.
I see you tested this on the Fedora23 image. Are you going to take this issue and script over to the Fedora-arm list, or may I?
Next on to resizing the rootfs as part of the same script. See the Fedora-arm-installer script that has:
if [ "$RESIZEFS" != "" ] ; then echo "= Resizing $MEDIA ...." sync echo ", +" | sudo sfdisk -N 3 "$MEDIA" sudo fsck.ext4 -fy "$ROOTPART" sudo partprobe "$MEDIA" sudo resize2fs "$ROOTPART" fi
Where $MEDIA is where mSD card is (e.g. /dev/sdb) and $ROOTPART is the rootfs partition (e.g. /dev/sdb3).
Very fast compared to other methods.
My system (F22) started developing problems and I finally had to reboot. I run the script a number of times and strangeness was occuring, ending with /dev/sdb not disapearing after removing one mSD card, and then could no longer dd to new cards that were trying to mount as /dev/sdb. I don't know if the script was at fault or something, else. But things definitely went south.
One clear problem with this script is that the [INFO] messages report the old UUID wrong after the first time run. Each time it lists the old UUIDs as the last UUIDs. Not the UUIDs on the device.
I will hold off on using this script again until I hear back.
On 12/28/2015 08:58 AM, Robert Moskowitz wrote:
On 12/25/2015 03:30 PM, 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.
- KB
I just finished writing a script to change UUIDs and LABELs. It's changeuuid.py in https://github.com/mndar/rbf/tree/master/commonscripts It doesn't depend on anything else in the repo, so you can just download that script.
Sample Usage:
# just show what is going to change ./changeuuid.py pretend /dev/sdb /tmp/temp/
# actually change ./changeuuid.py change /dev/sdb /tmp/temp/
Refer the README for more details. Let me know if you have any issues.
Worked fine after I figured out a way to get the script. I clicked on 'raw' and saved, then chmod +x.
I see you tested this on the Fedora23 image. Are you going to take this issue and script over to the Fedora-arm list, or may I?
Next on to resizing the rootfs as part of the same script. See the Fedora-arm-installer script that has:
if [ "$RESIZEFS" != "" ] ; then echo "= Resizing $MEDIA ...." sync echo ", +" | sudo sfdisk -N 3 "$MEDIA" sudo fsck.ext4 -fy "$ROOTPART" sudo partprobe "$MEDIA" sudo resize2fs "$ROOTPART" fi
Where $MEDIA is where mSD card is (e.g. /dev/sdb) and $ROOTPART is the rootfs partition (e.g. /dev/sdb3).
Very fast compared to other methods.
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
# just show what is going to change ./changeuuid.py pretend /dev/sdb /tmp/temp/
# actually change ./changeuuid.py change /dev/sdb /tmp/temp/
It's best to first run the 'pretend' command and review the changes before actually writing the changes using 'change'. The reason behind this is that once the UUIDs have been changed in fstab and not on the partitions, there is just one way to recover-> manually. I really appreciate the time you are taking for testing various things. Can you please post the output of the 'pretend' command and the 'change' command?
Regards Mandar Joshi
On 12/28/2015 05:51 PM, Mandar Joshi wrote:
# just show what is going to change ./changeuuid.py pretend /dev/sdb /tmp/temp/
# actually change ./changeuuid.py change /dev/sdb /tmp/temp/
It's best to first run the 'pretend' command and review the changes before actually writing the changes using 'change'.
I did that the first time to ensure it was working. After that, I only did 'change'.
The reason behind this is that once the UUIDs have been changed in fstab and not on the partitions, there is just one way to recover-> manually. I really appreciate the time you are taking for testing various things. Can you please post the output of the 'pretend' command and the 'change' command?
I will have to do the testing again. Making another image or two and see what happens. I really don't like having to boot my notebook. It takes ~30min to get everything set the way I work and why I typically boot once a month or so.
One clear problem with this script is that the [INFO] messages report the old UUID wrong after the first time run. Each time it lists the old UUIDs as the last UUIDs. Not the UUIDs on the device.
The output of pretend and change would be really useful.
One problem I did face with the script is that the files fstab,extlinux.conf and boot.ini were being modified on the microSD card but the UUIDs could not be changed on the partitions because there were automounted by the system. That's why the REAME says "Make sure you have unmounted all partitions on the device before executing this script.". Could that have been the case with you too?
Regards Mandar Joshi
On 12/28/2015 06:10 PM, Mandar Joshi wrote:
One clear problem with this script is that the [INFO] messages report the old UUID wrong after the first time run. Each time it lists the old UUIDs as the last UUIDs. Not the UUIDs on the device.
The output of pretend and change would be really useful.
One problem I did face with the script is that the files fstab,extlinux.conf and boot.ini were being modified on the microSD card but the UUIDs could not be changed on the partitions because there were automounted by the system. That's why the REAME says "Make sure you have unmounted all partitions on the device before executing this script.". Could that have been the case with you too?
My system is set up to require manual mounting. Well actually, on a fairly unused workspace (I am using Xfce on F22), I see the partition icons, and I right-click and select mount, or unmount as the case may be.
See how fedora-arm-installer forces an unmount of the partitions.
See how fedora-arm-installer forces an unmount of the partitions.
It seems to be doing "umount $MEDIA*" which I can't do from a python script. I have to iterate over a list of partitions and call umount on the individual partitions.
This is my output with a fresh install of the F22 image. Can you please post your output? and I think you are right, if we are discussing F22, we should probably move this discussion to the Fedora Arm mailing list. I'll start a thread there. -------------------------------------------------------------------------------------------------------------------------------------------------------------------. # ./changeuuid.py change /dev/sdd /tmp/temp/ [INFO ] ['/dev/sdd1', '/dev/sdd2', '/dev/sdd3'] [INFO ] /dev/sdd1 ext3 da527931-ac9c-4c49-9c0c-6d7c414a44d3 a5381305-f382-44e0-ad98-4786d218b289 [INFO ] /dev/sdd2 swap babd584c-ef9c-4480-80bd-643e7dd22d3e 730bf048-9252-4564-8891-50bed55495f2 [INFO ] /dev/sdd3 ext4 7c321d6b-f2b0-4783-9576-e3dfe657f9b3 5bb7ffd6-84eb-4a16-9a13-957d8f42388f [INFO ] Unmounting all partitions on /dev/sdd umount: /dev/sdd1: not mounted umount: /dev/sdd2: not mounted umount: /dev/sdd3: not mounted [INFO ] Unmounting /dev/sdd1 /tmp/temp/ [INFO ] Mounting /dev/sdd3 /tmp/temp/ [INFO ] Processing File: /tmp/temp//etc/fstab **** Old /etc/fstab **** UUID=7c321d6b-f2b0-4783-9576-e3dfe657f9b3 / ext4 defaults,noatime 0 0 UUID=da527931-ac9c-4c49-9c0c-6d7c414a44d3 /boot ext3 defaults,noatime 0 0 UUID=babd584c-ef9c-4480-80bd-643e7dd22d3e swap swap defaults,noatime 0 0
**** New /etc/fstab **** UUID=5bb7ffd6-84eb-4a16-9a13-957d8f42388f / ext4 defaults,noatime 0 0 UUID=a5381305-f382-44e0-ad98-4786d218b289 /boot ext3 defaults,noatime 0 0 UUID=730bf048-9252-4564-8891-50bed55495f2 swap swap defaults,noatime 0 0
[INFO ] Writing /tmp/temp//etc/fstab [INFO ] Unmounting /tmp/temp/ [INFO ] Mounting /dev/sdd1 /tmp/temp/ [INFO ] Processing File: /tmp/temp//extlinux/extlinux.conf **** Old /extlinux/extlinux.conf **** # extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-22-3. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-22-3 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-22-3 (4.0.4-301.fc22.armv7hl) kernel /vmlinuz-4.0.4-301.fc22.armv7hl append ro root=UUID=7c321d6b-f2b0-4783-9576-e3dfe657f9b3 fdtdir /dtb-4.0.4-301.fc22.armv7hl/ initrd /initramfs-4.0.4-301.fc22.armv7hl.img
**** New /extlinux/extlinux.conf **** # extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-22-3. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-22-3 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-22-3 (4.0.4-301.fc22.armv7hl) kernel /vmlinuz-4.0.4-301.fc22.armv7hl append ro root=UUID=5bb7ffd6-84eb-4a16-9a13-957d8f42388f fdtdir /dtb-4.0.4-301.fc22.armv7hl/ initrd /initramfs-4.0.4-301.fc22.armv7hl.img
[INFO ] Writing /tmp/temp//extlinux/extlinux.conf [INFO ] Unmounting /tmp/temp/ [INFO ] Unmounting /dev/sdd1 /tmp/temp/ [INFO ] Unmounting /dev/sdd3 /tmp/temp/ [INFO ] Changing UUID/LABEL for /dev/sdd1 [INFO ] Old:da527931-ac9c-4c49-9c0c-6d7c414a44d3 New:a5381305-f382-44e0-ad98-4786d218b289 tune2fs 1.42.13 (17-May-2015) [INFO ] Changing UUID/LABEL for /dev/sdd2 [INFO ] Old:babd584c-ef9c-4480-80bd-643e7dd22d3e New:730bf048-9252-4564-8891-50bed55495f2 mkswap: /dev/sdd2: warning: wiping old swap signature. Setting up swapspace version 1, size = 244 MiB (255848448 bytes) no label, UUID=730bf048-9252-4564-8891-50bed55495f2 [INFO ] Changing UUID/LABEL for /dev/sdd3 [INFO ] Old:7c321d6b-f2b0-4783-9576-e3dfe657f9b3 New:5bb7ffd6-84eb-4a16-9a13-957d8f42388f tune2fs 1.42.13 (17-May-2015) -------------------------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------------------------- # blkid /dev/sdd* /dev/sdd: PTUUID="bcdd5210" PTTYPE="dos" /dev/sdd1: LABEL="_/boot" UUID="a5381305-f382-44e0-ad98-4786d218b289" TYPE="ext3" PARTUUID="bcdd5210-01" /dev/sdd2: UUID="730bf048-9252-4564-8891-50bed55495f2" TYPE="swap" PARTUUID="bcdd5210-02" /dev/sdd3: LABEL="_/" UUID="5bb7ffd6-84eb-4a16-9a13-957d8f42388f" TYPE="ext4" PARTUUID="bcdd5210-03" -------------------------------------------------------------------------------------------------------------------------------------------------------------------
Regards Mandar Joshi
On 12/28/2015 07:36 PM, Mandar Joshi wrote:
See how fedora-arm-installer forces an unmount of the partitions.
It seems to be doing "umount $MEDIA*" which I can't do from a python script. I have to iterate over a list of partitions and call umount on the individual partitions.
This is my output with a fresh install of the F22 image. Can you please post your output? and I think you are right, if we are discussing F22,
Actually they have shipped F23 and are gearing up for F24...
we should probably move this discussion to the Fedora Arm mailing list. I'll start a thread there. -------------------------------------------------------------------------------------------------------------------------------------------------------------------. # ./changeuuid.py change /dev/sdd /tmp/temp/ [INFO ] ['/dev/sdd1', '/dev/sdd2', '/dev/sdd3'] [INFO ] /dev/sdd1 ext3 da527931-ac9c-4c49-9c0c-6d7c414a44d3 a5381305-f382-44e0-ad98-4786d218b289 [INFO ] /dev/sdd2 swap babd584c-ef9c-4480-80bd-643e7dd22d3e 730bf048-9252-4564-8891-50bed55495f2 [INFO ] /dev/sdd3 ext4 7c321d6b-f2b0-4783-9576-e3dfe657f9b3 5bb7ffd6-84eb-4a16-9a13-957d8f42388f [INFO ] Unmounting all partitions on /dev/sdd umount: /dev/sdd1: not mounted umount: /dev/sdd2: not mounted umount: /dev/sdd3: not mounted [INFO ] Unmounting /dev/sdd1 /tmp/temp/ [INFO ] Mounting /dev/sdd3 /tmp/temp/ [INFO ] Processing File: /tmp/temp//etc/fstab **** Old /etc/fstab **** UUID=7c321d6b-f2b0-4783-9576-e3dfe657f9b3 / ext4 defaults,noatime 0 0 UUID=da527931-ac9c-4c49-9c0c-6d7c414a44d3 /boot ext3 defaults,noatime 0 0 UUID=babd584c-ef9c-4480-80bd-643e7dd22d3e swap swap defaults,noatime 0 0
**** New /etc/fstab **** UUID=5bb7ffd6-84eb-4a16-9a13-957d8f42388f / ext4 defaults,noatime 0 0 UUID=a5381305-f382-44e0-ad98-4786d218b289 /boot ext3 defaults,noatime 0 0 UUID=730bf048-9252-4564-8891-50bed55495f2 swap swap defaults,noatime 0 0
[INFO ] Writing /tmp/temp//etc/fstab [INFO ] Unmounting /tmp/temp/ [INFO ] Mounting /dev/sdd1 /tmp/temp/ [INFO ] Processing File: /tmp/temp//extlinux/extlinux.conf **** Old /extlinux/extlinux.conf **** # extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-22-3. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-22-3 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-22-3 (4.0.4-301.fc22.armv7hl) kernel /vmlinuz-4.0.4-301.fc22.armv7hl append ro root=UUID=7c321d6b-f2b0-4783-9576-e3dfe657f9b3 fdtdir /dtb-4.0.4-301.fc22.armv7hl/ initrd /initramfs-4.0.4-301.fc22.armv7hl.img
**** New /extlinux/extlinux.conf **** # extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-22-3. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-22-3 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-22-3 (4.0.4-301.fc22.armv7hl) kernel /vmlinuz-4.0.4-301.fc22.armv7hl append ro root=UUID=5bb7ffd6-84eb-4a16-9a13-957d8f42388f fdtdir /dtb-4.0.4-301.fc22.armv7hl/ initrd /initramfs-4.0.4-301.fc22.armv7hl.img
[INFO ] Writing /tmp/temp//extlinux/extlinux.conf [INFO ] Unmounting /tmp/temp/ [INFO ] Unmounting /dev/sdd1 /tmp/temp/ [INFO ] Unmounting /dev/sdd3 /tmp/temp/ [INFO ] Changing UUID/LABEL for /dev/sdd1 [INFO ] Old:da527931-ac9c-4c49-9c0c-6d7c414a44d3 New:a5381305-f382-44e0-ad98-4786d218b289 tune2fs 1.42.13 (17-May-2015) [INFO ] Changing UUID/LABEL for /dev/sdd2 [INFO ] Old:babd584c-ef9c-4480-80bd-643e7dd22d3e New:730bf048-9252-4564-8891-50bed55495f2 mkswap: /dev/sdd2: warning: wiping old swap signature. Setting up swapspace version 1, size = 244 MiB (255848448 bytes) no label, UUID=730bf048-9252-4564-8891-50bed55495f2 [INFO ] Changing UUID/LABEL for /dev/sdd3 [INFO ] Old:7c321d6b-f2b0-4783-9576-e3dfe657f9b3 New:5bb7ffd6-84eb-4a16-9a13-957d8f42388f tune2fs 1.42.13 (17-May-2015)
# blkid /dev/sdd* /dev/sdd: PTUUID="bcdd5210" PTTYPE="dos" /dev/sdd1: LABEL="_/boot" UUID="a5381305-f382-44e0-ad98-4786d218b289" TYPE="ext3" PARTUUID="bcdd5210-01" /dev/sdd2: UUID="730bf048-9252-4564-8891-50bed55495f2" TYPE="swap" PARTUUID="bcdd5210-02" /dev/sdd3: LABEL="_/" UUID="5bb7ffd6-84eb-4a16-9a13-957d8f42388f" TYPE="ext4" PARTUUID="bcdd5210-03"
Regards Mandar Joshi _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Actually they have shipped F23 and are gearing up for F24...
Oh. Well, if you could post the output of the changeuuid.py script, either here or there; I can have a look if anything is going wrong. To ease out your testing issues, instead of writing to a microSD everytime, you could uncompress from the original *.xz everytime and setup the raw image using losetup and partprobe before runnning ./changeuuid.py
# losetup /dev/loop0 <path/to/img> # partprobe /dev/loop0 # ./changeuuid.py change /dev/loop0 /tmp/temp/ # losetup -d /dev/loop0
Regards Mandar Joshi
On 12/28/2015 08:16 PM, Mandar Joshi wrote:
Actually they have shipped F23 and are gearing up for F24...
Oh. Well, if you could post the output of the changeuuid.py script,
So here is my first attempt:
# ./changeuuid.py pretend /dev/sdb /mnt [INFO ] ['/dev/sdb1', '/dev/sdb2', '/dev/sdb3'] [INFO ] /dev/sdb1 ext3 fa926fa0-ddcb-47ea-9731-ea5c92d9f959 7ecd1452-4878-445f-a3f7-78aace20b338 [INFO ] /dev/sdb2 swap 6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 6798ee01-c4a9-4a21-8862-19c67485e74c [INFO ] /dev/sdb3 ext4 770af0f9-c7d9-4ae9-b024-1ba3c78d7550 0ed99662-da6a-4da3-b88f-8e1f78330cbc [INFO ] Unmounting all partitions on /dev/sdb umount: /dev/sdb1: not mounted umount: /dev/sdb2: not mounted umount: /dev/sdb3: not mounted [INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Mounting /dev/sdb3 /mnt [INFO ] Processing File: /mnt/etc/fstab **** Old /etc/fstab **** #Generated by RootFS Build Factory UUID=fa926fa0-ddcb-47ea-9731-ea5c92d9f959 /boot ext3 noatime 0 0 UUID=6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 swap swap noatime 0 0 UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 / ext4 noatime 0 0
**** New /etc/fstab **** #Generated by RootFS Build Factory UUID=7ecd1452-4878-445f-a3f7-78aace20b338 /boot ext3 noatime 0 0 UUID=6798ee01-c4a9-4a21-8862-19c67485e74c swap swap noatime 0 0 UUID=0ed99662-da6a-4da3-b88f-8e1f78330cbc / ext4 noatime 0 0
[INFO ] Mounting /dev/sdb1 /mnt [INFO ] Processing File: /mnt/extlinux/extlinux.conf **** Old /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
**** New /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=0ed99662-da6a-4da3-b88f-8e1f78330cbc fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
[INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Unmounting /dev/sdb3 /mnt [INFO ] Changing UUID/LABEL for /dev/sdb1 [INFO ] Old:fa926fa0-ddcb-47ea-9731-ea5c92d9f959 New:7ecd1452-4878-445f-a3f7-78aace20b338 [INFO ] Changing UUID/LABEL for /dev/sdb2 [INFO ] Old:6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 New:6798ee01-c4a9-4a21-8862-19c67485e74c [INFO ] Changing UUID/LABEL for /dev/sdb3 [INFO ] Old:770af0f9-c7d9-4ae9-b024-1ba3c78d7550 New:0ed99662-da6a-4da3-b88f-8e1f78330cbc
====================
# ./changeuuid.py change /dev/sdb /mnt [INFO ] ['/dev/sdb1', '/dev/sdb2', '/dev/sdb3'] [INFO ] /dev/sdb1 ext3 fa926fa0-ddcb-47ea-9731-ea5c92d9f959 efdc3d68-a75f-428b-947c-27e2644b8e55 [INFO ] /dev/sdb2 swap 6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 1a5516ef-ee4e-4826-96d2-ea8536f83143 [INFO ] /dev/sdb3 ext4 770af0f9-c7d9-4ae9-b024-1ba3c78d7550 4931f2d3-3d01-4482-9134-735a930c27e3 [INFO ] Unmounting all partitions on /dev/sdb umount: /dev/sdb1: not mounted umount: /dev/sdb2: not mounted umount: /dev/sdb3: not mounted [INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Mounting /dev/sdb3 /mnt [INFO ] Processing File: /mnt/etc/fstab **** Old /etc/fstab **** #Generated by RootFS Build Factory UUID=fa926fa0-ddcb-47ea-9731-ea5c92d9f959 /boot ext3 noatime 0 0 UUID=6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 swap swap noatime 0 0 UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 / ext4 noatime 0 0
**** New /etc/fstab **** #Generated by RootFS Build Factory UUID=efdc3d68-a75f-428b-947c-27e2644b8e55 /boot ext3 noatime 0 0 UUID=1a5516ef-ee4e-4826-96d2-ea8536f83143 swap swap noatime 0 0 UUID=4931f2d3-3d01-4482-9134-735a930c27e3 / ext4 noatime 0 0
[INFO ] Writing /mnt/etc/fstab [INFO ] Unmounting /mnt [INFO ] Mounting /dev/sdb1 /mnt [INFO ] Processing File: /mnt/extlinux/extlinux.conf **** Old /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
**** New /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=4931f2d3-3d01-4482-9134-735a930c27e3 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
[INFO ] Writing /mnt/extlinux/extlinux.conf [INFO ] Unmounting /mnt [INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Unmounting /dev/sdb3 /mnt [INFO ] Changing UUID/LABEL for /dev/sdb1 [INFO ] Old:fa926fa0-ddcb-47ea-9731-ea5c92d9f959 New:efdc3d68-a75f-428b-947c-27e2644b8e55 tune2fs 1.42.12 (29-Aug-2014) [INFO ] Changing UUID/LABEL for /dev/sdb2 [INFO ] Old:6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 New:1a5516ef-ee4e-4826-96d2-ea8536f83143 mkswap: /dev/sdb2: warning: wiping old swap signature. Setting up swapspace version 1, size = 512 MiB (536866816 bytes) no label, UUID=1a5516ef-ee4e-4826-96d2-ea8536f83143 [INFO ] Changing UUID/LABEL for /dev/sdb3 [INFO ] Old:770af0f9-c7d9-4ae9-b024-1ba3c78d7550 New:4931f2d3-3d01-4482-9134-735a930c27e3 tune2fs 1.42.12 (29-Aug-2014)
=========
I now will unmount this and do it again.
On 12/28/2015 08:16 PM, Mandar Joshi wrote:
Actually they have shipped F23 and are gearing up for F24...
Oh. Well, if you could post the output of the changeuuid.py script, either here or there; I can have a look if anything is going wrong.
Round 2:
# ./changeuuid.py pretend /dev/sdb /mnt[INFO ] ['/dev/sdb1', '/dev/sdb2', '/dev/sdb3'] [INFO ] /dev/sdb1 ext3 fa926fa0-ddcb-47ea-9731-ea5c92d9f959 51571332-cef6-4a04-a3e9-3a78d716fed8 [INFO ] /dev/sdb2 swap 6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 ec4017fe-4dc7-4842-ae55-e9355c271947 [INFO ] /dev/sdb3 ext4 770af0f9-c7d9-4ae9-b024-1ba3c78d7550 5244b218-4c77-456e-9c83-ad5eeb32cb41 [INFO ] Unmounting all partitions on /dev/sdb umount: /dev/sdb1: not mounted umount: /dev/sdb2: not mounted umount: /dev/sdb3: not mounted [INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Mounting /dev/sdb3 /mnt [INFO ] Processing File: /mnt/etc/fstab **** Old /etc/fstab **** #Generated by RootFS Build Factory UUID=fa926fa0-ddcb-47ea-9731-ea5c92d9f959 /boot ext3 noatime 0 0 UUID=6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 swap swap noatime 0 0 UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 / ext4 noatime 0 0
**** New /etc/fstab **** #Generated by RootFS Build Factory UUID=51571332-cef6-4a04-a3e9-3a78d716fed8 /boot ext3 noatime 0 0 UUID=ec4017fe-4dc7-4842-ae55-e9355c271947 swap swap noatime 0 0 UUID=5244b218-4c77-456e-9c83-ad5eeb32cb41 / ext4 noatime 0 0
[INFO ] Mounting /dev/sdb1 /mnt [INFO ] Processing File: /mnt/extlinux/extlinux.conf **** Old /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
**** New /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=5244b218-4c77-456e-9c83-ad5eeb32cb41 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
[INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Unmounting /dev/sdb3 /mnt [INFO ] Changing UUID/LABEL for /dev/sdb1 [INFO ] Old:fa926fa0-ddcb-47ea-9731-ea5c92d9f959 New:51571332-cef6-4a04-a3e9-3a78d716fed8 [INFO ] Changing UUID/LABEL for /dev/sdb2 [INFO ] Old:6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 New:ec4017fe-4dc7-4842-ae55-e9355c271947 [INFO ] Changing UUID/LABEL for /dev/sdb3 [INFO ] Old:770af0f9-c7d9-4ae9-b024-1ba3c78d7550 New:5244b218-4c77-456e-9c83-ad5eeb32cb41
==============
# ./changeuuid.py change /dev/sdb /mnt[INFO ] ['/dev/sdb1', '/dev/sdb2', '/dev/sdb3'] [INFO ] /dev/sdb1 ext3 fa926fa0-ddcb-47ea-9731-ea5c92d9f959 607a8ac9-8ffc-47d7-8666-fe689dc16bed [INFO ] /dev/sdb2 swap 6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 054b606f-b169-4f1d-8fac-10edef957fec [INFO ] /dev/sdb3 ext4 770af0f9-c7d9-4ae9-b024-1ba3c78d7550 e6e8388e-4c7d-4e76-8936-6ba3a45c0927 [INFO ] Unmounting all partitions on /dev/sdb umount: /dev/sdb1: not mounted umount: /dev/sdb2: not mounted umount: /dev/sdb3: not mounted [INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Mounting /dev/sdb3 /mnt [INFO ] Processing File: /mnt/etc/fstab **** Old /etc/fstab **** #Generated by RootFS Build Factory UUID=fa926fa0-ddcb-47ea-9731-ea5c92d9f959 /boot ext3 noatime 0 0 UUID=6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 swap swap noatime 0 0 UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 / ext4 noatime 0 0
**** New /etc/fstab **** #Generated by RootFS Build Factory UUID=607a8ac9-8ffc-47d7-8666-fe689dc16bed /boot ext3 noatime 0 0 UUID=054b606f-b169-4f1d-8fac-10edef957fec swap swap noatime 0 0 UUID=e6e8388e-4c7d-4e76-8936-6ba3a45c0927 / ext4 noatime 0 0
[INFO ] Writing /mnt/etc/fstab [INFO ] Unmounting /mnt [INFO ] Mounting /dev/sdb1 /mnt [INFO ] Processing File: /mnt/extlinux/extlinux.conf **** Old /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
**** New /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=e6e8388e-4c7d-4e76-8936-6ba3a45c0927 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
[INFO ] Writing /mnt/extlinux/extlinux.conf [INFO ] Unmounting /mnt [INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Unmounting /dev/sdb3 /mnt [INFO ] Changing UUID/LABEL for /dev/sdb1 [INFO ] Old:fa926fa0-ddcb-47ea-9731-ea5c92d9f959 New:607a8ac9-8ffc-47d7-8666-fe689dc16bed tune2fs 1.42.12 (29-Aug-2014) [INFO ] Changing UUID/LABEL for /dev/sdb2 [INFO ] Old:6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 New:054b606f-b169-4f1d-8fac-10edef957fec mkswap: /dev/sdb2: warning: wiping old swap signature. Setting up swapspace version 1, size = 512 MiB (536866816 bytes) no label, UUID=054b606f-b169-4f1d-8fac-10edef957fec [INFO ] Changing UUID/LABEL for /dev/sdb3 [INFO ] Old:770af0f9-c7d9-4ae9-b024-1ba3c78d7550 New:e6e8388e-4c7d-4e76-8936-6ba3a45c0927 tune2fs 1.42.12 (29-Aug-2014)
========
I then did a new mSD and just did a change without the pretend:
# ./changeuuid.py change /dev/sdb /mnt[INFO ] ['/dev/sdb1', '/dev/sdb2', '/dev/sdb3'] [INFO ] /dev/sdb1 ext3 fa926fa0-ddcb-47ea-9731-ea5c92d9f959 5e01ccaa-561a-474d-ab1a-7ba5b94d3db9 [INFO ] /dev/sdb2 swap 6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 a6f62d25-c7a9-4445-b8a2-692a7a834245 [INFO ] /dev/sdb3 ext4 770af0f9-c7d9-4ae9-b024-1ba3c78d7550 11ec1de2-d656-4aa5-93b6-2f73182b89d4 [INFO ] Unmounting all partitions on /dev/sdb umount: /dev/sdb1: not mounted umount: /dev/sdb2: not mounted umount: /dev/sdb3: not mounted [INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Mounting /dev/sdb3 /mnt [INFO ] Processing File: /mnt/etc/fstab **** Old /etc/fstab **** #Generated by RootFS Build Factory UUID=fa926fa0-ddcb-47ea-9731-ea5c92d9f959 /boot ext3 noatime 0 0 UUID=6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 swap swap noatime 0 0 UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 / ext4 noatime 0 0
**** New /etc/fstab **** #Generated by RootFS Build Factory UUID=5e01ccaa-561a-474d-ab1a-7ba5b94d3db9 /boot ext3 noatime 0 0 UUID=a6f62d25-c7a9-4445-b8a2-692a7a834245 swap swap noatime 0 0 UUID=11ec1de2-d656-4aa5-93b6-2f73182b89d4 / ext4 noatime 0 0
[INFO ] Writing /mnt/etc/fstab [INFO ] Unmounting /mnt [INFO ] Mounting /dev/sdb1 /mnt [INFO ] Processing File: /mnt/extlinux/extlinux.conf **** Old /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=770af0f9-c7d9-4ae9-b024-1ba3c78d7550 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
**** New /extlinux/extlinux.conf **** #Created by RootFS Build Factory ui menu.c32 menu autoboot centos menu title centos Options #menu hidden timeout 60 totaltimeout 600 label centos kernel /vmlinuz-4.2.3-200.el7.armv7hl append enforcing=0 root=UUID=11ec1de2-d656-4aa5-93b6-2f73182b89d4 fdtdir /dtb-4.2.3-200.el7.armv7hl initrd /initramfs-4.2.3-200.el7.armv7hl.img
[INFO ] Writing /mnt/extlinux/extlinux.conf [INFO ] Unmounting /mnt [INFO ] Unmounting /dev/sdb1 /mnt [INFO ] Unmounting /dev/sdb3 /mnt [INFO ] Changing UUID/LABEL for /dev/sdb1 [INFO ] Old:fa926fa0-ddcb-47ea-9731-ea5c92d9f959 New:5e01ccaa-561a-474d-ab1a-7ba5b94d3db9 tune2fs 1.42.12 (29-Aug-2014) [INFO ] Changing UUID/LABEL for /dev/sdb2 [INFO ] Old:6d5e843e-7dd8-4d70-a08e-4ee9d26828d7 New:a6f62d25-c7a9-4445-b8a2-692a7a834245 mkswap: /dev/sdb2: warning: wiping old swap signature. Setting up swapspace version 1, size = 512 MiB (536866816 bytes) no label, UUID=a6f62d25-c7a9-4445-b8a2-692a7a834245 [INFO ] Changing UUID/LABEL for /dev/sdb3 [INFO ] Old:770af0f9-c7d9-4ae9-b024-1ba3c78d7550 New:11ec1de2-d656-4aa5-93b6-2f73182b89d4 tune2fs 1.42.12 (29-Aug-2014)
SEEMS to be working right now, but then why not before...
hmmmmm.
When the system was going bad, I first did a dnf update, as I was a few weeks behind. Perhaps I picked up something new and useful?
On 12/28/2015 10:25 PM, Mandar Joshi wrote:
Round 2:
Well if something going wrong again, please post this output. Just to clarify, between 'Round 1' and 'Round 2', you re-wrote the image to the microSD card?
Yes. Every time. I have LOTS of mSD cards here.
On 12/28/2015 07:36 PM, Mandar Joshi wrote:
See how fedora-arm-installer forces an unmount of the partitions.
It seems to be doing "umount $MEDIA*" which I can't do from a python script. I have to iterate over a list of partitions and call umount on the individual partitions.
But if you look in that script you will see variable names for boot and rootfs, and it would not be hard to figure out swap.
This is my output with a fresh install of the F22 image. Can you please post your output? and I think you are right, if we are discussing F22, we should probably move this discussion to the Fedora Arm mailing list. I'll start a thread there. -------------------------------------------------------------------------------------------------------------------------------------------------------------------. # ./changeuuid.py change /dev/sdd /tmp/temp/ [INFO ] ['/dev/sdd1', '/dev/sdd2', '/dev/sdd3'] [INFO ] /dev/sdd1 ext3 da527931-ac9c-4c49-9c0c-6d7c414a44d3 a5381305-f382-44e0-ad98-4786d218b289 [INFO ] /dev/sdd2 swap babd584c-ef9c-4480-80bd-643e7dd22d3e 730bf048-9252-4564-8891-50bed55495f2 [INFO ] /dev/sdd3 ext4 7c321d6b-f2b0-4783-9576-e3dfe657f9b3 5bb7ffd6-84eb-4a16-9a13-957d8f42388f [INFO ] Unmounting all partitions on /dev/sdd umount: /dev/sdd1: not mounted umount: /dev/sdd2: not mounted umount: /dev/sdd3: not mounted [INFO ] Unmounting /dev/sdd1 /tmp/temp/ [INFO ] Mounting /dev/sdd3 /tmp/temp/ [INFO ] Processing File: /tmp/temp//etc/fstab **** Old /etc/fstab **** UUID=7c321d6b-f2b0-4783-9576-e3dfe657f9b3 / ext4 defaults,noatime 0 0 UUID=da527931-ac9c-4c49-9c0c-6d7c414a44d3 /boot ext3 defaults,noatime 0 0 UUID=babd584c-ef9c-4480-80bd-643e7dd22d3e swap swap defaults,noatime 0 0
**** New /etc/fstab **** UUID=5bb7ffd6-84eb-4a16-9a13-957d8f42388f / ext4 defaults,noatime 0 0 UUID=a5381305-f382-44e0-ad98-4786d218b289 /boot ext3 defaults,noatime 0 0 UUID=730bf048-9252-4564-8891-50bed55495f2 swap swap defaults,noatime 0 0
[INFO ] Writing /tmp/temp//etc/fstab [INFO ] Unmounting /tmp/temp/ [INFO ] Mounting /dev/sdd1 /tmp/temp/ [INFO ] Processing File: /tmp/temp//extlinux/extlinux.conf **** Old /extlinux/extlinux.conf **** # extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-22-3. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-22-3 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-22-3 (4.0.4-301.fc22.armv7hl) kernel /vmlinuz-4.0.4-301.fc22.armv7hl append ro root=UUID=7c321d6b-f2b0-4783-9576-e3dfe657f9b3 fdtdir /dtb-4.0.4-301.fc22.armv7hl/ initrd /initramfs-4.0.4-301.fc22.armv7hl.img
**** New /extlinux/extlinux.conf **** # extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Fedora-Minimal-armhfp-22-3. Automatic boot in # second{,s}. Press a key for options. menu title Fedora-Minimal-armhfp-22-3 Boot Options. menu hidden timeout 20 totaltimeout 600
label Fedora-Minimal-armhfp-22-3 (4.0.4-301.fc22.armv7hl) kernel /vmlinuz-4.0.4-301.fc22.armv7hl append ro root=UUID=5bb7ffd6-84eb-4a16-9a13-957d8f42388f fdtdir /dtb-4.0.4-301.fc22.armv7hl/ initrd /initramfs-4.0.4-301.fc22.armv7hl.img
[INFO ] Writing /tmp/temp//extlinux/extlinux.conf [INFO ] Unmounting /tmp/temp/ [INFO ] Unmounting /dev/sdd1 /tmp/temp/ [INFO ] Unmounting /dev/sdd3 /tmp/temp/ [INFO ] Changing UUID/LABEL for /dev/sdd1 [INFO ] Old:da527931-ac9c-4c49-9c0c-6d7c414a44d3 New:a5381305-f382-44e0-ad98-4786d218b289 tune2fs 1.42.13 (17-May-2015) [INFO ] Changing UUID/LABEL for /dev/sdd2 [INFO ] Old:babd584c-ef9c-4480-80bd-643e7dd22d3e New:730bf048-9252-4564-8891-50bed55495f2 mkswap: /dev/sdd2: warning: wiping old swap signature. Setting up swapspace version 1, size = 244 MiB (255848448 bytes) no label, UUID=730bf048-9252-4564-8891-50bed55495f2 [INFO ] Changing UUID/LABEL for /dev/sdd3 [INFO ] Old:7c321d6b-f2b0-4783-9576-e3dfe657f9b3 New:5bb7ffd6-84eb-4a16-9a13-957d8f42388f tune2fs 1.42.13 (17-May-2015)
# blkid /dev/sdd* /dev/sdd: PTUUID="bcdd5210" PTTYPE="dos" /dev/sdd1: LABEL="_/boot" UUID="a5381305-f382-44e0-ad98-4786d218b289" TYPE="ext3" PARTUUID="bcdd5210-01" /dev/sdd2: UUID="730bf048-9252-4564-8891-50bed55495f2" TYPE="swap" PARTUUID="bcdd5210-02" /dev/sdd3: LABEL="_/" UUID="5bb7ffd6-84eb-4a16-9a13-957d8f42388f" TYPE="ext4" PARTUUID="bcdd5210-03"
Regards Mandar Joshi _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-
Karanbir Singh -
Mandar Joshi -
Manuel Wolfshant -
Robert Moskowitz