我最近在我的家庭服务器中添加了 SSD 并重新加载了操作系统。但是,当我尝试访问基于 dm-crypt 的旧磁盘时,出现以下错误:
读取所有物理卷。这可能需要一段时间...
警告:重复的 VG 名称 server01:现有 bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc(在此处创建)优先于 RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87
警告:重复VG 名称 server01:现有 bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc(在此处创建)优先于 RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87
使用元数据类型 lvm2 找到卷组“server01”找到
卷使用元数据类型 lvm2 的组“server01”
问题出在我的卷组上。我在新旧硬盘上都设置为server01。如何重命名旧的 LVM2?如何访问我的旧硬盘?
dm-crypt 是 Linux 内核 v2.6+ 及更高版本中的透明磁盘加密子系统。它可以加密整个磁盘、可移动介质、分区、软件 RAID 卷、逻辑卷和文件。让我们看看如何使用命令行选项修复 Linux 警告:重复的 VG 名称 server1 LVM2 错误。
教程详情 | |
---|---|
难度级别 | 先进的 |
根权限 | 是的 |
要求 | Linux终端 |
类别 | 系统管理 |
操作系统兼容性 | Alma • Alpine • Arch • Debian • Fedora • Linux • Mint • openSUSE • Pop!_OS • RHEL • Rocky • Stream • SUSE • Ubuntu |
美东时间。阅读时间 | 4分钟 |
Linux 警告:重复 VG 名称 server1 LVM2 错误和解决方案
使用cryptsetup 命令打开 device,输入:
# cryptsetup luksOpen /dev/sdXY your-name-here
您需要运行 vgdisplay 命令才能获取有关 LVM2 卷组的准确信息。以 root 用户身份键入以下命令:
# vgdisplay
示例输出:
警告:重复的 VG 名称 server01:现有 bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc(在此处创建)优先于 RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87 警告:重复的 VG 名称 server01:现有 bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc(在此处创建)优先于 RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87 警告:重复的 VG 名称 server01:现有 RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87(在此处创建)优先于 bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc --- 卷组 --- VG名称服务器01 系统ID 格式化lvm2 元数据区域 1 元数据序列号 4 VG 访问读/写 VG 状态可调整大小 最大等级0 当前 LV 2 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 465.52 GiB PE Size 4.00 MiB Total PE 119173 Alloc PE / Size 119173 / 465.52 GiB Free PE / Size 0 / 0 VG UUID RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87 WARNING: Duplicate VG name server01: Existing bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc (created here) takes precedence over RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87 --- Volume group --- VG Name server01 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 3 Open LV 3 Max PV 0 Cur PV 1 Act PV 1 VG Size 476.70 GiB PE Size 4.00 MiB Total PE 122034 Alloc PE / Size 122034 / 476.70 GiB Free PE / Size 0 / 0 VG UUID bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc
Note down VG UUID for the old LVM2 volume and use the following comamnd to rename the same. The syntax is:
# vgrename VG-UUID-HERE new-name-here
In this example, rename volume with UUID RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87 to oldharddisk, type:
# vgrename RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87 oldharddisk
Sample outputs:
WARNING: Duplicate VG name server01: Existing bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc (created here) takes precedence over RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87
WARNING: Duplicate VG name server01: Existing bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc (created here) takes precedence over RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87
WARNING: Duplicate VG name server01: Existing RIKiar-w3MG-Gzh5-VFWq-bkRT-9IFc-ia8k87 (created here) takes precedence over bc7YA8-eEXt-1aA1-OHTr-zJkA-ucd0-DsbRTc
Volume group "server01" successfully renamed to "oldharddisk"
You need to scan all disks for volume groups and rebuild caches:
# vgscan --mknodes
Sample outputs:
Reading all physical volumes. This may take a while... Found volume group "oldharddisk" using metadata type lvm2 Found volume group "server01" using metadata type lvm2
Next, activate all known volume groups in the system, type:
# vgchange -ay
Sample outputs:
2 logical volume(s) in volume group "oldharddisk" now active 3 logical volume(s) in volume group "server01" now active
To see a mapping name use the following command:
# ls -l /dev/mapper/oldharddisk-*
Sample outputs:
lrwxrwxrwx 1 root root 7 May 5 16:56 /dev/mapper/oldharddisk-root -> ../dm-5 lrwxrwxrwx 1 root root 7 May 5 16:56 /dev/mapper/oldharddisk-swap_1 -> ../dm-6
To mount /dev/mapper/oldharddisk-root, type the mkdir command and then use the cd command:
# mkdir -p /mnt/oldharddisk
# mount /dev/mapper/oldharddisk-root /mnt/oldharddisk
# df -H
Now you can copy or restore data from old hard disk mounted at /mnt/oldharddisk:
# cd /mnt/oldharddisk
Try the cp command or rsync command to copy data from old HDD to a new location. For example:
# rsync -avrP home/* /home/
Summing up
这个问题看起来很令人担忧,因为磁盘上的数据很有价值。然而,通过 CLI 选项,人们可以快速修复此类警告并访问数据。请使用 --help 选项或 man 命令阅读以下手册页:
像这样的问题很好地提醒您为所有数据保留经过验证的备份。
$ man cryptsetup
$ man vgdisplay
$ man vgrename
$ man vgscan
$ man vgchange