Date: Sat, 2 Dec 2023 15:00:37 +1030 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: FreeBSD Cloud <freebsd-cloud@FreeBSD.org> Subject: Re: Resizing EBS with ZFS on AWS Message-ID: <ee8385fc-83d4-fd53-96f0-c2475941fa7b@ShaneWare.Biz> In-Reply-To: <9f04355d-4657-7781-0797-3518a164119d@ShaneWare.Biz> References: <9f04355d-4657-7781-0797-3518a164119d@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/12/23 11:26, Shane Ambler wrote: > Hi, > > I recently started an EC2 with the 14.0 ZFS AMI > > After filling the drive, I expanded it, recovered the gpart partition > and expanded the partition and zpool size and kept going. > > Then I saw that I would need more space, so I have expanded the EBS vol > again, while the EC2 was shutdown. This time the EC2 will not boot. > > Using the EC2 console I get to... > > Trying to mount root from zfs:zroot/ROOT/default []... > Mounting from zfs:zroot/ROOT/default failed with error 2: unknown file > system. > GEOM: nda0: the secondary GPT header is not in the last LBA. > > > What can I do at mountroot> to recover gpart? or boot from here? > OK so it seems the expanding disk was a red herring, I had altered loader.conf to break boot. I came up with steps to attach the unbootable EBS to another instance, import the pool, fix loader.conf, then re-attached to the original instance and got it to boot. Might need to document these cloud recovery steps somewhere. -- FreeBSD - the place to B...Scaring Daemons Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ee8385fc-83d4-fd53-96f0-c2475941fa7b>