On 2/20/2014 17:03, Chris Murphy wrote: > > On Feb 18, 2014, at 3:46 PM, Don Levey <fedora-list@xxxxxxxxxxxxx> wrote: > >> ... >> After several weeks of schedule hell, I was finally able to work on >> this. The upshot is that the previously installed kernels weren't >> available (so I had to pull the more recent available one), I got some >> errors on the grub2 commands, > > What commands and errors? > Disk /dev/sda: 160.0 GB, 160000000000 bytes, 312500000 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0xe686f016 Device Boot Start End Blocks Id System /dev/sda1 63 102760511 51380224+ 7 HPFS/NTFS/exFAT /dev/sda2 * 102760512 103170111 204800 83 Linux /dev/sda3 103170112 312496379 104663134 8e Linux LVM [root@localhost /]# grub2-install /dev/sda WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. Found duplicate PV ViBcLU2wBD0Yv1UCFdxM4LQxAY4mFj1f: using /dev/sdc3 not /dev/sda3 /usr/sbin/grub2-bios-setup: warning: your core.img is unusually large. It won't fit in the embedding area. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install. I am wondering about the /dev/sda vs /dev/sdc thing shown above, but this is a hardware RAID situation; could it be that /dev/sdc is the RAID itself while sda/b are the individual parts? -Don -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx 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
