On 18 December 2014 at 18:52, Chris Murphy wrote:
> On Thu, Dec 18, 2014 at 6:47 AM, Markus Lindholm
> 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 file
On 18 December 2014 at 15:50, Roger Heflin 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
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription
On Thu, Dec 18, 2014 at 6:47 AM, Markus Lindholm
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 vo
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
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: cre
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: cr
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 ge
