Experience in configuring and installing centos on server DELL R710
Introduction | When I wrote this article, I had just installed the system on a DELL R710. Installing the system on the server for the first time. The article will not describe the installation process in detail, there are many online. I will only describe the problems I encountered. In fact, the server is just larger, and the hardware self-test time is longer. Others are no different from ordinary PCs. |
I checked a lot of information at that time. I forgot to modify the boot options. Some old systems default to BIOS boot and must be modified to UEFI boot. Change the settings in the BIOS.
I checked a lot of information at that time and suspected that it might be related to RAID. In fact, it doesn't matter. My server only had one disk, and various configurations were not working well at that time. Maybe our BIOS does not support RAID. Of course, it still needs to be configured if necessary in actual scenarios.
1: Requires allocation of /boot/efi partition. This must be analyzed when doing 64-bit centos. Generally, it should be about the same size as the boot partition.
2: Require GPT partition processing. The prompt is roughly: sda must have GPT label. Processing method:
ctrl+alt+F2
Enter the command line
parted /dev/sda
Enter parted state
mklabel gpt
prompts that all data will be deleted, enter yes
ctrl+alt+F6
Return to the graphical interface, click "Back", and then click "Next" to re-enter the partition interface to partition.
This problem is usually caused by a previous 32-bit operating system. This is caused by running a 64-bit system now.
There are many specific ways to set a static IP address on the Internet. Note that not only the configuration of the interfaces under /etc/sysconfig/network-scripts/ must be modified, but also the configuration of the /etc/sysconfig/network gateway must be modified.
If the interface is installed. After setting, you will find that the graphical interface always displays device no manager. similar. Because in the centos interface, the network is not only managed by network, but also by NetworkManager. And the two of them are prone to conflict. When using configuration file modification. You can stop /etc/init.d/NetworkManager directly.
Then //etc/init.d/network restart. That's it.
I also encountered a problem at that time, that is, the IP assigned by the administrator could not access the external network, but the automatically obtained IP could. This may be related to network management and needs to be negotiated with the network administrator.
yum install vnc yum -y install vnc-server yum install tigervnc-server tigervnc-server-module
Modify the configuration file after the installation is complete:
vim /etc/sysconfig/vncservers VNCSERVERS="1:root" VNCSERVERARGS[2]="-geometry 800x600"
Modify firewall port:
vim /etc/sysconfig/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 5900 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 5902 -j ACCEPT service iptables restart /etc/init.d/vncserver start chkconfig vncserver on
Then you can access it through the client VNC viewer.
samba installationyum install samba samba-client samba-swat
Add samba account command:
smbpasswd –a
Modify vim /etc/samba/smb.conf configuration file
[share] comment = ***** share dir path = /home/*******/share writable = yes valid users = ******* vim /etc/samba/smbusers
Add ***** = *****The user just added.
Modify the firewall to open ports 139 445. The two ports that samba needs to use.
Restart the firewall and start samba
/etc/init.d/smb start chkconfig smb on
If windows does not have permission to access the path
Make sure setlinux is closed and execute the :setenforce 0 command
vi /etc/selinux/config
Modify SELINUX=enforcing to SELINUX=disabled
KVM virtual manager installationExecute the command under administrator privileges:
Shut down the selinux system. (setenforce 0)
yum -y groupinstall "Virtualization" "Virtualization Client" "Virtualization Platform" "Virtualization Tools" yum -y install bridge-utils yum install libvirt #sudo apt-get install kvm qemu service libvirtd start
You can see it by running lsmod | grep kvm
Kvm kvm_intel
Using Intel CPU: Load Intel kernel module: modprobe kvm-intel
If the following error message is returned when you load the module, it means that VT may be turned off in the BIOS:
FATAL: Error inserting kvm_intel (/lib/modules/2.6.20-15-generic/kernel/drivers/kvm/kvm-intel.ko): Operation not supported
Just open it in BIOS.
Using AMD CPU:
modprobe kvm-amd
The above is the detailed content of Experience in configuring and installing centos on server DELL R710. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.
