On Sun, Nov 08, 2026 at 09:10:16PM +0000, Roderick wrote: > Installing on an SSD, the installer did not offer a big offset. > As I remeber it offered 0. I just put 2 (enough for MBR).
An offset of 2 will work, but it's probably not the best choice. Using an offset of 0 is _not_ really recommended, even though it will mostly work for normal operations, as there are various ways that doing so can cause unexpected problems. Usually, the idea is to align the start of the partition with some kind of physical characteristic of the storage device. In the old days, (I.E. on disks that showed their true geometry to the OS), that was a cylinder boundary. On modern spinning disks, such alignment wasn't possible or even as important. On SSDs, the optimal value is probably some multiple of the flash page size, which in many cases we can only make an educated guess at. (The alignment of the partitions defined in the disklabel is more of an influence for performance than the exact placement of the MBR partition.) > Then I put BSD label a immediately with offset 2: > > # size offset fstype [fsize bsize cpg] > a: 375089662 2 4.2BSD 4096 32768 26062 > c: 468862128 0 unused On a disk that size, wasting the first 1 Mb is probably not an issue, and an offset of, say, 2048 might well give better performance.

