CentOS - Jan 2017 - Strange (?) device.map in CentOS 7 VM installations

On 01/04/2017 03:07 AM, Nikolaos Milas wrote:
> Is it normal in CentOS 7 to have a device map with two entries esp. 
> when the (physical or virtual) hardware  has only one hd ? 

I don't see that on VMs that I manage.  Some of the physical machines 
that I manage do have duplicates in the device.map.

On 4/1/2017 7:37 ??, Gordon Messmer wrote:
> I don't see that on VMs that I manage.  Some of the physical machines 
> that I manage do have duplicates in the device.map. 
Thank you Gordon for your feedback!

Can others please report the content of /boot/grub2/device.map on their 
CentOS 7 (physical or virtual) installations?

And can any tech geek please explain when why do we have these 
duplicates and if they are intentional or not?

Thanks,
Nick

On Thu, Jan 5, 2017 at 4:04 AM, Nikolaos Milas <nmilas at noa.gr> wrote:
> On 4/1/2017 7:37 ??, Gordon Messmer wrote:
>
> I don't see that on VMs that I manage.  Some of the physical machines
that
>> I manage do have duplicates in the device.map.
>>
>
> Thank you Gordon for your feedback!
>
> Can others please report the content of /boot/grub2/device.map on their
> CentOS 7 (physical or virtual) installations?
>
On my CentOS7 installs I find dups too.

Physical
# this device map was generated by anaconda
(hd0)      /dev/sda
(hd1)      /dev/sda

Virtual (KVM VM)
# this device map was generated by anaconda
(hd0)      /dev/vda
(hd1)      /dev/vda

-- 
---~~.~~---
Mike
//  SilverTip257  //

On 5/1/2017 11:04 ??, Nikolaos Milas wrote:
> Can others please report the content of /boot/grub2/device.map on 
> their CentOS 7 (physical or virtual) installations?
Thank you all for your reports. Since it seems this is generally the 
case with CentOS 7, does anyone also have access to RHEL 7 installations 
to verify if this is the case with these installations as well?
> And can any tech geek please explain when/why do we have these 
> "duplicates" and if they are intentional or not?
Any feedback regarding this "issue" and its possible repercussions
will
be appreciated!

Thanks a lot,
Nick