docs(deploy): bump dd count 2200 → 2800 for 25.11 image size
The 24.05-era image was ~6 GB actual; the README's count=2200 (8.8 GB) gave a small margin. The 25.11 image is 7.3 GB actual (linux-firmware- zstd grew, plus the version churn) — count=2200 would now truncate. Bump to count=2800 (~11.2 GB) and note that future bumps may need another increase — image size is the right thing to check via \`ls -lh result/\`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
01fcff45c1
commit
9bbe2a8aef
1 changed files with 4 additions and 3 deletions
|
|
@ -88,9 +88,10 @@ The bitSpire-flashed USB will show up as another disk (`sdb` or similar) — not
|
|||
### 4. dd the bitSpire image to the eMMC
|
||||
|
||||
```sh
|
||||
# Limit count to ~8.8 GB (the actual image size + small margin) to avoid
|
||||
# spending 30 minutes copying empty USB tail
|
||||
dd if=/dev/sdb of=/dev/mmcblk0 bs=4M count=2200 status=progress conv=fsync && sync
|
||||
# Limit count to ~11.2 GB (the actual image size + small margin) to avoid
|
||||
# spending 30 minutes copying empty USB tail. Bump this count if the
|
||||
# image grows further on future nixpkgs bumps — check `ls -lh result/`.
|
||||
dd if=/dev/sdb of=/dev/mmcblk0 bs=4M count=2800 status=progress conv=fsync && sync
|
||||
```
|
||||
|
||||
### 5. Repair the GPT secondary header
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue