Well, it is obvious I screwed up...again.
First, I was trying to build a second installation of FreeBSD 14.3 on a much larger, 6TB, HDD, on my desktop computer.
I had to tweak the mobo settings to get the bios to recognize the 6TB drive, and in doing so, obviously corrupted the bootblock on my previously-working system, which is installed on a 320 GB drive.
One of the tweaks I tried was to activate "safe boot" or CSM. Undoubtedly, this is what caused the error. I have since turned that back off.
After looking for a solution, I tried the following commands:
But that command string is not recognized by gpart.
So, how do I fix the original error message and what other info might folks here need to help me figure out a solution?
BTW, due to some serious problems with Windows 10, I have been forced to have my FreeBSD installation become my daily driver. I like it very much despite there being a rather steep learning curve to all the unfamiliar software.
Ken Gordon
First, I was trying to build a second installation of FreeBSD 14.3 on a much larger, 6TB, HDD, on my desktop computer.
I had to tweak the mobo settings to get the bios to recognize the 6TB drive, and in doing so, obviously corrupted the bootblock on my previously-working system, which is installed on a 320 GB drive.
One of the tweaks I tried was to activate "safe boot" or CSM. Undoubtedly, this is what caused the error. I have since turned that back off.
After looking for a solution, I tried the following commands:
gpart bootcode -b /boot/pmbr -pBut that command string is not recognized by gpart.
So, how do I fix the original error message and what other info might folks here need to help me figure out a solution?
BTW, due to some serious problems with Windows 10, I have been forced to have my FreeBSD installation become my daily driver. I like it very much despite there being a rather steep learning curve to all the unfamiliar software.
Ken Gordon