> On Sat, May 28, 2016 at 06:15:35PM +0200, Robert Campbell wrote: > > I followed the steps in the FAQ for setting up full disk encryption. > > Everything goes according to plan until I attempt to write zeros to the > > first megabyte of the new pseudo-device; as you can see below, dd informs > > me that the file system is full, that there is no space left on the device. > > Interestingly, the last line of dmesg is also "uid 0 on /: file system > > full". I've retried this with 5.9 and -current, but the outcome is the > > same. I've also tried rebooting after disklabel and bioctl. I have pasted > > below the relevant sequence, followed by the full dmesg. > > > # bioctl -c C -l sd0a softraid0 > > New passphrase: > > Re-type passphrase: > > sd3 at scsibus3 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct fixed > > sd3: 114470MB, 512 bytes/sector, 234435953 sectors > > softraid0: CRYPTO volume attached as sd3 > > Here you need to do this first: > > cd /dev > sh MAKEDEV sd3 > > > # dd if=/dev/zero of=/dev/rsd3c bs=1m count=1 > > uid 0 on /: file system full > > If you skip the above step, /dev/rsd3c is created as a regular file and fills > up the root fs.
I'll tell everyone the secret. The ramdisk does not contain disk device nodes. We potentially need too many. So it creates them on the fly, in the script. As soon as you go into do-things-by-hand, you are on your own.
