grub2 Big mistake

[Patrick Dupre]

Hello,

I have not been able to provide my paraphrase at boot.

I mount the encrypted partition manually after removing it from
/etc/fstab

Then I run
grub2-mkconfig -o /boot/grub2/grub.cfg
(there was almost no diffrence with the previous grub.cfg that I saved).
Then I run grub2-install /dev/sda

Now I cannot boot

I enter in grub mode, but I cannot find a booting configuration
Even super-grub does cannot find a valid option

I have 2 disks
A SSD (normally sda, and a HD normally sdb)

How can I recover a booting system?

I have a copy of dev/sda
(dd if=/dev/sda of=/root/Backup/sda-mbr bs=512 count=1)

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: [phone]                    | | Room# D114A
===========================================================================

[Patrick Dupre]

The big mistake is fixed.

Now, I am back to the previous situation where the boot does
not ask me for the paraphrase.

How can I fix this?

I though to make an additional installation with anaconda
However,
anaconda do see 2 installations
and a list of unknown partitions.
my /home encrypted partition is visible here
If I provide the paraphrase, this partition is shown associated with the
2 other installations, and not anymore as unknown.
I cannot removed from these installations.
It seems that the reason is because of the fstab of these installations.

How can I create a new installation with a /home encrypted which
already exists?

Thank.

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: [phone]                    | | Room# D114A
===========================================================================
> Sent: Friday, July 22, 2022 at 11:16 PM
> From: "Patrick Dupre" 
> To: "fedora" 
> Subject: grub2 Big mistake
>
> Hello,
>
> I have not been able to provide my paraphrase at boot.
>
> I mount the encrypted partition manually after removing it from
> /etc/fstab
>
> Then I run
> grub2-mkconfig -o /boot/grub2/grub.cfg
> (there was almost no diffrence with the previous grub.cfg that I saved).
> Then I run grub2-install /dev/sda
>
> Now I cannot boot
>
> I enter in grub mode, but I cannot find a booting configuration
> Even super-grub does cannot find a valid option
>
> I have 2 disks
> A SSD (normally sda, and a HD normally sdb)
>
> How can I recover a booting system?
>
> I have a copy of dev/sda
> (dd if=/dev/sda of=/root/Backup/sda-mbr bs=512 count=1)
>
> ===========================================================================
>  Patrick DUPRÉ                                 | | email: [e-mail]
>  Laboratoire interdisciplinaire Carnot de Bourgogne
>  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
>  Tel: [phone]                    | | Room# D114A
> ===========================================================================
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Tim]

On Sat, 2022-07-23 at 10:29 +0200, Patrick Dupre wrote:
> Now, I am back to the previous situation where the boot does
> not ask me for the paraphrase.
>
> How can I fix this?

Not really enough information provided.  e.g. Show us your fstab files.

Generally speaking, if all your partitions are encrypted with the same
*passphrase* it'll unlock them all after you type it in once.  If
you've used different passphrases, you'd have to type them all in.  I
could guess that on different installations the encryption *techniques*
 may be different.

NB:  "paraphrase" is the wrong term, if you've been searching for help
using that term you won't get as far.  It means to say the same thing
in a different way (an alternative).

[Patrick Dupre]

OK,

I should have say passphrase !

Anyway, I made a touch /.autorelabel
ans now, the passphrase is asked.
Both partition are mount correctly.

Here are the new issues.

I cannot login th graphics mode as a user.

Login in text mode and loading startx I get

xauth:  file /home/pdupre/.serverauth.6203 does not exist

X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
Build Operating System:  5.18.10-200.fc36.x86_64
Current Operating System: Linux Sappho 5.18.11-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Jul 12 22:52:35 UTC 2022 x86_64
Kernel command line: BOOT_IMAGE=(hd0,msdos6)/vmlinuz-5.18.11-200.fc36.x86_64 root=/dev/mapper/VolSys1-root ro resume=UUID=cc01ef93-ef1c-4a18-9bbb-6339aa8a5e97 rd.lvm.lv=VolSys1/root rhgb quiet
Build Date: 12 July 2022  12:00:00AM
Build ID: xorg-x11-server 1.20.14-7.fc36
Current version of pixman: 0.40.0
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/pdupre/.local/share/xorg/Xorg.0.log", Time: Sat Jul 23 16:44:17 2022
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
(II) modeset(G0): Initializing kms color map for depth 24, 8 bpc.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86EmojiPicker

Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86EmojiPicker

Errors from xkbcomp are not fatal to the X server
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
------------------------------------------------------------------------------------------
Issue #2
 I get

[  615.740988] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  615.740997] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
[  615.741007] pcieport 0000:00:1c.0:    [ 0] RxErr
[  616.048156] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[  616.048179] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  616.048188] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
[  616.048198] pcieport 0000:00:1c.0:    [ 0] RxErr
[  616.355356] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[  616.355380] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  616.355389] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
[  616.355399] pcieport 0000:00:1c.0:    [ 0] RxErr
[  616.764981] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[  616.765005] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  616.765014] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
[  616.765023] pcieport 0000:00:1c.0:    [ 0] RxErr
> On Sat, 2022-07-23 at 10:29 +0200, Patrick Dupre wrote:
> > Now, I am back to the previous situation where the boot does
> > not ask me for the paraphrase.
> >
> > How can I fix this?
>
> Not really enough information provided.  e.g. Show us your fstab files.
>
> Generally speaking, if all your partitions are encrypted with the same
> *passphrase* it'll unlock them all after you type it in once.  If
> you've used different passphrases, you'd have to type them all in.  I
> could guess that on different installations the encryption *techniques*
>  may be different.
>
> NB:  "paraphrase" is the wrong term, if you've been searching for help
> using that term you won't get as far.  It means to say the same thing
> in a different way (an alternative).
>
> --
>
> uname -rsvp
> Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC 2022 x86_64
>
> Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> I will only get to see the messages that are posted to the mailing list.
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure