Hi there!
Most likely I am overlooking the right sentence in the FAQ, man fdisk(8)
or man disklabel(8) ... but I am lost at present.
<sight>
Need help!
I finally had the money to buy myself a new laptop from Schenker; a
different model seems to work just fine
(https://marc.info/?l=openbsd-misc&m=143965407100554&w=2). Comes with a
m.2-SSD and a SATA-SSD. As I need to visit different customers and
chances are high that I receive really sensible data I'd like to set up
a fully encrypted system with a key disk following stsp@'s fine
presentation on this
(http://www.openbsd.org/papers/eurobsdcon2015-softraid-boot.pdf, core
instructions at page 11).
UEFI-boot is disabled; boot sequence is CD, USB-stick, m.2-SSD.
Checking the USB-stick with the to-be-replaced laptop:
$ doas disklabel sd1
# /dev/rsd1c:
type: SCSI
disk: SCSI disk
label: UDisk
duid: xxxxxxxxxxxxxxxx
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 979
total sectors: 15730688
boundstart: 64
boundend: 15727635
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg]
c: 15730688 0 unused
d: 16001 64 RAID
e: 16065 16065 RAID
f: 16065 32130 RAID
g: 16065 48195 RAID
h: 16065 64260 RAID
i: 15647310 80325 RAID
The idea is to use partition 'd' to unlock the m.2-SSD and 'e' to unlock
the other SSD (which shall be mounted as '/home'), 'f' will unlock the
backup disk, 'g' & 'h' are for other media and 'i' might be used to
store other sensible information (e.g. passwords).
What is the problem? I have downloaded the 'install58.iso'-file
(amd64-current) and burned the disk to start from. dmesg recognizes the
three media and reports them as 'sd0' (=m.2-SSD), 'sd1' (SATA-SSD) and
'sd2' (USB-stick). I can start from the CD and hit 's' at the prompt.
< Transcription from here on >
# fdisk -iy sd0
Writing MBR at offset0
# fdisk -iy sd1
fdisk: sd2: No such file or directory
# fdisk -iy sd2
fdisk: sd2: No such file or directory
< End of transcription >
You might think "Hold on - sd1 is a SATA-device! This should be handled
as 'wdx' (x=0,1,2,...)" OK...
# fdisk -iy wd0
fdisk: wd0: Device not configured
# disklabel -E wd0
disklabel: /dev/rwd0c: Device not configured
PLEASE: Point my curiosity into the right direction! How come that the
SATA-SSD and the USB-stick are recognized by dmesg, but neither by fdisk
not disklabel???
I tried to plug in a 'normal' MSDOS-formatted USB-stick but it is not
possible to mount the stick to copy this system's dmesg onto it ("no
such file or directory").
Here are the last visible lines from the dmesg:
sd0 at scsibus0 targ 4 lun0: <ATA, Samsung SSD 850, EMT4> SCSI3 0/direct
fixed naa.xxxxxxxxxxxxxxxx
sd0: 114473MB, 512 bytes/sector, 234441648 sectors, thin
sd1 at scsibus0 targ5 lun0: <ATA, Samsung SSD 850, EXM0> SCSI3 0/direct
fixed naa.yyyyyyyyyyyyyyyy
sd1: 976762MB, 512 bytes/sector, 2000409264 sectors, thin
"Intel 8 Series SMBus" rev 0x05 at pci0 dev 31 function 3 not configured
isa0 at mainbus0
pckbc0 at isa0 port 0x60/5 irq 1 irq12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay1
umass0 at uhub0 port 6 configuration 1 interface 0 "General UDisk" rev
2.00/1.00 addr 2
umass0: using scsi over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
sd2 at scsibus1 targ 1 lun0: <General, UDisk,5.00> SCSI2 0/direct
removable serial.zzzzzzzzzzzzzzzz
sd2: 7681MB, 512 bytes/sector, 15730688 sectors
uhub3 at uhub1 port 1 "vendor 0x8087 product 0x8008" rev 2.00/0.05 addr 2
uhub4 at uhub2 port 1 "vendor 0x8087 product 0x8000" rev 2.00/0.05 addr 2
softraid0 at root
scsibus2 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
iwm0: could not read firmnware iwm-7260-9 (error 2)
How should I proceed???
TIA!
Best,
STEFAN
