💾 Archived View for bogwonch.smol.pub › always_use_duids captured on 2024-03-21 at 14:57:34. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Always use DUIDs. Never use device nodes.
I poured half a cup of tea on my beloved laptop (an X2100 via Xue Yao). But this is no biggie. I have a repairable laptop for this exact reason: I am a clumsy oaf and things break. Got the laptop shutdown before any permanent damage, but they keyboard is glitchy now. Again, no biggie: it uses the chassis from an X201s, so the keyboards are still gettable... okay I use a US keyboard so it takes longer to get one than I'd like, but it is but an eBay purchase away. No biggie. Remove the keyboard while its glitching, and use an external one until the new one comes (and what an external one!)
I start up my computer... and my home folder isn't mounted. Well that is odd. No worries drop to root, have a look at dmesg
sd4 at scsibus5 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006>
sd4: 457860MB, 512 bytes/sector, 937697393 sectors
root on sd4a (3d2df091bcd5611f.a) swap on sd4b dump on sd4b
sd5 at scsibus5 targ 2 lun 0: <OPENBSD, SR CRYPTO, 006>
Er what now? These are normally sd2 and sd3. Root on a small encrypted reliable disk, and my home folder on a separate big fast NVMe one in case I need to wipe the OS and don't want to muck about in disklabel(8). A script like below to bring it up every boot.
bioctl -c C -l sd1a -s softraid0 <keyfile
fsck -y sd1i
mount sd1i /home/me
What the heck is sd2 and sd3? Back to dmesg...
sd2 at scsibus3 targ 1 lun 0: <Generic-, SD/MMC, 1.00> removable
sd3 at scsibus3 targ 1 lun 1: <Generic-, Micro SD/M2, 1.08> removable
WTF? What are these SD card devices? Then of course look at the adapter plugging my keyboard into the computer... a little USB-C adapter with, sure enough two SD card slots in it. And they had their devices set up before the crypto devices were up of course (this laptop is somewhat weird sometimes).
Lesson learned. Use the DUIDs. Never use the devices.
⋕ doas disklabel -n sd5 | awk -F: '$1 ~ /duid/ { print $2 }'
0123456789abcdef
Bung the output into the appropriate rc scripts and its all fixed. Lesson learned. Never use the device nodes. Follow best practice. Always use DUIDs.