aDeploy pre-uppdate check failed (local partition space)

Patrick Chan Lv1Posted Sep-02-2025 10:40

Need to advise on how to solve the problem.
I want to upgrade from 6.10 to 6.11

QUOTE
The local space is too large at T level, and the fast upgrade option may not be available before the hot upgrade.
Suggestion: If you encounter the KB: /cases/list?product_id=33&type=1&category_id=31044, if not encountered, it can be ignored.
UNQUOTE

Sangfor Jojo has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Hello Patrick, I have forwarded your issue to Sangfor technical support via a ticket and looped you.
Is this answer helpful?
mantasha Lv2Posted Sep-11-2025 04:01
  
I want to get some community insight because I don't have the authority to start a support ticket.  Anyway, I appreciate your input.
Patrick Chan Lv1Posted Sep-03-2025 17:45
  
I don't have privilege to open Support ticket, that's why want to have some insight from community.
Anyway, thanks your advice.
Patrick Chan Lv1Posted Sep-03-2025 14:50
  
Thanks, but it seems I can ssh but failed to login (using admin). Any account I can use to login,  such as root?
Newbie337989 Lv2Posted Sep-02-2025 13:10
  
During upgrade, aDeploy checks system partitions (T-level partitions, temporary upgrade staging space).

If it detects the partition usage too high or space allocation mismatch, it blocks the fast upgrade / hot upgrade path.

Try this

1. Check Disk Partition Usage
- From SCP or CLI (if accessible), check space:
- df -h
- Confirm if /t* partitions (like /tboot, /troot) are near full.

2. Free Up Local Partition Space (if needed)
- Clear old upgrade packages or logs.
- In SCP, go to Maintenance > Upgrade > Package List and delete unused packages.

3. Upgrade Path Options
- If fast upgrade is blocked, choose:
  - Hot Upgrade (with reboot) > minimal downtime.
  - Normal Upgrade (cold reboot) > longer downtime but safest.

4. If You’re Unsure
- If you don’t see the KB case issue in your environment > ignore the warning and continue with normal upgrade.
- If production-critical > open Sangfor TAC to confirm before proceeding.

I Can Help:

Change

Board Leaders

NyxZale...

Weekly Sharers

Newbie5...

Weekly Questioners