搜索到
199
篇与
默认分类
的结果
-
Linux文件系统故障，Input/output error 事情是这样的，在启动某一个应用程序的时候，出现 Input/output error 的报错，磁盘以及目录无法使用的情况下，进行了重启，重启完成后是可以正常使用的，过一段时间后就会再次出现这个问题，一番Google之后怀疑是磁盘出现问题，根据网友的解决方案尝试之后发现，这个方法可行，下文是命令及回显： 使用ls命令查看的时候出现这个报错[root@webc ~]# ls /data/ ls: 无法访问/data/: 输入/输出错误 [root@webc ~]# 这个是xfs的文件系统，所以使用如下命令进行修复[root@webc ~]# xfs_repair /dev/sdc1 xfs_repair: cannot open /dev/sdc1: 设备或资源忙 这时这个问题，不要慌，先把磁盘卸载了在进行修复[root@webc ~]# umount /dev/sdc1 [root@webc ~]# xfs_repair /dev/sdc1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. [root@webc ~]# [root@webc ~]# [root@webc ~]# xfs_repair /dev/sdc1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. [root@webc ~]# xfs_repair /dev/sdc1 -L Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... agi unlinked bucket 31 is 7620063 in ag 5 (inode=10745038303) sb_icount 533632, counted 533568 sb_ifree 617, counted 614 sb_fdblocks 2852137932, counted 2860186916 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 correcting bt key (was 91997, now 92001) in inode 10745038303 data fork, btree block 1343129285 correcting bt key (was 226254, now 226257) in inode 10745038303 data fork, btree block 1345535075 correcting bt key (was 241554, now 241557) in inode 10745038303 data fork, btree block 1345535075 correcting bt key (was 795517, now 795515) in inode 10745038303 data fork, btree block 1343659983 data fork in regular inode 10745038303 claims used block 1353137709 correcting nextents for inode 10745038303 bad data fork in inode 10745038303 cleared inode 10745038303 - agno = 6 - agno = 7 - agno = 8 correcting nextents for inode 17197661037, was 870903 - counted 870911 - agno = 9 - agno = 10 correcting bt key (was 1923723, now 1923730) in inode 21481716216 data fork, btree block 2687659655 correcting bt key (was 1997785, now 1997794) in inode 21481716216 data fork, btree block 2687659655 correcting nextents for inode 21481716216, was 918874 - counted 918898 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 4 - agno = 2 - agno = 5 - agno = 6 - agno = 1 - agno = 7 - agno = 9 - agno = 8 - agno = 10 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (15:166217) is ahead of log (1:2). Format log to cycle 18. done [root@webc ~]# 修复完成后在把磁盘挂上，即可生效[root@webc ~]# mount /dev/sdc1 /data/ 查看一下这个磁盘是否可以正常使用[root@webc ~]# cd /data/vm/ [root@webc vm]# ls CentOS7-Clone-1 CentOS7-Clone-3 CentOS7-Clone-4 CentOS7-Clone-5 CentOS8 Ubuntu此刻文件系统已修复完毕 注意： 修复其他文件系统使用fsck命令进行修复 例如ext4文件系统fsck -t ext4 -y /dev/sda1不同的文件系统，命令会有些许不同，灵活变通一下Linux运维交流社区Linux运维交流社区，互联网新闻以及技术交流。28篇原创内容公众号本文使用 文章同步助手 同步 -
华为 A800-9000 服务器 离线安装MindX DL MindX DL（昇腾深度学习组件）是支持 Atlas 800 训练服务器、Atlas 800 推理服务器的深度学习组件参考设计，提供昇腾 AI 处理器资源管理和监控、昇腾 AI 处理器优化调度、分布式训练集合通信配置生成等基础功能，快速使能合作伙伴进行深度学习平台开发。 操作系统使用的是Ubuntu-1804，CPU是华为自研ARM架构。一、安装前准备配置apt网络源hello@ubuntu:/etc/apt$ sudo cp sources.list~ sources.list hello@ubuntu:/etc/apt$ cat sources.list # # deb cdrom:[Ubuntu-Server 18.04.5 LTS _Bionic Beaver_ - Release arm64 (20200810)]/ bionic main restricted #deb cdrom:[Ubuntu-Server 18.04.5 LTS _Bionic Beaver_ - Release arm64 (20200810)]/ bionic main restricted # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://cn.ports.ubuntu.com/ubuntu-ports/ bionic main restricted # deb-src http://cn.ports.ubuntu.com/ubuntu-ports/ bionic main restricted ## Major bug fix updates produced after the final release of the ## distribution. deb http://cn.ports.ubuntu.com/ubuntu-ports/ bionic-updates main restricted # deb-src http://cn.ports.ubuntu.com/ubuntu-ports/ bionic-updates main restricted ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. deb http://cn.ports.ubuntu.com/ubuntu-ports/ bionic universe # deb-src http://cn.ports.ubuntu.com/ubuntu-ports/ bionic universe deb http://cn.ports.ubuntu.com/ubuntu-ports/ bionic-updates universe # deb-src http://cn.ports.ubuntu.com/ubuntu-ports/ bionic-updates universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://cn.ports.ubuntu.com/ubuntu-ports/ bionic multiverse # deb-src http://cn.ports.ubuntu.com/ubuntu-ports/ bionic multiverse deb http://cn.ports.ubuntu.com/ubuntu-ports/ bionic-updates multiverse # deb-src http://cn.ports.ubuntu.com/ubuntu-ports/ bionic-updates multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://cn.ports.ubuntu.com/ubuntu-ports/ bionic-backports main restricted universe multiverse # deb-src http://cn.ports.ubuntu.com/ubuntu-ports/ bionic-backports main restricted universe multiverse ## Uncomment the following two lines to add software from Canonical's ## 'partner' repository. ## This software is not part of Ubuntu, but is offered by Canonical and the ## respective vendors as a service to Ubuntu users. # deb http://archive.canonical.com/ubuntu bionic partner # deb-src http://archive.canonical.com/ubuntu bionic partner deb http://ports.ubuntu.com/ubuntu-ports bionic-security main restricted # deb-src http://ports.ubuntu.com/ubuntu-ports bionic-security main restricted deb http://ports.ubuntu.com/ubuntu-ports bionic-security universe # deb-src http://ports.ubuntu.com/ubuntu-ports bionic-security universe deb http://ports.ubuntu.com/ubuntu-ports bionic-security multiverse # deb-src http://ports.ubuntu.com/ubuntu-ports bionic-security multiverse 2.配置kubernetes网络源root@ubuntu:~/123/offline-pkg-arm64# cat <<EOF >/etc/apt/sources.list.d/kubernetes.list > deb https://mirrors.aliyun.com/kubernetes/apt/ kubernetes-xenial main > EOF 3.创建目录并下载基础包root@ubuntu:~/123# mkdir offline-pkg-arm64 root@ubuntu:~/123# cd offline-pkg-arm64/ root@ubuntu:~/123/offline-pkg-arm64# sudo apt update root@ubuntu:~/123/offline-pkg-arm64# apt-get download conntrack cri-tools haveged keyutils libhavege1 libltdl7 libnfsidmap2 libtirpc-dev libtirpc1 nfs-common nfs-kernel-server rpcbind socat sshpass root@ubuntu:~/123/offline-pkg-arm64# wget --no-check-certificate https://download.docker.com/linux/ubuntu/dists/bionic/pool/stable/arm64/docker-ce_18.06.3~ce~3-0~ubuntu_arm64.deb root@ubuntu:~/123/offline-pkg-arm64# apt-get download kubelet=1.17.3-00 kubeadm=1.17.3-00 kubectl=1.17.3-00 kubernetes-cni=0.8.6-00 4.下载docker镜像并导出保存root@ubuntu:~/123# mkdir docker_images root@ubuntu:~/123# cd docker_images/ root@ubuntu:~/123/docker_images# docker pull calico/node:v3.11.3 root@ubuntu:~/123/docker_images# docker save -o calico-node_arm64.tar.gz calico/node:v3.11.3 root@ubuntu:~/123/docker_images# docker pull calico/pod2daemon-flexvol:v3.11.3 root@ubuntu:~/123/docker_images# docker save -o calico-pod2daemon-flexvol_arm64.tar.gz calico/pod2daemon-flexvol:v3.11.3 root@ubuntu:~/123/docker_images# docker pull calico/cni:v3.11.3 root@ubuntu:~/123/docker_images# docker save -o calico-cni_arm64.tar.gz calico/cni:v3.11.3 root@ubuntu:~/123/docker_images# docker pull calico/kube-controllers:v3.11.3 root@ubuntu:~/123/docker_images# docker save -o calico-kube-controllers_arm64.tar.gz calico/kube-controllers:v3.11.3 root@ubuntu:~/123/docker_images# docker pull coredns/coredns:1.6.5 root@ubuntu:~/123/docker_images# docker save -o coredns_arm64.tar.gz coredns/coredns:1.6.5 root@ubuntu:~/123/docker_images# docker pull cruse/etcd-arm64:3.4.3-0 root@ubuntu:~/123/docker_images# docker save -o etcd_arm64.tar.gz cruse/etcd-arm64:3.4.3-0 root@ubuntu:~/123/docker_images# docker pull cruse/kube-apiserver-arm64:v1.17.3 root@ubuntu:~/123/docker_images# docker save -o kube-apiserver_arm64.tar.gz cruse/kube-apiserver-arm64:v1.17.3 root@ubuntu:~/123/docker_images# docker pull cruse/kube-controller-manager-arm64:v1.17.3 root@ubuntu:~/123/docker_images# docker save -o kube-controller-manager_arm64.tar.gz cruse/kube-controller-manager-arm64:v1.17.3 root@ubuntu:~/123/docker_images# docker pull cruse/kube-proxy-arm64:v1.17.3-beta.0 root@ubuntu:~/123/docker_images# docker save -o kube-proxy_arm64.tar.gz cruse/kube-proxy-arm64:v1.17.3-beta.0 root@ubuntu:~/123/docker_images# docker pull cruse/kube-scheduler-arm64:v1.17.3-beta.0 root@ubuntu:~/123/docker_images# docker save -o kube-scheduler_arm64.tar.gz cruse/kube-scheduler-arm64:v1.17.3-beta.0 root@ubuntu:~/123/docker_images# docker pull cruse/pause-arm64:3.1 root@ubuntu:~/123/docker_images# docker save -o pause_arm64.tar.gz cruse/pause-arm64:3.1 root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# docker login -u 15648907522 -p RtZOXgmpYAQd5cj93uFCabNXUWB7wOftGw4pFdcal4XZH4bf06hvFxTOrYtr1nRao ascendhub.huawei.com root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# docker pull ascendhub.huawei.com/public-ascendhub/vc-controller-manager_arm64:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker pull ascendhub.huawei.com/public-ascendhub/vc-scheduler_arm64:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker pull ascendhub.huawei.com/public-ascendhub/vc-webhook-manager_arm64:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker pull ascendhub.huawei.com/public-ascendhub/vc-webhook-manager-base_arm64:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker pull ascendhub.huawei.com/public-ascendhub/hccl-controller_arm64:v20.2.0 root@ubuntu:~/123/docker_images# docker pull ascendhub.huawei.com/public-ascendhub/ascend-k8sdeviceplugin_arm64:v20.2.0 root@ubuntu:~/123/docker_images# docker pull ascendhub.huawei.com/public-ascendhub/cadvisor_arm64:v0.34.0-r40 root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# docker tag ascendhub.huawei.com/public-ascendhub/vc-controller-manager_arm64:v1.0.1-r40 volcanosh/vc-controller-manager:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker tag ascendhub.huawei.com/public-ascendhub/vc-scheduler_arm64:v1.0.1-r40 volcanosh/vc-scheduler:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker tag ascendhub.huawei.com/public-ascendhub/vc-webhook-manager_arm64:v1.0.1-r40 volcanosh/vc-webhook-manager:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker tag ascendhub.huawei.com/public-ascendhub/vc-webhook-manager-base_arm64:v1.0.1-r40 volcanosh/vc-webhook-manager-base:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker tag ascendhub.huawei.com/public-ascendhub/hccl-controller_arm64:v20.2.0 hccl-controller:v20.2.0 root@ubuntu:~/123/docker_images# docker tag ascendhub.huawei.com/public-ascendhub/ascend-k8sdeviceplugin_arm64:v20.2.0 ascend-k8sdeviceplugin:v20.2.0 root@ubuntu:~/123/docker_images# docker tag ascendhub.huawei.com/public-ascendhub/cadvisor_arm64:v0.34.0-r40 google/cadvisor:v0.34.0-r40 root@ubuntu:~/123/docker_images# docker rmi ascendhub.huawei.com/public-ascendhub/vc-controller-manager_arm64:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker rmi ascendhub.huawei.com/public-ascendhub/vc-scheduler_arm64:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker rmi ascendhub.huawei.com/public-ascendhub/vc-webhook-manager_arm64:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker rmi ascendhub.huawei.com/public-ascendhub/vc-webhook-manager-base_arm64:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker rmi ascendhub.huawei.com/public-ascendhub/hccl-controller_arm64:v20.2.0 root@ubuntu:~/123/docker_images# docker rmi ascendhub.huawei.com/public-ascendhub/ascend-k8sdeviceplugin_arm64:v20.2.0 root@ubuntu:~/123/docker_images# docker rmi ascendhub.huawei.com/public-ascendhub/cadvisor_arm64:v0.34.0-r40 root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# root@ubuntu:~/123/docker_images# docker save -o Ascend-K8sDevicePlugin-v20.2.0-arm64-Docker.tar.gz ascend-k8sdeviceplugin:v20.2.0 root@ubuntu:~/123/docker_images# docker save -o hccl-controller-v20.2.0-arm64.tar.gz hccl-controller:v20.2.0 root@ubuntu:~/123/docker_images# docker save -o huawei-cadvisor-v0.34.0-r40-arm64.tar.gz google/cadvisor:v0.34.0-r40 root@ubuntu:~/123/docker_images# docker save -o vc-controller-manager-v1.0.1-r40-arm64.tar.gz volcanosh/vc-controller-manager:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker save -o vc-scheduler-v1.0.1-r40-arm64.tar.gz volcanosh/vc-scheduler:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker save -o vc-webhook-manager-base-v1.0.1-r40-arm64.tar.gz volcanosh/vc-webhook-manager-base:v1.0.1-r40 root@ubuntu:~/123/docker_images# docker save -o vc-webhook-manager-v1.0.1-r40-arm64.tar.gz volcanosh/vc-webhook-manager:v1.0.1-r40 注* 其中部分镜像是需要在华为hub里面进行获取权限后进行下载 https://support.huaweicloud.com/usermanual-mindxdl202/atlasmindx_03_0047.html 5.完成后的目录root@ubuntu:~/123# tree . ├── docker_images │ ├── Ascend-K8sDevicePlugin-v20.2.0-arm64-Docker.tar.gz │ ├── calico-cni_arm64.tar.gz │ ├── calico-kube-controllers_arm64.tar.gz │ ├── calico-node_arm64.tar.gz │ ├── calico-pod2daemon-flexvol_arm64.tar.gz │ ├── coredns_arm64.tar.gz │ ├── etcd_arm64.tar.gz │ ├── hccl-controller-v20.2.0-arm64.tar.gz │ ├── huawei-cadvisor-v0.34.0-r40-arm64.tar.gz │ ├── kube-apiserver_arm64.tar.gz │ ├── kube-controller-manager_arm64.tar.gz │ ├── kube-proxy_arm64.tar.gz │ ├── kube-scheduler_arm64.tar.gz │ ├── pause_arm64.tar.gz │ ├── vc-controller-manager-v1.0.1-r40-arm64.tar.gz │ ├── vc-scheduler-v1.0.1-r40-arm64.tar.gz │ ├── vc-webhook-manager-base-v1.0.1-r40-arm64.tar.gz │ └── vc-webhook-manager-v1.0.1-r40-arm64.tar.gz ├── offline-pkg-arm64 │ ├── conntrack_1%3a1.4.4+snapshot20161117-6ubuntu2_arm64.deb │ ├── cri-tools_1.13.0-01_arm64.deb │ ├── docker-ce_18.06.3~ce~3-0~ubuntu_arm64.deb │ ├── haveged_1.9.1-6_arm64.deb │ ├── keyutils_1.5.9-9.2ubuntu2_arm64.deb │ ├── kubeadm_1.17.3-00_arm64.deb │ ├── kubectl_1.17.3-00_arm64.deb │ ├── kubelet_1.17.3-00_arm64.deb │ ├── kubernetes-cni_0.8.6-00_arm64.deb │ ├── libhavege1_1.9.1-6_arm64.deb │ ├── libltdl7_2.4.6-2_arm64.deb │ ├── libnfsidmap2_0.25-5.1_arm64.deb │ ├── libtirpc1_0.2.5-1.2ubuntu0.1_arm64.deb │ ├── libtirpc-dev_0.2.5-1.2ubuntu0.1_arm64.deb │ ├── nfs-common_1%3a1.3.4-2.1ubuntu5.5_arm64.deb │ ├── nfs-kernel-server_1%3a1.3.4-2.1ubuntu5.5_arm64.deb │ ├── rpcbind_0.2.3-0.6ubuntu0.18.04.4_arm64.deb │ ├── socat_1.7.3.2-2ubuntu2_arm64.deb │ └── sshpass_1.06-1_arm64.deb ├── offline-pkg-arm64.zip └── yamls ├── ascendplugin-310-v20.2.0.yaml ├── ascendplugin-volcano-v20.2.0.yaml ├── cadvisor-v0.34.0-r40.yaml ├── calico.yaml ├── hccl-controller-v20.2.0.yaml ├── npu-exporter-v20.2.0.yaml └── volcano-v1.0.1-r40.yaml 3 directories, 46 files root@ubuntu:~/123#注* 其中yamls文件在下方链接中下载 https://gitee.com/ascend/mindxdl-deploy/tree/20201230-V20.2.0/ 6.配置免密登陆root@ubuntu:~# ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Created directory '/root/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: SHA256:07dTbsAycQqT2w7HdCwjIyJig5T20FQ/eHZGxWg7pbY root@ubuntu The key's randomart image is: +---[RSA 2048]----+ | .+... .+. | |o+ . o .+ + | |+o+ ...=BoO + | |...o .o.+/ O | | S @ + . | | E + = | | . o o | | o | | | +----[SHA256]-----+ root@ubuntu:~# root@ubuntu:~# ssh-copy-id -i 127.0.0.1 7.配置安装ansibleroot@ubuntu:~# root@ubuntu:~# apt install ansible root@ubuntu:~# vim /etc/ansible/hosts #配置内容如下 [all:vars] # default shared directory, you can change it as yours nfs_shared_dir=/data/atlas_dls # NFS service IP nfs_service_ip=192.168.1.110 # Master IP master_ip=192.168.1.110 # dls install package dir dls_root_dir=/root/123 # set proxy proxy="" # Command for logging in to the Asend hub ascendhub_login_command="login_command" # Generally, you do not need to change the value or delete it. ascendhub_prefix="ascendhub.huawei.com/public-ascendhub" # versions deviceplugin_version="v20.2.0" cadvisor_version="v0.34.0-r40" volcano_version="v1.0.1-r40" hccl_version="v20.2.0" [nfs_server] ubuntu ansible_host=192.168.1.110 ansible_ssh_user="root" ansible_ssh_pass="123123" [localnode] ubuntu ansible_host=192.168.1.110 ansible_ssh_user="root" ansible_ssh_pass="123123" [training_node] ubuntu ansible_host=192.168.1.110 ansible_ssh_user="root" ansible_ssh_pass="123123" [inference_node] [A300T_node] [arm] ubuntu ansible_host=192.168.1.110 ansible_ssh_user="root" ansible_ssh_pass="123123" [x86] [workers:children] training_node inference_node A300T_node root@ubuntu:~/mindxdl/deploy/offline/steps# vim /etc/ansible/ansible.cfg log_path = /var/log/ansible.log host_key_checking = False deprecation_warnings = False 注* 参数说明，请根据实际写入：nfs-host-ip：NFS节点服务器IP地址，即服务器IP地址，如果不安装NFS可设置为空字符串，如：""。 master-host-ip：管理节点服务器IP地址，即服务器IP地址。 install_dir：基础软件包、镜像包和yamls文件夹的上传目录。 proxy_address：代理地址，请根据实际情况配置，如果不需要代理，设置为空字符串，如：""。 login_command：从Ascend Hub中心获取镜像需要使用的登录命令，仅在线安装需要配置，如："docker login -u xxxxxx@xxxxxx -p xxxxxxxx ascendhub.huawei.com"，注意不要遗漏命令前后的引号，获取方式请参见获取MindX DL镜像中1~2。离线安装可设置为空字符串，如：""。 single-node-host-name：请使用单节点主机名，可通过hostname命令查看。 IP：服务器IP地址。 username：登录服务器的用户名。建议使用root用户，避免权限不足。 passwd：登录服务器的用户密码。 二、一键安装root@ubuntu:~/sshpass# apt install sshpass root@ubuntu:~/mindxdl/deploy/offline/steps# dos2unix * root@ubuntu:~/mindxdl/deploy/offline/steps# chmod 500 entry.sh root@ubuntu:~/mindxdl/deploy/offline/steps# bash -x entry.sh三、安装后进行验证 1.docker信息查看root@ubuntu:~# docker info Containers: 35 Running: 30 Paused: 0 Stopped: 5 Images: 18 Server Version: 18.06.3-ce Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: systemd Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog Swarm: inactive Runtimes: ascend runc Default Runtime: ascend Init Binary: docker-init containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e runc version: a592beb5bc4c4092b1b1bac971afed27687340c5 init version: fec3683 Security Options: apparmor seccomp Profile: default Kernel Version: 4.15.0-112-generic Operating System: Ubuntu 18.04.5 LTS OSType: linux Architecture: aarch64 CPUs: 192 Total Memory: 503.6GiB Name: ubuntu ID: MUTU:QOYU:2P6F:P2QB:4JKZ:QNKE:PPMQ:PQLL:3PDG:QEYU:LMDK:KNMF Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: docker.mirrors.ustc.edu.cn 127.0.0.0/8 Registry Mirrors: https://dockerhub.azk8s.cn/ https://docker.mirrors.ustc.edu.cn/ http://hub-mirror.c.163.com/ Live Restore Enabled: false WARNING: No swap limit support 2. kubectl的pod信息查看root@ubuntu:~# kubectl get pod --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE cadvisor cadvisor-nsn4r 1/1 Running 0 5m23s default hccl-controller-645bb466f-5fqq6 1/1 Running 0 5m34s kube-system ascend-device-plugin-daemonset-vxj8s 1/1 Running 0 5m23s kube-system calico-kube-controllers-8464785d6b-bnjdn 1/1 Running 0 5m50s kube-system calico-node-blshl 1/1 Running 0 5m51s kube-system coredns-6955765f44-5jr59 1/1 Running 0 5m50s kube-system coredns-6955765f44-wbzvz 1/1 Running 0 5m50s kube-system etcd-ubuntu 1/1 Running 0 5m43s kube-system kube-apiserver-ubuntu 1/1 Running 0 5m43s kube-system kube-controller-manager-ubuntu 1/1 Running 0 5m43s kube-system kube-proxy-b78fm 1/1 Running 0 5m51s kube-system kube-scheduler-ubuntu 1/1 Running 0 5m43s volcano-system volcano-admission-74776688c8-g9p9q 1/1 Running 0 5m31s volcano-system volcano-admission-init-sbktn 0/1 Completed 0 5m31s volcano-system volcano-controllers-6786db54f-vn797 1/1 Running 0 5m31s volcano-system volcano-scheduler-844f9b547b-xxjm7 1/1 Running 0 5m31s root@ubuntu:~# root@ubuntu:~# kubectl describe node ubuntu Name: ubuntu Roles: master,worker Labels: accelerator=huawei-Ascend910 beta.kubernetes.io/arch=arm64 beta.kubernetes.io/os=linux host-arch=huawei-arm kubernetes.io/arch=arm64 kubernetes.io/hostname=ubuntu kubernetes.io/os=linux masterselector=dls-master-node node-role.kubernetes.io/master= node-role.kubernetes.io/worker=worker workerselector=dls-worker-node Annotations: huawei.com/Ascend910: Ascend910-1,Ascend910-2,Ascend910-3,Ascend910-0 kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock node.alpha.kubernetes.io/ttl: 0 projectcalico.org/IPv4Address: 192.168.1.110/24 projectcalico.org/IPv4IPIPTunnelAddr: 10.30.243.192 volumes.kubernetes.io/controller-managed-attach-detach: true CreationTimestamp: Thu, 05 Aug 2021 16:34:33 +0800 Taints: <none> Unschedulable: false Lease: HolderIdentity: ubuntu AcquireTime: <unset> RenewTime: Thu, 05 Aug 2021 16:41:29 +0800 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Thu, 05 Aug 2021 16:35:06 +0800 Thu, 05 Aug 2021 16:35:06 +0800 CalicoIsUp Calico is running on this node MemoryPressure False Thu, 05 Aug 2021 16:40:30 +0800 Thu, 05 Aug 2021 16:34:27 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Thu, 05 Aug 2021 16:40:30 +0800 Thu, 05 Aug 2021 16:34:27 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Thu, 05 Aug 2021 16:40:30 +0800 Thu, 05 Aug 2021 16:34:27 +0800 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Thu, 05 Aug 2021 16:40:30 +0800 Thu, 05 Aug 2021 16:35:19 +0800 KubeletReady kubelet is posting ready status. AppArmor enabled Addresses: InternalIP: 192.168.1.110 Hostname: ubuntu Capacity: cpu: 192 ephemeral-storage: 920422204Ki huawei.com/Ascend910: 4 hugepages-2Mi: 0 memory: 528101392Ki pods: 110 Allocatable: cpu: 192 ephemeral-storage: 848261101802 huawei.com/Ascend910: 4 hugepages-2Mi: 0 memory: 527998992Ki pods: 110 System Info: Machine ID: 3996e745414f461b9e0e990f6d0b597e System UUID: CD56756C-607E-BD02-EB11-5292EAFB068C Boot ID: adb96127-7fdc-4d84-8867-a13005f9b535 Kernel Version: 4.15.0-112-generic OS Image: Ubuntu 18.04.5 LTS Operating System: linux Architecture: arm64 Container Runtime Version: docker://18.6.3 Kubelet Version: v1.17.3 Kube-Proxy Version: v1.17.3 PodCIDR: 10.30.0.0/24 PodCIDRs: 10.30.0.0/24 Non-terminated Pods: (15 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits AGE --------- ---- ------------ ---------- --------------- ------------- --- cadvisor cadvisor-nsn4r 500m (0%) 1 (0%) 300Mi (0%) 2000Mi (0%) 6m17s default hccl-controller-645bb466f-5fqq6 500m (0%) 500m (0%) 300Mi (0%) 300Mi (0%) 6m28s kube-system ascend-device-plugin-daemonset-vxj8s 500m (0%) 500m (0%) 500Mi (0%) 500Mi (0%) 6m17s kube-system calico-kube-controllers-8464785d6b-bnjdn 0 (0%) 0 (0%) 0 (0%) 0 (0%) 6m44s kube-system calico-node-blshl 250m (0%) 0 (0%) 0 (0%) 0 (0%) 6m45s kube-system coredns-6955765f44-5jr59 100m (0%) 0 (0%) 70Mi (0%) 170Mi (0%) 6m44s kube-system coredns-6955765f44-wbzvz 100m (0%) 0 (0%) 70Mi (0%) 170Mi (0%) 6m44s kube-system etcd-ubuntu 0 (0%) 0 (0%) 0 (0%) 0 (0%) 6m37s kube-system kube-apiserver-ubuntu 250m (0%) 0 (0%) 0 (0%) 0 (0%) 6m37s kube-system kube-controller-manager-ubuntu 200m (0%) 0 (0%) 0 (0%) 0 (0%) 6m37s kube-system kube-proxy-b78fm 0 (0%) 0 (0%) 0 (0%) 0 (0%) 6m45s kube-system kube-scheduler-ubuntu 100m (0%) 0 (0%) 0 (0%) 0 (0%) 6m37s volcano-system volcano-admission-74776688c8-g9p9q 500m (0%) 500m (0%) 300Mi (0%) 300Mi (0%) 6m25s volcano-system volcano-controllers-6786db54f-vn797 500m (0%) 500m (0%) 300Mi (0%) 300Mi (0%) 6m25s volcano-system volcano-scheduler-844f9b547b-xxjm7 500m (0%) 500m (0%) 300Mi (0%) 300Mi (0%) 6m25s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 4 (2%) 3500m (1%) memory 2140Mi (0%) 4040Mi (0%) ephemeral-storage 0 (0%) 0 (0%) huawei.com/Ascend910 0 0 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal NodeHasSufficientMemory 7m10s (x8 over 7m11s) kubelet, ubuntu Node ubuntu status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 7m10s (x7 over 7m11s) kubelet, ubuntu Node ubuntu status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 7m10s (x6 over 7m11s) kubelet, ubuntu Node ubuntu status is now: NodeHasSufficientPID Normal Starting 6m37s kubelet, ubuntu Starting kubelet. Normal NodeHasSufficientMemory 6m37s kubelet, ubuntu Node ubuntu status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 6m37s kubelet, ubuntu Node ubuntu status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 6m37s kubelet, ubuntu Node ubuntu status is now: NodeHasSufficientPID Normal NodeAllocatableEnforced 6m37s kubelet, ubuntu Updated Node Allocatable limit across pods Normal Starting 6m33s kube-proxy, ubuntu Starting kube-proxy. Normal NodeReady 6m17s kubelet, ubuntu Node ubuntu status is now: NodeReady root@ubuntu:~#注* 再此信息中可以看到CPU和加速卡的信息Capacity: cpu: 192 ephemeral-storage: 920422204Ki huawei.com/Ascend910: 4 hugepages-2Mi: 0 memory: 528101392Ki pods: 110 Allocatable: cpu: 192 ephemeral-storage: 848261101802 huawei.com/Ascend910: 4 hugepages-2Mi: 0 memory: 527998992Ki pods: 110**详情可以查看华为官方文档： **https://support.huaweicloud.com/mindxdl201/Linux运维交流社区Linux运维交流社区，互联网新闻以及技术交流。30篇原创内容公众号本文使用 文章同步助手 同步
-
人工智能NVIDIA显卡计算（CUDA+CUDNN）平台搭建 NVIDIA是GPU（图形处理器）的发明者，也是人工智能计算的引领者。我们创建了世界上最大的游戏平台和世界上最快的超级计算机。 第一步，首先安装N卡驱动。cby@cby-Inspiron-7577:~$ sudo add-apt-repository ppa:graphics-drivers/ppa [sudo] cby 的密码： PPA publishes dbgsym, you may need to include 'main/debug' component Repository: 'deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ hirsute main' Description: Fresh drivers from upstream, currently shipping Nvidia. ## Current Status Current long-lived branch release: `nvidia-430` (430.40) Dropped support for Fermi series (https://nvidia.custhelp.com/app/answers/detail/a_id/4656) Old long-lived branch release: `nvidia-390` (390.129) For GF1xx GPUs use `nvidia-390` (390.129) For G8x, G9x and GT2xx GPUs use `nvidia-340` (340.107) For NV4x and G7x GPUs use `nvidia-304` (304.137) End-Of-Life! Support timeframes for Unix legacy GPU releases: https://nvidia.custhelp.com/app/answers/detail/a_id/3142 ## What we're working on right now: - Normal driver updates - Help Wanted: Mesa Updates for Intel/AMD users, ping us if you want to help do this work, we're shorthanded. ## WARNINGS: This PPA is currently in testing, you should be experienced with packaging before you dive in here: Volunteers welcome! ### How you can help: ## Install PTS and benchmark your gear: sudo apt-get install phoronix-test-suite Run the benchmark: phoronix-test-suite default-benchmark openarena xonotic tesseract gputest unigine-valley and then say yes when it asks you to submit your results to openbechmarking.org. Then grab a cup of coffee, it takes a bit for the benchmarks to run. Depending on the version of Ubuntu you're using it might preferable for you to grabs PTS from upstream directly: http://www.phoronix-test-suite.com/?k=downloads ## Share your results with the community: Post a link to your results (or any other feedback to): https://launchpad.net/~graphics-drivers-testers Remember to rerun and resubmit the benchmarks after driver upgrades, this will allow us to gather a bunch of data on performance that we can share with everybody. If you run into old documentation referring to other PPAs, you can help us by consolidating references to this PPA. If someone wants to go ahead and start prototyping on `software-properties-gtk` on what the GUI should look like, please start hacking! ## Help us Help You! We use the donation funds to get the developers hardware to test and upload these drivers, please consider donating to the "community" slider on the donation page if you're loving this PPA: http://www.ubuntu.com/download/desktop/contribute More info: https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa Adding repository. Press [ENTER] to continue or Ctrl-c to cancel. Adding deb entry to /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-hirsute.list Adding disabled deb-src entry to /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-hirsute.list Adding key to /etc/apt/trusted.gpg.d/graphics-drivers-ubuntu-ppa.gpg with fingerprint 2388FF3BE10A76F638F80723FCAE110B1118213C 命中:1 http://security.ubuntu.com/ubuntu hirsute-security InRelease 命中:3 http://dl.google.com/linux/chrome/deb stable InRelease 获取:4 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu hirsute InRelease [24.4 kB] 命中:5 http://cn.archive.ubuntu.com/ubuntu hirsute InRelease 获取:6 http://cn.archive.ubuntu.com/ubuntu hirsute-updates InRelease [109 kB] 获取:7 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu hirsute/main amd64 Packages [23.4 kB] 命中:8 http://cn.archive.ubuntu.com/ubuntu hirsute-backports InRelease 获取:9 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu hirsute/main i386 Packages [10.6 kB] 获取:10 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu hirsute/main Translation-en [5,880 B] 忽略:2 https://developer.download.nvidia.cn/compute/machine-learning/repos/ubuntu1604/x86_64 InRelease 命中:11 https://developer.download.nvidia.cn/compute/machine-learning/repos/ubuntu1604/x86_64 Release 已下载 173 kB，耗时 21秒 (8,156 B/s) 正在读取软件包列表... 完成 cby@cby-Inspiron-7577:~$ 第二步，更新源同时查看可安装的驱动cby@cby-Inspiron-7577:~$ sudo apt update 命中:1 http://dl.google.com/linux/chrome/deb stable InRelease 命中:2 http://cn.archive.ubuntu.com/ubuntu hirsute InRelease 获取:4 http://cn.archive.ubuntu.com/ubuntu hirsute-updates InRelease [109 kB] 命中:5 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu hirsute InRelease 命中:6 http://security.ubuntu.com/ubuntu hirsute-security InRelease 忽略:3 https://developer.download.nvidia.cn/compute/machine-learning/repos/ubuntu1604/x86_64 InRelease 命中:7 https://developer.download.nvidia.cn/compute/machine-learning/repos/ubuntu1604/x86_64 Release 命中:8 http://cn.archive.ubuntu.com/ubuntu hirsute-backports InRelease 已下载 109 kB，耗时 2秒 (64.2 kB/s) 正在读取软件包列表... 完成 正在分析软件包的依赖关系树... 完成 正在读取状态信息... 完成 有 4 个软件包可以升级。请执行 ‘apt list --upgradable’ 来查看它们。 cby@cby-Inspiron-7577:~$ ubuntu-drivers devices WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support Legacyheader, cannot determine support level == /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 == modalias : pci:v000010DEd00001C8Csv00001028sd000007FAbc03sc02i00 vendor : NVIDIA Corporation model : GP107M [GeForce GTX 1050 Ti Mobile] manual_install: True driver : nvidia-driver-460 - distro non-free recommended driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-390 - distro non-free driver : nvidia-driver-465 - distro non-free driver : nvidia-driver-460-server - distro non-free driver : nvidia-driver-418-server - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin cby@cby-Inspiron-7577:~$ sudo apt install nvidia-driver-465 ...略... 第三步，查看显卡信息cby@cby-Inspiron-7577:~$ nvidia-smi Sun Jun 6 21:58:45 2021 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 465.27 Driver Version: 465.27 CUDA Version: 11.3 | |-------------------------------+----------------------+----------------------+ | 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 GeForce ... Off | 00000000:01:00.0 Off | N/A | | N/A 59C P3 N/A / N/A | 919MiB / 4042MiB | 6% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=============================================================================| | 0 N/A N/A 1976 G /usr/lib/xorg/Xorg 351MiB | | 0 N/A N/A 2620 G /usr/bin/gnome-shell 213MiB | | 0 N/A N/A 4020 G gnome-control-center 1MiB | | 0 N/A N/A 4258 G ...AAAAAAAAA= --shared-files 349MiB | | 0 N/A N/A 6333 G /usr/bin/nvidia-settings 1MiB | +-----------------------------------------------------------------------------+ cby@cby-Inspiron-7577:~$ 第四步，安装 CUDA Toolkit Archivehttps://developer.nvidia.com/cuda-toolkit-archive在如上官网中下载安装CUDA 第五步，根据官方教程进行安装cby@cby-Inspiron-7577:~$ wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin --2021-06-06 21:59:36-- https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin 正在解析主机 developer.download.nvidia.com (developer.download.nvidia.com)... 192.254.94.202, 45.43.32.210, 45.43.32.211, ... 正在连接 developer.download.nvidia.com (developer.download.nvidia.com)|192.254.94.202|:443... 已连接。 已发出 HTTP 请求，正在等待回应... 301 Moved Permanently 位置：https://developer.download.nvidia.cn/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin [跟随至新的 URL] --2021-06-06 21:59:37-- https://developer.download.nvidia.cn/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin 正在解析主机 developer.download.nvidia.cn (developer.download.nvidia.cn)... 124.132.138.66, 124.132.138.73, 124.132.138.69 正在连接 developer.download.nvidia.cn (developer.download.nvidia.cn)|124.132.138.66|:443... 已连接。 已发出 HTTP 请求，正在等待回应... 200 OK 长度：190 [application/octet-stream] 正在保存至: ‘cuda-ubuntu2004.pin’ cuda-ubuntu2004.pin 100%[==================>] 190 --.-KB/s 用时 0s 2021-06-06 21:59:37 (26.1 MB/s) - 已保存 ‘cuda-ubuntu2004.pin’ [190/190]) cby@cby-Inspiron-7577:~$ sudo mv cuda-ubuntu2004.pin /etc/apt/preferences.d/cuda-repository-pin-600 cby@cby-Inspiron-7577:~$ wget https://developer.download.nvidia.com/compute/cuda/11.3.1/local_installers/cuda-repo-ubuntu2004-11-3-local_11.3.1-465.19.01-1_amd64.deb --2021-06-06 21:59:48-- https://developer.download.nvidia.com/compute/cuda/11.3.1/local_installers/cuda-repo-ubuntu2004-11-3-local_11.3.1-465.19.01-1_amd64.deb 正在解析主机 developer.download.nvidia.com (developer.download.nvidia.com)... 45.43.32.210, 192.254.94.203, 45.43.32.211, ... 正在连接 developer.download.nvidia.com (developer.download.nvidia.com)|45.43.32.210|:443... 已连接。 已发出 HTTP 请求，正在等待回应... 301 Moved Permanently 位置：https://developer.download.nvidia.cn/compute/cuda/11.3.1/local_installers/cuda-repo-ubuntu2004-11-3-local_11.3.1-465.19.01-1_amd64.deb [跟随至新的 URL] --2021-06-06 21:59:48-- https://developer.download.nvidia.cn/compute/cuda/11.3.1/local_installers/cuda-repo-ubuntu2004-11-3-local_11.3.1-465.19.01-1_amd64.deb 正在解析主机 developer.download.nvidia.cn (developer.download.nvidia.cn)... 124.132.138.66, 124.132.138.73, 124.132.138.69 正在连接 developer.download.nvidia.cn (developer.download.nvidia.cn)|124.132.138.66|:443... 已连接。 已发出 HTTP 请求，正在等待回应... 200 OK 长度：2374574280 (2.2G) [application/x-deb] 正在保存至: ‘cuda-repo-ubuntu2004-11-3-local_11.3.1-465.19.01-1_amd64.deb’ cuda-repo-ubuntu200 100%[==================>] 2.21G 44.0MB/s 用时 51s 2021-06-06 22:00:40 (44.3 MB/s) - 已保存 ‘cuda-repo-ubuntu2004-11-3-local_11.3.1-465.19.01-1_amd64.deb’ [2374574280/2374574280]) cby@cby-Inspiron-7577:~$ sudo dpkg -i cuda-repo-ubuntu2004-11-3-local_11.3.1-465.19.01-1_amd64.deb 正在选中未选择的软件包 cuda-repo-ubuntu2004-11-3-local。 (正在读取数据库 ... 系统当前共安装有 209119 个文件和目录。) 准备解压 cuda-repo-ubuntu2004-11-3-local_11.3.1-465.19.01-1_amd64.deb ... 正在解压 cuda-repo-ubuntu2004-11-3-local (11.3.1-465.19.01-1) ... 正在设置 cuda-repo-ubuntu2004-11-3-local (11.3.1-465.19.01-1) ... cby@cby-Inspiron-7577:~$ sudo apt-key add /var/cuda-repo-ubuntu2004-11-3-local/7fa2af80.pub Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). OK cby@cby-Inspiron-7577:~$ sudo apt-get update 获取:1 file:/var/cuda-repo-ubuntu2004-11-3-local InRelease 忽略:1 file:/var/cuda-repo-ubuntu2004-11-3-local InRelease 获取:2 file:/var/cuda-repo-ubuntu2004-11-3-local Release [564 B] 获取:2 file:/var/cuda-repo-ubuntu2004-11-3-local Release [564 B] 获取:3 file:/var/cuda-repo-ubuntu2004-11-3-local Release.gpg [836 B] 获取:3 file:/var/cuda-repo-ubuntu2004-11-3-local Release.gpg [836 B] 获取:4 file:/var/cuda-repo-ubuntu2004-11-3-local Packages [30.4 kB] 命中:5 http://cn.archive.ubuntu.com/ubuntu hirsute InRelease 获取:7 http://cn.archive.ubuntu.com/ubuntu hirsute-updates InRelease [109 kB] 命中:8 http://dl.google.com/linux/chrome/deb stable InRelease 命中:9 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu hirsute InRelease 命中:10 http://security.ubuntu.com/ubuntu hirsute-security InRelease 忽略:6 https://developer.download.nvidia.cn/compute/machine-learning/repos/ubuntu1604/x86_64 InRelease 命中:11 https://developer.download.nvidia.cn/compute/machine-learning/repos/ubuntu1604/x86_64 Release 命中:13 http://cn.archive.ubuntu.com/ubuntu hirsute-backports InRelease 已下载 109 kB，耗时 2秒 (52.6 kB/s) 正在读取软件包列表... 完成 cby@cby-Inspiron-7577:~$ cby@cby-Inspiron-7577:~$ cby@cby-Inspiron-7577:~$ sudo apt-get -y install cuda 正在读取软件包列表... 完成 正在分析软件包的依赖关系树... 完成 正在读取状态信息... 完成 下列软件包是自动安装的并且现在不需要了： libaccinj64-11.2 libcub-dev libcublas11 libcublaslt11 libcudart11.0 libcufft10 libcufftw10 libcuinj64-11.2 libcupti-dev libcupti-doc libcupti11.2 libcurand10 libcusolver11 libcusolvermg11 libcusparse11 libegl-dev libgl-dev libgl1-mesa-dev libgles-dev libgles1 libglvnd-dev libglx-dev libnppc11 libnppial11 libnppicc11 libnppidei11 libnppif11 libnppig11 libnppim11 libnppist11 libnppisu11 libnppitc11 libnpps11 libnvblas11 libnvjpeg11 libnvrtc11.2 libnvtoolsext1 libnvvm4 libopengl-dev libopengl0 libpthread-stubs0-dev libthrust-dev libvdpau-dev libx11-dev libxau-dev libxcb1-dev libxdmcp-dev node-html5shiv nsight-compute nsight-compute-target nsight-systems nsight-systems-target nvidia-cuda-gdb nvidia-cuda-toolkit-doc nvidia-opencl-dev nvidia-profiler nvidia-visual-profiler ocl-icd-opencl-dev opencl-c-headers opencl-clhpp-headers x11proto-dev xorg-sgml-doctools xtrans-dev 使用'sudo apt autoremove'来卸载它(它们)。 将会同时安装下列软件： cuda-11-3 cuda-command-line-tools-11-3 cuda-compiler-11-3 cuda-cudart-11-3 cuda-cudart-dev-11-3 cuda-cuobjdump-11-3 cuda-cupti-11-3 cuda-cupti-dev-11-3 cuda-cuxxfilt-11-3 cuda-demo-suite-11-3 cuda-documentation-11-3 cuda-driver-dev-11-3 cuda-drivers cuda-drivers-465 cuda-gdb-11-3 cuda-libraries-11-3 cuda-libraries-dev-11-3 cuda-memcheck-11-3 cuda-nsight-11-3 cuda-nsight-compute-11-3 cuda-nsight-systems-11-3 cuda-nvcc-11-3 cuda-nvdisasm-11-3 cuda-nvml-dev-11-3 cuda-nvprof-11-3 cuda-nvprune-11-3 cuda-nvrtc-11-3 cuda-nvrtc-dev-11-3 cuda-nvtx-11-3 cuda-nvvp-11-3 cuda-runtime-11-3 cuda-samples-11-3 cuda-sanitizer-11-3 cuda-thrust-11-3 cuda-toolkit-11-3 cuda-toolkit-11-3-config-common cuda-toolkit-11-config-common cuda-toolkit-config-common cuda-tools-11-3 cuda-visual-tools-11-3 default-jre default-jre-headless libcublas-11-3 libcublas-dev-11-3 libcufft-11-3 libcufft-dev-11-3 libcurand-11-3 libcurand-dev-11-3 libcusolver-11-3 libcusolver-dev-11-3 libcusparse-11-3 libcusparse-dev-11-3 libnpp-11-3 libnpp-dev-11-3 libnvjpeg-11-3 libnvjpeg-dev-11-3 nsight-compute-2021.1.1 nsight-systems-2021.1.3 nvidia-modprobe nvidia-settings openjdk-11-jre openjdk-11-jre-headless 建议安装： fonts-ipafont-gothic fonts-ipafont-mincho fonts-wqy-microhei | fonts-wqy-zenhei 下列【新】软件包将被安装： cuda cuda-11-3 cuda-command-line-tools-11-3 cuda-compiler-11-3 cuda-cudart-11-3 cuda-cudart-dev-11-3 cuda-cuobjdump-11-3 cuda-cupti-11-3 cuda-cupti-dev-11-3 cuda-cuxxfilt-11-3 cuda-demo-suite-11-3 cuda-documentation-11-3 cuda-driver-dev-11-3 cuda-drivers cuda-drivers-465 cuda-gdb-11-3 cuda-libraries-11-3 cuda-libraries-dev-11-3 cuda-memcheck-11-3 cuda-nsight-11-3 cuda-nsight-compute-11-3 cuda-nsight-systems-11-3 cuda-nvcc-11-3 cuda-nvdisasm-11-3 cuda-nvml-dev-11-3 cuda-nvprof-11-3 cuda-nvprune-11-3 cuda-nvrtc-11-3 cuda-nvrtc-dev-11-3 cuda-nvtx-11-3 cuda-nvvp-11-3 cuda-runtime-11-3 cuda-samples-11-3 cuda-sanitizer-11-3 cuda-thrust-11-3 cuda-toolkit-11-3 cuda-toolkit-11-3-config-common cuda-toolkit-11-config-common cuda-toolkit-config-common cuda-tools-11-3 cuda-visual-tools-11-3 default-jre default-jre-headless libcublas-11-3 libcublas-dev-11-3 libcufft-11-3 libcufft-dev-11-3 libcurand-11-3 libcurand-dev-11-3 libcusolver-11-3 libcusolver-dev-11-3 libcusparse-11-3 libcusparse-dev-11-3 libnpp-11-3 libnpp-dev-11-3 libnvjpeg-11-3 libnvjpeg-dev-11-3 nsight-compute-2021.1.1 nsight-systems-2021.1.3 nvidia-modprobe openjdk-11-jre openjdk-11-jre-headless 下列软件包将被升级： nvidia-settings 升级了 1 个软件包，新安装了 62 个软件包，要卸载 0 个软件包，有 5 个软件包未被升级。 需要下载 37.4 MB/2,162 MB 的归档。 解压缩后会消耗 4,934 MB 的额外空间。 获取:1 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-toolkit-config-common 11.3.109-1 [16.1 kB] 获取:2 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-toolkit-11-config-common 11.3.109-1 [16.1 kB] 获取:3 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-toolkit-11-3-config-common 11.3.109-1 [16.1 kB] 获取:4 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-cudart-11-3 11.3.109-1 [157 kB] 获取:5 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvrtc-11-3 11.3.109-1 [26.1 MB] 获取:6 http://cn.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 openjdk-11-jre-headless amd64 11.0.11+9-0ubuntu2 [37.2 MB] 获取:7 file:/var/cuda-repo-ubuntu2004-11-3-local libcublas-11-3 11.5.1.109-1 [168 MB] 获取:8 file:/var/cuda-repo-ubuntu2004-11-3-local libcufft-11-3 10.4.2.109-1 [108 MB] 获取:9 file:/var/cuda-repo-ubuntu2004-11-3-local libcurand-11-3 10.2.4.109-1 [39.4 MB] 获取:10 file:/var/cuda-repo-ubuntu2004-11-3-local libcusolver-11-3 11.1.2.109-1 [85.5 MB] 获取:11 file:/var/cuda-repo-ubuntu2004-11-3-local libcusparse-11-3 11.6.0.109-1 [104 MB] 获取:12 file:/var/cuda-repo-ubuntu2004-11-3-local libnpp-11-3 11.3.3.95-1 [75.1 MB] 获取:13 file:/var/cuda-repo-ubuntu2004-11-3-local libnvjpeg-11-3 11.5.0.109-1 [1,742 kB] 获取:14 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-libraries-11-3 11.3.1-1 [2,498 B] 获取:15 file:/var/cuda-repo-ubuntu2004-11-3-local nvidia-modprobe 465.19.01-0ubuntu1 [19.9 kB] 获取:16 file:/var/cuda-repo-ubuntu2004-11-3-local nvidia-settings 465.19.01-0ubuntu1 [928 kB] 获取:17 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-drivers-465 465.19.01-1 [2,628 B] 获取:18 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-drivers 465.19.01-1 [2,504 B] 获取:19 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-runtime-11-3 11.3.1-1 [2,424 B] 获取:20 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-cuobjdump-11-3 11.3.58-1 [112 kB] 获取:21 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-cuxxfilt-11-3 11.3.58-1 [44.1 kB] 获取:22 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-thrust-11-3 11.3.109-1 [981 kB] 获取:23 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-driver-dev-11-3 11.3.109-1 [26.2 kB] 获取:24 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-cudart-dev-11-3 11.3.109-1 [737 kB] 获取:25 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvcc-11-3 11.3.109-1 [46.5 MB] 获取:26 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvprune-11-3 11.3.58-1 [54.9 kB] 获取:27 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-compiler-11-3 11.3.1-1 [2,430 B] 获取:28 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvrtc-dev-11-3 11.3.109-1 [23.4 kB] 获取:29 http://cn.archive.ubuntu.com/ubuntu hirsute/main amd64 default-jre-headless amd64 2:1.11-72 [3,192 B] 获取:30 http://cn.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 openjdk-11-jre amd64 11.0.11+9-0ubuntu2 [177 kB] 获取:31 http://cn.archive.ubuntu.com/ubuntu hirsute/main amd64 default-jre amd64 2:1.11-72 [1,084 B] 获取:32 file:/var/cuda-repo-ubuntu2004-11-3-local libcublas-dev-11-3 11.5.1.109-1 [171 MB] 获取:33 file:/var/cuda-repo-ubuntu2004-11-3-local libcufft-dev-11-3 10.4.2.109-1 [181 MB] 获取:34 file:/var/cuda-repo-ubuntu2004-11-3-local libcurand-dev-11-3 10.2.4.109-1 [39.9 MB] 获取:35 file:/var/cuda-repo-ubuntu2004-11-3-local libcusolver-dev-11-3 11.1.2.109-1 [22.2 MB] 获取:36 file:/var/cuda-repo-ubuntu2004-11-3-local libcusparse-dev-11-3 11.6.0.109-1 [104 MB] 获取:37 file:/var/cuda-repo-ubuntu2004-11-3-local libnpp-dev-11-3 11.3.3.95-1 [71.7 MB] 获取:38 file:/var/cuda-repo-ubuntu2004-11-3-local libnvjpeg-dev-11-3 11.5.0.109-1 [1,435 kB] 获取:39 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-libraries-dev-11-3 11.3.1-1 [2,526 B] 获取:40 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-cupti-11-3 11.3.111-1 [11.7 MB] 获取:41 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-cupti-dev-11-3 11.3.111-1 [2,404 kB] 获取:42 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvdisasm-11-3 11.3.58-1 [32.9 MB] 获取:43 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-gdb-11-3 11.3.109-1 [3,622 kB] 获取:44 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-memcheck-11-3 11.3.109-1 [145 kB] 获取:45 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvprof-11-3 11.3.111-1 [1,925 kB] 获取:46 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvtx-11-3 11.3.109-1 [51.1 kB] 获取:47 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-sanitizer-11-3 11.3.111-1 [7,543 kB] 获取:48 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-command-line-tools-11-3 11.3.1-1 [2,478 B] 获取:49 file:/var/cuda-repo-ubuntu2004-11-3-local nsight-compute-2021.1.1 2021.1.1.5-1 [273 MB] 获取:50 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nsight-compute-11-3 11.3.1-1 [3,704 B] 获取:51 file:/var/cuda-repo-ubuntu2004-11-3-local nsight-systems-2021.1.3 2021.1.3.14-b695ea9 [248 MB] 获取:52 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nsight-systems-11-3 11.3.1-1 [3,296 B] 获取:53 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nsight-11-3 11.3.109-1 [119 MB] 获取:54 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvml-dev-11-3 11.3.58-1 [73.3 kB] 获取:55 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-nvvp-11-3 11.3.111-1 [114 MB] 获取:56 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-visual-tools-11-3 11.3.1-1 [2,866 B] 获取:57 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-tools-11-3 11.3.1-1 [2,378 B] 获取:58 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-samples-11-3 11.3.58-1 [59.2 MB] 获取:59 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-documentation-11-3 11.3.111-1 [48.1 kB] 获取:60 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-toolkit-11-3 11.3.1-1 [3,300 B] 获取:61 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-demo-suite-11-3 11.3.58-1 [3,978 kB] 获取:62 file:/var/cuda-repo-ubuntu2004-11-3-local cuda-11-3 11.3.1-1 [2,450 B] 获取:63 file:/var/cuda-repo-ubuntu2004-11-3-local cuda 11.3.1-1 [2,396 B] 已下载 37.4 MB，耗时 15秒 (2,527 kB/s) Requesting to save current system state Successfully saved as "autozsys_el84cc" 正在从软件包中解出模板：100% 正在选中未选择的软件包 cuda-toolkit-config-common。 (正在读取数据库 ... 系统当前共安装有 209232 个文件和目录。) 准备解压 .../00-cuda-toolkit-config-common_11.3.109-1_all.deb ... 正在解压 cuda-toolkit-config-common (11.3.109-1) ... 正在选中未选择的软件包 cuda-toolkit-11-config-common。 准备解压 .../01-cuda-toolkit-11-config-common_11.3.109-1_all.deb ... 正在解压 cuda-toolkit-11-config-common (11.3.109-1) ... 正在选中未选择的软件包 cuda-toolkit-11-3-config-common。 准备解压 .../02-cuda-toolkit-11-3-config-common_11.3.109-1_all.deb ... 正在解压 cuda-toolkit-11-3-config-common (11.3.109-1) ... 正在选中未选择的软件包 cuda-cudart-11-3。 准备解压 .../03-cuda-cudart-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-cudart-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-nvrtc-11-3。 准备解压 .../04-cuda-nvrtc-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-nvrtc-11-3 (11.3.109-1) ... 正在选中未选择的软件包 libcublas-11-3。 准备解压 .../05-libcublas-11-3_11.5.1.109-1_amd64.deb ... 正在解压 libcublas-11-3 (11.5.1.109-1) ... 正在选中未选择的软件包 libcufft-11-3。 准备解压 .../06-libcufft-11-3_10.4.2.109-1_amd64.deb ... 正在解压 libcufft-11-3 (10.4.2.109-1) ... 正在选中未选择的软件包 libcurand-11-3。 准备解压 .../07-libcurand-11-3_10.2.4.109-1_amd64.deb ... 正在解压 libcurand-11-3 (10.2.4.109-1) ... 正在选中未选择的软件包 libcusolver-11-3。 准备解压 .../08-libcusolver-11-3_11.1.2.109-1_amd64.deb ... 正在解压 libcusolver-11-3 (11.1.2.109-1) ... 正在选中未选择的软件包 libcusparse-11-3。 准备解压 .../09-libcusparse-11-3_11.6.0.109-1_amd64.deb ... 正在解压 libcusparse-11-3 (11.6.0.109-1) ... 正在选中未选择的软件包 libnpp-11-3。 准备解压 .../10-libnpp-11-3_11.3.3.95-1_amd64.deb ... 正在解压 libnpp-11-3 (11.3.3.95-1) ... 正在选中未选择的软件包 libnvjpeg-11-3。 准备解压 .../11-libnvjpeg-11-3_11.5.0.109-1_amd64.deb ... 正在解压 libnvjpeg-11-3 (11.5.0.109-1) ... 正在选中未选择的软件包 cuda-libraries-11-3。 准备解压 .../12-cuda-libraries-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-libraries-11-3 (11.3.1-1) ... 正在选中未选择的软件包 nvidia-modprobe。 准备解压 .../13-nvidia-modprobe_465.19.01-0ubuntu1_amd64.deb ... 正在解压 nvidia-modprobe (465.19.01-0ubuntu1) ... 准备解压 .../14-nvidia-settings_465.19.01-0ubuntu1_amd64.deb ... 正在解压 nvidia-settings (465.19.01-0ubuntu1) 并覆盖 (460.56-0ubuntu2) ... 正在选中未选择的软件包 cuda-drivers-465。 准备解压 .../15-cuda-drivers-465_465.19.01-1_amd64.deb ... 正在解压 cuda-drivers-465 (465.19.01-1) ... 正在选中未选择的软件包 cuda-drivers。 准备解压 .../16-cuda-drivers_465.19.01-1_amd64.deb ... 正在解压 cuda-drivers (465.19.01-1) ... 正在选中未选择的软件包 cuda-runtime-11-3。 准备解压 .../17-cuda-runtime-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-runtime-11-3 (11.3.1-1) ... 正在选中未选择的软件包 cuda-cuobjdump-11-3。 准备解压 .../18-cuda-cuobjdump-11-3_11.3.58-1_amd64.deb ... 正在解压 cuda-cuobjdump-11-3 (11.3.58-1) ... 正在选中未选择的软件包 cuda-cuxxfilt-11-3。 准备解压 .../19-cuda-cuxxfilt-11-3_11.3.58-1_amd64.deb ... 正在解压 cuda-cuxxfilt-11-3 (11.3.58-1) ... 正在选中未选择的软件包 cuda-thrust-11-3。 准备解压 .../20-cuda-thrust-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-thrust-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-driver-dev-11-3。 准备解压 .../21-cuda-driver-dev-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-driver-dev-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-cudart-dev-11-3。 准备解压 .../22-cuda-cudart-dev-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-cudart-dev-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-nvcc-11-3。 准备解压 .../23-cuda-nvcc-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-nvcc-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-nvprune-11-3。 准备解压 .../24-cuda-nvprune-11-3_11.3.58-1_amd64.deb ... 正在解压 cuda-nvprune-11-3 (11.3.58-1) ... 正在选中未选择的软件包 cuda-compiler-11-3。 准备解压 .../25-cuda-compiler-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-compiler-11-3 (11.3.1-1) ... 正在选中未选择的软件包 cuda-nvrtc-dev-11-3。 准备解压 .../26-cuda-nvrtc-dev-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-nvrtc-dev-11-3 (11.3.109-1) ... 正在选中未选择的软件包 libcublas-dev-11-3。 准备解压 .../27-libcublas-dev-11-3_11.5.1.109-1_amd64.deb ... 正在解压 libcublas-dev-11-3 (11.5.1.109-1) ... 正在选中未选择的软件包 libcufft-dev-11-3。 准备解压 .../28-libcufft-dev-11-3_10.4.2.109-1_amd64.deb ... 正在解压 libcufft-dev-11-3 (10.4.2.109-1) ... 正在选中未选择的软件包 libcurand-dev-11-3。 准备解压 .../29-libcurand-dev-11-3_10.2.4.109-1_amd64.deb ... 正在解压 libcurand-dev-11-3 (10.2.4.109-1) ... 正在选中未选择的软件包 libcusolver-dev-11-3。 准备解压 .../30-libcusolver-dev-11-3_11.1.2.109-1_amd64.deb ... 正在解压 libcusolver-dev-11-3 (11.1.2.109-1) ... 正在选中未选择的软件包 libcusparse-dev-11-3。 准备解压 .../31-libcusparse-dev-11-3_11.6.0.109-1_amd64.deb ... 正在解压 libcusparse-dev-11-3 (11.6.0.109-1) ... 正在选中未选择的软件包 libnpp-dev-11-3。 准备解压 .../32-libnpp-dev-11-3_11.3.3.95-1_amd64.deb ... 正在解压 libnpp-dev-11-3 (11.3.3.95-1) ... 正在选中未选择的软件包 libnvjpeg-dev-11-3。 准备解压 .../33-libnvjpeg-dev-11-3_11.5.0.109-1_amd64.deb ... 正在解压 libnvjpeg-dev-11-3 (11.5.0.109-1) ... 正在选中未选择的软件包 cuda-libraries-dev-11-3。 准备解压 .../34-cuda-libraries-dev-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-libraries-dev-11-3 (11.3.1-1) ... 正在选中未选择的软件包 cuda-cupti-11-3。 准备解压 .../35-cuda-cupti-11-3_11.3.111-1_amd64.deb ... 正在解压 cuda-cupti-11-3 (11.3.111-1) ... 正在选中未选择的软件包 cuda-cupti-dev-11-3。 准备解压 .../36-cuda-cupti-dev-11-3_11.3.111-1_amd64.deb ... 正在解压 cuda-cupti-dev-11-3 (11.3.111-1) ... 正在选中未选择的软件包 cuda-nvdisasm-11-3。 准备解压 .../37-cuda-nvdisasm-11-3_11.3.58-1_amd64.deb ... 正在解压 cuda-nvdisasm-11-3 (11.3.58-1) ... 正在选中未选择的软件包 cuda-gdb-11-3。 准备解压 .../38-cuda-gdb-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-gdb-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-memcheck-11-3。 准备解压 .../39-cuda-memcheck-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-memcheck-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-nvprof-11-3。 准备解压 .../40-cuda-nvprof-11-3_11.3.111-1_amd64.deb ... 正在解压 cuda-nvprof-11-3 (11.3.111-1) ... 正在选中未选择的软件包 cuda-nvtx-11-3。 准备解压 .../41-cuda-nvtx-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-nvtx-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-sanitizer-11-3。 准备解压 .../42-cuda-sanitizer-11-3_11.3.111-1_amd64.deb ... 正在解压 cuda-sanitizer-11-3 (11.3.111-1) ... 正在选中未选择的软件包 cuda-command-line-tools-11-3。 准备解压 .../43-cuda-command-line-tools-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-command-line-tools-11-3 (11.3.1-1) ... 正在选中未选择的软件包 nsight-compute-2021.1.1。 准备解压 .../44-nsight-compute-2021.1.1_2021.1.1.5-1_amd64.deb ... 正在解压 nsight-compute-2021.1.1 (2021.1.1.5-1) ... 正在选中未选择的软件包 cuda-nsight-compute-11-3。 准备解压 .../45-cuda-nsight-compute-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-nsight-compute-11-3 (11.3.1-1) ... 正在选中未选择的软件包 nsight-systems-2021.1.3。 准备解压 .../46-nsight-systems-2021.1.3_2021.1.3.14-1_amd64.deb ... 正在解压 nsight-systems-2021.1.3 (2021.1.3.14-b695ea9) ... 正在选中未选择的软件包 cuda-nsight-systems-11-3。 准备解压 .../47-cuda-nsight-systems-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-nsight-systems-11-3 (11.3.1-1) ... 正在选中未选择的软件包 openjdk-11-jre-headless:amd64。 准备解压 .../48-openjdk-11-jre-headless_11.0.11+9-0ubuntu2_amd64.deb ... 正在解压 openjdk-11-jre-headless:amd64 (11.0.11+9-0ubuntu2) ... 正在选中未选择的软件包 default-jre-headless。 准备解压 .../49-default-jre-headless_2%3a1.11-72_amd64.deb ... 正在解压 default-jre-headless (2:1.11-72) ... 正在选中未选择的软件包 openjdk-11-jre:amd64。 准备解压 .../50-openjdk-11-jre_11.0.11+9-0ubuntu2_amd64.deb ... 正在解压 openjdk-11-jre:amd64 (11.0.11+9-0ubuntu2) ... 正在选中未选择的软件包 default-jre。 准备解压 .../51-default-jre_2%3a1.11-72_amd64.deb ... 正在解压 default-jre (2:1.11-72) ... 正在选中未选择的软件包 cuda-nsight-11-3。 准备解压 .../52-cuda-nsight-11-3_11.3.109-1_amd64.deb ... 正在解压 cuda-nsight-11-3 (11.3.109-1) ... 正在选中未选择的软件包 cuda-nvml-dev-11-3。 准备解压 .../53-cuda-nvml-dev-11-3_11.3.58-1_amd64.deb ... 正在解压 cuda-nvml-dev-11-3 (11.3.58-1) ... 正在选中未选择的软件包 cuda-nvvp-11-3。 准备解压 .../54-cuda-nvvp-11-3_11.3.111-1_amd64.deb ... 正在解压 cuda-nvvp-11-3 (11.3.111-1) ... 正在选中未选择的软件包 cuda-visual-tools-11-3。 准备解压 .../55-cuda-visual-tools-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-visual-tools-11-3 (11.3.1-1) ... 正在选中未选择的软件包 cuda-tools-11-3。 准备解压 .../56-cuda-tools-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-tools-11-3 (11.3.1-1) ... 正在选中未选择的软件包 cuda-samples-11-3。 准备解压 .../57-cuda-samples-11-3_11.3.58-1_amd64.deb ... 正在解压 cuda-samples-11-3 (11.3.58-1) ... 正在选中未选择的软件包 cuda-documentation-11-3。 准备解压 .../58-cuda-documentation-11-3_11.3.111-1_amd64.deb ... 正在解压 cuda-documentation-11-3 (11.3.111-1) ... 正在选中未选择的软件包 cuda-toolkit-11-3。 准备解压 .../59-cuda-toolkit-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-toolkit-11-3 (11.3.1-1) ... 正在选中未选择的软件包 cuda-demo-suite-11-3。 准备解压 .../60-cuda-demo-suite-11-3_11.3.58-1_amd64.deb ... 正在解压 cuda-demo-suite-11-3 (11.3.58-1) ... 正在选中未选择的软件包 cuda-11-3。 准备解压 .../61-cuda-11-3_11.3.1-1_amd64.deb ... 正在解压 cuda-11-3 (11.3.1-1) ... 正在选中未选择的软件包 cuda。 准备解压 .../62-cuda_11.3.1-1_amd64.deb ... 正在解压 cuda (11.3.1-1) ... 正在设置 cuda-toolkit-config-common (11.3.109-1) ... 正在设置 cuda-cuxxfilt-11-3 (11.3.58-1) ... 正在设置 cuda-toolkit-11-3-config-common (11.3.109-1) ... Setting alternatives update-alternatives: 使用 /usr/local/cuda-11.3 来在自动模式中提供 /usr/local/cuda (cuda) update-alternatives: 使用 /usr/local/cuda-11.3 来在自动模式中提供 /usr/local/cuda-11 (cuda-11) 正在设置 cuda-toolkit-11-config-common (11.3.109-1) ... 正在设置 cuda-nvtx-11-3 (11.3.109-1) ... 正在设置 cuda-memcheck-11-3 (11.3.109-1) ... 正在设置 cuda-nvprune-11-3 (11.3.58-1) ... 正在设置 cuda-driver-dev-11-3 (11.3.109-1) ... 正在设置 openjdk-11-jre-headless:amd64 (11.0.11+9-0ubuntu2) ... update-alternatives: 使用 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 来在自动模式中提供 /usr/bin/java (java) update-alternatives: 使用 /usr/lib/jvm/java-11-openjdk-amd64/bin/jjs 来在自动模式中提供 /usr/bin/jjs (jjs) update-alternatives: 使用 /usr/lib/jvm/java-11-openjdk-amd64/bin/keytool 来在自动模式中提供 /usr/bin/keytool (keytool) update-alternatives: 使用 /usr/lib/jvm/java-11-openjdk-amd64/bin/rmid 来在自动模式中提供 /usr/bin/rmid (rmid) update-alternatives: 使用 /usr/lib/jvm/java-11-openjdk-amd64/bin/rmiregistry 来在自动模式中提供 /usr/bin/rmiregistry (rmiregistry) update-alternatives: 使用 /usr/lib/jvm/java-11-openjdk-amd64/bin/pack200 来在自动模式中提供 /usr/bin/pack200 (pack200) update-alternatives: 使用 /usr/lib/jvm/java-11-openjdk-amd64/bin/unpack200 来在自动模式中提供 /usr/bin/unpack200 (unpack200) update-alternatives: 使用 /usr/lib/jvm/java-11-openjdk-amd64/lib/jexec 来在自动模式中提供 /usr/bin/jexec (jexec) 正在设置 openjdk-11-jre:amd64 (11.0.11+9-0ubuntu2) ... 正在设置 libnvjpeg-11-3 (11.5.0.109-1) ... 正在设置 cuda-nvprof-11-3 (11.3.111-1) ... 正在设置 nvidia-modprobe (465.19.01-0ubuntu1) ... 正在设置 cuda-thrust-11-3 (11.3.109-1) ... 正在设置 cuda-nvml-dev-11-3 (11.3.58-1) ... 正在设置 libnvjpeg-dev-11-3 (11.5.0.109-1) ... 正在设置 cuda-cudart-11-3 (11.3.109-1) ... 正在设置 cuda-cudart-dev-11-3 (11.3.109-1) ... 正在设置 nsight-compute-2021.1.1 (2021.1.1.5-1) ... 正在设置 libnpp-11-3 (11.3.3.95-1) ... 正在设置 libcusparse-11-3 (11.6.0.109-1) ... 正在设置 nsight-systems-2021.1.3 (2021.1.3.14-b695ea9) ... update-alternatives: 使用 /opt/nvidia/nsight-systems/2021.1.3/target-linux-x64/nsys 来在自动模式中提供 /usr/local/bin/nsys (nsys) update-alternatives: 错误: alternative path /opt/nvidia/nsight-systems/2021.1.3/host-linux-x64/nsight-sys doesn't exist update-alternatives: 错误: 无 nsight-sys 的候选项 update-alternatives: 使用 /opt/nvidia/nsight-systems/2021.1.3/host-linux-x64/nsys-ui 来在自动模式中提供 /usr/local/bin/nsys-ui (nsys-ui) 正在设置 cuda-nvdisasm-11-3 (11.3.58-1) ... 正在设置 nvidia-settings (465.19.01-0ubuntu1) ... 正在设置 libcurand-11-3 (10.2.4.109-1) ... 正在设置 cuda-cuobjdump-11-3 (11.3.58-1) ... 正在设置 libcufft-11-3 (10.4.2.109-1) ... 正在设置 libcusparse-dev-11-3 (11.6.0.109-1) ... 正在设置 cuda-nvrtc-11-3 (11.3.109-1) ... 正在设置 cuda-sanitizer-11-3 (11.3.111-1) ... 正在设置 libcusolver-11-3 (11.1.2.109-1) ... 正在设置 libcublas-11-3 (11.5.1.109-1) ... 正在设置 cuda-nsight-systems-11-3 (11.3.1-1) ... 正在设置 cuda-nvrtc-dev-11-3 (11.3.109-1) ... 正在设置 libcurand-dev-11-3 (10.2.4.109-1) ... 正在设置 default-jre-headless (2:1.11-72) ... 正在设置 libcublas-dev-11-3 (11.5.1.109-1) ... 正在设置 cuda-nsight-compute-11-3 (11.3.1-1) ... 正在设置 cuda-nvcc-11-3 (11.3.109-1) ... 正在设置 cuda-drivers-465 (465.19.01-1) ... 正在设置 libnpp-dev-11-3 (11.3.3.95-1) ... 正在设置 cuda-libraries-11-3 (11.3.1-1) ... 正在设置 cuda-gdb-11-3 (11.3.109-1) ... 正在设置 default-jre (2:1.11-72) ... 正在设置 cuda-compiler-11-3 (11.3.1-1) ... 正在设置 cuda-drivers (465.19.01-1) ... 正在设置 libcufft-dev-11-3 (10.4.2.109-1) ... 正在设置 cuda-nvvp-11-3 (11.3.111-1) ... 正在设置 libcusolver-dev-11-3 (11.1.2.109-1) ... 正在设置 cuda-runtime-11-3 (11.3.1-1) ... 正在设置 cuda-cupti-11-3 (11.3.111-1) ... 正在设置 cuda-nsight-11-3 (11.3.109-1) ... 正在设置 cuda-demo-suite-11-3 (11.3.58-1) ... 正在设置 cuda-cupti-dev-11-3 (11.3.111-1) ... 正在设置 cuda-libraries-dev-11-3 (11.3.1-1) ... 正在设置 cuda-visual-tools-11-3 (11.3.1-1) ... 正在设置 cuda-samples-11-3 (11.3.58-1) ... 正在设置 cuda-command-line-tools-11-3 (11.3.1-1) ... 正在设置 cuda-documentation-11-3 (11.3.111-1) ... 正在设置 cuda-tools-11-3 (11.3.1-1) ... 正在设置 cuda-toolkit-11-3 (11.3.1-1) ... Setting alternatives 正在设置 cuda-11-3 (11.3.1-1) ... 正在设置 cuda (11.3.1-1) ... 正在处理用于 libc-bin (2.33-0ubuntu5) 的触发器 ... 正在处理用于 man-db (2.9.4-2) 的触发器 ... 正在处理用于 mailcap (3.68ubuntu1) 的触发器 ... 正在处理用于 desktop-file-utils (0.26-1ubuntu1) 的触发器 ... 正在处理用于 hicolor-icon-theme (0.17-2) 的触发器 ... 正在处理用于 gnome-menus (3.36.0-1ubuntu1) 的触发器 ... ZSys is adding automatic system snapshot to GRUB menu 第六步，配置环境变量cby@cby-Inspiron-7577:~$ vim ~/.bashrc cby@cby-Inspiron-7577:~$ cat ~/.bashrc # ...略... export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.3/lib64 export PATH=$PATH:/usr/local/cuda-11.3/bin export CUDA_HOME=$CUDA_HOME:/usr/local/cuda-11.3 cby@cby-Inspiron-7577:~$ source ~/.bashrc第七步，下载安装CUDNNhttps://developer.nvidia.com/cudnn访问如向连接，进行注册英伟达开发者，注册完成后下载安装包第八步，下载完成后进入目录后进行安装刚刚下载的安装包cby@cby-Inspiron-7577:~/Downloads$ ls libcudnn8_8.2.0.53-1+cuda11.3_amd64.deb libcudnn8-dev_8.2.0.53-1+cuda11.3_amd64.deb libcudnn8-samples_8.2.0.53-1+cuda11.3_amd64.deb pycharm-community-2021.1.2.tar.gz cby@cby-Inspiron-7577:~/Downloads$ sudo apt install ./libcudnn8* 正在读取软件包列表... 完成 正在分析软件包的依赖关系树... 完成 正在读取状态信息... 完成 注意，选中 'libcudnn8' 而非 './libcudnn8_8.2.0.53-1+cuda11.3_amd64.deb' 注意，选中 'libcudnn8-dev' 而非 './libcudnn8-dev_8.2.0.53-1+cuda11.3_amd64.deb' 注意，选中 'libcudnn8-samples' 而非 './libcudnn8-samples_8.2.0.53-1+cuda11.3_amd64.deb' 下列软件包是自动安装的并且现在不需要了： libaccinj64-11.2 libcub-dev libcublas11 libcublaslt11 libcudart11.0 libcufft10 libcufftw10 libcuinj64-11.2 libcupti-dev libcupti-doc libcupti11.2 libcurand10 libcusolver11 libcusolvermg11 libcusparse11 libegl-dev libgl-dev libgl1-mesa-dev libgles-dev libgles1 libglvnd-dev libglx-dev libnppc11 libnppial11 libnppicc11 libnppidei11 libnppif11 libnppig11 libnppim11 libnppist11 libnppisu11 libnppitc11 libnpps11 libnvblas11 libnvjpeg11 libnvrtc11.2 libnvtoolsext1 libnvvm4 libopengl-dev libopengl0 libpthread-stubs0-dev libthrust-dev libvdpau-dev libx11-dev libxau-dev libxcb1-dev libxdmcp-dev node-html5shiv nsight-compute nsight-compute-target nsight-systems nsight-systems-target nvidia-cuda-gdb nvidia-cuda-toolkit-doc nvidia-opencl-dev nvidia-profiler nvidia-visual-profiler ocl-icd-opencl-dev opencl-c-headers opencl-clhpp-headers x11proto-dev xorg-sgml-doctools xtrans-dev 使用'sudo apt autoremove'来卸载它(它们)。 下列【新】软件包将被安装： libcudnn8 libcudnn8-dev libcudnn8-samples 升级了 0 个软件包，新安装了 3 个软件包，要卸载 0 个软件包，有 5 个软件包未被升级。 需要下载 0 B/823 MB 的归档。 解压缩后会消耗 2,899 MB 的额外空间。 获取:1 /home/cby/Downloads/libcudnn8_8.2.0.53-1+cuda11.3_amd64.deb libcudnn8 amd64 8.2.0.53-1+cuda11.3 [454 MB] 获取:2 /home/cby/Downloads/libcudnn8-dev_8.2.0.53-1+cuda11.3_amd64.deb libcudnn8-dev amd64 8.2.0.53-1+cuda11.3 [366 MB] 获取:3 /home/cby/Downloads/libcudnn8-samples_8.2.0.53-1+cuda11.3_amd64.deb libcudnn8-samples amd64 8.2.0.53-1+cuda11.3 [1,672 kB] Requesting to save current system state Successfully saved as "autozsys_mptxg3" 正在选中未选择的软件包 libcudnn8。 (正在读取数据库 ... 系统当前共安装有 216273 个文件和目录。) 准备解压 .../libcudnn8_8.2.0.53-1+cuda11.3_amd64.deb ... 正在解压 libcudnn8 (8.2.0.53-1+cuda11.3) ... 正在选中未选择的软件包 libcudnn8-dev。 准备解压 .../libcudnn8-dev_8.2.0.53-1+cuda11.3_amd64.deb ... 正在解压 libcudnn8-dev (8.2.0.53-1+cuda11.3) ... 正在选中未选择的软件包 libcudnn8-samples。 准备解压 .../libcudnn8-samples_8.2.0.53-1+cuda11.3_amd64.deb ... 正在解压 libcudnn8-samples (8.2.0.53-1+cuda11.3) ... 正在设置 libcudnn8 (8.2.0.53-1+cuda11.3) ... 正在设置 libcudnn8-dev (8.2.0.53-1+cuda11.3) ... update-alternatives: 使用 /usr/include/x86_64-linux-gnu/cudnn_v8.h 来在自动模 式中提供 /usr/include/cudnn.h (libcudnn) 正在设置 libcudnn8-samples (8.2.0.53-1+cuda11.3) ... 正在处理用于 libc-bin (2.33-0ubuntu5) 的触发器 ... ZSys is adding automatic system snapshot to GRUB menu N: 由于文件'/home/cby/Downloads/libcudnn8_8.2.0.53-1+cuda11.3_amd64.deb'无法被用户'_apt'访问，已脱离沙盒并提权为根用户来进行下载。- pkgAcquire::Run (13: 权限不够) cby@cby-Inspiron-7577:~/Downloads$ 第九步，进行验证cby@cby-Inspiron-7577:~/Downloads$ python Python 3.9.5 (default, May 11 2021, 08:20:37) [GCC 10.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import paddle >>> paddle.utils.run_check() Running verify PaddlePaddle program ... W0606 22:39:35.543371 63149 device_context.cc:404] Please NOTE: device: 0, GPU Compute Capability: 6.1, Driver API Version: 11.3, Runtime API Version: 10.2 W0606 22:39:35.572693 63149 device_context.cc:422] device: 0, cuDNN Version: 8.2. PaddlePaddle works well on 1 GPU. PaddlePaddle works well on 1 GPUs. PaddlePaddle is installed successfully! Let's start deep learning with PaddlePaddle now. >>> 第十步，运行情感训练模型，查看结果 至此，已完成安装，需要注意的是：在windows下安装及其困难，部分工具无法安装，导致无法正常运行AMD的显卡是无法使用GPU进行人工智能计算的特别注意IDE开发环境中的PYTHON和系统中的环境Linux运维交流社区Linux运维交流社区，互联网新闻以及技术交流。27篇原创内容公众号本文使用 文章同步助手 同步
-
Proxmox VE镜像分析与定制 Proxmox VE（Proxmox Virtual Environment，简称PVE）是一个开源的服务器虚拟化环境Linux发行版，基于Debian，使用给予Ubuntu的定制内核。相比于其他虚拟化平台，PVE具有的一个显著的特点就是无需master节点，安装完成后，无需特殊配置即可将多个节点组成集群。由于工程要求，PVE需要大规模部署在物理服务器上，所以定制镜像就显得很有必要。定制目标包括（1）修改initrd中init脚本的提示信息（2）删除GRUB界面多余选项，直接进入安装界面（3）添加预装软件（4）在安装过程中对软件进行个性化配置（5）修改PVE安装界面，在PVE安装界面中的所有输入框设置默认文本Proxmox VE镜像分析下载Proxmox VE 6.4版镜像后挂载，观察文件结构$ tree -L 2 . ├── boot │ ├── boot.cat │ ├── grub │ ├── initrd.img │ ├── linux26 │ └── memtest86+.bin ├── COPYING ├── COPYRIGHT ├── debian -> . ├── dists │ └── stretch ├── efi.img ├── EULA ├── mach_kernel ├── proxmox │ ├── country.dat │ ├── packages │ └── pve-base.cnt ├── pve-base.squashfs ├── pve-installer.squashfs ├── Release.txt └── System └── Library 9 directories, 14 files其中：grub文件夹：包含引导程序GRUB所用到的文件。 initrd.img：系统初始化所使用的镜像，里面包含一个最小化的系统，包含了/dev、/etc、/bin等很多基本的目录，还有关键的init程序，负责驱动的加载和文件系统的初始化。 linux26：Linux 2.6内核 efi.img：系统引导镜像，内含boot.efi、bootia32.efi、bootx64.efi。 proxmox文件夹：系统预安装包的存放目录 PVE的根系统默认安装包是在proxmox文件夹下的，只要不破坏其依赖关系，可以将需要预安装的包及其依赖放到这个文件夹下。 PVE预安装包时候使用的是循环读取proxmox/packages中的deb，然后使用的安装方法是先解压然后再配置，这样不会产生依赖关系而导致装不上deb的问题。 pve-base.squashfs：安装的根系统，也就是最终的系统 pve-installer.squashfs：安装时需要的系统Proxmox VE安装流程PVE安装流程主要分为以下4个步骤：（1）Boot Loader：由 BIOS 加载，用于将后续的 kernel 和 initrd 的装载到内存中。（PVE安装时使用的是UEFI模式的安装，但是又不是传统意义上的UEFI，它先是使用了BIOS加载kernel和initrd到内存，然后又跳到UEFI分区执行efi.img文件，调用proxinstall进入到系统安装界面，然后是挂载pve-base.squashfs进行系统安装）（2）kernel：为 initrd 运行提供基础的运行环境，对应boot目录下的linux26文件（3）initrd：检测并加载各种驱动程序，并执行init，对应boot目录下的initrd.img文件（4）rootfs：根文件系统，用户的各种操作都是基于这个被最后加载的文件系统，这里对应了pve-base.squashfsProxmox VE镜像定制ISO解压与压缩在原先使用ISO Master作为解压缩ISO的工具中，产生的ISO文件可以直接作为cdrom启动，但刻录进USB设备后缺失MBR等重要部分所以无法启动，因此改用命令行进行解压缩。（1）ISO提取首先挂载镜像文件。$ mount -o loop Desktop/proxmox-ve_6.4-1.iso cby/挂载点目录中的文件是只读的，所以需要同步到工作目录下。$ cd cby $ sudo rsync -av /home/cby/cby/ /home/cby/同步之后就即可修改ISO内的文件。$ sudo umount /home/cby/cby $ ll total 386672 dr-xr-xr-x 10 root root 4096 Apr 27 04:26 ./ dr-xr-xr-x 23 root root 4096 May 19 18:56 ../ dr-xr-xr-x 3 root root 4096 Apr 27 04:26 boot/ -r--r--r-- 1 root root 89 Apr 27 04:26 .cd-info -r--r--r-- 1 root root 32386 Apr 27 04:26 COPYING -r--r--r-- 1 root root 955 Apr 27 04:26 COPYRIGHT lrwxrwxrwx 1 root root 1 Apr 27 04:26 debian -> ./ dr-xr-xr-x 3 root root 4096 Apr 27 04:26 dists/ -r--r--r-- 1 root root 2949120 Apr 27 04:26 efi.img -r--r--r-- 1 root root 4470 Apr 27 04:26 EULA -r--r--r-- 1 root root 0 Apr 27 04:26 mach_kernel dr-xr-xr-x 3 root root 4096 Apr 27 04:26 proxmox/ dr-xr-xr-x 2 root root 4096 Apr 27 04:26 .pve-base/ -r--r--r-- 1 root root 101306368 Apr 27 04:26 pve-base.squashfs -r--r--r-- 1 root root 37 Apr 27 04:26 .pve-cd-id.txt dr-xr-xr-x 2 root root 4096 Apr 27 04:26 .pve-installer/ dr-xr-xr-x 2 root root 4096 Apr 27 04:26 .pve-installer-mp/ -r--r--r-- 1 root root 291586048 Apr 27 04:26 pve-installer.squashfs -r--r--r-- 1 root root 15792 Apr 27 04:26 Release.txt dr-xr-xr-x 3 root root 4096 Apr 27 04:26 System/ dr-xr-xr-x 2 root root 4096 Apr 27 04:26 .workdir/（2）ISO压缩使用原镜像的MBR（前512字节）作为定制镜像的MBR$ sudo dd if=/home/cby/proxmox-ve_6.4-1.iso bs=512 count=1 of=proxmox.mbr 1+0 records in 1+0 records out 512 bytes copied, 0.000134541 s, 3.8 MB/s打包ISO镜像$ sudo xorriso -as mkisofs -o proxmox-ve_6.4-1.iso -r -V 'inspur' --grub2-mbr proxmox.mbr --protective-msdos-label -efi-boot-part --efi-boot-image -c '/boot/boot.cat' -b '/boot/grub/i386-pc/eltorito.img' -no-emul-boot -boot-load-size 4 -boot-info-table --grub2-boot-info -eltorito-alt-boot -e '/efi.img' -no-emul-boot . xorriso 1.5.2 : RockRidge filesystem manipulator, libburnia project. Drive current: -outdev 'stdio:proxmox-ve_6.4-1.iso' Media current: stdio file, overwriteable Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 80.6g free xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules Added to ISO image: directory '/'='/home/cby/chenby' xorriso : UPDATE : 1421 files added in 1 seconds xorriso : UPDATE : 1421 files added in 1 seconds xorriso : NOTE : Copying to System Area: 512 bytes from file '/home/cby/chenby/proxmox.mbr' xorriso : UPDATE : 1.00% done xorriso : UPDATE : 42.39% done xorriso : UPDATE : 86.68% done ISO image produced: 453265 sectors Written to medium : 453265 sectors at LBA 0 Writing to 'stdio:proxmox-ve_6.4-1.iso' completed successfully.修改initrd initrd.img位于原始镜像的boot目录下，修改initrd的目的是修改安装过程中的输出文本，是一个比较特殊的部分，要从initrd引入的目的讲起。 initrd 的英文含义是 boot loader initialized RAM disk，就是由 boot loader 初始化的内存盘。initrd的最初的目的是为了把kernel的启动分成两个阶段：在kernel中保留最少最基本的启动代码，然后把对各种各样硬件设备的支持以模块的方式放在initrd中，这样就在启动过程中可以从initrd所mount的根文件系统中装载需要的模块。这样的一个好处就是在保持kernel不变的情况下，通过修改initrd中的内容就可以灵活的支持不同的硬件。在启动完成的最后阶段，根文件系统可以重新mount到其他设备上。也就是说由于initrd会在内存虚拟一个文件系统，然后可以根据不同的硬件加载不同的驱动，而不需要重新编译整个核心。所以，大部分的发行版都会通过这种方式对驱动进行加载。initrd引入之后Linux的引导会变成如下流程。（1）boot loader 把内核以及 initrd 文件加载到内存的特定位置。（2）内核判断initrd的文件格式，如果是cpio格式。（3）将initrd的内容释放到rootfs中。（4）执行initrd中的/init文件，执行到这一点，内核的工作全部结束，完全交给/init文件处理。 根据核心版本的不同，initrd文件有两种格式：image和cpio。**kernel 2.4只使用image格式，而kernel 2.6可同时支持两种格式。**它们不单格式不一样，而且运作的机制和流程也完全不同，甚至制作方法也不一样。pve的kernel版本是2.6，所以在此只讲cpio格式的initrd制作。initrd解压、修改与压缩流程：（1）解压proxmox-ve_6.4-1.iso，boot目录下的initrd.img就是gz格式的压缩文件（2）将initrd.img备份后重命名为initrd.org.img，并解压缩$ sudo gzip -d -S ".img" ./initrd.org.img执行file后查看格式$ sudo file initrd.org initrd.org: ASCII cpio archive (SVR4 with no CRC)（3）创建initrd.tmp目录以存放后续还原出来的文件，然后执行cpio命令将文件还原$ sudo mkdir initrd.tmp $ cd initrd.tmp $ sudo cpio -id < ../initrd.org 241820 blocks $ ls bin dev devfs etc init lib lib64 mnt proc sbin sys tmp usr去除GRUB界面 pve在安装时使用了GRUB2，所以想要去除掉GRUB界面需要找到原始镜像中boot/grub/grub.cfg文件，添加set timeout=0，就可以直接进入默认选项Install Proxmox VE模式。如果有需要我们也可以修改默认选项来实现直接进入其他模式的功能。$ vim grub.cfg $ cat grub.cfg insmod gzio insmod iso9660 insmod png loadfont /boot/grub/unicode.pf2 set gfxmode=640x400 # set kernel parameter vga=791 # do not specify color depth here (else efifb can fall back to 800x600) set gfxpayload=1024x768 #set gfxmode=auto #set gfxpayload=keep set timeout=0 insmod all_video insmod gfxterm set theme=/boot/grub/pvetheme/theme.txt ...定制预装软件 Proxmox VE所有的预装软件都以deb包的形式存放在镜像的proxmox/packages下，并将在安装pve的过程中统一安装这些软件包，全部安装完成之后再进行配置，这样可以避免依赖关系出现问题。 所以定制预装软件只需要在proxmox/packages目录下放入需要的deb包，pve将会自动安装并进行默认配置。配置预装程序 pve在配置软件是只会按照默认的配置，如果希望将软件配置成我们想要的形式，则只需要修改pve-installer.squashfs里的usr/bin/proxinstall文件。pve-installer.squashfs是pve安装时由initrd加载的系统，安装过程中proxinstall负责所有业务逻辑，其中配置软件部分的代码如下：# needed for postfix postinst in case no other NIC is active syscmd("chroot $targetdir ifup lo"); my $cmd = "chroot $targetdir dpkg $dpkg_opts --force-confold --configure -a"; $count = 0; run_command ($cmd, sub { my $line = shift; if ($line =~ m/Setting up\s+(\S+)/) { update_progress ((++$count)/$pkg_count, 0.75, 0.95, "configuring $1"); } });...# set apt mirror if (my $mirror = $cmap->{country}->{$country}->{mirror}) { my $fn = "$targetdir/etc/apt/sources.list"; syscmd ("sed -i 's/ftp\\.debian\\.org/$mirror/' '$fn'"); } # create extended_states for apt (avoid cron job warning if that # file does not exist) write_config ('', "$targetdir/var/lib/apt/extended_states"); # allow ssh root login syscmd(['sed', '-i', 's/^#\?PermitRootLogin.*/PermitRootLogin yes/', "$targetdir/etc/ssh/sshd_config"]); 可以看出pve也是对部分程序进行了个性化的配置，所以对配置文件的编辑的代码只需要仿照后者，使用syscmd函数，将修改的命令作为参数，写在前者之后即可。定制安装界面 在pve-installer.squashfs里的usr/bin/proxinstall文件中，有create_main_window函数，这个函数的功能是创建图形界面窗口里的各种组件，通过分析这个函数我们可以得到安装UI的结构。 顶部的image、中心的htmlview窗口以及下方的cmdbox构成了我们所看到的外观。在此只修改image和htmlview。定制安装界面 在pve-installer.squashfs里的usr/bin/proxinstall文件中，有create_main_window函数，这个函数的功能是创建图形界面窗口里的各种组件，通过分析这个函数我们可以得到安装UI的结构。 顶部的image、中心的htmlview窗口以及下方的cmdbox构成了我们所看到的外观。在此只修改image和htmlview。 顶部的image是在1785行加载pve-installer下var/lib/pve-installer/pve-banner.png来完成的，所以只需要用一个尺寸同样为1024X164的图像替代。 中心的htmlview是通过在每个create_*函数中调用display_html函数来加载，加载的html文件都位于var/lib/pve-installer/html文件夹下，对应的只需要修改每个html文件就可以实现外观上的替换。 另外由于窗口运行环境openbox的语言设置默认不是中文，所以使用中文字符展示会出现乱码，因此可以由html加载含中文的图片，以此来展示中文。 默认输入信息的修改就只需要在proxinstall中找到对应的输入框，修改预设文本。使用命令unsquashfs将unsquashfs格式的镜像将其解压$ sudo unsquashfs pve-installer.squashfs Parallel unsquashfs: Using 16 processors 20078 inodes (25826 blocks) to write [===========================================================\] 25826/25826 100% created 19247 files created 2620 directories created 819 symlinks created 0 devices created 0 fifos $ ll total 3256748 dr-xr-xr-x 12 root root 4096 May 19 19:55 ./ dr-xr-xr-x 24 root root 4096 May 19 19:29 ../ -rw-r--r-- 1 root root 348389376 May 19 19:42 pve-installer.squashfs drwxr-xr-x 17 root root 4096 Apr 27 04:23 squashfs-root/ ... 解压完成后会出现pve-installer.squashfs镜像盘的squashfs-root/ 文件夹，进入该文件夹即可看到安装时的引导系统$ ll total 68 drwxr-xr-x 11 root root 4096 Mar 19 03:08 ./ dr-xr-xr-x 12 root root 4096 May 19 19:55 ../ drwxr-xr-x 2 root root 4096 Mar 19 03:08 boot/ drwxr-xr-x 2 root root 4096 Apr 27 04:25 cdrom/ drwxr-xr-x 2 root root 4096 Apr 27 04:25 devfs/ drwxr-xr-x 40 root root 4096 Apr 27 04:25 etc/ drwxr-xr-x 2 root root 4096 Apr 27 04:25 rpool/ -rwxr-xr-x 1 root root 376 Apr 26 09:53 .spice-vdagent.sh* drwxr-xr-x 2 root root 4096 Apr 27 04:25 target/ drwxr-xr-x 2 root root 4096 Apr 27 04:25 tmp/ drwxr-xr-x 8 root root 4096 Mar 19 03:08 usr/ drwxr-xr-x 5 root root 4096 Apr 26 09:53 var/ -rw-r--r-- 1 root root 87 Apr 26 09:53 .Xdefaults -rw-r--r-- 1 root root 140 Apr 26 09:53 .xinitrc 把准备好的图片替换$ sudo cp /home/cby/Desktop/pve-banner.png . 使用命令解压完成后会出现pve-base.squashfs镜像盘的squashfs-root/ 文件夹$ sudo unsquashfs pve-base.squashfs Parallel unsquashfs: Using 16 processors 12892 inodes (14248 blocks) to write [===========================================================-] 14248/14248 100% created 10856 files created 1385 directories created 2024 symlinks created 9 devices created 0 fifos 进入该文件夹即可看到安装后的系统根目录$ ll total 68 drwxr-xr-x 17 root root 4096 Apr 27 04:23 ./ dr-xr-xr-x 12 root root 4096 May 19 19:55 ../ lrwxrwxrwx 1 root root 7 Apr 27 04:22 bin -> usr/bin/ drwxr-xr-x 3 root root 4096 Apr 27 04:23 boot/ drwxr-xr-x 5 root root 4096 Apr 27 04:23 dev/ drwxr-xr-x 57 root root 4096 Apr 27 04:23 etc/ drwxr-xr-x 2 root root 4096 Mar 19 16:44 home/ lrwxrwxrwx 1 root root 7 Apr 27 04:22 lib -> usr/lib/ lrwxrwxrwx 1 root root 9 Apr 27 04:22 lib32 -> usr/lib32/ lrwxrwxrwx 1 root root 9 Apr 27 04:22 lib64 -> usr/lib64/ lrwxrwxrwx 1 root root 10 Apr 27 04:22 libx32 -> usr/libx32/ drwxr-xr-x 2 root root 4096 Apr 27 04:22 media/ drwxr-xr-x 2 root root 4096 Apr 27 04:22 mnt/ drwxr-xr-x 2 root root 4096 Apr 27 04:22 opt/ drwxr-xr-x 2 root root 4096 Mar 19 16:44 proc/ drwx------ 2 root root 4096 Apr 27 04:23 root/ drwxr-xr-x 5 root root 4096 Apr 27 04:23 run/ lrwxrwxrwx 1 root root 8 Apr 27 04:22 sbin -> usr/sbin/ drwxr-xr-x 2 root root 4096 Apr 27 04:22 srv/ drwxr-xr-x 2 root root 4096 Mar 19 16:44 sys/ drwxrwxrwt 2 root root 4096 Apr 27 04:23 tmp/ drwxr-xr-x 13 root root 4096 Apr 27 04:22 usr/ drwxr-xr-x 11 root root 4096 Apr 27 04:22 var/ 修改完需要定制的文件系统后，使用如下命进行打包$ sudo mksquashfs squashfs-root/ pve-installer.squashfs Parallel mksquashfs: Using 16 processors Creating 4.0 filesystem on pve-installer.squashfs-, block size 131072. [===========================================================\] 25008/25008 100% Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 131072 compressed data, compressed metadata, compressed fragments, compressed xattrs, compressed ids duplicates are removed Filesystem size 340223.99 Kbytes (332.25 Mbytes) 33.70% of uncompressed filesystem size (1009698.26 Kbytes) Inode table size 225637 bytes (220.35 Kbytes) 29.06% of uncompressed inode table size (776542 bytes) Directory table size 235667 bytes (230.14 Kbytes) 38.69% of uncompressed directory table size (609117 bytes) Xattr table size 673 bytes (0.66 Kbytes) 7.40% of uncompressed xattr table size (9096 bytes) Number of duplicate files found 853 Number of inodes 22686 Number of files 19247 Number of fragments 1982 Number of symbolic links 819 Number of device nodes 0 Number of fifo nodes 0 Number of socket nodes 0 Number of directories 2620 Number of ids (unique uids + gids) 9 Number of uids 3 root (0) man (6) syslog (104) Number of gids 7 root (0) shadow (42) bluetooth (112) utmp (43) staff (50) man (12) tss (111) 使用该名进行制作ISO镜像盘$ sudo xorriso -as mkisofs -o proxmox-ve_6.4-1.iso -r -V 'inspur' --grub2-mbr proxmox.mbr --protective-msdos-label -efi-boot-part --efi-boot-image -c '/boot/boot.cat' -b '/boot/grub/i386-pc/eltorito.img' -no-emul-boot -boot-load-size 4 -boot-info-table --grub2-boot-info -eltorito-alt-boot -e '/efi.img' -no-emul-boot . xorriso 1.5.2 : RockRidge filesystem manipulator, libburnia project. Drive current: -outdev 'stdio:proxmox-ve_6.4-1.iso' Media current: stdio file, overwriteable Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 78.0g free xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules Added to ISO image: directory '/'='/home/cby/chenby' xorriso : UPDATE : 32892 files added in 1 seconds xorriso : UPDATE : 32892 files added in 1 seconds xorriso : NOTE : Copying to System Area: 512 bytes from file '/home/cby/chenby/proxmox.mbr' libisofs: NOTE : Automatically adjusted MBR geometry to 1021/155/32 xorriso : UPDATE : 0.66% done xorriso : UPDATE : 8.03% done xorriso : UPDATE : 19.34% done xorriso : UPDATE : 34.06% done, estimate finish Wed May 19 19:46:25 2021 xorriso : UPDATE : 48.84% done, estimate finish Wed May 19 19:46:24 2021 xorriso : UPDATE : 61.72% done, estimate finish Wed May 19 19:46:24 2021 xorriso : UPDATE : 73.41% done, estimate finish Wed May 19 19:46:25 2021 xorriso : UPDATE : 82.19% done, estimate finish Wed May 19 19:46:25 2021 xorriso : UPDATE : 92.15% done xorriso : UPDATE : 97.28% done ISO image produced: 1264917 sectors Written to medium : 1264917 sectors at LBA 0 Writing to 'stdio:proxmox-ve_6.4-1.iso' completed successfully. 使用新创建的ISO镜像盘启动后，已出现修改过后的背景图，以此类推，通过修改根目录文件，可以实现完全定制化的pve系统。 若修改安装后的管理后台的页面，在proxmox/packages目录下找到pve-manager的deb安装包。$ ls | grep manager pve-ha-manager_3.1-1_amd64.deb pve-manager_6.4-4_amd64.deb$ mkdir extract，在当前目录下新建文件夹，用于存放解压后的内容 $ mkdir extract/DEBIAN，新建DEBIAN目录用于存放包的控制信息 $ sudo dpkg -X ./pve-manager_6.4-4_amd64.deb extract/，将要修改的deb包解压到extract目录下，可以看到： 在其解压出来的包内修改所需的代码后，导入debian包的控制信息，可以使用命令再次打包成deb包。$ sudo dpkg-deb -e ./pve-manager_6.4-4_amd64.deb extract/DEBIAN/ $ ls extract/DEBIAN/ conffiles control md5sums postinst postrm preinst prerm triggers $ sudo dpkg-deb -b ./extract 123.deb dpkg-deb: building package 'pve-manager' in '123.deb'. $ ll 123.deb -rw-r--r-- 1 root root 2042764 May 19 21:54 123.deb 查看deb包的详细信息。$ dpkg-deb -I 123.deb new Debian package, version 2.0. size 2042764 bytes: control archive=16976 bytes. 320 bytes, 10 lines conffiles 1532 bytes, 15 lines control 56553 bytes, 574 lines md5sums 3246 bytes, 101 lines * postinst #!/bin/sh 1645 bytes, 44 lines * postrm #!/bin/sh 192 bytes, 5 lines * preinst #!/bin/sh 626 bytes, 24 lines * prerm #!/bin/sh 33 bytes, 1 lines triggers Package: pve-manager Version: 6.4-4 Architecture: amd64 Maintainer: Proxmox Support Team <support@proxmox.com> Installed-Size: 9876 Depends: apt-transport-https | apt (>= 1.5~), ca-certificates, cstream, dtach, fonts-font-awesome, gdisk, hdparm, ifenslave (>= 2.6) | ifupdown2 (>= 2.0.1-1+pve8), libapt-pkg-perl, libc6 (>= 2.14), libcrypt-ssleay-perl, libfile-readbackwards-perl, libfilesys-df-perl, libjs-extjs (>= 6.0.1), libjson-perl, liblwp-protocol-https-perl, libnet-dns-perl, libproxmox-acme-perl, libpve-access-control (>= 6.0-6), libpve-cluster-api-perl, libpve-cluster-perl (>= 6.1-6), libpve-common-perl (>= 6.2-2), libpve-guest-common-perl (>= 3.1-5), libpve-http-server-perl (>= 3.2-1), libpve-storage-perl (>= 6.3-6), librados2-perl, libtemplate-perl, libterm-readline-gnu-perl, liburi-perl, libuuid-perl, libwww-perl (>= 6.04-1), logrotate, lsb-base, lzop, zstd, novnc-pve, pciutils, perl (>= 5.10.0-19), postfix | mail-transport-agent, proxmox-mini-journalreader, proxmox-widget-toolkit (>= 2.5-2), pve-cluster (>= 6.0-4), pve-container (>= 2.0-21), pve-docs, pve-firewall, pve-ha-manager, pve-i18n (>= 1.0-3), pve-xtermjs (>= 0.1-1), qemu-server (>= 6.2-17), rsync, spiceterm, systemd, vncterm, wget Suggests: libpve-network-perl (>= 0.5-1) Conflicts: vlan, vzdump Breaks: libpve-network-perl (<< 0.5-1) Replaces: vlan, vzdump Provides: vlan, vzdump Section: admin Priority: optional Description: Proxmox Virtual Environment Management Tools This package contains the Proxmox Virtual Environment management tools. 将打好的deb包放回到原目录后，在进行ISO的打包，这样在安装系统后的镜像即可是定制化的页面。 本文使用 文章同步助手 同步
-
MINIO搭建单机以及集群 MINIO简介 Minio是Apache License v2.0下发布的对象存储服务器。它与Amazon S3云存储服务兼容。它最适合存储非结构化数据，如照片，视频，日志文件，备份和容器/VM映像。对象的大小可以从几KB到最大5TB。Minio服务器足够轻，可以与应用程序堆栈捆绑在一起，类似于NodeJS，Redis和MySQL。 https://docs.minio.io/一、单机版搭建<section style="text-indent: 0em;">操作系统</section><section style="text-indent: 0em;">搭建方式</section><section style="text-indent: 0em;">Linux</section><section style="text-indent: 0em;">docker</section><section style="text-indent: 0em;">Linux</section><section style="text-indent: 0em;">宿主机</section> 1. docker模式搭建 1.1安装docker curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun [root@localhost ~]# systemctl start docker #启动docker [root@localhost ~]# docker ps -a #查看一下命令是否可以执行 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES [root@localhost ~]#1.2使用docker安装MINIO[root@localhost ~]# docker search minio NAME DESCRIPTION STARS OFFICIAL AUTOMATED minio/minio Kubernetes Native, High Performance Object S… 445 [OK] minio/mc Minio Client (mc) provides a modern alternat… 22 [OK] bitnami/minio Bitnami MinIO Docker Image 6 pixelchrome/minio-arm This Dockerfile installs Minio on your ARM-P… 5 jessestuart/minio Minio server — supports arm (arm32v6, arm32v… 5 minio/console A graphical user interface for MinIO server 4 webhippie/minio Docker images for Minio 3 [OK] opennms/minion Application container runs Minion by OpenNMS… 3 [OK] bitnami/minio-client Bitnami MinIO Client Docker Image 3 rook/minio Minio is a high performance distributed obje… 2 rancher/minio-minio 1 zenithar/minio-server Minio.io Server in Alpine Linux docker 1 [OK] teamwork/minio Minio for Teamwork 1 azinchen/minio Minio server Docker image. Always up-to-date… 1 minio/mint Collection of tests to detect overall correc… 0 [OK] tobilg/minio-dcos minio on DC/OS 0 [OK] topdockercat/minio-unraid Minio is an Amazon S3 compatible object stor… 0 [OK] keikoproj/minion-manager https://github.com/orkaproj/minion-manager 0 joepll/minio-exporter Prometheus exporter for Minio server 0 opsmx11/minio Minio for Openshift 0 [OK] leviy/minio Minio image for development and testing of (… 0 [OK] minio/k8s-operator Minio Operator for k8s https://kubernetes.io/ 0 rwsdockercf/minio-resource 0 nerc/minio Minio container for use in the datalab proje… 0 [OK] kazesberger/miniomc-postgres this image is used to create postgres dumps … 0 [root@localhost ~]# [root@localhost ~]# docker pull minio/minio Using default tag: latest latest: Pulling from minio/minio 8f403cb21126: Pull complete 65c0f2178ac8: Pull complete 6e32ce08526e: Pull complete 932fb72de569: Pull complete 71bfd33c61af: Pull complete 588b2addab38: Pull complete 093f7de724c9: Pull complete Digest: sha256:fe69dcaed404faa1a36953513bf2fe2d5427071fa612487295eddb2b18cfe918 Status: Downloaded newer image for minio/minio:latest docker.io/minio/minio:latest [root@localhost ~]# [root@localhost ~]# docker run -p 9000:9000 --name minio1 \ > -e "MINIO_ACCESS_KEY=admin" \ > -e "MINIO_SECRET_KEY=12345678" \ > -v /Users/xiyou/my_minio/data:/data \ > -v /Users/xiyou/my_minio/config:/root/.minio \ > minio/minio server /data Endpoint: http://172.17.0.2:9000 http://127.0.0.1:9000 Browser Access: http://172.17.0.2:9000 http://127.0.0.1:9000 Object API (Amazon S3 compatible): Go: https://docs.min.io/docs/golang-client-quickstart-guide Java: https://docs.min.io/docs/java-client-quickstart-guide Python: https://docs.min.io/docs/python-client-quickstart-guide JavaScript: https://docs.min.io/docs/javascript-client-quickstart-guide .NET: https://docs.min.io/docs/dotnet-client-quickstart-guide IAM initialization complete 1.3使用该命令将其放置在后台启动[root@localhost ~]# docker run -d -p 9000:9000 --name minio1 \ > -e "MINIO_ACCESS_KEY=admin" \ > -e "MINIO_SECRET_KEY=12345678" \ > -v /my_minio/data:/data \ > -v /my_minio/config:/root/.minio \ > minio/minio server /data b6fca0d91b4bc5ef5f5b4b2a77a6f4761fc18e1d4b08f88519304813b52586d7 [root@localhost ~]# 1.4宿主机安装[root@localhost ~]# wget https://dl.min.io/server/minio/release/linux-amd64/minio --2021-05-12 23:14:06-- https://dl.min.io/server/minio/release/linux-amd64/minio Resolving dl.min.io (dl.min.io)... 178.128.69.202 Connecting to dl.min.io (dl.min.io)|178.128.69.202|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 58748928 (56M) [application/octet-stream] Saving to: ‘minio’ minio 100%[============================================================================>] 56.03M 7.24MB/s in 9.5s 2021-05-12 23:14:17 (5.89 MB/s) - ‘minio’ saved [58748928/58748928] [root@localhost ~]# chmod +x minio [root@localhost ~]# MINIO_ACCESS_KEY=minio MINIO_SECRET_KEY=minio123 ./minio server /cby Endpoint: http://192.168.100.139:9000 http://127.0.0.1:9000 RootUser: minio RootPass: minio123 Browser Access: http://192.168.100.139:9000 http://127.0.0.1:9000 Command-line Access: https://docs.min.io/docs/minio-client-quickstart-guide $ mc alias set myminio http://192.168.100.139:9000 minio minio123 Object API (Amazon S3 compatible): Go: https://docs.min.io/docs/golang-client-quickstart-guide Java: https://docs.min.io/docs/java-client-quickstart-guide Python: https://docs.min.io/docs/python-client-quickstart-guide JavaScript: https://docs.min.io/docs/javascript-client-quickstart-guide .NET: https://docs.min.io/docs/dotnet-client-quickstart-guide IAM initialization complete 二、集群版搭建2. 集群搭建2.1 集群服务器配置及启动启动一个分布式Minio实例，你只需要把硬盘位置做为参数传给minio server命令即可，然后，你需要在所有其它节点运行同样的命令。*注意 分布式Minio里所有的节点需要有同样的access秘钥和secret秘钥，这样这些节点才能建立联接。为了实现这个，你需要在执行minio server命令之前，先将access秘钥和secret秘钥export成环境变量。同时分布式Minio使用的磁盘里必须是干净的，里面没有数据。 分布式Minio里的节点时间差不能超过3秒，你可以使用NTP 来保证时间一致。在Windows下运行分布式Minio处于实验阶段，请悠着点使用。参考：https://docs.min.io/cn/distributed-minio-quickstart-guide.html名称IPnode192.168.100.138node192.168.100.139node192.168.100.140node192.168.100.141 2.2每台上面搭建 [root@localhost software]# mkdir -p /chenby/software [root@localhost software]# cd /chenby/software [root@localhost software]# wget https://dl.min.io/server/minio/release/linux-amd64/minio --2021-05-13 00:06:25-- https://dl.min.io/server/minio/release/linux-amd64/minio Resolving dl.min.io (dl.min.io)... 178.128.69.202 Connecting to dl.min.io (dl.min.io)|178.128.69.202|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 58748928 (56M) [application/octet-stream] Saving to: ‘minio’ minio 100%[============================================================================>] 56.03M 1.95MB/s in 21s 2021-05-13 00:06:48 (2.63 MB/s) - ‘minio’ saved [58748928/58748928] [root@localhost software]# chmod +x minio [root@localhost software]# MINIO_ACCESS_KEY=minio MINIO_SECRET_KEY=minio123 ./minio server http://192.168.100.138/chenby/software/cby http://192.168.100.139/chenby/software/cby http://192.168.100.140/chenby/software/cby http://192.168.100.141/chenby/software/cby Waiting for all MinIO sub-systems to be initialized.. lock acquired All MinIO sub-systems initialized successfully Status: 4 Online, 0 Offline. Endpoint: http://192.168.100.138:9000 http://127.0.0.1:9000 RootUser: minio RootPass: minio123 Browser Access: http://192.168.100.138:9000 http://127.0.0.1:9000 Command-line Access: https://docs.min.io/docs/minio-client-quickstart-guide $ mc alias set myminio http://192.168.100.138:9000 minio minio123 Object API (Amazon S3 compatible): Go: https://docs.min.io/docs/golang-client-quickstart-guide Java: https://docs.min.io/docs/java-client-quickstart-guide Python: https://docs.min.io/docs/python-client-quickstart-guide JavaScript: https://docs.min.io/docs/javascript-client-quickstart-guide .NET: https://docs.min.io/docs/dotnet-client-quickstart-guide Waiting for all MinIO IAM sub-system to be initialized.. lock acquired IAM initialization complete 2.3 访问测试[root@localhost ~]# curl -I http://192.168.100.138:9000/minio/login HTTP/1.1 403 Forbidden Accept-Ranges: bytes Content-Length: 256 Content-Type: application/xml Server: MinIO Vary: Origin Date: Wed, 12 May 2021 16:09:19 GMT [root@localhost ~]# curl -I http://192.168.100.139:9000/minio/login HTTP/1.1 403 Forbidden Accept-Ranges: bytes Content-Length: 256 Content-Type: application/xml Server: MinIO Vary: Origin Date: Wed, 12 May 2021 16:09:25 GMT [root@localhost ~]# curl -I http://192.168.100.140:9000/minio/login HTTP/1.1 403 Forbidden Accept-Ranges: bytes Content-Length: 256 Content-Type: application/xml Server: MinIO Vary: Origin Date: Wed, 12 May 2021 16:09:32 GMT [root@localhost ~]# curl -I http://192.168.100.141:9000/minio/login HTTP/1.1 403 Forbidden Accept-Ranges: bytes Content-Length: 256 Content-Type: application/xml Server: MinIO Vary: Origin Date: Wed, 12 May 2021 16:09:36 GMT 本文使用 文章同步助手 同步