On 6/12/26 16:54, dan wrote:
Sorry, I read the thread very fastly.Can you give us any clue (full view) about your disklabel ? Especially, what you own as sd{x}a as a range ? Otherwise I think difficult to say or guess what you really can/can't do.. what you have at 0 - 2048 position.. Second, worst as it could be you can pax everything important and restore your partitions on a good system. Third, sometimes happened to me to be on a stick and to have s disk root unaccessible for a *foo reason*.. I then copy machine (data copy) my stick to an external disk to have the upgrade running smoothly then. Never said.
Here is the file containing the first 2048 bytes of the disk, attached to this message. This is the output of "disklabel sd0" command: # /dev/rsd0c: type: SCSI disk: SCSI disk label: Virtual disk duid: f5c72aedee148bac flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 7832 total sectors: 125829120 boundstart: 0 boundend: 125829120 16 partitions: # size offset fstype [fsize bsize cpg] a: 2097152 0 4.2BSD 2048 16384 12960 # / b: 8388608 2097152 swap # none c: 125829120 0 unused d: 2097152 10485760 4.2BSD 2048 16384 12960 # /tmp e: 69206016 12582912 4.2BSD 2048 16384 12960 # /var f: 10485760 81788928 4.2BSD 2048 16384 12960 # /usr g: 2097152 92274688 4.2BSD 2048 16384 12960 # /usr/X11R6 h: 20971520 94371840 4.2BSD 2048 16384 12960 # /usr/local k: 10485760 115343360 4.2BSD 2048 16384 12960 # /home
d1.dsk
Description: Binary data
