ubuntu22.04 + 驱动570.211.01 + cuda12.8

原创 已于 2026-05-18 19:02:25 修改 · 279 阅读 · 1 ·
本内容遵循CC 4.0 BY-SA版权协议
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
GEO检测
标签
#raid #ubuntu
于 2026-04-28 19:51:46 首次发布

1.更新源

sudo apt update

2.查看推荐驱动

ubuntu-drivers devices

如果570驱动已经不存在了就要本地安装了

root@root:~# ubuntu-drivers list
ERROR:root:aplay command not found
nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-generic)
nvidia-driver-595, (kernel modules provided by linux-modules-nvidia-595-generic)
nvidia-driver-545, (kernel modules provided by nvidia-dkms-545)
nvidia-driver-580, (kernel modules provided by linux-modules-nvidia-580-generic)
nvidia-driver-595-server, (kernel modules provided by linux-modules-nvidia-595-server-generic)
nvidia-driver-595-open, (kernel modules provided by linux-modules-nvidia-595-open-generic)
nvidia-driver-545-open, (kernel modules provided by nvidia-dkms-545-open)
nvidia-driver-535-open, (kernel modules provided by linux-modules-nvidia-535-open-generic)
nvidia-driver-595-server-open, (kernel modules provided by linux-modules-nvidia-595-server-open-generic)
nvidia-driver-580-open, (kernel modules provided by linux-modules-nvidia-580-open-generic)
nvidia-driver-535-server-open, (kernel modules provided by linux-modules-nvidia-535-server-open-generic)
nvidia-driver-535-server, (kernel modules provided by linux-modules-nvidia-535-server-generic)
nvidia-driver-580-server, (kernel modules provided by linux-modules-nvidia-580-server-generic)
nvidia-driver-580-server-open, (kernel modules provided by linux-modules-nvidia-580-server-open-generic)

卸载清理所有 CUDA/NVIDIA 包

apt purge 'cuda*' 'nvidia*'  'libnvidia*'

自动清理不需要的安装包

sudo apt autoremove -y

删除 CUDA repo

rm -f /etc/apt/sources.list.d/cuda*
apt update

确认系统已经干净

dpkg -l | grep -E 'nvidia|cuda'

3.安装 570驱动

3.1 如果在线源存在570版本

sudo apt install nvidia-driver-570

这种安装方式一般不需要手动关闭 nouveau，官方 NVIDIA 驱动包会自动做这些事情：

  • blacklist nouveau
  • 更新 initramfs
  • 处理内核模块冲突

3.2 如果在线源不存在570版本

安装 headers

sudo apt install build-essential dkms linux-headers-$(uname -r)

关闭 nouveau（你必须确认）

sudo bash -c "cat > /etc/modprobe.d/blacklist-nouveau.conf <<EOF
blacklist nouveau
options nouveau modeset=0
EOF"

sudo update-initramfs -u
sudo reboot

安装缺失基础库

sudo apt install -y \
libgbm1 \
libwayland-client0 \
libwayland-server0 \
libx11-xcb1 \
libxcb-dri3-0 \
libxcb-present0 \
xserver-xorg-core

禁用远程源

sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak

安装本地驱动包

dpkg -i nvidia-driver-local-repo-ubuntu2204-570.211.01_1.0-1_amd64.deb

更新源

apt update

root@root:/home/rootroot# apt update
Get:1 file:/var/nvidia-driver-local-repo-ubuntu2204-570.211.01  InRelease [1,572 B]
Get:1 file:/var/nvidia-driver-local-repo-ubuntu2204-570.211.01  InRelease [1,572 B]
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

安装驱动

sudo apt install nvidia-driver-570

重新生成initramfs 正确生成

update-initramfs -u

不重新生成nvidia模块不会在启动时自动加载。

4.安装驱动同版本的nvidia-fabricmanager

sudo apt install nvidia-fabricmanager-570

启动服务

sudo systemctl enable nvidia-fabricmanager
sudo systemctl start nvidia-fabricmanager


5. 重启后验证

root@root:~# nvidia-smi
Mon Apr 27 08:33:24 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 570.211.01             Driver Version: 570.211.01     CUDA Version: 12.8     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA H200                    Off |   00000000:18:00.0 Off |                    0 |
| N/A   27C    P0             75W /  700W |       0MiB / 143771MiB |      0%      Default |
|                                         |                        |             Disabled |
+-----------------------------------------+------------------------+----------------------+
|   1  NVIDIA H200                    Off |   00000000:2A:00.0 Off |                    0 |
| N/A   30C    P0             75W /  700W |       0MiB / 143771MiB |      0%      Default |
|                                         |                        |             Disabled |
+-----------------------------------------+------------------------+----------------------+
|   2  NVIDIA H200                    Off |   00000000:3A:00.0 Off |                    0 |
| N/A   31C    P0             79W /  700W |       0MiB / 143771MiB |      0%      Default |
|                                         |                        |             Disabled |
+-----------------------------------------+------------------------+----------------------+
|   3  NVIDIA H200                    Off |   00000000:5D:00.0 Off |                    0 |
| N/A   27C    P0             76W /  700W |       0MiB / 143771MiB |      0%      Default |
|                                         |                        |             Disabled |
+-----------------------------------------+------------------------+----------------------+
|   4  NVIDIA H200                    Off |   00000000:9A:00.0 Off |                    0 |
| N/A   27C    P0             76W /  700W |       0MiB / 143771MiB |      0%      Default |
|                                         |                        |             Disabled |
+-----------------------------------------+------------------------+----------------------+
|   5  NVIDIA H200                    Off |   00000000:AB:00.0 Off |                    0 |
| N/A   31C    P0             77W /  700W |       0MiB / 143771MiB |      0%      Default |
|                                         |                        |             Disabled |
+-----------------------------------------+------------------------+----------------------+
|   6  NVIDIA H200                    Off |   00000000:BA:00.0 Off |                    0 |
| N/A   31C    P0             78W /  700W |       0MiB / 143771MiB |      0%      Default |
|                                         |                        |             Disabled |
+-----------------------------------------+------------------------+----------------------+
|   7  NVIDIA H200                    Off |   00000000:DB:00.0 Off |                    0 |
| N/A   27C    P0             75W /  700W |       0MiB / 143771MiB |      0%      Default |
|                                         |                        |             Disabled |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+
root@root:~# nvidia-smi topo -p2p n
        GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7
 GPU0   X       OK      OK      OK      OK      OK      OK      OK
 GPU1   OK      X       OK      OK      OK      OK      OK      OK
 GPU2   OK      OK      X       OK      OK      OK      OK      OK
 GPU3   OK      OK      OK      X       OK      OK      OK      OK
 GPU4   OK      OK      OK      OK      X       OK      OK      OK
 GPU5   OK      OK      OK      OK      OK      X       OK      OK
 GPU6   OK      OK      OK      OK      OK      OK      X       OK
 GPU7   OK      OK      OK      OK      OK      OK      OK      X

Legend:

  X    = Self
  OK   = Status Ok
  CNS  = Chipset not supported
  GNS  = GPU not supported
  TNS  = Topology not supported
  NS   = Not supported
  U    = Unknown
root@root:~#

6.安装 CUDA 12.8（推荐官方repo）

还原官方源

mv /etc/apt/sources.list.bak /etc/apt/sources.list

apt update

安装cuda

wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.1-1_all.deb
sudo dpkg -i cuda-keyring_1.1-1_all.deb

sudo apt update
sudo apt install cuda-toolkit-12-8

日志

root@root:~# wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.1-1_all.deb
--2026-04-27 07:46:44--  https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.1-1_all.deb
Resolving developer.download.nvidia.com (developer.download.nvidia.com)... 23.213.43.207, 23.213.43.199
Connecting to developer.download.nvidia.com (developer.download.nvidia.com)|23.213.43.207|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://developer.download.nvidia.cn/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.1-1_all.deb [following]
--2026-04-27 07:46:45--  https://developer.download.nvidia.cn/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.1-1_all.deb
Resolving developer.download.nvidia.cn (developer.download.nvidia.cn)... 66.253.47.121, 66.253.47.122
Connecting to developer.download.nvidia.cn (developer.download.nvidia.cn)|66.253.47.121|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4332 (4.2K) [application/x-deb]
Saving to: ‘cuda-keyring_1.1-1_all.deb’

cuda-keyring_1.1-1_all.deb                          100%[============================================================================================================

2026-04-27 07:46:50 (1.33 GB/s) - ‘cuda-keyring_1.1-1_all.deb’ saved [4332/4332]

root@root:~# sudo dpkg -i cuda-keyring_1.1-1_all.deb
Selecting previously unselected package cuda-keyring.
(Reading database ... 96698 files and directories currently installed.)
Preparing to unpack cuda-keyring_1.1-1_all.deb ...
Unpacking cuda-keyring (1.1-1) ...
Setting up cuda-keyring (1.1-1) ...
root@root:~# apt update
Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:5 https://developer.download.nvidia.cn/compute/cuda/repos/ubuntu2204/x86_64  InRelease [1,581 B]
Get:6 https://developer.download.nvidia.cn/compute/cuda/repos/ubuntu2204/x86_64  Packages [2,546 kB]
Fetched 2,547 kB in 8s (326 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
233 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@root:~# apt install cuda-toolkit-12-8
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.

7.配环境变量

echo 'export PATH=/usr/local/cuda/bin:$PATH' >> ~/.bashrc
echo 'export LD_LIBRARY_PATH=/usr/local/cuda/lib64:$LD_LIBRARY_PATH' >> ~/.bashrc
source ~/.bashrc

8.重启

9.创建RAID0

root@root:~# fdisk /dev/nvme0n1

Welcome to fdisk (util-linux 2.37.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): g
Created a new GPT disklabel (GUID: 8709FFF1-4E4A-944C-BF9D-9063739C3FAA).

Command (m for help): n
Partition number (1-128, default 1):
First sector (2048-15002931854, default 2048):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-15002931854, default 15002931854):

Created a new partition 1 of type 'Linux filesystem' and of size 7 TiB.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

root@root:~# fdisk /dev/nvme1n1

Welcome to fdisk (util-linux 2.37.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): g
Created a new GPT disklabel (GUID: F02844D7-B46D-1543-A5B6-15BB1A746DEB).

Command (m for help): n
Partition number (1-128, default 1):
First sector (2048-15002931854, default 2048):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-15002931854, default 15002931854):

Created a new partition 1 of type 'Linux filesystem' and of size 7 TiB.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

root@root:~#
root@root:~# lsblk
NAME                      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0                       7:0    0  63.9M  1 loop /snap/core20/2318
loop1                       7:1    0  63.8M  1 loop /snap/core20/2769
loop2                       7:2    0    87M  1 loop /snap/lxd/29351
loop3                       7:3    0  38.8M  1 loop /snap/snapd/21759
sda                         8:0    0 447.1G  0 disk
├─sda1                      8:1    0     1G  0 part /boot/efi
├─sda2                      8:2    0     2G  0 part /boot
└─sda3                      8:3    0 444.1G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   100G  0 lvm  /
nvme0n1                   259:0    0     7T  0 disk
└─nvme0n1p1               259:3    0     7T  0 part
nvme1n1                   259:1    0     7T  0 disk
└─nvme1n1p1               259:4    0     7T  0 part
root@root:~# mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/nvme0n1p1 /dev/nvme1n1p1
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@root:~# mkfs.ext4 /dev/md0
mke2fs 1.46.5 (30-Dec-2021)
Discarding device blocks: done
Creating filesystem with 3750666240 4k blocks and 468836352 inodes
Filesystem UUID: b85e7d0c-0a31-4745-8a97-2d521d50c55e
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,
        2560000000

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

root@root:~# mdadm --detail --scan > /etc/mdadm/mdadm.conf
root@root:~# cat /etc/mdadm/mdadm.conf
ARRAY /dev/md0 metadata=1.2 name=root:0 UUID=5c31dc5b:1e6f7530:a6d6a18b:655d91ea
root@root:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.15.0-119-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
root@root:~#
root@root:~#
root@root:~#
root@root:~#
root@root:~#
root@root:~# mkdir -p /data
root@root:~# mount /dev/md0 /data
root@root:~#
root@root:~# df
Filesystem                          1K-blocks     Used   Available Use% Mounted on
tmpfs                               211336940     4196   211332744   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   102626232 23520880    73846088  25% /
tmpfs                              1056684688        0  1056684688   0% /dev/shm
tmpfs                                    5120        0        5120   0% /run/lock
/dev/sda2                             1992552   278488     1592824  15% /boot
/dev/sda1                             1098628     6228     1092400   1% /boot/efi
tmpfs                               211336936        4   211336932   1% /run/user/1000
/dev/md0                          14883294896       28 14133145236   1% /data
root@root:~# blkid /dev/md0
/dev/md0: UUID="b85e7d0c-0a31-4745-8a97-2d521d50c55e" BLOCK_SIZE="4096" TYPE="ext4"
root@root:~#
root@root:~# vim /etc/fstab
root@root:~# vim /etc/fstab
root@root:~#
root@root:~#
root@root:~# vim /etc/fstab
root@root:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-lik8ZYp0YmIrQ3tN0FJ7zV3TYUv6jNziCWT1hG6dwWo8icwvsp7LxijBmb0WlbYG / ext4 defaults 0 1
# /boot was on /dev/sda2 during curtin installation
/dev/disk/by-uuid/d71c1052-4883-41cf-9092-8d56c5d8144f /boot ext4 defaults 0 1
# /boot/efi was on /dev/sda1 during curtin installation
/dev/disk/by-uuid/817B-A3E2 /boot/efi vfat defaults 0 1
/swap.img       none    swap    sw      0       0
UUID=b85e7d0c-0a31-4745-8a97-2d521d50c55e  /data  ext4  defaults,noatime,nofail  0 2
root@root:~# reboot

root@root:~# nvme list
Node                  SN                   Model                                    Namespace Usage                      Format           FW Rev
--------------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1          24484C9E2838         Micron_7450_MTFDKBA960TFR                1         362.60  GB / 960.20  GB    512   B +  0 B   E2MU206
/dev/nvme1n1          PHAX409205UP7P6DGN   INTEL SSDPF2KX076T1                      1           7.68  TB /   7.68  TB    512   B +  0 B   9CV10450
/dev/nvme2n1          PHAX402100DY7P6DGN   INTEL SSDPF2KX076T1                      1           7.68  TB /   7.68  TB    512   B +  0 B   9CV10200
/dev/nvme3n1          PHAX401200LU7P6DGN   INTEL SSDPF2KX076T1                      1           7.68  TB /   7.68  TB    512   B +  0 B   9CV10200
/dev/nvme4n1          PHAX410208A67P6DGN   INTEL SSDPF2KX076T1                      1           7.68  TB /   7.68  TB    512   B +  0 B   9CV10450
root@root:~#
root@root:~#
root@root:~# mdadm --create /dev/md0 --level=0 --raid-devices=4 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1
mdadm: partition table exists on /dev/nvme1n1
mdadm: partition table exists on /dev/nvme1n1 but will be lost or
       meaningless after creating array
mdadm: partition table exists on /dev/nvme2n1
mdadm: partition table exists on /dev/nvme2n1 but will be lost or
       meaningless after creating array
mdadm: partition table exists on /dev/nvme3n1
mdadm: partition table exists on /dev/nvme3n1 but will be lost or
       meaningless after creating array
mdadm: partition table exists on /dev/nvme4n1
mdadm: partition table exists on /dev/nvme4n1 but will be lost or
       meaningless after creating array
Continue creating array? mdadm --zero-superblock
root@root:~#
root@root:~# mdadm --zero-superblock /dev/nvme1n1
mdadm: Unrecognised md component device - /dev/nvme1n1
root@root:~# mdadm --zero-superblock /dev/nvme1n1
mdadm: Unrecognised md component device - /dev/nvme1n1
root@root:~# mdadm --zero-superblock /dev/nvme2n1
mdadm: Unrecognised md component device - /dev/nvme2n1
root@root:~# mdadm --zero-superblock /dev/nvme3n1
mdadm: Unrecognised md component device - /dev/nvme3n1
root@root:~# mdadm --zero-superblock /dev/nvme4n1
mdadm: Unrecognised md component device - /dev/nvme4n1
root@root:~# wipefs -a /dev/nvme1n1
/dev/nvme1n1: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
/dev/nvme1n1: 8 bytes were erased at offset 0x6fc7d255e00 (gpt): 45 46 49 20 50 41 52 54
/dev/nvme1n1: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
/dev/nvme1n1: calling ioctl to re-read partition table: Success
root@root:~# wipefs -a /dev/nvme2n1
/dev/nvme2n1: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
/dev/nvme2n1: 8 bytes were erased at offset 0x6fc7d255e00 (gpt): 45 46 49 20 50 41 52 54
/dev/nvme2n1: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
/dev/nvme2n1: calling ioctl to re-read partition table: Success
root@root:~# wipefs -a /dev/nvme3n1
/dev/nvme3n1: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
/dev/nvme3n1: 8 bytes were erased at offset 0x6fc7d255e00 (gpt): 45 46 49 20 50 41 52 54
/dev/nvme3n1: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
/dev/nvme3n1: calling ioctl to re-read partition table: Success
root@root:~# wipefs -a /dev/nvme4n1
/dev/nvme4n1: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
/dev/nvme4n1: 8 bytes were erased at offset 0x6fc7d255e00 (gpt): 45 46 49 20 50 41 52 54
/dev/nvme4n1: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
/dev/nvme4n1: calling ioctl to re-read partition table: Success
root@root:~#
root@root:~# mdadm --create /dev/md0 --level=0 --raid-devices=4 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@root:~#
root@root:~# df
Filesystem                         1K-blocks     Used  Available Use% Mounted on
tmpfs                              211340800     4308  211336492   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv  102626232 23634000   73732968  25% /
tmpfs                             1056703992        0 1056703992   0% /dev/shm
tmpfs                                   5120        0       5120   0% /run/lock
/dev/nvme0n1p2                       1992552   278220    1593092  15% /boot
/dev/nvme0n1p1                       1098632     6228    1092404   1% /boot/efi
tmpfs                              211340796        8  211340788   1% /run/user/1000
root@root:~# lsblk
NAME                      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
loop0                       7:0    0  63.9M  1 loop  /snap/core20/2318
loop1                       7:1    0  63.8M  1 loop  /snap/core20/2769
loop2                       7:2    0    87M  1 loop  /snap/lxd/29351
loop3                       7:3    0  91.7M  1 loop  /snap/lxd/38800
loop4                       7:4    0  38.8M  1 loop  /snap/snapd/21759
nvme1n1                   259:0    0     7T  0 disk
└─md0                       9:0    0  27.9T  0 raid0
nvme3n1                   259:1    0     7T  0 disk
└─md0                       9:0    0  27.9T  0 raid0
nvme4n1                   259:2    0     7T  0 disk
└─md0                       9:0    0  27.9T  0 raid0
nvme2n1                   259:3    0     7T  0 disk
└─md0                       9:0    0  27.9T  0 raid0
nvme0n1                   259:4    0 894.3G  0 disk
├─nvme0n1p1               259:5    0     1G  0 part  /boot/efi
├─nvme0n1p2               259:6    0     2G  0 part  /boot
└─nvme0n1p3               259:7    0 891.2G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   100G  0 lvm   /
root@root:~# mkfs.ext4 /dev/md0
mke2fs 1.46.5 (30-Dec-2021)
Discarding device blocks: done
Creating filesystem with 3750666752 4k blocks and 468836352 inodes
Filesystem UUID: e6643a03-87b4-4d8d-bd24-57577d3c7988
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,
        2560000000

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

root@root:~#
root@root:~# mdadm --detail --scan
ARRAY /dev/md0 metadata=1.2 name=root:0 UUID=7d1bb99b:01a9cd22:abebeb6c:376bb97f
root@root:~# vim /etc/mdadm/mdadm.conf
root@root:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays

# This configuration was auto-generated on Wed, 11 Sep 2024 14:22:21 +0000 by mkconf
ARRAY /dev/md0 metadata=1.2 name=root:0 UUID=7d1bb99b:01a9cd22:abebeb6c:376bb97f
root@root:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.15.0-119-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
root@root:~#
root@root:~#
root@root:~$ mkdir -p /data
root@root:~$mount /dev/md0 /data
root@root:~$ df
Filesystem                          1K-blocks     Used   Available Use% Mounted on
tmpfs                               211340796     4300   211336496   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   102626232 23667724    73699244  25% /
tmpfs                              1056703976        0  1056703976   0% /dev/shm
tmpfs                                    5120        0        5120   0% /run/lock
/dev/nvme0n1p2                        1992552   278220     1593092  15% /boot
/dev/nvme0n1p1                        1098632     6228     1092404   1% /boot/efi
tmpfs                               211340792        8   211340784   1% /run/user/1000
/dev/md0                          29884873368       24 28384590260   1% /data
root@root:~$ blkid /dev/md0
/dev/md0: LABEL="data" UUID="25ecd7c5-29ed-4111-8007-41aef657d26b" BLOCK_SIZE="4096" TYPE="ext4"
root@root:~# vim /etc/fstab
root@root:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-dfYlZlqxChWoWdFq8zUlGyfxT3SX51Bb7NWSYMYoiL4oJvyNJM7YDoSiTKJQGU2F / ext4 defaults 0 1
# /boot was on /dev/sda2 during curtin installation
/dev/disk/by-uuid/24a1830e-a8e6-4d66-a0a1-bca1dfc1fa04 /boot ext4 defaults 0 1
# /boot/efi was on /dev/sda1 during curtin installation
/dev/disk/by-uuid/5F98-1A06 /boot/efi vfat defaults 0 1
/swap.img       none    swap    sw      0       0
UUID=25ecd7c5-29ed-4111-8007-41aef657d26b  /data  ext4  defaults,noatime,nofail  0 2
root@root:~#
root@root:~#
root@root:~#
root@root:~$ df -h
Filesystem                         Size  Used Avail Use% Mounted on
tmpfs                              202G  4.2M  202G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   98G   23G   71G  25% /
tmpfs                             1008G     0 1008G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
/dev/nvme0n1p2                     2.0G  272M  1.6G  15% /boot
/dev/nvme0n1p1                     1.1G  6.1M  1.1G   1% /boot/efi
/dev/md0                            28T   24K   27T   1% /data
tmpfs                              202G  8.0K  202G   1% /run/user/1000
rootroot@root:~$ Read from remote host 14.215.214.111: Connection reset by peer
Connection to 14.215.214.111 closed.
client_loop: send disconnect: Connection reset by peer
                                                                                                                                                                    ✗

  2026-04-28   12:53.06   /home/mobaxterm  ssh -p 22222 rootroot@14.215.214.111
Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-176-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/pro

 System information as of Tue Apr 28 06:14:39 AM UTC 2026

  System load:  0.0                Temperature:              43.0 C
  Usage of /:   12.7% of 97.87GB   Processes:                1697
  Memory usage: 0%                 Users logged in:          1
  Swap usage:   0%                 IPv4 address for ens20f0: 192.168.1.241

 * Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
   just raised the bar for easy, resilient and secure K8s cluster deployment.

   https://ubuntu.com/engage/secure-kubernetes-at-the-edge

Expanded Security Maintenance for Applications is not enabled.

76 updates can be applied immediately.
5 of these updates are standard security updates.
To see these additional updates run: apt list --upgradable

Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status


Last login: Tue Apr 28 03:16:38 2026 from 39.144.129.89
rootroot@root:~$
rootroot@root:~$
rootroot@root:~$ ifconfig
ens20f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.241  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::925a:8ff:fe3d:80bc  prefixlen 64  scopeid 0x20<link>
        ether 90:5a:08:3d:80:bc  txqueuelen 1000  (Ethernet)
        RX packets 567486  bytes 116505657 (116.5 MB)
        RX errors 0  dropped 6  overruns 0  frame 0
        TX packets 493723  bytes 105804325 (105.8 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens20f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.1.10  netmask 255.255.255.0  broadcast 10.0.1.255
        ether 90:5a:08:3d:80:bd  txqueuelen 1000  (Ethernet)
        RX packets 43  bytes 11259 (11.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 23  bytes 3628 (3.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 175  bytes 17468 (17.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 175  bytes 17468 (17.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Ubuntu22.04安装NVIDIA驱动+CUDA+CUDNN+Anaconda+PyTorch+Pycharm
m0_63615485的博客
02-12 4631
新设备安装深度学习环境。
ubuntu22.04安装NVIDIA显卡驱动（已上机实验）
lanZhou233的博客
12-14 9181
我这里是gcc版本不同，所以我需要更换gcc版本，你可以选择直接删除原来的gcc安装新的gcc，或者你也可以直接安装需要版本的gcc，在通过命令进行切换，具体的可以自行查找其他博客进行安装。这个问题其实常见的，我翻了很多个博客发现每个博客说的原因都不太一样，大致分为俩类，一类是说linux的内核不一样或者是ubuntu自带的gcc版本与kernel编译gcc版本不同，安装成功后，系统识别的GCC默认安装路径在/usr/bin文件夹下，需要创建软链接。更新后，输入以下命令，检查nouveau是否关闭。
Ubuntu24安装Steam客户端NVIDIA 显卡驱动异常：从诊断到修复的全过程
缘友一世的博客
05-17 854
Ubuntu24安装Steam客户端NVIDIA 显卡驱动异常：从诊断到修复的全过程
Ubuntu安装NVIDIA显卡驱动
Keep Learning, Keep Growing, Keep Succeeding!
08-31 763
这篇文章介绍了在Linux系统上清理旧NVIDIA驱动并安装开源驱动的完整步骤：首先彻底卸载原有驱动及相关文件，然后禁用nouveau驱动；接着添加PPA软件源并安装开源驱动；最后配置内核参数并重启系统。验证步骤建议通过运行nvidia-smi命令确认GPU是否被正确识别。整个过程涵盖了从旧驱动清理到新驱动验证的全流程，适用于需要更换NVIDIA显卡驱动的Linux用户。
5.0 k8s(ubuntu版)-部署前准备（下）——系统初始化（更新、ssh、IP地址、主机名）...
我睡醒刚刚
12-01 1847
1 更新系统 sudo apt update sudo apt upgrade 参考输出： image.png image.png 更新完成后，提示(Which services should be restarted？)哪些服务需要重新启动 这里输入8不用重启 image.png 2 安装 ifconfig、vim sudo apt install net-too...
Linux学习笔记-Ubuntu系统用户、群组、权限管理
向往的是：佛祖堂前的鱼，静静听禅。
09-09 6056
本文记录Ubuntu系统下通过命令操作用户账户进行管理。查看系统版本号的指令如下uname -a刚装完的ubuntu系统，root账户的密码是随机生成，每次开机都会随机生成一个密码，我们客户根据自己的需要设置root账户密码，毕竟管理Ubuntu系统，大部分需要用到root权限。
解决UserWarning: CUDA initialization: Unexpected error from cudaGetDeviceCount().Error 802: system not
qq_32526087的博客
04-15 139
摘要：在8卡H20的Ubuntu 22.04服务器上，当运行Python并导入PyTorch时，出现CUDA初始化错误（Error 802），导致torch.cuda.is_available()返回False。该问题是由于缺少nvidia-fabricmanager服务所致，该服务是管理多GPU互联的核心组件。解决方法包括安装CUDA密钥环、更新软件源，然后安装并启用nvidia-fabricmanager-580服务。通过执行systemctl命令启动服务后，即可解决CUDA初始化问题。
在 RTX 4090 + Python 3.10 上成功安装 Mamba‑3 的避坑指南
最新发布
zhendianluli的博客
05-28 379
官方给出的安装命令看似简单，但实际在特定环境下（如 RTX 4090 + 高版本驱动）会引发一连串的依赖冲突，导致反复卸载、重装 PyTorch，甚至卡死在源码编译阶段。本文详细记录了我从零搭建 Mamba‑3 环境的完整过程，以及中间遇到的各种错误和最终解决方案，希望能帮助同样踩坑的朋友们一劳永逸。，无需提前下载任何本地源码，全程在线完成（若网络实在太差，可替换为 Gitee 镜像，文中一并给出）。安装 Mamba‑3，再手动补上缺失的包，让 pip 不再“自作聪明”。
Ubuntu 下 P106-100 矿卡 `nvidia-smi No devices were found` 问题解决全过程
m0_61749394的博客
05-19 507
本文详细记录了在Ubuntu 22.04系统中解决P106-100矿卡"nvidia-smi No devices were found"问题的全过程。通过分析现象发现，虽然系统能识别显卡且驱动已加载，但570版本驱动与矿卡存在兼容性问题。最终解决方案是降级到470驱动，并添加关键参数NVreg_OpenRmEnableUnsupportedGpus=1。文章提供了完整的解决步骤，包括驱动卸载、nouveau禁用、470驱动安装等操作，并附带了常用排查命令。对于470驱动安装失败的情况，建议改用Linux
Ubuntu 安装 Mysql 5.7（非apt方式安装）
weixin_45562068的博客
07-19 2390
Ubuntu 安装 Mysql 5.7（非apt方式安装），使用在线安装模式。
树莓派上ubuntu22.04版本安装软件错误提示
Linux/Windows、C/C++、嵌入式开发、物联网、消费电子领域的技术博客
06-30 8086
树莓派新烧写了ubuntu22.04的版本，新版本需要安装更新一些软件，发现只要一更新，就报错
【小记】重装一台A6000 GPU主机
旻璿的专栏
08-22 584
本文介绍了在Ubuntu 24.04.3 LTS系统上配置深度学习环境的完整流程。主要内容包括：1）安装SSH服务并补充常用工具；2）安装NVIDIA驱动（含禁用Nouveau驱动步骤）；3）通过系统附加驱动选择驱动版本；4）安装CUDA工具包；5）使用Miniconda创建Python 3.12虚拟环境，配置清华PyPI镜像并安装vLLM框架；6）最后启动vLLM服务加载Qwen3-8B模型。该流程涵盖了从基础系统配置到深度学习环境搭建的关键步骤。
ULTRA论文部署与复现报告Uncertainty-aware Label Distribution Learning for Breast Tumor Cellularity Assessment
m0_63324772的博客
04-15 440
ULTRA论文部署与复现报告 Uncertainty-aware Label Distribution Learning for Breast Tumor Cellularity Assessment
Linux ubuntu22.04在线安装NVIDIA CUDA 12.8
学亮编程手记
08-19 1009
【代码】Linux ubuntu22.04在线安装NVIDIA CUDA 12.8。
出现 No services need to be restarted. No containers need to be restarted. No user sessions are 解决方法
码农研究僧的博客
08-17 4677
此提示严重，如果有意关闭，可继续往下看。
linux shell脚本中copy带空格的目录或文件
热门推荐
lu_linux的博客
11-16 1万+
在linux下复制带空格的文件夹（文件）时，需要加反斜杠，如： mkdir "te st" cp -rf te\ st te\ st-org/ 但有时候会需要在shell脚本中cp 带空格的路径会出错： 在脚本内复制带空格的文件夹（文件）时，不能直接把带空格的路径赋值给一个变量然后复制。 例如： usb_path=/mnt/sda1 folder_path="/Library/Ap...
Linux系统中通过/etc/shadow文件更改root默认密码和密码过期时间
lu_linux的博客
05-30 9837
文件中每行代表一个用户，使用 ":" 作为分隔符，每行用户信息被划分为 9 个字段。每个字段的含义如下：用户名：加密密码：最后一次修改时间：最小修改时间间隔：密码有效期：密码需要变更前的警告天数：密码过期后的宽限时间：账号失效时间：保留字段字段含义用户名(账户)用户登录系统时使用的用户名加密后的密码1.若删除此密码，那么登录就不需要密码了2.这里保存的是真正加密的密码。目前 Linux 的密码采用的是 SHA512 散列加密算法，一些嵌入式设备依然采用的是 MD5 或 DES 加密算法。
Linux上安装指定版本的torch
lu_linux的博客
07-03 8174
1.安装pip和pip3 sudo apt-get install python-setuptools python-dev build-essential sudo easy_install pip sudo apt-get install python3-pip 2.安装torch pip3 install torch==0.4.1 -f https://download.p...
linux服务器测试NVIDIA显卡性能
lu_linux的博客
05-14 5697
Linux服务器NVIDIA显卡驱动+cuda+cudnn安装及显卡性能测试
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值