Prepare the SVPE V2.0 Maintenance USB and Review Its Tools

This archived SV after-sales guide describes preparing the SVPE V2.0 maintenance USB with FbinstTool and an FBA archive. Its English figures explain the Chinese source interface and boot menu. They do not modify or translate the downloadable PE package, its executables or the actual boot menu. No USB drive was formatted and no maintenance command was run while preparing this article.

1. Obtain the appropriate maintenance package

The source points to a Baidu-hosted maintenance-package share. A share URL alone does not establish current availability, integrity, entitlement or support for the target server. Obtain the appropriate archive and any required access information through the authorized support channel. Access codes are not reproduced in this documentation.

The source names Udisk Tool V2.0.fba, FbinstTool.exe and an executable launched as FbinstTool(1).exe. Keep the appropriate extracted files together in a local folder. These are the source filenames; do not rename an unrelated image to .fba or treat an FBA archive as an ordinary OS installation ISO.

2. Back up and identify the USB drive

Back up all required USB data first. Creating this maintenance drive destroys the existing data on the selected target. Insert the intended USB drive and open the appropriate FbinstTool executable. Confirm the physical device, capacity and drive letter before selecting it; selecting a different disk can destroy that disk’s contents:

English illustration of the initial FbinstTool disk selector — The source crop shows v1.604 and USB_Netac (15g, E:). Later figures show v1.606 and another drive; do not copy a disk index or drive letter without checking the actual target.

English illustration of selecting the USB drive before Boot Settings — This figure shows (hd3): USB_SanDisk (15g, I:). Its existing file list is not a new formatting-complete result.

3. Open the formatting dialog

After selecting the intended USB device, choose Boot Settings → Format. The cropped menu figure shows USB_SanDisk with H: whereas the previous figure uses I:. These are source examples from different states; the letter does not prove which physical disk should be selected now:

English illustration of Boot Settings, Format

4. Review the archived FBA parameters

For the pictured SVPE archive, the source selects Force format, Archive file and UD extended area with 2000 in the field labeled (M). The archive dropdown text is truncated as Inspur UDis; the full local archive must be identified separately. The source’s named FBA is Udisk Tool V2.0.fba, and the truncated dropdown does not establish an identical full filename.

English illustration of the archived formatting parameters — Checked: Force format, Archive file, UD extended area 2000 (M). Other optional controls remain unchecked as in the source.

The pictured CHS mode, Format as ZIP, UD primary area, sectors-per-read option, non-UD size and reset-disk option are unchecked. Do not enable extra options or assume 2000 is a universal minimum for another archive, tool version or USB device. The upstream fbinst source documents separate force, archive and extended-data options; it is a reference for the underlying concepts, not proof that another FbinstTool release has identical behavior.

When the correct target, package and supported parameters are verified and the backup is complete, choose Format and review the actual confirmation. The source says to wait a few minutes; elapsed time alone does not establish success. Check the tool’s final result and any errors before removing the drive.

5. Boot the intended server from the maintenance drive

Insert the completed media into the intended server and select that USB device using the server’s supported boot menu or boot-order settings. Verify that the actual firmware mode and hardware are supported by this old maintenance package. The source supplies this maintenance menu:

English illustration of the Server USB Maintenance System V2.0 menu — The unusual [004] identifier is retained and remains highlighted for Windows 10 PE x64. An English illustration does not change the language of the supplied boot package.

6. Source troubleshooting example: not enough space

The source error popup reads not enough space. Its background dialog has UD extended area set to 650 (M), along with Force format and Archive file selected. The partially filled progress bar is an error state, not a successful result:

English illustration of the original not enough space error at 650 M

For the specific archived package, the source emphasizes this order before retrying:

Select Force format.
Select Archive file and the intended FBA archive.
Select UD extended area, enter 2000 in the (M) field, then choose Format.

English illustration of the source parameter-selection order — The red numbers identify 1 Force format, 2 Archive file, 3 UD extended area 2000 (M). No subsequent success dialog is supplied.

Reconfirm the intended target and backup before a destructive retry. The source sequence addresses its displayed package/settings; it is not a general cure for every capacity, damaged-media or incompatible-archive error. If it still fails, inspect the actual archive requirements, available target capacity and tool/version guidance instead of repeatedly formatting an unidentified disk.

7. Maintenance-menu functions

The source menu contains the following identifiers and functions. Choosing a diagnostic environment is separate from running its potentially destructive storage or restore tools:

Item	Source function
01	Ghost backup and restore, multiple versions
02	MaxDOS toolbox, Inspur enhanced
03	Windows Server 2003 PE x86
04	Windows 8 PE x64
004	Windows 10 PE x64
05	Puppy Linux PE x86
06	Sysrcd Linux PE x64
07	Common server diagnostic tools
08	Install Windows
09	Grub4DOS command line
10	Boot the custom Inspur.ISO
11	Continue booting from the local disk

8. Modules highlighted by the source

[02] MaxDOS toolbox: the source describes a MAXDOS 9.3 environment with megacli, ipmitool, ipmicfg and amidedos added. The menu includes automatic and manual Ghost multicast, backup/restore, shared-resource access, USB/SATA/1394/PCMCIA drive support and a minimal DOS mode. The highlighted toolbox entry does not show any of these commands being executed:

English illustration of the MAXDOS 9.3 main menu

[03] Windows Server 2003 PE x86: the source describes a 32-bit PE environment for older servers with its usual support tools. It reports a 2 GB recognized-memory limit for this particular PE build. That is not a general memory-limit specification for every 32-bit Windows or PE configuration:

English illustration of the source Windows Server 2003 PE desktop

[04] Windows 8 PE x64: the source says this package includes multiple RAID drivers and tools and reports testing with more than 512 GB memory. Treat that as an attributed claim about its test/build, not a guaranteed maximum or current hardware-support list:

English illustration of the source Windows 8 PE desktop

[004] Windows 10 PE x64: the source describes another 64-bit environment with RAID drivers, including an onboard RAID driver for a dual-socket M4 platform, and additional tools. It does not identify every supported M4 controller/firmware combination or supply a new compatibility test here:

English illustration of the source menu highlighting Windows 10 PE x64 — This repeats the same original menu image and reuses its reviewed English asset.

References

No equivalent official English SVPE V2.0 package guide or exact English replacements for these screenshots were located. The upstream command help corroborates the parameter concepts; this article retains the original GUI sequence rather than substituting untested command-line formatting instructions.