Re: weird issue after -p8 update
- Reply: Yuri : "Re: weird issue after -p8 update"
- Reply: Julien Cigar : "Re: weird issue after -p8 update"
- In reply to: David Christensen : "Re: weird issue after -p8 update"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 20 Mar 2022 14:16:44 UTC
On Fri, Mar 18, 2022 at 09:15:40PM -0700, David Christensen wrote: > On 3/18/22 05:55, Julien Cigar wrote: > > Hello, > > > > I've updated an old HPE Microserver Gen8 from FreeBSD 13.0-p7 to 13.0-p8 > > and since I'm unable to boot. I thought it was the bootcode but even > > after updating I'm getting this: https://pasteboard.co/WesqiS5Lrw56.png > > > > (this is classical non-uefi bios) > > > > any idea? I'm lost. > > > > Thanks, > > Julien > > > The BIOS sees 4 drives. > > > It looks like the FreeBSD bootloader (?) is having trouble reading the > drive(s) that contain the pool "zroot_jupiler" (is that supposed to be > "zroot_jupiter"?), which contains the / (root) and /boot filesystems (?). yes it is supposed to be zroot_jupiler. > > > I would boot a 13.0-R installer USB stick into a live system, start a root > shell, and try to determine if the disks, partitions, ZFS pools, etc., are > okay. If you run a 'zpool import ...', consider using the "altroot=..." > and "readonly=on" properties. > I tried, zpool import -NR /foo zroot_jupiler works, no error, scrub works well too. I finally reinstalled the machine and I think there is a serious issue with that latest -p8 ZFS updates as the machine is unbootable again (this is what I'm getting: https://gist.github.com/silenius/e7c14d639c058f2734e6ffc078a43646 any idea? Julien > > David > -- Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.