Re: 10.0 - Installer newfs segfaults on SS2

[vom513 <vom513%gmail.com@localhost>]

> On Sep 1, 2024, at 11:50 AM, Brian Buhrow <buhrow%nfbcal.org@localhost> wrote:
> 
> Hello.  I think what we're interested in is the contents of the disklabel, which should be
> written to the disk before newfs runs, but after you've zeroed it with dd.  Have you verified,
> with disklabel -r the contents of the disklabel on the media itself from the shell prompt?
> That should show you the partition table for the media.  Based on your description of the
> problem, I'd say, the disklabel isn't getting written to the media for some reason, which is
> causing newfs to bomb out before it does anything useful.  Obviously, it should give an error
> message, but probably no one thought newfs would ever run against a blank disk.

Figured I’d get a second opinion as well - here is what linux says:

root@ocl:/home/vom# losetup /dev/loop19 ss2.img 
root@ocl:/home/vom# fdisk -l /dev/loop19

Detected sun disklabel with wrong version [-2108275369].
Detected sun disklabel with wrong vtoc.sanity [0x010de910].
Detected sun disklabel with wrong vtoc.nparts [0].
Warning: Wrong values need to be fixed up and will be corrected by w(rite)
Disk /dev/loop19: 8.43 GiB, 9056690176 bytes, 17688848 sectors
Geometry: 255 heads, 63 sectors/track, 1101 cylinders
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: sun

Device           Start      End  Sectors  Size Id Type       Flags
/dev/loop19p1        0 17619361 17619362  8.4G  0 Unassigned  
/dev/loop19p2 17623305 17688840    65536   32M  0 Unassigned  
/dev/loop19p3        0 17688847 17688848  8.4G  0 Unassigned    u  
Partition table entries are not in disk order.