On Nov 20, 2016 4:55 PM, "jd1008" <jd1008@gmail.com> wrote:
>
>
>
> On 11/20/2016 02:15 PM, peterlesterhuis@telfort.nl wrote:
>>
>> Hi,
>> After a Windows update my (dual boot) system won't boot into fedora anymore.
>> Somehow the grub bootloader doesn' t start.
>>
>> After booting this is what I see:
>>
>> /Minimal Bash-like line editing is supported. For the first word TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
>>
>> grub>_/
>>
>>
>> When I issue the command "exit" the Windows bootloader pops up.
>>
>> I googled on this subject, but found many completely different answers.
>> I would appreciate any suggestion. How can I recover my system?
>
> The Solution:
> 01. Boot a live fedora cd or dvd
> 02. mount your on-disk  fedora linux on .... say /fedora, like so:
>       mkdir /fedora
>       mount /dev/sd??  /fedora   # where ?? is the disk and partition where your fedora is installed.
> 03. tar cf - dev   | tar -C /fedora -xpvf -
> 04. chroot /fedora
> 05. grub2-install --recheck  /dev/sd??
> 06. grub2-mkconfig -o /etc/grub2.cfg
>
> When the command (at point 8) returns, then
> 07. cd /dev
> 08. rm -rf *
> Why? because /dev/  is populated  dynamically at boot time.
>
> Let the list know how it went.
>
> _______________________________________________

This tar+rm business with dev looks confusing and dangerous.  Use bind mounts to place the virtual filesystems in the chroot path.

-- Pete