Date: Tue, 31 May 2022 07:10:12 +0800 From: Alastair Hogge <agh@riseup.net> To: current@freebsd.org, David Wolfskill <david@catwhisker.org> Subject: =?US-ASCII?Q?Re=3A_Loader_can=27t_find_/boot/ua/loader=2El?= =?US-ASCII?Q?ua_on_UFS_after_main-n255828-18054d0220c?= Message-ID: <AE7E8FE2-4026-4AE4-BC3C-4D3D442F4B2B@riseup.net> In-Reply-To: <YpS6w2Jye%2B472SL1@albert.catwhisker.org> References: <YpP9fO4v%2BdE1pCgu@albert.catwhisker.org> <06ba3be54117e4feb8f250756b25c1c5@riseup.net> <YpS6w2Jye%2B472SL1@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 May 2022 8:38:27 pm AWST, David Wolfskill <david@catwhisker=2Eorg> w= rote: >On Mon, May 30, 2022 at 05:16:57AM -0700, Alastair Hogge wrote: >> =2E=2E=2E >> I have not been able to use a new /boot/loader=2Eefi (following -CURREN= T) >> since=20 >> mid to late 2021, and your symptoms look the same; fortunately, I found >> bug=20 >> report 264282[0] last night, which I think is related=2E Yamagi has >> already done=20 >> the investigation, and found a possible cause=2E For the time being, in >> the case=20 >> of a GELI backed UFS mount, after GELI decrypts the mount, one has to >> manually=20 >> set currdev back to the correct disk=2E >>=20 >> 0: https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D264282 >> =2E=2E=2E=2E > >I (just) checked; after switching back to the Lua loader, the currdev >variable is set to "disk0s4a:", which is correct for my case=2E > >Trying loader's "lsdev" command shows the expected disks, slices, and >partitions, correctly identified as FreeBSD UFS, swap, or ZFS=2E > >Trying to (e=2Eg=2E) "ls disk0s4a:" fails, saying that it can't find /=2E Thanks for having a look into that mate=2E --=20 Sent from a device with a tiny bloody screen and no hard keyboard; please = excuse my brevity=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE7E8FE2-4026-4AE4-BC3C-4D3D442F4B2B>