Files
u-claw/bootable/TROUBLESHOOTING.md
zheng 3221856d50
Some checks failed
Tests / test (push) Has been cancelled
docs: 文档改为英文,并修正过时内容
不是翻译 —— 多数文档描述的行为已经不存在了。

先修一个更基本的问题:我们不拥有 u-claw.org 域名,那是上游的。所以之前写在
README、诊断包提示、联系方式里的 help@u-claw.org 全都会把用户的问题发给
上游 —— 一个没有理由回复的人。改为指向我们自己的 issue tracker,并加断言
禁止再出现指向该域名的支持入口。

重写(内容过时,不是语言问题):
- install/README.md —— 还写着 10 个中国技能、DeepSeek 优先、国内镜像。
  现在按实际流程写:技能读 manifest、模型菜单 Gemini 优先、bundle 有
  SHA256 校验。并如实写明 curl|bash 在受管企业电脑上会被 EDR 拦。
- CLAUDE.md 的模型配置整节 —— 还在描述虾盘云首选卡片和 12 个 provider,
  那个界面已经换成单框 Key 输入了。
- SECURITY.md —— 安全报告原本指向上游维护者个人邮箱。fork 之后那条路由
  是错的:漏洞会发给写不了这份代码、也修不了的人。
- CONTRIBUTING.md —— 补上 fork 关系、pre-push 钩子怎么装、以及
  `node --test tests/` 为什么不能用。

翻译并保留:
- bootable/README.md、TROUBLESHOOTING.md —— 面向用户,顺带把
  「国内镜像」「小米/华为 BIOS 按键」等换成目标市场的实际情况

HANDOFF.md 重写为一份事故复盘:原文一半是过时的一次性交接笔记(引用的
website/guide.html 已不在本仓库),另一半是 persistence.dat 未格式化导致
启动失败的排查记录 —— 后者有长期价值,尤其是「读 offset 1080 的两字节
验证 ext4」这个判断方法,已同时写进 bootable/README.md。

bootable/IMPROVEMENTS_SUMMARY.md 保留中文,加了说明:它是上游 fork 前的
历史改进记录,没人引用,描述的是已完成的工作而非当前行为。翻译它反而会
让人误以为是现行文档。

新增 skills/en/uclaw-help —— 把「怎么用、东西在哪、出问题怎么办」做成
内置知识,每个角色都装。方案 C10.8:能问的产品才是不需要学的产品。
2026-08-17 19:12:07 +08:00

5.5 KiB

Troubleshooting the bootable USB

While building the drive

Ventoy will not install

"Access Denied", or it cannot write to the drive.

  1. Run PowerShell as Administrator
  2. Close anything holding the drive open — File Explorer, antivirus, backup tools
  3. Try Ventoy's read-only install mode
  4. Check for a physical write-protect switch on the drive

The ISO download is slow or fails

The script pulls from releases.ubuntu.com and verifies the SHA256. If it keeps failing, download it yourself:

Put it in bootable/.download-cache/ and run 2-download-iso.ps1 again — it finds the cached file and verifies it rather than downloading again.

Not enough space for the persistence image

3-create-persistence.ps1 needs room for a 20 GB file alongside a 5.8 GB ISO.

  • A 32 GB drive is the practical minimum
  • Change $PersistenceSizeGB in the script to use less
  • Below about 8 GB there is not enough room to install anything meaningful

While booting

Black screen, or it hangs before the desktop

Press F6 or Esc at the boot menu to add kernel parameters:

Parameter What it does
nomodeset Skips the graphics driver — the usual fix
nouveau.modeset=0 For NVIDIA cards specifically
quiet splash Removes the splash screen so you can see where it stops

It drops into an initramfs prompt

persistence.dat has no ext4 filesystem in it. This is the single most common build failure, and the error message says nothing about the real cause.

sudo mkfs.ext4 -F -L casper-rw /media/*/Ventoy/persistence.dat

Then reboot — formatting does not take effect in the same session.

To check whether a file is actually formatted, read two bytes at offset 1080; they should be 0x53 0xEF.

No USB entry in the boot menu

  • Try a different port
  • In BIOS: disable Secure Boot, enable USB boot
  • Try both UEFI and Legacy/CSM modes

After booting

The OpenClaw install fails

Network — it needs to reach nodejs.org and registry.npmjs.org:

curl -I https://registry.npmjs.org
curl -I https://nodejs.org/dist

# behind a corporate proxy
export http_proxy=http://your-proxy:port
export https_proxy=http://your-proxy:port

Permissions — it has to run as root:

sudo bash setup-openclaw.sh

Missing packages:

sudo apt-get update && sudo apt-get install curl xdg-utils

U-Claw will not start

Check Node.js is there and is the version we pin:

/opt/u-claw/runtime/node-linux-x64/bin/node --version

Check OpenClaw landed:

ls -la /opt/u-claw/core/node_modules/openclaw/

Check for a port conflict — U-Claw uses 18789 to 18799:

ss -tlnp | grep :18789

# start it somewhere else if something else owns the range
cd /opt/u-claw/core
node node_modules/openclaw/openclaw.mjs gateway run --port 18800

The browser does not open by itself

Go to http://localhost:18789 yourself. Ubuntu Live normally has no firewall, but if you suspect one:

sudo ufw status

Data disappears after a reboot

  1. Make sure you picked the persistence entry in the Ventoy menu
  2. Check the file is the size you expect:
ls -lh /media/*/Ventoy/persistence.dat
  1. If it is corrupt, re-run 3-create-persistence.ps1 on the Windows machine

Everything is slow

Some of this is unavoidable — a USB drive is slower than a disk. What helps:

  • USB 3.0 drive in a USB 3.0 port. The largest single difference by far.
  • Turn down desktop effects: sudo apt-get install gnome-tweaks
  • Add swap, if you are running with persistence:
sudo fallocate -l 2G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile

Inference happens at your model provider, so conversation speed is not affected by any of this — only startup and file operations are.

Wi-Fi, Bluetooth or sound does not work

With persistence enabled you can install drivers and keep them:

sudo apt-get update
sudo apt-get install linux-generic-hwe-24.04    # newer kernel

ubuntu-drivers devices                          # what is available
sudo ubuntu-drivers autoinstall                 # install the recommended ones

If Wi-Fi still will not come up, tether over USB from a phone — it needs no drivers.

Digging deeper

# U-Claw's own log
tail -f /opt/u-claw/data/logs/openclaw.log

# kernel and system
dmesg | tail -20
journalctl -xe

# is the network reachable
curl -I https://registry.npmjs.org

# where the space went
df -h /media/*/Ventoy
du -sh /opt/u-claw/*

If it will not boot at all

  1. Get your data off first. Plug the drive into any Windows or Mac machine — the Ventoy data partition is readable, so back up anything under u-claw-linux/ before you touch anything else.
  2. Rebuild. Format the drive and run the four PowerShell scripts again.
  3. Ask. Open an issue at https://gitea.fanghe.it.com/zhenghy/u-claw/issues with what you saw on screen and which step it failed at.

Getting a better result

When building: use a good USB 3.0 drive, give persistence at least 20 GB, and turn off real-time antivirus scanning for the build — it slows the ISO write enormously and occasionally corrupts it.

On first boot: run the system updates and install the recommended drivers once, while you have network. With persistence on, you only do it once.

Long term: if you find yourself using it daily on the same machine, a real dual-boot install will be faster than any USB drive can be.