On 2025-10-14, Gabriel Wicki wrote: > On Tue, Oct 14, 2025 at 10:11:57PM +0200, Rutherther wrote: >> > (device "/dev/mmcblk2p1") >> So here you have mmcblk2. >> >/dev/mmcblk1p1 does exist, or at least it is listed when i >> >> Here also mmcblk1. > >> Did you rewrite this from the screen? Which one is correct, are you sure >> the config is the same as what you're expecting? > ah, darn! i pasted the wrong definition from the `guix system image` > invocation here. all references are to /dev/mmcblk1 or the first > partition thereof (which is the external SD card of the pinebook pro). > > root@coney ~# lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS > mtdblock0 31:0 0 16M 0 disk > mmcblk2 179:0 0 58.2G 0 disk > ├─mmcblk2p1 179:1 0 457.8M 0 part > └─mmcblk2p2 179:2 0 57.8G 0 part > mmcblk2boot0 179:32 0 4M 1 disk > mmcblk2boot1 179:64 0 4M 1 disk > mmcblk1 179:96 0 29.7G 0 disk > └─mmcblk1p1 179:97 0 29.7G 0 part /gnu/store > / > > so i reconfigure on the running machine with all devices pointing to > that external card. the reconfiguration works (it creates a new system > generation) but that generation fails to boot. > > > > huh. so replacing > (device "/dev/mmcblk1p1") > with > (device (file-system-label "Guix_image")) > did the trick — the machine now boots! thanks for your input, > Rutherther! > > > but, the puzzle remains: are devices really named differently during > boot? even though i can `ls` them?
They are notorious for getting assigned unpredictibly, e.g. /dev/mmcblk0 might be eMMC one boot, or might be the insertable microSD card on the next... sometimes they get stabalized in the kernel, and then regressions happen, or someone thinks the order is wrong and swaps it, etc. I like uuid best, but labels can work as long as you don't use the same labels on any media you might ever insert... caveat emptor! live well, vagrant
signature.asc
Description: PGP signature
