Hi
I just updated a computer from Fedora 19 to 21. I did it by adding a second SSD to the computer on which I installed F21. The problem is now that I can't access the files from the old SSD. They seem to be overshadowed as the volume group has the same name as the new installation.
Any way to get access to the old disk in this new setting?
/Markus
This is what I see in the log when I attach the disk
kernel: sd 7:0:0:0: [sdb] Attached SCSI disk lvm[2859]: device-mapper: create ioctl on fedora-swap failed: Device or resource busy lvm[2859]: device-mapper: create ioctl on fedora-home failed: Device or resource busy lvm[2859]: device-mapper: create ioctl on fedora-root failed: Device or resource busy lvm[2859]: 0 logical volume(s) in volume group "fedora" now active lvm[2859]: fedora: autoactivation failed. kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) kernel: SELinux: initialized (dev sdb1, type ext4), uses xattr udisksd[1680]: Mounted /dev/sdb1 at /run/media/mli/e746019e-de05-40e6-9883-daf16e8c929a on behalf of uid 1000
/dev/sdb1 is the old boot partition
On 18 December 2014 at 14:47, Markus Lindholm markus.lindholm@gmail.com wrote:
Hi
I just updated a computer from Fedora 19 to 21. I did it by adding a second SSD to the computer on which I installed F21. The problem is now that I can't access the files from the old SSD. They seem to be overshadowed as the volume group has the same name as the new installation.
Any way to get access to the old disk in this new setting?
/Markus
vgrename can rename using a uuid to know who to rename, so rename it to something that does not conflict.
On Thu, Dec 18, 2014 at 8:27 AM, Markus Lindholm markus.lindholm@gmail.com wrote:
This is what I see in the log when I attach the disk
kernel: sd 7:0:0:0: [sdb] Attached SCSI disk lvm[2859]: device-mapper: create ioctl on fedora-swap failed: Device or resource busy lvm[2859]: device-mapper: create ioctl on fedora-home failed: Device or resource busy lvm[2859]: device-mapper: create ioctl on fedora-root failed: Device or resource busy lvm[2859]: 0 logical volume(s) in volume group "fedora" now active lvm[2859]: fedora: autoactivation failed. kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) kernel: SELinux: initialized (dev sdb1, type ext4), uses xattr udisksd[1680]: Mounted /dev/sdb1 at /run/media/mli/e746019e-de05-40e6-9883-daf16e8c929a on behalf of uid 1000
/dev/sdb1 is the old boot partition
On 18 December 2014 at 14:47, Markus Lindholm markus.lindholm@gmail.com wrote:
Hi
I just updated a computer from Fedora 19 to 21. I did it by adding a second SSD to the computer on which I installed F21. The problem is now that I can't access the files from the old SSD. They seem to be overshadowed as the volume group has the same name as the new installation.
Any way to get access to the old disk in this new setting?
/Markus
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 18 December 2014 at 15:50, Roger Heflin rogerheflin@gmail.com wrote:
vgrename can rename using a uuid to know who to rename, so rename it to something that does not conflict.
Thanks, vgrename solved the conflict.
/Markus
On Thu, Dec 18, 2014 at 6:47 AM, Markus Lindholm markus.lindholm@gmail.com wrote:
Hi
I just updated a computer from Fedora 19 to 21. I did it by adding a second SSD to the computer on which I installed F21. The problem is now that I can't access the files from the old SSD. They seem to be overshadowed as the volume group has the same name as the new installation.
Odd. The Fedora 21 installer should have avoided using the same VG name as before. I just tried this with Fedora 20 and 21. Both default to VG name "fedora" but Fedora 21's installer knows to add numbers if "fedora" already exists. This is what I end up with:
[root@f21s ~]# lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert home fedora -wi-ao---- 27.49g root fedora -wi-ao---- 50.00g swap fedora -wi-ao---- 2.02g home fedora00 -wi-a----- 27.45g root fedora00 -wi-a----- 50.00g swap fedora00 -wi-a----- 2.00g
And hence no conflict.
Any way to get access to the old disk in this new setting?
vgrename
And then you need to make sure that you update grub.cfg and fstab or you won't be able to boot. There's also a chance you'll need to rebuild the initramfs too. So I suggest you pick which VG you want to rename, and boot that instance first. Do the rename, change the fstab, dracut -f, and then grub2-mkconfig -o /boot/grub2/grub.cfg.
On 18 December 2014 at 18:52, Chris Murphy lists@colorremedies.com wrote:
On Thu, Dec 18, 2014 at 6:47 AM, Markus Lindholm markus.lindholm@gmail.com wrote:
Hi
I just updated a computer from Fedora 19 to 21. I did it by adding a second SSD to the computer on which I installed F21. The problem is now that I can't access the files from the old SSD. They seem to be overshadowed as the volume group has the same name as the new installation.
Odd. The Fedora 21 installer should have avoided using the same VG name as before. I just tried this with Fedora 20 and 21. Both default to VG name "fedora" but Fedora 21's installer knows to add numbers if "fedora" already exists. This is what I end up with:
Ah, I physically disconnected the old disk during installation of F21, as it is identical in size with the new one. Just to make sure I wouldn't mix the two during installation.
/Markus
-
Chris Murphy -
Markus Lindholm -
Roger Heflin