On 5/20/24 10:31 AM, Tim Evans wrote:
Woke up yesterday to terminal messages about /var/log being read-only;
all graphical apps (Thunderbird, Chrome) had crashed. So, I decided to
reboot.
Background first: this is a new (3-months-old) PC. It came with two
disks, an NVME with Windows 11 pre-installed and an empty second HDD. I
DID NOT boot the system in Windows when it arrived. Instead, I popped
in a Fedora 39 Live thumbdrive, hit the BIOS hot key, and booted from
the thumbdrive, then installed F39.
Again, the system has never, ever, booted into Windows. Which means I
have no Bitlocker recovery key, nor any means to access it. Contacting
Microsoft won't do any good, since the system was never registered. (I
will have to try Dell.)
F39 install was successful, and I've been using the system ever since.
Normal grub bootup, offering Fedora kernels, rescue boot, and Windows.
So, getting back to yesterday, I went to reboot the system, and it came
up with the blue MS Bitlocker screen, asking for the Bitlocker Recovery
key. Have never seen this before.
Then, I noted the "skip this drive" button on the Bitlocker screen,
which brought up a second screen, with an alternative devices button.
Clicking this reveals a "Fedora" button. Clicking it brings up the
normal grub boot screen and away we go into Fedora.
Repeating the reboot gets the same results. I have to click through the
Bitlocker screens to get to a Fedora boot.
Not a big, big deal, but this prevents any sort of unattended reboot
from being possible.
Suggestions for restoring the normal boot process, please? Thanks.
Closing the loop on this, as I have resolved this issue.
First, though, I have to eat some crow. I repeatedly stated this system
had never been booted into Windows. This is not true. As I worked on
the issue, I did let the system come up in Windows. Much to my chagrin,
I was presentd with a login screen with my own name on it, prompting
for my "PIN." So, I tried my usual PIN and, lo and behold, I was logged in.
Obviously, I had in fact booted the system into Windows and set up an
account at some point back in February when the system was new. So,
googling led me to a Microsoft documnet on BitLocker key recovery, which
includes the URL: https://account.microsoft.com/devices/recoverykey
Tried that and entered the (above) Winows login and PIN and was
presented with BitLocker recover keys for the two disks on a system with
my very own hostname. Printed them out and rebooted to the BitLocker
screen and entered the one for the Fedora boot disk.
And, once, I diddled with the BIOS boot order, I got my unattended
Fedora boot back.
How the system got into the read-only state (see initial problem
desription way above), is a mystery. But multiple boots later, that
issue has not recurred.
Thanks, again, for all the responses and suggestions. I'll try to
remember not to trust my memory next time.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
