Reinstalled Qubes 3.2 -> /grub2/i386-pc/normal.mod not found

58 views
Skip to first unread message

[799]

unread,
Oct 30, 2017, 2:27:57 PM10/30/17
to qubes-users
Hello,

After Qubes 4 wasn't working for me I reinstalled Qubes 3.2 but on the first boot I get the following error message:

error: file '/grub2/i386-pc/normal.mod' not found.
Entering rescue mode...

I had 4 partitions before:

/dev/hda1 = windows boot
/dev/hda1 = windows 10
/dev/hda3 = Qubes boot
/dev/hda4 = logical partition
/dev/hda5 = Qubes LUKS partition

I tried to install Qubes a second time but iI get the same Error message.

I booted with a gparted Live disk and changed to boot flag from /dev/hda1 to /dev/hda3 still the same problem.

Any idea where to go from here?

[799]



[799]

unread,
Oct 30, 2017, 2:43:06 PM10/30/17
to qubes...@googlegroups.com
Additional information:
I found out that Qubes didn't boot into /dev/sda3 but in /dev/sda5 which can't be started as this is not primary partition.
See also my attached screenshot.

I have mounted both partition with a live Linux and copied all files from /dev/sda5 to /dev/sda3.
I have also edited in /dev/sda3 grub2/grub.cfg and edited all entries which said msdos5 and changed it to msdos3.
Not sure if I need to changes some more lines and what to do afterwards.

As far as I know there are also references which are referenced to with a UUID (some weirds long numbers/characters) - do I need to change them also?

Also do I need to run a specific Grub command to apply the manually modified grub.cfg?

I tried to boot up, but run into the same error.
How can I reinstalled Qubes 3.2 and force it to use dev/sda3 as boot not a logical partition?

[799]


Gesendet von ProtonMail mobile



-------- Original-Nachricht --------
--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/_3tyghg4Vw7vQiie4gA8Cs_QidAzs5OPKo4fMNymrggMbS58D02Y_ebWic8ohUb1xEDvHOlVckWi-mwiflRNVVWcyJJ6_2Zndo2sJzJ-vPE%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

awokd

unread,
Oct 30, 2017, 4:16:21 PM10/30/17
to [799], qubes...@googlegroups.com
Try repeating the Qubes install but when you get to the custom
partitioning step, make sure to specify the appropriate partitions for
boot and /.
You will probably want to re-enable the boot flag on your hda1 partition
as well.


[799]

unread,
Oct 30, 2017, 4:58:01 PM10/30/17
to aw...@elude.in, qubes...@googlegroups.com
Hello,


> Try repeating the Qubes install but when you
> get to the custom partitioning step, make sure
> to specify the appropriate partitions for boot
> and /. You will probably want to re-enable the
> boot flag on your hda1 partition as well

Thank you for the feedback, I have meanwhile installed a fresh installation of Fedora 26 and could boot up fine, I reinstalled Qubes 3.2 afterwards and got the same result.

Can't boot, tried to setup the partitions manually and made sure that the Boot partition is installed correctly.
I also set the Boot flag to the first partition.
It doesn't matter ... Can't boot.
Totally annoyed that I tried Qubes 4 which can't boot any VMs and that I can't go back to Qubes 3.2 without deleting all partitions including my windows setup.

I think I'll try to reboot into windows when Fedora is installed, make a backup of my windows partition and then reinstall Qubes from scratch.
Have invested so much time already in this Qubes upgrade/downgrade topic that I am done for the year.

[799]

awokd

unread,
Oct 31, 2017, 10:14:04 AM10/31/17
to [799], aw...@elude.in, qubes...@googlegroups.com
Remembered later I encountered this issue on a fresh 3.2 install, maybe
you are hitting it too. This does not apply if you are doing UEFI boot,
only GRUB. Found a fix in
https://groups.google.com/forum/?_escaped_fragment_=msg/qubes-users/TS1zfKZ7q8w/JQFkVF4xBgAJ#!msg/qubes-users/TS1zfKZ7q8w/JQFkVF4xBgAJ:

"after a Clean Install of Qubes R3.2, it fails to boot - stuck at "Booting
from hard drive:" SeaBIOS message with blinking "_" character, cant reach
GRUB Boot Menu because MBR (or GRUB) is corrupted out-of-the-box. Luckily
it can be fixed: boot from your Qubes R3.2 installation media, go to
"Troubleshooting -> Rescue a Qubes system", after booting to anaconda
installer please choose "1) Continue" (and enter your Qubes partition
password if you chose to encrypt it during install), then enter "chroot
/mnt/sysimage" - and, finally, "grub2-install /dev/sdX" (where X is a
letter for your hard drive with Qubes, in my case it was sda:
"grub2-install /dev/sda")"


Reply all
Reply to author
Forward
0 new messages