Re: grub configuration, boot.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thursday December 24 2009 13:25:11 Chris Smart wrote:
> 2009/12/24 Dj YB <yehielb@xxxxxxx>:
> > thanks
> > I have noticed that the uuids  are the same
> > how do you suggest doing what you said, and how do i make grub use this
> > idntification
> > and uuids?
> > YB
> 
> Boot your normal Fedora, once booted plug in the USB drive.
> 
> Scan for and activate all lvm volumes:
> su -c "vgscan && vgchange -ay"
> 
> Then have a look at what volumes you have. The first VolGroup should
> be your internal drive.
> 
> You'll need to run something like:
> su -c "vgrename VolGroup1 usbdrive"
> 
> You can tell grub to boot the USB drive by replacing its GRUB entry
> from root=blahblah with root=/dev/mapper/usbdrive-lv_root
> 
> Of course, your initramfs also needs to support booting from USB..
> 
> -c
> 
thanks
this is vgscan output:

[root@localhost djyb]# vgscan
File descriptor 3 (/proc/16681/status) leaked on vgscan invocation. Parent PID 
16857: bash
File descriptor 4 (/lib/libnspr4.so) leaked on vgscan invocation. Parent PID 
16857: bash
File descriptor 5 (/lib/libnspr4.so) leaked on vgscan invocation. Parent PID 
16857: bash
File descriptor 6 (/dev/nvidiactl) leaked on vgscan invocation. Parent PID 
16857: bash
File descriptor 7 (/dev/nvidia0) leaked on vgscan invocation. Parent PID 
16857: bash
File descriptor 8 (/dev/nvidia0) leaked on vgscan invocation. Parent PID 
16857: bash
File descriptor 9 (/dev/nvidia0) leaked on vgscan invocation. Parent PID 
16857: bash
File descriptor 10 (/dev/nvidia0) leaked on vgscan invocation. Parent PID 
16857: bash
File descriptor 11 (inotify) leaked on vgscan invocation. Parent PID 16857: 
bash
  Reading all physical volumes.  This may take a while...
  Found duplicate PV OZG9Z5DZ1BG0aN0uFilnjKpoluv1iKzZ: using /dev/sdf2 not 
/dev/sdb2
  Found volume group "VolGroup" using metadata type lvm2


while sdf is the usb-hdd and sdb is the internal hdd.

this is vgchange output:

[root@localhost djyb]# vgchange -ay
File descriptor 3 (/proc/16681/status) leaked on vgchange invocation. Parent 
PID 16857: bash
File descriptor 4 (/lib/libnspr4.so) leaked on vgchange invocation. Parent PID 
16857: bash
File descriptor 5 (/lib/libnspr4.so) leaked on vgchange invocation. Parent PID 
16857: bash
File descriptor 6 (/dev/nvidiactl) leaked on vgchange invocation. Parent PID 
16857: bash
File descriptor 7 (/dev/nvidia0) leaked on vgchange invocation. Parent PID 
16857: bash
File descriptor 8 (/dev/nvidia0) leaked on vgchange invocation. Parent PID 
16857: bash
File descriptor 9 (/dev/nvidia0) leaked on vgchange invocation. Parent PID 
16857: bash
File descriptor 10 (/dev/nvidia0) leaked on vgchange invocation. Parent PID 
16857: bash
File descriptor 11 (inotify) leaked on vgchange invocation. Parent PID 16857: 
bash
  Found duplicate PV OZG9Z5DZ1BG0aN0uFilnjKpoluv1iKzZ: using /dev/sdf2 not 
/dev/sdb2
  2 logical volume(s) in volume group "VolGroup" now active

this is vgrename output:

[root@localhost djyb]# vgrename VolGroup usbFC11
File descriptor 3 (/proc/16681/status) leaked on vgrename invocation. Parent 
PID 16857: bash
File descriptor 4 (/lib/libnspr4.so) leaked on vgrename invocation. Parent PID 
16857: bash
File descriptor 5 (/lib/libnspr4.so) leaked on vgrename invocation. Parent PID 
16857: bash
File descriptor 6 (/dev/nvidiactl) leaked on vgrename invocation. Parent PID 
16857: bash
File descriptor 7 (/dev/nvidia0) leaked on vgrename invocation. Parent PID 
16857: bash
File descriptor 8 (/dev/nvidia0) leaked on vgrename invocation. Parent PID 
16857: bash
File descriptor 9 (/dev/nvidia0) leaked on vgrename invocation. Parent PID 
16857: bash
File descriptor 10 (/dev/nvidia0) leaked on vgrename invocation. Parent PID 
16857: bash
File descriptor 11 (inotify) leaked on vgrename invocation. Parent PID 16857: 
bash
  Found duplicate PV OZG9Z5DZ1BG0aN0uFilnjKpoluv1iKzZ: using /dev/sdf2 not 
/dev/sdb2
  Volume group "VolGroup" still has active LVs

I have no idea what to do next, please help
thanks a lot,
YB.

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux