>
> On Tue, Feb 25, 2025 at 11:09 PM izzy Meyer <izder456@disroot.org> wrote:
>>
>> Let me jump in here (sorry for poor formatting, I'm on mobile).
>>
>> I used to run -current on my Panasonic Lets's Note CF-NX4 using a GPT-formatted SATA SSD. I was also using full disk encryption set up by the installer of 7.6 before I made the initial sysupgrade -s to -current.
>>
>> I did a sysupgrade -s a few days ago during my weekly system management cycle, and I got hit by this issue as well.
>>
>> Naturally, I chocked this up to my own pebcak as I run a custom kernel due to quirks of my touchpad. As such, I never bothered to report this to misc@.
>>
>> I later re-installed 7.6 and decided it'd be better if I ran -stable for the time being. But- now that I notice that others had this issue, it might not just be my "pebcak".
>>
>> Maybe it is full disk encryption? Or- possibly full disk encrypted setups are additionally affected? Dirk, do you use full disk encryption on your affected machine? Or- do you have a multi-disk setup? More information on your disk and partitioning scheme on the affected hardware would
>
>
> I am using a two-disk system without disk encryption. The first disk, sd0, is the boot disk and contains the root fs. The second disk is externally attached via USB and contains /var/www and a /Development partition.
>
> It is noteworthy to me that the behavior appeared last week. This machine in the same configuration has been running current for about two years.
>
>
> Ron
>>
>>
I've done some more testing. What is failing is installboot while
trying to set an EFI variable. Managed to run installboot with the -v
option during this step of the upgrade as shown in this picture to get
additional information. I'm not using FDE and sd0 is the right disk to
use.
No comments:
Post a Comment