[Bug 273555] GPT table lost or filesystem became invalid for new disk hot added on an existing LSILogic/LSILogicSAS controller in VM with guest OS FreeBSD 13.2-RELEASE i386 running on ESXi
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 13 May 2025 09:58:39 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273555 --- Comment #4 from Yanhui He <yanhui.he@broadcom.com> --- Tested today on FreeBSD 13.5 (32-bit), FreeBSD 14.2 GA (32-bit), and FreeBSD 14.3 Beta2 (both 32-bit and 64-bit), and found no issues on any of these versions. One point to note: when hot-adding an LSILogic Parallel controller and attaching a hard disk to this existing LSILogic Parallel controller in these VMs, a reboot is required for the system to recognize the newly added disk. After the reboot, it's necessary to enter the system setup (BIOS/UEFI) and adjust the boot order. In this scenario, the new LSILogic Parallel hard disk is assigned /dev/da0, causing the original boot disk to shift from /dev/da0 to /dev/da1. In contrast, when hot-adding an LSI Logic SAS controller and attaching a hard disk to an existing SAS controller, no reboot is needed. The newly added disk is recognized immediately and assigned as /dev/da1. Since this behavior is expected and there are no issues from the vSphere side, I’ll go ahead and close this PR. If you encounter any further issues, please feel free to reopen it. Thanks! -- You are receiving this mail because: You are the assignee for the bug.