Hi.
I've done some attempts and following a guide for ubunto I got some
improvements.

At the moment  the normal.mod is in the boot partition and I'm not starting
with the grub2 rescue terminal but with still the selection menu doesn' t
appear and the system doesn' t boot.

At the moment the system get stuck on:
   grub2>
prompt.

I dug a littel in the system and
   - the boot flag still points to the sda2 (the dell recopvery partition)
instead of the one with /boot partition (sda5)
   - in /etc there is a grub2.cfg file that it is a dangling link to
/boot/grub2/grub.cfg
probably both of these points are part of the problem.

Looking around I found some guides about ubunto (e.g.,
https://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-grub-2-on-linux/)
that uses an update-grub command to create the boot loader but I can' t
find anything like that for fedora. What I'm I doing wrong now?

Walter

On Wed, Dec 23, 2015 at 1:08 PM, Doug H. <fedoraproject....@wombatz.com>
wrote:

> On Wed, 2015-12-23 at 11:48 -0500, Walter Cazzola wrote:
> > Hi
> > few more questions inline with your reply.
>
> >  chroot /mnt/sysimage
> > what should sysimage be? is this a file in the /boot partition? I
> > don't have any file with this name in /boot
>
> Historically (and currently I think), the rescue/repair option for the
> Fedora CD & DVD is to look for a Fedora install and then mount it in
> /mnt/sysimage.  So there would be a /mnt/sysimage/boot for example.
> Thus you can do `chroot /mnt/sysimage` and the shell will act like you
> are simply logged into the Fedora system.  Things would work as if you
> had booted normally into the Fedora system.  That allows you to do
> maintenance using the same full paths as "normal".
>
>
> > >  fdisk /dev/sda
> > >  Command (m for help): a
> > >  Partition number ([snip] default x): 5
> > >  Command (m for help): w
> > >  The partition table has been altered.
> > >  Calling ioctl() to re-read partition table.
> > do the numbers already refer to my partitions or I've to change
> > something? what should this do?
>
> I ran an fdisk on a temp loopfile and then altered the output to show
> "5" since I think that is the partition that I think might need to be
> bootable.  What that does is to make partition 5 the boot/bootable
> partition.  I don't really know how that works at a deeper level and I
> have little experience with efi so far.  My suggestions are based on
> the idea that your bios setup is presenting a traditional/older system
> type.
>
>
> > >  grub2-install /dev/sda
> > if this doesn't work can I go back to the previous situation? if yes
> > how?
>
> The above assumes that your Windows boot utility has already been
> messed with and is not usable at the moment.  If that is true then I am
> not even sure you need to do the grub2-install but it seems like it
> would not make it worse.
>
> But again I don't feel comfortable suggesting these actions unless we
> get some community support for it.
>
> --
> Doug H.
>



--
-- 
users mailing list
users@lists.fedoraproject.org
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

Reply via email to