{"id":2301,"date":"2026-05-04T08:24:27","date_gmt":"2026-05-04T08:24:27","guid":{"rendered":"https:\/\/sreschool.com\/blog\/?p=2301"},"modified":"2026-05-04T08:24:28","modified_gmt":"2026-05-04T08:24:28","slug":"godaddy-vps-recovery-console-and-rescue-mode-tutorial","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/","title":{"rendered":"GoDaddy VPS Recovery Console and Rescue Mode Tutorial:"},"content":{"rendered":"\n

Complete GoDaddy VPS Recovery Console and Rescue Mode Tutorial: End-to-End Troubleshooting, Recovery, Disk Repair, Firewall, Nydus, Snapshot Restore, and Disk Expansion<\/h1>\n\n\n\n

GoDaddy VPS issues can become stressful very quickly because one problem often leads to another: SSH stops working, Recovery Console shows GRUB rescue, disk reaches 100%, snapshot restore fails, Nydus services stop, port 2224 is reported blocked, and after a plan upgrade Linux still shows the old disk size.<\/p>\n\n\n\n

This tutorial consolidates the complete practical workflow we followed and turns it into a reusable master guide for GoDaddy VPS recovery.<\/p>\n\n\n\n

GoDaddy\u2019s Recovery Console is meant to help regain VPS access when normal SSH\/RDP access is broken, such as after a firewall or iptables mistake. GoDaddy says the Recovery Console is available from Servers \u2192 Manage \u2192 Server Actions \u2192 Recovery Console<\/strong>, and port 2224<\/strong> must not be blocked for Recovery Console access. (GoDaddy<\/a>)<\/p>\n\n\n\n

GoDaddy also documents that VPS Hosting depends on port 2224<\/strong> and Nydus services<\/strong>, specifically nydus-ex<\/code> and nydus-ex-api<\/code>; if these are blocked or modified, dashboard\/management capability may be disrupted. (GoDaddy<\/a>)<\/p>\n\n\n\n

\n\n\n\n

1. Recovery Console vs Rescue Mode<\/h2>\n\n\n\n

Recovery Console<\/h3>\n\n\n\n

Recovery Console is like a browser-based screen\/keyboard attached to your VPS. It shows what the server is doing during boot.<\/p>\n\n\n\n

Use Recovery Console when:<\/p>\n\n\n\n

SSH is not working\nserver is stuck at GRUB rescue\nyou need to see boot errors\nyou need emergency console access\nyou accidentally blocked SSH\/firewall\nyou need to log in from browser console\n<\/code><\/pre>\n\n\n\n
Example screen you may see:<\/p>\n\n\n\n
grub rescue>\n<\/code><\/pre>\n\n\n\n
At this point, you are not inside Linux. You cannot clean files, run df -h<\/code>, restart services, or delete logs. You can only run limited GRUB commands.<\/p>\n\n\n\n
Rescue Mode<\/h3>\n\n\n\n
Rescue Mode boots your VPS into a temporary Linux rescue OS. Your original VPS disk is attached as a secondary disk, usually something like \/dev\/sda<\/code>.<\/p>\n\n\n\n
Use Rescue Mode when:<\/p>\n\n\n\n
normal OS does not boot\nGRUB is broken\nfilesystem needs repair\nyou need to mount the original disk\nyou need to recover files\nyou need to run xfs_repair\nyou need to inspect partitions\n<\/code><\/pre>\n\n\n\n
Simple difference:<\/p>\n\n\n\n
Recovery Console = see\/control the broken server boot screen\nRescue Mode      = boot into temporary repair Linux OS\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
2. Common GoDaddy VPS Failure Scenarios<\/h2>\n\n\n\n
You may need Recovery Console or Rescue Mode for these cases:<\/p>\n\n\n\n
SSH not connecting\nserver stuck in GRUB rescue\ndisk reached 100%\nroot filesystem corrupted\n\/boot partition empty or missing GRUB files\nsnapshot restore failed\nGoDaddy says port 2224 is blocked\nNydus services not running\nplan upgraded but Linux still shows old disk size\nroot prompt changed to bash-5.1#\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
3. When Server Drops to GRUB Rescue<\/h2>\n\n\n\n
Example error:<\/p>\n\n\n\n
error: file '\/grub2\/i386-pc\/normal.mod' not found\ngrub rescue>\n<\/code><\/pre>\n\n\n\n
This means GRUB cannot load its normal module. Common causes:<\/p>\n\n\n\n
\/boot partition damaged\nGRUB files missing\nkernel\/initramfs missing\nfilesystem corruption\ndisk\/partition changed\nfailed update\n<\/code><\/pre>\n\n\n\n
At grub rescue><\/code>, first list partitions:<\/p>\n\n\n\n
ls\n<\/code><\/pre>\n\n\n\n
Example output:<\/p>\n\n\n\n
(hd0) (hd0,gpt4) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1)\n<\/code><\/pre>\n\n\n\n
Check partitions one by one:<\/p>\n\n\n\n
ls (hd0,gpt1)\/\nls (hd0,gpt2)\/\nls (hd0,gpt3)\/\nls (hd0,gpt4)\/\n<\/code><\/pre>\n\n\n\n
You are looking for directories like:<\/p>\n\n\n\n
boot\/\netc\/\nhome\/\nvar\/\nusr\/\n<\/code><\/pre>\n\n\n\n
If you find \/boot\/grub2<\/code>, try:<\/p>\n\n\n\n
set root=(hd0,gptX)\nset prefix=(hd0,gptX)\/boot\/grub2\ninsmod normal\nnormal\n<\/code><\/pre>\n\n\n\n
If \/boot<\/code> is a separate partition and GRUB files are directly under \/grub2<\/code>, try:<\/p>\n\n\n\n
set root=(hd0,gptX)\nset prefix=(hd0,gptX)\/grub2\ninsmod normal\nnormal\n<\/code><\/pre>\n\n\n\n
But if you see that \/boot<\/code> is empty or normal.mod<\/code> is missing, do not waste too much time. Move to Rescue Mode.<\/p>\n\n\n\n
\n\n\n\n
4. Entering Rescue Mode and Logging In<\/h2>\n\n\n\n
After enabling Rescue Mode in GoDaddy, you may receive rescue credentials.<\/p>\n\n\n\n
SSH command example:<\/p>\n\n\n\n
ssh rescue_user@SERVER_IP\n<\/code><\/pre>\n\n\n\n
If you get this warning:<\/p>\n\n\n\n
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!\nHost key verification failed.\n<\/code><\/pre>\n\n\n\n
It is expected because Rescue Mode uses a different temporary OS and SSH host key.<\/p>\n\n\n\n
Fix on your local machine:<\/p>\n\n\n\n
ssh-keygen -R SERVER_IP\n<\/code><\/pre>\n\n\n\n
Then connect again:<\/p>\n\n\n\n
ssh rescue_user@SERVER_IP\n<\/code><\/pre>\n\n\n\n
Type:<\/p>\n\n\n\n
yes\n<\/code><\/pre>\n\n\n\n
Then enter the rescue password.<\/p>\n\n\n\n
\n\n\n\n
5. Identify Original Disk in Rescue Mode<\/h2>\n\n\n\n
Once inside Rescue Mode, run:<\/p>\n\n\n\n
lsblk -f\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
sda\n\u251c\u2500sda1\n\u251c\u2500sda2 vfat\n\u251c\u2500sda3 xfs\n\u2514\u2500sda4 xfs\n\nsdb\n\u251c\u2500sdb2 vfat \/boot\/efi\n\u251c\u2500sdb3 xfs  \/boot\n\u2514\u2500sdb4 xfs  \/\n<\/code><\/pre>\n\n\n\n
In this example:<\/p>\n\n\n\n
sdb = rescue OS disk\nsda = original broken VPS disk\n<\/code><\/pre>\n\n\n\n
Typical GoDaddy AlmaLinux\/cPanel layout:<\/p>\n\n\n\n
\/dev\/sda1 = BIOS boot\n\/dev\/sda2 = EFI\n\/dev\/sda3 = \/boot\n\/dev\/sda4 = \/\n<\/code><\/pre>\n\n\n\n
Confirm partition table:<\/p>\n\n\n\n
fdisk -l \/dev\/sda\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
6. Mount Original VPS Disk<\/h2>\n\n\n\n
Create mount point and mount root partition:<\/p>\n\n\n\n
mkdir -p \/mnt\/original\nmount \/dev\/sda4 \/mnt\/original\n<\/code><\/pre>\n\n\n\n
Check usage:<\/p>\n\n\n\n
df -h \/mnt\/original\n<\/code><\/pre>\n\n\n\n
Mount boot partition:<\/p>\n\n\n\n
mkdir -p \/mnt\/original\/boot\nmount \/dev\/sda3 \/mnt\/original\/boot\n<\/code><\/pre>\n\n\n\n
Check boot usage:<\/p>\n\n\n\n
df -h \/mnt\/original\/boot\n<\/code><\/pre>\n\n\n\n
Inspect root filesystem:<\/p>\n\n\n\n
ls -lah \/mnt\/original\n<\/code><\/pre>\n\n\n\n
A healthy Linux root should contain:<\/p>\n\n\n\n
bin\nboot\ndev\netc\nhome\nlib\nlib64\nopt\nproc\nroot\nrun\nsbin\ntmp\nusr\nvar\n<\/code><\/pre>\n\n\n\n
If critical directories are missing:<\/p>\n\n\n\n
\/etc\n\/bin\n\/sbin\n\/lib\n\/lib64\n\/root\n<\/code><\/pre>\n\n\n\n
then the OS is seriously damaged or incomplete.<\/p>\n\n\n\n
\n\n\n\n
7. Check Whether Disk Is Actually Full<\/h2>\n\n\n\n
From rescue mode:<\/p>\n\n\n\n
df -h \/mnt\/original\ndu -h --max-depth=1 \/mnt\/original | sort -h\n<\/code><\/pre>\n\n\n\n
Check \/home<\/code>:<\/p>\n\n\n\n
du -h --max-depth=2 \/mnt\/original\/home | sort -h\n<\/code><\/pre>\n\n\n\n
Check largest files:<\/p>\n\n\n\n
find \/mnt\/original -xdev -type f -printf '%s %p\\n' | sort -nr | head -50\n<\/code><\/pre>\n\n\n\n
Check backups, WordPress configs, SQL dumps, archives:<\/p>\n\n\n\n
find \/mnt\/original \\\n  -iname '*mysql*' -o \\\n  -iname '*wp-config*' -o \\\n  -iname '*.sql' -o \\\n  -iname '*.tar*' -o \\\n  -iname '*.zip' | head -100\n<\/code><\/pre>\n\n\n\n
Check cPanel traces:<\/p>\n\n\n\n
find \/mnt\/original -maxdepth 5 \\\n  -iname '*cpanel*' -o \\\n  -iname 'userdata' -o \\\n  -iname 'domains' | head -100\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
8. XFS Filesystem Repair<\/h2>\n\n\n\n
If original root partition is XFS, first unmount it:<\/p>\n\n\n\n
umount \/mnt\/original\/boot\numount \/mnt\/original\n<\/code><\/pre>\n\n\n\n
Run dry-run repair first:<\/p>\n\n\n\n
xfs_repair -n \/dev\/sda4\n<\/code><\/pre>\n\n\n\n
If dry-run shows issues, run actual repair:<\/p>\n\n\n\n
xfs_repair \/dev\/sda4\n<\/code><\/pre>\n\n\n\n
Then mount again:<\/p>\n\n\n\n
mkdir -p \/mnt\/original\nmount \/dev\/sda4 \/mnt\/original\n<\/code><\/pre>\n\n\n\n
Check:<\/p>\n\n\n\n
ls -lah \/mnt\/original\nfind \/mnt\/original -maxdepth 2 -name 'lost+found' -type d -print\n<\/code><\/pre>\n\n\n\n
Important: xfs_repair<\/code> may fix metadata, but it cannot magically restore deleted OS files if the data is gone.<\/p>\n\n\n\n
\n\n\n\n
9. When to Stop Local Repair and Ask for Snapshot Restore<\/h2>\n\n\n\n
If you find only a few files left, or critical directories are missing, stop trying local repair.<\/p>\n\n\n\n
Bad signs:<\/p>\n\n\n\n
\/etc missing\n\/bin missing\n\/lib64 missing\n\/root missing\n\/boot empty\n\/home websites nearly empty\nonly a few files remain\n<\/code><\/pre>\n\n\n\n
At this point, ask GoDaddy for snapshot restore.<\/p>\n\n\n\n
Message template:<\/p>\n\n\n\n
Hello GoDaddy Support,\n\nMy VPS became unbootable and dropped into GRUB rescue mode with this error:\n\nfile \/grub2\/i386-pc\/normal.mod not found\n\nI enabled Rescue Mode and mounted the original disk.\n\nOriginal disk: \/dev\/sda\nOriginal root partition: \/dev\/sda4\nOriginal boot partition: \/dev\/sda3\n\nThe filesystem appears damaged\/incomplete. Critical OS directories such as \/etc, \/bin, \/sbin, \/lib, \/lib64, \/root, and normal \/boot files are missing.\n\nPlease restore the full VPS from the latest available snapshot\/backup before the issue occurred.\n\nIf full restore is not possible, please attach the backup\/snapshot as a secondary disk so I can recover website files, databases, emails, and cPanel data.\n\nPlease do not rebuild\/reinstall the VPS until backup\/snapshot options are confirmed.\n<\/code><\/pre>\n\n\n\n
GoDaddy\u2019s own guidance for port\/Nydus problems also mentions restoring from a backup when you know a recent date when the server was operational, and rebuild only after other options are exhausted. (GoDaddy<\/a>)<\/p>\n\n\n\n
\n\n\n\n
10. Restore vs Rebuild<\/h2>\n\n\n\n
Restore<\/h3>\n\n\n\n
Restore means GoDaddy uses an old backup\/snapshot to bring back your full server.<\/p>\n\n\n\n
Best option if available.<\/p>\n\n\n\n
It can restore:<\/p>\n\n\n\n
OS\ncPanel\/WHM\nApache\/Nginx\nPHP\nMySQL\/MariaDB\nwebsite files\nemail data\nDNS\/cPanel configs\nSSLs\ncron jobs\n<\/code><\/pre>\n\n\n\n
Rebuild<\/h3>\n\n\n\n
Rebuild means fresh OS install.<\/p>\n\n\n\n
Danger:<\/p>\n\n\n\n
It can wipe old data.\n<\/code><\/pre>\n\n\n\n
Only rebuild if:<\/p>\n\n\n\n
no snapshot exists\nyou have external backups\nGoDaddy confirms restore is impossible\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11. Port 2224 and Nydus Services<\/h2>\n\n\n\n
GoDaddy states that VPS Hosting requires port 2224<\/strong> and Nydus services nydus-ex<\/code> and nydus-ex-api<\/code>; if blocked or modified, service disruption may happen. (GoDaddy<\/a>)<\/p>\n\n\n\n
Check services:<\/p>\n\n\n\n
systemctl is-active nydus-ex.service nydus-ex-api.service\n<\/code><\/pre>\n\n\n\n
Expected:<\/p>\n\n\n\n
active\nactive\n<\/code><\/pre>\n\n\n\n
Detailed status:<\/p>\n\n\n\n
systemctl status nydus-ex.service --no-pager -l\nsystemctl status nydus-ex-api.service --no-pager -l\n<\/code><\/pre>\n\n\n\n
Logs:<\/p>\n\n\n\n
journalctl -u nydus-ex.service -n 80 --no-pager\njournalctl -u nydus-ex-api.service -n 80 --no-pager\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
12. Fix Nydus Log File Issues<\/h2>\n\n\n\n
In our real case, nydus-ex<\/code> failed because:<\/p>\n\n\n\n
FileNotFoundError: No such file or directory: \/var\/log\/nydus\/worker.log\nValueError: Unable to configure handler 'rotfile'\n<\/code><\/pre>\n\n\n\n
Fix:<\/p>\n\n\n\n
mkdir -p \/var\/log\/nydus\ntouch \/var\/log\/nydus\/worker.log\nchmod 755 \/var\/log\/nydus\nsystemctl restart nydus-ex.service\n<\/code><\/pre>\n\n\n\n
Then verify:<\/p>\n\n\n\n
systemctl status nydus-ex.service --no-pager -l\n<\/code><\/pre>\n\n\n\n
For nydus-ex-api<\/code>, we saw:<\/p>\n\n\n\n
PermissionError: Permission denied: \/var\/log\/nydus\/server.log\nValueError: Unable to configure handler 'rotfile'\n<\/code><\/pre>\n\n\n\n
Temporary repair:<\/p>\n\n\n\n
touch \/var\/log\/nydus\/server.log \/var\/log\/nydus\/worker.log\nchown -R root:root \/var\/log\/nydus\nchmod 777 \/var\/log\/nydus\nchmod 666 \/var\/log\/nydus\/server.log \/var\/log\/nydus\/worker.log\nsystemctl restart nydus-ex.service nydus-ex-api.service\n<\/code><\/pre>\n\n\n\n
Verify:<\/p>\n\n\n\n
systemctl is-active nydus-ex.service nydus-ex-api.service\n<\/code><\/pre>\n\n\n\n
Expected:<\/p>\n\n\n\n
active\nactive\n<\/code><\/pre>\n\n\n\n
Security note: 777<\/code> and 666<\/code> are temporary emergency permissions to get the GoDaddy agent running. Once GoDaddy finishes upgrade\/restore, ask support for the correct ownership\/permission for \/var\/log\/nydus<\/code>, or tighten carefully.<\/p>\n\n\n\n
\n\n\n\n
13. Check Port 2224 Firewall Status<\/h2>\n\n\n\n
GoDaddy\u2019s firewallD example is:<\/p>\n\n\n\n
firewall-cmd --permanent --zone=public --add-port=2224\/tcp\nfirewall-cmd --reload\nfirewall-cmd --list-ports\n<\/code><\/pre>\n\n\n\n
But on some AlmaLinux\/cPanel VPS systems, firewall-cmd<\/code> may not exist:<\/p>\n\n\n\n
firewall-cmd: command not found\nUnit firewalld.service could not be found.\n<\/code><\/pre>\n\n\n\n
Check:<\/p>\n\n\n\n
systemctl status firewalld --no-pager -l\n<\/code><\/pre>\n\n\n\n
If firewalld is missing, use iptables.<\/p>\n\n\n\n
Allow port 2224:<\/p>\n\n\n\n
iptables -I INPUT 1 -p tcp --dport 2224 -j ACCEPT\n<\/code><\/pre>\n\n\n\n
Verify:<\/p>\n\n\n\n
iptables -L INPUT -n --line-numbers | grep 2224\niptables -S INPUT\n<\/code><\/pre>\n\n\n\n
Good output:<\/p>\n\n\n\n
-P INPUT ACCEPT\n-A INPUT -p tcp -m tcp --dport 2224 -j ACCEPT\n<\/code><\/pre>\n\n\n\n
If you temporarily want to open OS firewall completely:<\/p>\n\n\n\n
iptables -P INPUT ACCEPT\niptables -P FORWARD ACCEPT\niptables -P OUTPUT ACCEPT\niptables -F\niptables -S\n<\/code><\/pre>\n\n\n\n
Expected:<\/p>\n\n\n\n
-P INPUT ACCEPT\n-P FORWARD ACCEPT\n-P OUTPUT ACCEPT\n<\/code><\/pre>\n\n\n\n
Important: If ss -lntp | grep 2224<\/code> shows nothing, it means no service is listening on 2224. That is different from firewall blocking. A port can be allowed but still appear closed externally if no process listens.<\/p>\n\n\n\n
Check listener:<\/p>\n\n\n\n
ss -lntp | grep 2224\n<\/code><\/pre>\n\n\n\n
Check Nydus listeners\/connections:<\/p>\n\n\n\n
ss -lntp | grep nydus\nss -antp | grep nydus\n<\/code><\/pre>\n\n\n\n
If GoDaddy says 2224 is blocked, but your OS firewall is open, tell them:<\/p>\n\n\n\n
firewalld is not installed.\niptables INPUT policy is ACCEPT.\nPort 2224 is explicitly allowed.\nBoth nydus-ex and nydus-ex-api are active.\nNo process is listening locally on 2224, so please confirm whether Nydus is expected to bind to port 2224 or whether this is a GoDaddy platform\/network firewall check.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
14. Fix Root Prompt Showing bash-5.1#<\/code><\/h2>\n\n\n\n
If after recovery you see:<\/p>\n\n\n\n
bash-5.1#\n<\/code><\/pre>\n\n\n\n
but you expected:<\/p>\n\n\n\n
[root@server ~]#\n<\/code><\/pre>\n\n\n\n
Check root identity:<\/p>\n\n\n\n
id\n<\/code><\/pre>\n\n\n\n
If output is:<\/p>\n\n\n\n
uid=0(root) gid=0(root) groups=0(root)\n<\/code><\/pre>\n\n\n\n
then you are root. The prompt issue is usually shell profile related.<\/p>\n\n\n\n
Check files:<\/p>\n\n\n\n
ls -lah \/root\/.bashrc \/root\/.bash_profile \/etc\/profile \/etc\/bashrc 2>\/dev\/null\necho \"$PS1\"\n<\/code><\/pre>\n\n\n\n
If \/root\/.bashrc<\/code> and \/root\/.bash_profile<\/code> are empty, recreate them:<\/p>\n\n\n\n
cat > \/root\/.bashrc <<'EOF'\n# .bashrc\n\nif [ -f \/etc\/bashrc ]; then\n    . \/etc\/bashrc\nfi\n\nalias ls='ls --color=auto'\nalias ll='ls -alF --color=auto'\nalias la='ls -A --color=auto'\n\nexport PS1='[\\u@\\h \\W]\\$ '\nEOF\n\ncat > \/root\/.bash_profile <<'EOF'\n# .bash_profile\n\nif [ -f ~\/.bashrc ]; then\n    . ~\/.bashrc\nfi\nEOF\n\nsource \/root\/.bashrc\n<\/code><\/pre>\n\n\n\n
Now prompt should become:<\/p>\n\n\n\n
[root@47 home]#\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
15. Check Filesystem Permissions Safely<\/h2>\n\n\n\n
Do not run dangerous commands like:<\/p>\n\n\n\n
chmod -R 755 \/\nchown -R root:root \/\n<\/code><\/pre>\n\n\n\n
These can destroy cPanel, mail, MySQL, website users, SSH keys, and application permissions.<\/p>\n\n\n\n
Instead, inspect:<\/p>\n\n\n\n
ls -ld \/ \/root \/etc \/var \/var\/log \/var\/log\/nydus \/opt \/opt\/nydus \/home\n<\/code><\/pre>\n\n\n\n
Healthy examples:<\/p>\n\n\n\n
\/              root:root\n\/etc           root:root\n\/home          root:root\n\/opt           root:root\n\/opt\/nydus     nydus:nydus\n\/root          root:root\n\/var           root:root\n\/var\/log       root:root\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
16. After GoDaddy Plan Upgrade: Disk Shows 400 GB but Linux Still Shows 199 GB<\/h2>\n\n\n\n
This is very common.<\/p>\n\n\n\n
First check:<\/p>\n\n\n\n
lsblk\ndf -kh\n<\/code><\/pre>\n\n\n\n
Example before expansion:<\/p>\n\n\n\n
sda      400G disk\n\u2514\u2500sda4   198.8G part \/\n\ndf -kh \/\n\/dev\/sda4 199G 195G 4.7G 98% \/\n<\/code><\/pre>\n\n\n\n
Meaning:<\/p>\n\n\n\n
GoDaddy expanded virtual disk\nLinux partition\/filesystem not expanded yet\n<\/code><\/pre>\n\n\n\n
Install growpart if missing:<\/p>\n\n\n\n
dnf install -y cloud-utils-growpart\n<\/code><\/pre>\n\n\n\n
Expand partition 4:<\/p>\n\n\n\n
growpart \/dev\/sda 4\n<\/code><\/pre>\n\n\n\n
Example success:<\/p>\n\n\n\n
CHANGED: partition=4 start=2510848 old: size=416916481 end=419427328 new: size=836349919 end=838860766\n<\/code><\/pre>\n\n\n\n
For XFS filesystem, expand root filesystem:<\/p>\n\n\n\n
xfs_growfs \/\n<\/code><\/pre>\n\n\n\n
Verify:<\/p>\n\n\n\n
df -kh \/\nlsblk\n<\/code><\/pre>\n\n\n\n
Expected:<\/p>\n\n\n\n
\/dev\/sda4 399G 196G 204G 50% \/\nsda4      398.8G part \/\n<\/code><\/pre>\n\n\n\n
Final status example:<\/p>\n\n\n\n
Disk:        \/dev\/sda = 400G\nRoot part:   \/dev\/sda4 = 398.8G\nFilesystem:  \/ = 399G\nUsed:        196G\nAvailable:   204G\nUsage:       50%\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
17. Disk Full Cleanup Checklist After Server Is Booting<\/h2>\n\n\n\n
Once the server is booting normally and has enough space, clean safely.<\/p>\n\n\n\n
Check top-level usage:<\/p>\n\n\n\n
df -kh\ndu -h --max-depth=1 \/ | sort -h\n<\/code><\/pre>\n\n\n\n
Check \/home<\/code>:<\/p>\n\n\n\n
du -h --max-depth=1 \/home | sort -h\n<\/code><\/pre>\n\n\n\n
Check \/var<\/code>:<\/p>\n\n\n\n
du -h --max-depth=1 \/var | sort -h\n<\/code><\/pre>\n\n\n\n
Check logs:<\/p>\n\n\n\n
du -h --max-depth=1 \/var\/log | sort -h\ndu -h --max-depth=1 \/usr\/local\/cpanel\/logs | sort -h\n<\/code><\/pre>\n\n\n\n
Check cPanel backups:<\/p>\n\n\n\n
du -h --max-depth=2 \/backup 2>\/dev\/null | sort -h\ndu -h --max-depth=2 \/home\/*\/backup* 2>\/dev\/null | sort -h\n<\/code><\/pre>\n\n\n\n
Check large files:<\/p>\n\n\n\n
find \/ -xdev -type f -size +500M -printf '%s %p\\n' 2>\/dev\/null | sort -nr | head -50\n<\/code><\/pre>\n\n\n\n
Check deleted files still held open:<\/p>\n\n\n\n
lsof +L1\n<\/code><\/pre>\n\n\n\n
If a deleted log is held by a service, restart the service instead of rebooting blindly.<\/p>\n\n\n\n
\n\n\n\n
18. Safe Log Cleanup Examples<\/h2>\n\n\n\n
Do not delete random files. Truncate logs safely:<\/p>\n\n\n\n
truncate -s 0 \/var\/log\/messages\ntruncate -s 0 \/var\/log\/secure\ntruncate -s 0 \/var\/log\/maillog\n<\/code><\/pre>\n\n\n\n
For cPanel logs:<\/p>\n\n\n\n
du -sh \/usr\/local\/cpanel\/logs\/*\n<\/code><\/pre>\n\n\n\n
Truncate selected large logs:<\/p>\n\n\n\n
truncate -s 0 \/usr\/local\/cpanel\/logs\/error_log\ntruncate -s 0 \/usr\/local\/cpanel\/logs\/queueprocd.log\n<\/code><\/pre>\n\n\n\n
Clear temporary files carefully:<\/p>\n\n\n\n
find \/tmp -type f -mtime +2 -delete\nfind \/var\/tmp -type f -mtime +2 -delete\n<\/code><\/pre>\n\n\n\n
For package cache:<\/p>\n\n\n\n
dnf clean all\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
19. Recommended Communication With GoDaddy<\/h2>\n\n\n\n
When port 2224 is open but they still say blocked<\/h3>\n\n\n\n
I verified the VPS OS firewall.\n\nfirewalld is not installed.\niptables -S INPUT shows default policy ACCEPT.\nTCP port 2224 is explicitly allowed.\nBoth Nydus services are active.\n\nHowever, ss -lntp | grep 2224 shows no local listener on port 2224.\n\nPlease confirm whether Nydus is expected to bind locally to 2224, or whether this is checked at the GoDaddy platform\/network firewall layer.\n<\/code><\/pre>\n\n\n\n
When Nydus is fixed<\/h3>\n\n\n\n
I fixed the Nydus issue.\n\nnydus-ex.service is active.\nnydus-ex-api.service is active.\nThe OS firewall is open.\nPlease refresh the dashboard capability check and proceed with upgrade\/restore.\n<\/code><\/pre>\n\n\n\n
When disk upgrade is completed<\/h3>\n\n\n\n
The VPS disk upgrade is now visible inside Linux.\n\nCurrent status:\nDisk \/dev\/sda = 400G\nPartition \/dev\/sda4 = 398.8G mounted on \/\nFilesystem \/dev\/sda4 = 399G total, 196G used, 204G available, 50% used\n\nI expanded the partition using growpart \/dev\/sda 4 and expanded XFS using xfs_growfs \/.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
20. Full Emergency Command Flow<\/h2>\n\n\n\n
Use this as a quick checklist.<\/p>\n\n\n\n
In Recovery Console GRUB rescue<\/h3>\n\n\n\n
ls\nls (hd0,gpt1)\/\nls (hd0,gpt2)\/\nls (hd0,gpt3)\/\nls (hd0,gpt4)\/\n<\/code><\/pre>\n\n\n\n
In Rescue Mode<\/h3>\n\n\n\n
lsblk -f\nfdisk -l \/dev\/sda\nmkdir -p \/mnt\/original\nmount \/dev\/sda4 \/mnt\/original\ndf -h \/mnt\/original\nls -lah \/mnt\/original\n<\/code><\/pre>\n\n\n\n
Mount boot<\/h3>\n\n\n\n
mkdir -p \/mnt\/original\/boot\nmount \/dev\/sda3 \/mnt\/original\/boot\ndf -h \/mnt\/original\/boot\nls -lah \/mnt\/original\/boot\n<\/code><\/pre>\n\n\n\n
Repair XFS<\/h3>\n\n\n\n
umount \/mnt\/original\/boot\numount \/mnt\/original\nxfs_repair -n \/dev\/sda4\nxfs_repair \/dev\/sda4\n<\/code><\/pre>\n\n\n\n
Check Nydus<\/h3>\n\n\n\n
systemctl is-active nydus-ex.service nydus-ex-api.service\nsystemctl status nydus-ex.service --no-pager -l\nsystemctl status nydus-ex-api.service --no-pager -l\njournalctl -u nydus-ex.service -n 80 --no-pager\njournalctl -u nydus-ex-api.service -n 80 --no-pager\n<\/code><\/pre>\n\n\n\n
Fix Nydus logs<\/h3>\n\n\n\n
mkdir -p \/var\/log\/nydus\ntouch \/var\/log\/nydus\/server.log \/var\/log\/nydus\/worker.log\nchmod 777 \/var\/log\/nydus\nchmod 666 \/var\/log\/nydus\/server.log \/var\/log\/nydus\/worker.log\nsystemctl restart nydus-ex.service nydus-ex-api.service\nsystemctl is-active nydus-ex.service nydus-ex-api.service\n<\/code><\/pre>\n\n\n\n
Check firewall<\/h3>\n\n\n\n
systemctl status firewalld --no-pager -l\niptables -S INPUT\niptables -L INPUT -n --line-numbers | grep 2224\nss -lntp | grep 2224\n<\/code><\/pre>\n\n\n\n
Open iptables temporarily<\/h3>\n\n\n\n
iptables -P INPUT ACCEPT\niptables -P FORWARD ACCEPT\niptables -P OUTPUT ACCEPT\niptables -F\niptables -S\n<\/code><\/pre>\n\n\n\n
Expand disk after GoDaddy upgrade<\/h3>\n\n\n\n
lsblk\ndf -kh \/\ndnf install -y cloud-utils-growpart\ngrowpart \/dev\/sda 4\nxfs_growfs \/\ndf -kh \/\nlsblk\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
21. Final Best Practices<\/h2>\n\n\n\n
Keep these rules in mind:<\/p>\n\n\n\n
Do not rebuild unless backup restore is impossible.\nDo not run recursive chmod\/chown on \/.\nDo not delete files while unsure.\nDo not assume port 2224 is blocked only because no listener appears.\nDo not confuse Recovery Console with Rescue Mode.\nAlways check lsblk before mounting disks.\nAlways run xfs_repair -n before actual repair.\nAlways expand both partition and filesystem after VPS disk upgrade.\n<\/code><\/pre>\n\n\n\n
The safest recovery order is:<\/p>\n\n\n\n
1. Use Recovery Console to observe boot problem.\n2. Use Rescue Mode to inspect\/mount\/repair disk.\n3. If OS\/data is missing, request snapshot restore.\n4. Fix port 2224\/Nydus if GoDaddy dashboard capability is limited.\n5. After plan upgrade, expand partition using growpart.\n6. Expand XFS filesystem using xfs_growfs.\n7. Verify df -kh and lsblk.\n8. Clean disk only after server is stable.\n<\/code><\/pre>\n\n\n\n
This workflow gives you a reliable, end-to-end method to handle GoDaddy VPS emergencies without accidentally wiping data or making recovery harder.<\/p>\n","protected":false},"excerpt":{"rendered":"
Complete GoDaddy VPS Recovery Console and Rescue Mode Tutorial: End-to-End Troubleshooting, Recovery, Disk Repair, Firewall, Nydus, Snapshot Restore, and Disk […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2301","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nGoDaddy VPS Recovery Console and Rescue Mode Tutorial: - SRE School<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"GoDaddy VPS Recovery Console and Rescue Mode Tutorial: - SRE School\" \/>\n<meta property=\"og:description\" content=\"Complete GoDaddy VPS Recovery Console and Rescue Mode Tutorial: End-to-End Troubleshooting, Recovery, Disk Repair, Firewall, Nydus, Snapshot Restore, and Disk […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2026-05-04T08:24:27+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-04T08:24:28+00:00\" \/>\n<meta name=\"author\" content=\"Rajesh Kumar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rajesh Kumar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/\",\"url\":\"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/\",\"name\":\"GoDaddy VPS Recovery Console and Rescue Mode Tutorial: - SRE School\",\"isPartOf\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#website\"},\"datePublished\":\"2026-05-04T08:24:27+00:00\",\"dateModified\":\"2026-05-04T08:24:28+00:00\",\"author\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/0ffe446f77bb2589992dbe3a7f417201\"},\"breadcrumb\":{\"@id\":\"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sreschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"GoDaddy VPS Recovery Console and Rescue Mode Tutorial:\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/sreschool.com\/blog\/#website\",\"url\":\"https:\/\/sreschool.com\/blog\/\",\"name\":\"SRESchool\",\"description\":\"Master SRE. Build Resilient Systems. Lead the Future of Reliability\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/sreschool.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/0ffe446f77bb2589992dbe3a7f417201\",\"name\":\"Rajesh Kumar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f901a4f2929fa034a291a8363d589791d5a3c1f6a051c22e744acb8bfc8e022a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f901a4f2929fa034a291a8363d589791d5a3c1f6a051c22e744acb8bfc8e022a?s=96&d=mm&r=g\",\"caption\":\"Rajesh Kumar\"},\"sameAs\":[\"http:\/\/sreschool.com\/blog\"],\"url\":\"https:\/\/sreschool.com\/blog\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"GoDaddy VPS Recovery Console and Rescue Mode Tutorial: - SRE School","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/","og_locale":"en_US","og_type":"article","og_title":"GoDaddy VPS Recovery Console and Rescue Mode Tutorial: - SRE School","og_description":"Complete GoDaddy VPS Recovery Console and Rescue Mode Tutorial: End-to-End Troubleshooting, Recovery, Disk Repair, Firewall, Nydus, Snapshot Restore, and Disk […]","og_url":"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/","og_site_name":"SRE School","article_published_time":"2026-05-04T08:24:27+00:00","article_modified_time":"2026-05-04T08:24:28+00:00","author":"Rajesh Kumar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Rajesh Kumar","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/","url":"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/","name":"GoDaddy VPS Recovery Console and Rescue Mode Tutorial: - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2026-05-04T08:24:27+00:00","dateModified":"2026-05-04T08:24:28+00:00","author":{"@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/0ffe446f77bb2589992dbe3a7f417201"},"breadcrumb":{"@id":"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/godaddy-vps-recovery-console-and-rescue-mode-tutorial\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"GoDaddy VPS Recovery Console and Rescue Mode Tutorial:"}]},{"@type":"WebSite","@id":"https:\/\/sreschool.com\/blog\/#website","url":"https:\/\/sreschool.com\/blog\/","name":"SRESchool","description":"Master SRE. Build Resilient Systems. Lead the Future of Reliability","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sreschool.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Person","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/0ffe446f77bb2589992dbe3a7f417201","name":"Rajesh Kumar","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/f901a4f2929fa034a291a8363d589791d5a3c1f6a051c22e744acb8bfc8e022a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f901a4f2929fa034a291a8363d589791d5a3c1f6a051c22e744acb8bfc8e022a?s=96&d=mm&r=g","caption":"Rajesh Kumar"},"sameAs":["http:\/\/sreschool.com\/blog"],"url":"https:\/\/sreschool.com\/blog\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/2301","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/comments?post=2301"}],"version-history":[{"count":1,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/2301\/revisions"}],"predecessor-version":[{"id":2302,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/2301\/revisions\/2302"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=2301"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=2301"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=2301"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}