FreeBSD 12.0-RELEASE
I'm aware that this release is EOL, and this is part of the problem. I have a production VM that I am trying to update to something current (12.2 or 13.0), and when I followed the documentation for doing so, I was prompted to reboot, at which point the VM fails to boot. Thus, I am working with a replica of the VM to try to troubleshoot the problem with the upgrade. However the replicated VM itself fails to boot before attempting to do anything with it, which brings me here. The errors I see with the replica are different from those seen on the original VM after starting the upgraded process. In this post I am only trying to address the errors with the replica.
This VM replica was created with Veeam Backup and Replication v11. It is hosted on ESXi v7.0.3. The VM version is 13 (ESXi 6.5). When I start the VM I see the following errors on the console:
The carat at the bottom flashes but doesn't echo any keyboard input. I have confirmed that the following attributes match on the original VM and the replica:
Taking a look at
I've searched these errors and even for a FreeBSD noob such as myself, it seems clear enough that the bootloader is unable to import the boot pool, but I haven't been able to figure out why. Is there some modification we can make to our replication procedure that would result in a more viable replica VM? Or do I just need some tweak to make the replica bootable?
I'm aware that this release is EOL, and this is part of the problem. I have a production VM that I am trying to update to something current (12.2 or 13.0), and when I followed the documentation for doing so, I was prompted to reboot, at which point the VM fails to boot. Thus, I am working with a replica of the VM to try to troubleshoot the problem with the upgrade. However the replicated VM itself fails to boot before attempting to do anything with it, which brings me here. The errors I see with the replica are different from those seen on the original VM after starting the upgraded process. In this post I am only trying to address the errors with the replica.
This VM replica was created with Veeam Backup and Replication v11. It is hosted on ESXi v7.0.3. The VM version is 13 (ESXi 6.5). When I start the VM I see the following errors on the console:
Code:
ZFS: i/o error - all block copies unavailable
ZFS: can't read MOS of pool zroot
gptzfsboot: failed to mount default pool zroot
FreeBSD /x86 boot
_The carat at the bottom flashes but doesn't echo any keyboard input. I have confirmed that the following attributes match on the original VM and the replica:
- VM version
- CPU count
- RAM count
- HDD count, size and connection
Taking a look at
zpool status and /etc/fstab on the original VM gives some insight into what the boot pool should look like:
Code:
# zpool status
pool: zroot
state: ONLINE
scan: scrub repaired 0 in 0 days 00:16:51 with 0 errors on Thu Feb 3 16:21:07 2022
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
da0p3 ONLINE 0 0 0
da1p1 ONLINE 0 0 0
da2 ONLINE 0 0 0
da3 ONLINE 0 0 0
errors: No known data errors
root@wcdb [zpool status] ~ 22-02-08 3:03PM
# cat /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/da0p2 none swap sw 0 0
/dev/zvol/zroot/swap none swap sw 0 0
fdesc /dev/fd fdescfs rw 0 0I've searched these errors and even for a FreeBSD noob such as myself, it seems clear enough that the bootloader is unable to import the boot pool, but I haven't been able to figure out why. Is there some modification we can make to our replication procedure that would result in a more viable replica VM? Or do I just need some tweak to make the replica bootable?