terry/Arkie-Library-Frontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: clarify runner disk diagnostics
All checks were successful
Deploy to Frontend Servers / deploy (push) Successful in 1m11s
Details

Browse Source
This commit is contained in:
TerryM
2026-06-09 01:14:08 +08:00
parent 41d737da11
commit c882cce0a4
2 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/deploy.md
View File

@@ -59,7 +59,7 @@ sudo resize2fs <root-partition> # ext filesystems
# or sudo xfs_growfs / # xfs filesystems
```
If the step cannot find `growpart`, it tries to install `cloud-utils-growpart` with `dnf`/`yum`. If install is blocked, install it manually on the runner host and rerun the workflow. The step also prints `lsblk`; if the parent disk still shows 8GB there, AWS has not attached/refreshed the expanded EBS volume for this instance.
If the step cannot find `growpart`, it tries to install `cloud-utils-growpart` with `dnf`/`yum`. If install is blocked, install it manually on the runner host and rerun the workflow. The step also prints `hostname`, `lsblk`, and the visible parent disk byte size. If `growpart` says `NOCHANGE` and the parent disk still shows 8GB, the job is running on the wrong runner/volume or the OS still has not seen the expanded EBS volume; verify the EC2 instance/volume pair and reboot/rescan the runner host.
### Node version is too old