Thanks!
I'd just been preparing for PR. ;-)
Some additional notes:
*The reason stoppes booting would be different.
The last screen seen was like below.
===
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk1p5:
FreeBSD/amd64 EFI loader, Revision 1.1
Command li
On Thu, May 2, 2019 at 11:42 AM Kyle Evans wrote:
>
> On Thu, May 2, 2019 at 11:40 AM Larry Rosenman wrote:
> >
> > On 05/02/2019 11:34 am, Larry Rosenman wrote:
> > > On 05/02/2019 11:10 am, Larry Rosenman wrote:
> > >> On 05/02/2019 10:58 am, Warner Losh wrote:
> > >>> On Thu, May 2, 2019 at 9:
On Thu, May 2, 2019 at 11:40 AM Larry Rosenman wrote:
>
> On 05/02/2019 11:34 am, Larry Rosenman wrote:
> > On 05/02/2019 11:10 am, Larry Rosenman wrote:
> >> On 05/02/2019 10:58 am, Warner Losh wrote:
> >>> On Thu, May 2, 2019 at 9:54 AM Larry Rosenman wrote:
> >>>
> On 05/02/2019 9:41 am,
On 05/02/2019 11:34 am, Larry Rosenman wrote:
On 05/02/2019 11:10 am, Larry Rosenman wrote:
On 05/02/2019 10:58 am, Warner Losh wrote:
On Thu, May 2, 2019 at 9:54 AM Larry Rosenman wrote:
On 05/02/2019 9:41 am, Larry Rosenman wrote:
> On 05/02/2019 9:24 am, Warner Losh wrote:
>> On Thu, May
On 05/02/2019 11:10 am, Larry Rosenman wrote:
On 05/02/2019 10:58 am, Warner Losh wrote:
On Thu, May 2, 2019 at 9:54 AM Larry Rosenman wrote:
On 05/02/2019 9:41 am, Larry Rosenman wrote:
> On 05/02/2019 9:24 am, Warner Losh wrote:
>> On Thu, May 2, 2019 at 7:40 AM Larry Rosenman wrote:
>>
>>
On 05/02/2019 10:58 am, Warner Losh wrote:
On Thu, May 2, 2019 at 9:54 AM Larry Rosenman wrote:
On 05/02/2019 9:41 am, Larry Rosenman wrote:
> On 05/02/2019 9:24 am, Warner Losh wrote:
>> On Thu, May 2, 2019 at 7:40 AM Larry Rosenman wrote:
>>
>>> On 05/02/2019 8:29 am, Warner Losh wrote:
>>>
On Thu, May 2, 2019 at 9:54 AM Larry Rosenman wrote:
> On 05/02/2019 9:41 am, Larry Rosenman wrote:
> > On 05/02/2019 9:24 am, Warner Losh wrote:
> >> On Thu, May 2, 2019 at 7:40 AM Larry Rosenman wrote:
> >>
> >>> On 05/02/2019 8:29 am, Warner Losh wrote:
> >>> > On Wed, May 1, 2019 at 10:04 PM
On 05/02/2019 9:41 am, Larry Rosenman wrote:
On 05/02/2019 9:24 am, Warner Losh wrote:
On Thu, May 2, 2019 at 7:40 AM Larry Rosenman wrote:
On 05/02/2019 8:29 am, Warner Losh wrote:
> On Wed, May 1, 2019 at 10:04 PM Larry Rosenman wrote:
>
>> Upgraded from r346487 to r347007, and when I rebo
On 05/02/2019 9:24 am, Warner Losh wrote:
On Thu, May 2, 2019 at 7:40 AM Larry Rosenman wrote:
On 05/02/2019 8:29 am, Warner Losh wrote:
> On Wed, May 1, 2019 at 10:04 PM Larry Rosenman wrote:
>
>> Upgraded from r346487 to r347007, and when I reboot, I get a mountroot
>> prompt. If I answer
On Thu, May 2, 2019 at 7:40 AM Larry Rosenman wrote:
> On 05/02/2019 8:29 am, Warner Losh wrote:
> > On Wed, May 1, 2019 at 10:04 PM Larry Rosenman wrote:
> >
> >> Upgraded from r346487 to r347007, and when I reboot, I get a mountroot
> >> prompt. If I answer it with the same BootFS I booted fr
On 05/02/2019 8:29 am, Warner Losh wrote:
On Wed, May 1, 2019 at 10:04 PM Larry Rosenman wrote:
Upgraded from r346487 to r347007, and when I reboot, I get a mountroot
prompt. If I answer it with the same BootFS I booted from
(zfs:zroot/ROOT/r347007) it continues to boot, and run.
Dmesg: http
On Wed, May 1, 2019 at 10:04 PM Larry Rosenman wrote:
> Upgraded from r346487 to r347007, and when I reboot, I get a mountroot
> prompt. If I answer it with the same BootFS I booted from
> (zfs:zroot/ROOT/r347007) it continues to boot, and run.
>
> Dmesg: https://www.lerctr.org/~ler/Boot-NoRoot.
Upgraded from r346487 to r347007, and when I reboot, I get a mountroot
prompt. If I answer it with the same BootFS I booted from
(zfs:zroot/ROOT/r347007) it continues to boot, and run.
Dmesg: https://www.lerctr.org/~ler/Boot-NoRoot.txt
What else do we need?
I did upgrade the EFI partitions, an
13 matches
Mail list logo