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(a)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(a)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(a)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