Test and troubleshooting for Internet Public Virtual Disk for LINUX Server

Public Network Virtual Disk for LINUX server test and troubleshooting methods-Linux Enterprise Application-Linux server application information, the following is a detailed description. 1. View System Load
Run the w command in the server command window to obtain three groups of data (for example, 0.40 0.30 1.20), which are the first minute of the system, the last five minutes, and the last 15 minutes of load, generally, the load is normal under 2. If the load is longer than 3, the system load is considered too high, and the hard disk working status should be checked.

2. Test the reading speed of each hard disk to determine whether the hard disk is faulty.
Run the following command in the server command window:
Hdparm-t/dev/hda (IDE Hard Drive)
Hdparm-t/dev/sda (SATA, SCSI, hard RAID card array)
Hdparm-t/dev/md0 (soft RAID device)
The test results should be greater than 40 M/s under no-load conditions, and the test results should be equal to> 20 M/s under load conditions. If the test results are extremely low, you need to use a dedicated hard disk detection tool to test whether the disk is faulty.

3. unable to read or write data on the Network Disk
When an exception occurs frequently when a game is started and executed on a network disk on a client, the file system or data on the Network Disk may be damaged. You can try to fix the problem as follows.
Log on to a client and connect to the network disk as a super workstation. For example, if the network disk is H:, run chkdsk H:/F in the doscommand window to check and fix the Network Disk File System, after the repair is complete, restart the client to check whether the repair has played a corresponding role. If the fault persists, reformat and copy the data on the network disk.

4. Handling of client connection failure to Network Disk
The Server Virtual Disk Manager window must be opened when a new machine name needs to be connected to a network disk.
When the server is shut down and restarted illegally, it is likely that the virtual disk Network Service is not properly started and the client cannot connect to the network disk, in this case, restart the server normally or execute landisk restart in the command line window to start the Virtual Disk Service solution.

Solution to restoration failure of the public network virtual disk Client System
1. Restore the failed Client System by partitioning or completely.
2. Delete the restored invalid client from the server-side Virtual Disk Manager.
3. The client reconnects to the server and restores the server.

How to scan a virtual network disk without a drive letter

1. Run Command cmd on the server to enter the command line status
2. Run cd \ (this is to facilitate the generation of files directly stored in the c: \ directory)
3. Run mountvol> 1.bat (this will generate a batch file named 1. bat .)
4. Copy 1. bat to the desktop.
5. Edit 1.bat
Find \\? \ Volume {01847d10-ae98-11d9-a5d6-806d6172696f }\
No load point
The above line without a mount point is the disk volume marked with the drive letter removed. Delete all other contents in this row.
6. The last generated file should be in the following format:
Chkdsk/f \\? \ Volume {01847d10-ae98-11d9-a5d6-806d6172696f}
Please note! You must add the f parameter to chkdsk/f to fix the problem. The last character of the disk volume label is not \ and the generated file contains \. Delete it.

Finally, let's talk about when this batch can be used for scanning.
1. When you find that you are using a superuser update, some machines can see the network disk, some machines can not see the network disk, or open the market, but cannot see the content is not good, you can use.
2. when the server restarts, it prompts a disk scan and performs an automatic scan. Previously, you had to wait for the scan to complete before entering WINDOWS, but now you can skip the scan, wait until the system enters WINDOWS and then run this batch. This will not affect the guests playing games.
3. After the disk scan is complete, the client may have to restart to view the Network Disk Files normally.
4. be sure to note that this is a very dangerous command. You must ensure that no superuser exists (that is, a red computer) during use) otherwise, all files on the game disk may be lost!