Seeed-Jetson-DevelopTool / jetpack5-ssd-boot-fix
AGENTS.md57 starsChanged 4 months agoMITView on GitHub
Fix JetPack 5 boot failures from NVMe SSDs on Seeed Jetson devices. Two options — full SSD wipe via external enclosure, or re-flash with --erase-all flag. JetPack 6 is not affected.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository297 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-nvrAGENTS.md
- allxon-ota-updateAGENTS.md
- allxon-setupAGENTS.md
- alwaysai-setupAGENTS.md
- backup-restoreAGENTS.md
- bsp-source-buildAGENTS.md
- clawdbot-developmentAGENTS.md
- cochl-sense-setupAGENTS.md
- cvedia-setupAGENTS.md
- dashcamnet-xavier-nx-multicameraAGENTS.md
- deciai-setupAGENTS.md
- deepseek-quick-deployAGENTS.md
- deploy-deepseek-mlcAGENTS.md
- deploy-depth-anything-v3AGENTS.md
- deploy-diaAGENTS.md
- deploy-efficient-vision-engineAGENTS.md
- deploy-frigateAGENTS.md
- deploy-live-vlm-webuiAGENTS.md
- deploy-nvbloxAGENTS.md
- deploy-ollama-anythingllmAGENTS.md
- deploy-riva-llama2AGENTS.md
- developtool-deviceAGENTS.md
- disk-encryptionAGENTS.md
- diy-bsp-buildAGENTS.md
- ethercat-communicationAGENTS.md
- ethercat-setupAGENTS.md
- finetune-llm-llama-factoryAGENTS.md
- fix-browser-snap-jetsonAGENTS.md
- gapi-setupAGENTS.md
- generative-ai-introAGENTS.md
- gpt-oss-liveAGENTS.md
- gr00t-n1-5-deploy-thorAGENTS.md
- gr00t-n1-6-deploy-agxAGENTS.md
- hardhat-setupAGENTS.md
- hybrid-bsp-dk-to-recomputerAGENTS.md
- imx477-a603-setupAGENTS.md
- j501-viola-fruit-sortingAGENTS.md
- jetpack-flash-wsl2AGENTS.md
- jetpack-jetson-overviewAGENTS.md
- jetpack-ota-updateAGENTS.md
- jetson-ai-toolsAGENTS.md
- jetson-docker-setupAGENTS.md
- jetson-faqAGENTS.md
- jetson-pc-wired-shareAGENTS.md
- jetson-project-galleryAGENTS.md
- jetson-resource-indexAGENTS.md
- jetson-tutorial-exercisesAGENTS.md
- ko-module-buildAGENTS.md
- l4t-differencesAGENTS.md
- langchain-output-formattingAGENTS.md
- lerobot-env-setupAGENTS.md
- llama-cpp-rpc-distributedAGENTS.md
- llm-interface-controlAGENTS.md
- local-chatbot-multimodalAGENTS.md
- local-chatbot-physicalAGENTS.md
- local-llm-text-to-imageAGENTS.md
- local-rag-llamaindexAGENTS.md
- lumeo-setupAGENTS.md
- maskcam-nanoAGENTS.md
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Run one phase at a time. After each phase:
- Very specific: line 20
If output contains [STOP] → stop immediately, consult the failure decision tree
- Very specific: line 21
If output ends with [OK] → tell the user "Phase N complete" and proceed
- Distinctive: line 46
Remove the NVMe SSD from the Jetson device
- Distinctive: line 54
Verify it's the Jetson SSD by checking for Jetson device tree files:
- Distinctive: line 80
Put device into recovery mode
- Distinctive: line 92
Follow the Seeed BSP source build guide to prepare the flashing environment: …
- Very specific: line 97
Add --erase-all to the flash command to completely wipe the SSD during flash:
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fix JetPack 5 SSD Boot Failure
JetPack 5 may fail to boot from certain NVMe SSDs even after a successful flash. This is caused by filesystem incompatibility or incomplete wiping during flash. JetPack 6 is not affected by this issue.
Hardware: Seeed Jetson device, NVMe SSD, SSD enclosure (for Option A), USB cable Software: JetPack 5.x, Ubuntu host PC
Execution model
Run one phase at a time. After each phase:
- If output contains
[STOP]→ stop immediately, consult the failure decision tree - If output ends with
[OK]→ tell the user "Phase N complete" and proceed
Two repair options are available. Ask the user which they prefer before starting.
Phase 1 — confirm the issue (~1 min)
Symptom: JetPack 5 was flashed successfully to SSD, but device fails to boot with filesystem errors on screen.
# On the Jetson (if accessible via serial/recovery), check:
cat /etc/nv_tegra_release[OK] when user confirms JetPack 5 boot failure from SSD.
[STOP] if running JetPack 6 (this issue does not apply).
Option A — Wipe SSD externally
Phase 2A — connect SSD to host PC (~1 min)
- Remove the NVMe SSD from the Jetson device
- Connect it to a host PC using an NVMe-to-USB enclosure
- Identify the device name:
lsblkVerify it's the Jetson SSD by checking for Jetson device tree files:
ls /media/$USER/*/boot/
# Should show Jetson-specific device tree files (*.dtb)[OK] when SSD is identified (e.g. /dev/sda).
[STOP] if SSD not detected — check enclosure and cable.
Phase 3A — wipe the SSD (~5–15 min)
⚠️ DANGER: This destroys all data. Back up first. Double-check the device name.
Replace /dev/sdX with the actual device. Adjust count for larger SSDs
(count=800 with bs=100M = 80 GB wiped):
sudo wipefs -a /dev/sdX
sudo dd if=/dev/zero of=/dev/sdX bs=100M count=800[OK] when dd completes without errors.
Phase 4A — re-flash JetPack 5 (~15–30 min)
- Reinstall the SSD into the Jetson
- Put device into recovery mode
- Flash JetPack 5 following the standard Seeed flash guide: https://wiki.seeedstudio.com/flash/jetpack_to_selected_product/
[OK] when device boots successfully from SSD.
Option B — Re-flash with --erase-all
Phase 2B — prepare BSP source project
Follow the Seeed BSP source build guide to prepare the flashing environment: https://wiki.seeedstudio.com/how_to_build_the_source_code_project_for_seeed_jetson_bsp
Phase 3B — flash with full erase (~15–30 min)
Add --erase-all to the flash command to completely wipe the SSD during flash:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --erase-all \
--external-device nvme0n1p1 \
-c tools/kernel_flash/flash_l4t_nvme.xml \
-p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg" \
--network usb0 <DEVICE_NAME> externalReplace <DEVICE_NAME> with the appropriate board config name.
[OK] when flash completes and device boots.
Failure decision tree
| Symptom | Action |
| SSD not detected via enclosure | Try different USB port/cable. Check enclosure compatibility with NVMe. |
dd reports I/O error | SSD may be hardware-faulty. Try a different SSD. |
| Boot still fails after wipe + re-flash | Wipe more of the SSD (increase count). Or try Option B with --erase-all. |
--erase-all flash fails | Ensure device is in recovery mode. Check USB cable. Retry. |
| Issue persists after both options | Consider upgrading to JetPack 6, which is not affected. |
Reference files
references/source.body.md— Original Seeed wiki with screenshots and detailed context
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

