Date: Fri, 10 Dec 2021 18:29:22 +0200 From: Toomas Soome via freebsd-current <freebsd-current@freebsd.org> To: Sergey Dyatko <sergey.dyatko@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: 14-current: unable to boot after upgrade (installworld) Message-ID: <7BA117CA-0FC0-4BC9-BD50-9958C0A62573@me.com> In-Reply-To: <CAJ0WZYC-WJpaY9DtuZpZN1QiZDvvuUqCF8=iS-Y6c-sYV%2B3X%2Bg@mail.gmail.com> References: <20211209163610.0cc4f7c6@gmail.com> <20211209235807.31ee2ecea5bc08e243870da3@dec.sakura.ne.jp> <CANCZdfrrxscONTC2BX0JjubnnBo1n6AbF9tdX20xM=wgFG6ZHg@mail.gmail.com> <CAJ0WZYASN0jGb0_a1Wbb8hzUwEndp1LZetPzuS5Fepo4F2BeWA@mail.gmail.com> <13846D48-70DF-47FD-B2DA-187A33F0F5C0@me.com> <CAJ0WZYC-WJpaY9DtuZpZN1QiZDvvuUqCF8=iS-Y6c-sYV%2B3X%2Bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 9. Dec 2021, at 20:54, Sergey Dyatko <sergey.dyatko@gmail.com> =
wrote:
>=20
> tiger@dl:~ % gpart show
>=20
> |
> =3D> 40 3907029088 da4 GPT (1.8T)
> 40 1024 1 freebsd-boot (512K)
> 1064 984 - free - (492K)
> 2048 3907026944 2 freebsd-zfs (1.8T)
> 3907028992 136 - free - (68K)
>=20
> =3D> 40 3907029088 da5 GPT (1.8T)
> 40 1024 1 freebsd-boot (512K)
> 1064 984 - free - (492K)
> 2048 3907026944 2 freebsd-zfs (1.8T)
> 3907028992 136 - free - (68K)
>=20
> =3D> 40 3907029088 da6 GPT (1.8T)
> 40 1024 1 freebsd-boot (512K)
> 1064 984 - free - (492K)
> 2048 3907026944 2 freebsd-zfs (1.8T)
> 3907028992 136 - free - (68K)
>=20
> =3D> 40 3907029088 da7 GPT (1.8T)
> 40 1024 1 freebsd-boot (512K)
> 1064 984 - free - (492K)
> 2048 3907026944 2 freebsd-zfs (1.8T)
> 3907028992 136 - free - (68K)
>=20
> i'm not sure about video, everything happens faster than I can see :-) =
but
> sometimes the system does not freeze and I can enter commands. Can =
this
> help in some way?
>=20
maybe, maybe not; from one hand, BTX register dump may help us to =
identify possible location or give other clues - eip=3D0000004c from =
your screenshot is telling us that some structure with function pointers =
must have been corrupted, seems like NULL pointer derefernce caused by =
this corruption. So the investigation should try to identify what is =
causing such corruption=E2=80=A6.=20
Since it was booting before, does the old loader start? I see the iKVM =
windo does have record menu entry, can it be used to record whole =
incident?
rgds,
toomas
> =D1=87=D1=82, 9 =D0=B4=D0=B5=D0=BA. 2021 =D0=B3. =D0=B2 18:19, Toomas =
Soome <tsoome@me.com>:
>=20
>>=20
>>=20
>>> On 9. Dec 2021, at 20:06, Sergey Dyatko <sergey.dyatko@gmail.com> =
wrote:
>>>=20
>>> I was sure the installer did it when I reinstalled the system from
>> scratch. I
>>> can load 14-current successfully after boot via PXE and installworld =
with
>>> 13-current
>>> now I did the following:
>>> 1) boot from HDDs FreeBSD 14.0-CURRENT #0 main-n251494-f953785b3df =
(with
>>> 'old' world)
>>> 2)run installworld (f953785b3df)
>>> 3) run `gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 =
da${D}`
>>> command , where D=3D4..7
>>> root@dl:/usr/src # zpool status
>>> pool: zroot
>>> state: ONLINE
>>> config:
>>>=20
>>> NAME STATE READ WRITE CKSUM
>>> zroot ONLINE 0 0 0
>>> mirror-0 ONLINE 0 0 0
>>> da4p2 ONLINE 0 0 0
>>> da5p2 ONLINE 0 0 0
>>> mirror-1 ONLINE 0 0 0
>>> da6p2 ONLINE 0 0 0
>>> da7p2 ONLINE 0 0 0
>>> errors: No known data errors
>>>=20
>>> after `shutdown -r now` system still doesn't boot with the same =
error.
>> As
>>> far I can see, there is /boot/lua/config.lua present, but when I try =
to
>> run
>>> command more /boot/lua/config.lua system hangs with following error:
>>> https://imgur.com/5p0xu6W.png
>>>=20
>>=20
>> You seem to get 2x BTX panic, could you try to create video from =
console,
>> so we could get register dumps?
>>=20
>> can this system do UEFI boot and if so, can you test it? Could you =
post
>> partition tables?
>>=20
>> rgds,
>> toomas
>>=20
>>=20
>>>=20
>>> =D1=87=D1=82, 9 =D0=B4=D0=B5=D0=BA. 2021 =D0=B3. =D0=B2 15:56, =
Warner Losh <imp@bsdimp.com>:
>>>=20
>>>> On Thu, Dec 9, 2021 at 7:58 AM Tomoaki AOKI =
<junchoon@dec.sakura.ne.jp>
>>>> wrote:
>>>>=20
>>>>> On Thu, 9 Dec 2021 13:36:10 +0000
>>>>> "Sergey V. Dyatko" <sergey.dyatko@gmail.com> wrote:
>>>>>=20
>>>>>> Hi,
>>>>>>=20
>>>>>> Yesterday I tried to upgrade old 13-current (svn rev r368473) to =
fresh
>>>>>> 14-current from git,it looked like this:
>>>>>> 1) git pull https://git.freebsd.org/src.git /usr/src
>>>>>> 2) cd /usr/src ; make buildworld; make kernel
>>>>>> 3) shutdown -r now
>>>>>> after that I _successfully_ booted into 14-current and continued =
with
>>>>>> etcupdate -p
>>>>>> make installworld
>>>>>> etcupdate -B
>>>>>> shutdown -r now
>>>>>>=20
>>>>>> but after that server doesn't come back. After I conneted to this
>>>> server
>>>>> via
>>>>>> IPMI ip-kvm I saw following (sorry for external link):
>>>>>> https://i.imgur.com/jH6MHd2.png
>>>>>>=20
>>>>>> Well. There was a migration to zol between r368473 and current =
'main'
>>>>> branch so
>>>>>> I decided to install fresh 14-current from snapshot
>>>>>> FreeBSD-14.0-CURRENT-amd64-20211202-610d908f8a6-251253 in order =
to
>>>> avoid
>>>>>> possible problems
>>>>>>=20
>>>>>> and again, after make kernel and reboot OS runs, but after
>> installworld
>>>>> I ended up in the same situation
>>>>>>=20
>>>>>> thoughts ?
>>>>>>=20
>>>>>> --
>>>>>> wbr, Sergey
>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>> Bootcode should be updated.
>>>>> The procedure you wrote doesn't seem to update it.
>>>>>=20
>>>>=20
>>>> The posted error is one you get when you can't read the filesystem,
>> which
>>>> is why you need to update
>>>> boot blocks across the OpenZFS change.
>>>>=20
>>>> Warner
>>>>=20
>>=20
>>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7BA117CA-0FC0-4BC9-BD50-9958C0A62573>