Repository navigation
Description
A disk installed by 1bit-install does not boot on the cycle-13 image. Puppy's init resolves
pupsfs= as a label but not as UUID=…, and installer step 5 rewrites every entry to
pupsfs=UUID=<uuid>. So the installed system cannot find its own data partition, drops to the rescue
console, and the install gate's "boot the installed disk" row cannot pass.
Found while verifying the install docs (lane pi-rlk, ~/briefs/TDOCS-INSTALL.md), on the built artifact
~/wt/puppy-out-c13/1bit-os-puppy.img (sha256 dcc619ff74882f484e4c7dfb373980f294ce2f39b02291fb816ac7c62776beb7)
in QEMU, Secure Boot on with our MOK in db.
Measured
Install to a bare 8 GiB disk (1bit-install /dev/vda --yes): all seven steps green, exit 0, and the
installed grub.cfg carries what step 5 wrote:
linux /1bit/vmlinuz pmedia=usbhd pupsfs=UUID=7fa88580-b15a-469d-ab9b-f0215012eaf4 1bit.data=UUID=7fa88580-... psubdir=1bit pfix=copy,nox
Booting that disk (as a virtio disk, and again as the only USB device with the stick removed) fails in
init:
Waiting for partition [UUID=7fa88580-b15a-469d-ab9b-f0215012eaf4]...............failed
0: PMEDIA=usbhd PDRV=UUID=7fa88580-... PSUBDIR=/1bit pfix=copy,nox
1: PDRV= P_BP_ID=UUID=7fa88580-... P_BP_FN=
Partition UUID=7fa88580-b15a-469d-ab9b-f0215012eaf4 not found.
*** UUID=7fa88580-... /1bit/puppy_upup64r_26.04.sfs not found.
*** Error is too critical, dropping out to console...
The partition is there — from the rescue console on that same boot:
~ # blkid
/dev/sda2: LABEL="1BIT-DATA" UUID="7fa88580-b15a-469d-ab9b-f0215012eaf4" TYPE="ext4"
/dev/sda1: LABEL="1BIT-OS" UUID="3E36-7A05" TYPE="vfat"
So it is not enumeration, not pmedia=usbhd (the install booted from a USB device both times), and not the
disk: it is the UUID= form of the pinned partition that init does not resolve.
One-token A/B, same installed disk, nothing else changed
grub.cfg boot line |
result |
|---|---|
pupsfs=UUID=7fa88580-… (what step 5 writes) |
init: "Partition UUID=… not found", rescue console |
pupsfs=1BIT-DATA (label), 1bit.data=UUID=… kept |
boots: puppypc20143, /data/.installed present, lemond up, GET /api/v1/models 401 without the key and 200 with it, SSH on the stick's key |
Suggested fix
The pinning has to survive two 1BIT-DATA partitions (engine#539/#711), so the fix is in init, not in
installer step 5: teach the pupsfs= handling to resolve UUID=<uuid> (the same blkid -t path
1bit.data= already uses through findfs). If init can only take a label this cycle, step 5 should keep
pupsfs=1BIT-DATA and rely on 1bit.data=UUID=… — but then a machine with the stick in and a disk
installed can load the wrong save layer, which is the bug the pinning exists for.
Also noticed, cosmetic: step 5's sed rewrites the string pupsfs=1BIT-DATA inside the comment above
the menu entries too, so the installed grub.cfg says "pupsfs=UUID=… sets Puppy's PDRV" in a comment and
grep -c reports 4 pinned entries for 3 menuentries.
Verification rig and full transcript: ~/wt/rlk-vm/ (verify.sh, results.txt) on strixhalo; the
install/clients docs that found it are in the same lane's branch.
Activity
docs: install 1bit OS (stick, disk, USB) and connect a client to Lemo…
bong-water-water-bong commentedon Nov 3, 2026
Triaged at
origin/main692cfa25c— and the fix is in a file that is not inmainyet:os/v3/puppy/1bit-install.sh,patch-init.shand theembed/etc/init.d/*scripts live only on PR #828's branch (os/v3-fragment-parents, head5a310e89). Verified there, so the report stands on the branch tip and the row inherits #828.Confirmed, with the lines the fix has to touch:
1bit-install.sh:158-161— step 5 rewrites every entry withs|pupsfs=1BIT-DATA|pupsfs=UUID=$datauuid 1bit.data=UUID=$datauuid|g.patch-init.shnever touchespupsfs=handling at all: its whole surface is theone_rescuetrap, the threeexec /bin/shfailure paths and the two cycle-14 progress lines (git show pr828:os/v3/puppy/patch-init.sh | grep -c pupsfs→ 0). So nothing in our tree teaches init the UUID form; the A/B in the report is the whole story.The step that should have caught this is blind by construction
1bit-install.sh:163-164is the installer's own assertion:It greps for the exact string step 5 just wrote. A self-consistent check cannot fail, and it proves nothing about whether init resolves the value — which is why seven green steps, exit 0, and an unbootable disk coexist. That is the same class as #709's
securebootSKIP and #814's footer: a row that asserts its own write is not a gate. Whatever fixes the init side, the assertion should become a readback of the thing init needs (e.g.findfson the value that ends up on the boot line, in the installer's own environment).Our own data layer already speaks this form — so the fix is not a new mechanism
05onboard-data:39-42takesspecfrom1bit.data=and:46-53resolves it withfindfs "$spec";findfsaccepts both forms, one line on this box:So the init-side change is "resolve
pupsfs=UUID=…with the samefindfsour script already uses", not a new parser. If init cannot be patched this cycle, the fallback in the report (pupsfs=1BIT-DATA+1bit.data=UUID=…) is not equivalent: it reopens the wrong-save-layer bug #539/#711 on any machine with the stick in, and our layer would loadUUID=correctly while Puppy loads the SFS from the wrong partition — a split brain, worse than a rescue console.Two more, both cheap to fix in the same PR:
sed -irewrites thepupsfs=1BIT-DATAstring inside the comment above the menuentries too, so the installedgrub.cfgdocuments a value it does not use andgrep -ccounts 4 pinned lines for 3 entries. Anchor the sed on^linux(or-e '/^linux /s|…|…|').1bit-install.shends withsay "reboot and remove the stick"; the only thing that ever tests the installed disk is the QEMU rig in~/wt/rlk-vm/. os/v3/puppy: 1bit-install step 7 reads the wrong Boot#### id from efibootmgr, so BootNext points at the BootManagerMenuApp #866 (same report series) is the other half of "an install that says green and does not boot", so the two should land together with one row that boots the installed disk and reads it back — that row is also os: 1bit-install registers no firmware boot entry and the live kernel has no efivarfs - the installed disk only boots by firmware fallback #709's outstanding acceptance (efibootmgr -v+BootOrdernaming the entry after one install).Next action: patch
pupsfs=resolution on the init side inside PR #828 (this file set only exists there), turn:163into afindfsreadback, and anchor the sed onlinuxlines. Owner pi-os3 (PR #828), with #709's readback row as the shared gate. Bucket A — with the caveat that it closes on #828 (or a PR stacked on it), since the file is not inmain.os/v3/puppy install-probe: the installed-disk leg names the issue it …
os/v3/puppy install-probe: the installed-disk leg names the issue it …
docs: the appliance boots as 1bit-os, and installer #866 is fixed
bong-water-water-bong commentedon Nov 3, 2026
Closed by the merge of #890 (
8251ae597511e038e3f28879ee76c2a16c60201b). Verified at65460184inos/v3/puppy/patch-init.sh: the resolver is there (:247-250names this issue and the broken pattern, and prefixedUUID=/LABEL=tokens are matched against blkid's own quoted fields), and the build-time guard refuses an init that cannot resolve the form (:136-139). The acceptance in the issue — an installed disk reaching userspace from its ownpupsfs=UUID=…boot line — was measured on QEMU with Secure Boot on in the PR (PASS installed … the installed disk reached userspace on its own boot line).docs/install: both installed-disk fixes are in main, and a dd-only st…
docs: 1bit OS is the Puppy Linux appliance, and os/mini is a CI/VM ta…