Re: Re: grub2-install: Couldn't find physical volume ‘(null)’.

[Andrei Borzenkov]

On Mon, Apr 11, 2016 at 1:56 PM, Sam Varshavchik <address@hidden> wrote:
> Andrei Borzenkov writes:
>
>> 11.04.2016 05:03, Sam Varshavchik пишет:
>> > grub 2.02, Fedora x86-64.
>> >
>> > I have /dev/sda and /dev/sdb in a RAID-1 configuration. This is the
>> > Linux kernel's md-raid driver.
>> >
>> > /dev/sda started failing SMART.
>> >
>> > I ran /sbin/grub2-install /dev/sdb. My recollection is that it ran
>> > without any complaints.
>> >
>> > After that, I yanked out /dev/sda. I reattached /dev/sdb as /dev/sda,
>> > and put in a new hard drive as the new /dev/sdb.
>> >
>> > I booted up, and kicked off a rebuild of my RAID-1 volumes, everything
>> > is going well.
>> >
>> > Now, after all of that was done, I decided to install grub2 on the new
>> > /dev/sdb:
>> >
>> > address@hidden ~]# /sbin/grub2-install /dev/sdb
>> > Installing for i386-pc platform.
>> > /sbin/grub2-install: warning: Couldn't find physical volume ‘(null)’.
>> > Some modules may be missing from core image..
>> > /sbin/grub2-install: warning: Couldn't find physical volume ‘(null)’.
>> > Some modules may be missing from core image..
>> > Installation finished. No error reported.
>> >
>> > Now, anyone have any idea what's up with these warnings?
>> >
>>
>> Could you show output of "mdadm --detail" for your MD device?
>
>
> Below.
>
> Googling around finds some references of this warning coming out while the
> md-raid volumes are being synced. This warning still comes out after
> everything is fully synced up.
>

Which device is your /boot?