boot problem on my production qubes (urgent!)

[97a6sd67fs9]

Hi guys

In order not to ruin my 3.2 production installation I bought a new NVME SSD. After disk replacement I installed Qubes 4.0 and test my needs. Then I put the old SSD back in and now my PC doesn't start anymore. It hangs on the boot menu screen (Lenovo T460s) and when I enter into "Qubes" or the SSD device, it only refresh the screen.

In the BIOS I changed absolutely nothing.

How can I fix that?

It's my production environment without I can't work anymore! )-:

Thanks for your fast hints!

See you...

[Franz]

Really strange. May be an oxidized contact on the old SSD that stopped working after moving it. I would try to clean the contacts.

[berto0...@gmail.com]

On Wednesday, April 11, 2018 at 7:05:04 PM UTC+7, 97a6sd67fs9 wrote:

> In order not to ruin my 3.2 production installation I bought a new NVME SSD. After disk replacement I installed Qubes 4.0 and test my needs. Then I put the old SSD back in and now my PC doesn't start anymore. It hangs on the boot menu screen (Lenovo T460s) and when I enter into "Qubes" or the SSD device, it only refresh the screen.

Have you connected any other storage devices to your machine? That might mess up the the device names if the configs don't use the device UUIDs.

[97a6sd67fs9]

The lenovo diagnostics reads 11gb of data and says it's ok. It seems not to be a hardware problem...
-------- Original Message --------

[97a6sd67fs9]

Pure notebook only.

Maybe I have to repair the boot sector or grub? I don't know how...

-------- Original Message --------

--
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/d22b0749-57ad-45c1-a674-554383194f00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[berto0...@gmail.com]

On Wednesday, April 11, 2018 at 8:36:23 PM UTC+7, 97a6sd67fs9 wrote:
> Pure notebook only.
>
> Maybe I have to repair the boot sector or grub? I don't know how...
>

Have a look at https://www.supergrubdisk.org/ . I haven't tried it out myself, yet.

[awokd]

I think it's related to this. My guess is, when you installed 4.0, it
overwrote the boot menu entry in your EFI firmware, so now it doesn't work
for 3.2. If you were using legacy mode boot for 3.2, try to set that first
in your boot order. If EFI mode, you might have to boot into Qubes
recovery mode (possibly from the 3.2 DVD), then repair the EFI boot entry.
The command will be something like:

sudo efibootmgr -c -L Qubes32 -d /dev/sda -p 1 -l \\EFI\\qubes\\xen.efi

Note the "/dev/sda" and "-p 1" might vary. "-p 1" is the partition number
for your EFI partition (and this is what might have changed with your 4.0
install.

[97a6sd67fs9]

Thanks a lot guys! It works again and I learned something new...

The Qubes 4.0 installation changed the EFI boot entry. With the following command I fixed it:

"efibootmgr -v -c -L Qubes -l /EFI/qubes/xen.efi -d /dev/nvme0n1p1"

(With hint from awokd and https://github.com/QubesOS/qubes-issues/issues/2381#issuecomment-294405605)

See you


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

>
> 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/985f2785ea76ae44e0dfa2171bc4acc2.squirrel%40tt3j2x4k5ycaa5zt.onion.

[donoban]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 04/11/18 15:49, 'awokd' via qubes-users wrote:
>
> I think it's related to this. My guess is, when you installed 4.0,
> it overwrote the boot menu entry in your EFI firmware, so now it
> doesn't work for 3.2. If you were using legacy mode boot for 3.2,
> try to set that first in your boot order. If EFI mode, you might
> have to boot into Qubes recovery mode (possibly from the 3.2 DVD),
> then repair the EFI boot entry. The command will be something
> like:
>
> sudo efibootmgr -c -L Qubes32 -d /dev/sda -p 1 -l
> \\EFI\\qubes\\xen.efi
>
> Note the "/dev/sda" and "-p 1" might vary. "-p 1" is the partition
> number for your EFI partition (and this is what might have changed
> with your 4.0 install.
>

I also had this problem when I did my first Qubes 4 test. For avoid
fixing anytime I install Qubes 4, I renamed the Qubes 3.2 entry.

Maybe would be a good idea to default Qubes 4 to a different name to
avoid this kind of problems.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlrUwIYACgkQFBMQ2OPt
CKVXWg/6A4LBBn9V/RimfNrq9psvQZ9zAYUOkz1EnK4xXhBSES8DHL9trHeG0gng
4gYLbBBkNTbvDjMvbQGLnk7CqPr9XE7pwZUk5TjNlkUh9BjqG59kLlegmec6qKA6
cD82CU+nY58DKd99it4FZa8YDJRATgOwAEwI5Gvc5WKWLvvnFELFwqL2zOMCHfae
FNJt4uqKDpd2TBFQd1vtPI3qcNkRlttdgbZEvsDfEfEUh5dWpqYMtI+tGA7YAGlt
a9yc16xTI4+EwL5R9/p70rldUVQJBK8ZpsteaFY6ShsNpPWucd9P9M+j8/PpgvuH
T1C7fdTGN9/9f4SdKzXkGwTkR6+IrslY8Cd4/lPvGcgKAbjqU0KshIKJcEyTm46G
O52fmHue+XMcB3P+3JUHzXRakQWrGT6U2vltI2VPg7mWI7ufNZl81ZAaZMsNJl8S
tKp9e3i1VSBg1Bf7IUuxdh9vX9HxKMnagbzTVvSuc36FePcAD+rISXcUKUysp83b
UfHR3PoNmWLXcu8c90IElEE4JTd2kQgAGAD2EPP7mlDliikkyDvBv0zwhz/A83vK
YDF2zN68gU68lgeWDc6f/pn1j+szvSYb5sKQaxpcb4qWmw+Qf/gb0NvY8lR1VPUd
WeY7Xyu4ytpTCq19HA1eipQAVQljDMCUbYfAkyH1wQ7FF5fr+Jc=
=JdcM
-----END PGP SIGNATURE-----