tech:pb_lvm
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédente | |||
| tech:pb_lvm [2025/10/01 18:19] – Jean-Baptiste | tech:pb_lvm [2026/06/07 19:12] (Version actuelle) – modification externe 127.0.0.1 | ||
|---|---|---|---|
| Ligne 1: | Ligne 1: | ||
| + | < | ||
| + | {{tag> | ||
| + | |||
| + | # Pb LVM | ||
| + | |||
| + | ## Erreur Device /dev/sda excluded by a filter. | ||
| + | |||
| + | ~~~ | ||
| + | Device /dev/sda excluded by a filter. | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | ### Solutions | ||
| + | |||
| + | Solutions | ||
| + | ~~~bash | ||
| + | dd if=/ | ||
| + | ~~~ | ||
| + | |||
| + | Ou (à tester) | ||
| + | ~~~bash | ||
| + | sgdisk --zap-all -- /dev/sda | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | |||
| + | ## Erreur /dev/sdb: open failed: No medium found | ||
| + | |||
| + | |||
| + | ~~~ | ||
| + | # vgs | ||
| + | /dev/sdb: open failed: No medium found | ||
| + | VG #PV #LV #SN Attr | ||
| + | vg_data | ||
| + | vgos 1 | ||
| + | |||
| + | # lsblk | ||
| + | NAME | ||
| + | sda 8:0 0 931.5G | ||
| + | └─sda1 | ||
| + | └─vg_data-data 254:5 0 | ||
| + | nvme0n1 | ||
| + | ├─nvme0n1p1 | ||
| + | ├─nvme0n1p2 | ||
| + | └─nvme0n1p3 | ||
| + | ├─vgos-root | ||
| + | ├─vgos-swap | ||
| + | ├─vgos-var | ||
| + | └─vgos-home | ||
| + | ~~~ | ||
| + | |||
| + | Dans notre cas nous avons un /dev/sdb fantome | ||
| + | ~~~ | ||
| + | # fdisk /dev/sdb | ||
| + | |||
| + | Welcome to fdisk (util-linux 2.33.1). | ||
| + | Changes will remain in memory only, until you decide to write them. | ||
| + | Be careful before using the write command. | ||
| + | |||
| + | fdisk: cannot open /dev/sdb: No medium found | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | ### Solution | ||
| + | |||
| + | Solution temporaire | ||
| + | ~~~ | ||
| + | # mv /dev/sdb . | ||
| + | # vgs | ||
| + | VG #PV #LV #SN Attr | ||
| + | vg_data | ||
| + | vgos 1 | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | ## Erreur Locking type -1 initialisation failed | ||
| + | |||
| + | Voir : | ||
| + | * https:// | ||
| + | * http:// | ||
| + | |||
| + | ### Solution | ||
| + | |||
| + | |||
| + | * Vérifier si /var n'est pas monté en lecture seul (voir `locking_dir` dans `lvm.conf`) | ||
| + | * Utiliser l' | ||
| + | |||
| + | Exemple 1 | ||
| + | ~~~bash | ||
| + | vgchange --ignorelockingfailure -P -a y | ||
| + | ~~~ | ||
| + | |||
| + | Exemple 2 | ||
| + | ~~~bash | ||
| + | pvs --config ' | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | ## Err Device mismatch detected | ||
| + | |||
| + | Source : https:// | ||
| + | |||
| + | Cause | ||
| + | |||
| + | If the virtual machine where a File Recovery Enabler for Linux is installed is based on the same VM template or image as the guest virtual machines or instances that the FREL is browsing, then live browse of files and folders on the guest VMs might fail as a result of UUID conflicts with physical volumes (PVs) on the FREL. | ||
| + | |||
| + | #### Resolution | ||
| + | |||
| + | To resolve this issue, change the UUIDs of the PVs on the FREL: | ||
| + | |||
| + | List all the physical volumes: | ||
| + | ~~~ | ||
| + | pvs -o --noheadings | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | Change the UUID for each PV listed in step 1. | ||
| + | ~~~bash | ||
| + | pvchange -f --uuid pv_name --config " | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | List all the volume groups: | ||
| + | ~~~bash | ||
| + | vgs -o vg_name, | ||
| + | ~~~ | ||
| + | |||
| + | Run the following commands to change the UUIDs and rename each of the volume groups listed in step 3 and activate the changed configuration: | ||
| + | ~~~bash | ||
| + | vgchange --uuid vg_name --config " | ||
| + | ~~~ | ||
| + | |||
| + | ~~~bash | ||
| + | vgrename old_vg_name new_vg_name | ||
| + | ~~~ | ||
| + | |||
| + | ~~~bash | ||
| + | vgchange -ay new_vg_name | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | |||
| + | ### Autres RO FS | ||
| + | |||
| + | ~~~bash | ||
| + | touch /plop | ||
| + | ~~~ | ||
| + | |||
| + | ~~~ | ||
| + | touch: ne peut faire un touch sur `/ | ||
| + | ~~~ | ||
| + | |||
| + | ~~~bash | ||
| + | blockdev --setrw /dev/sda | ||
| + | mount -o remount,rw / | ||
| + | ~~~ | ||
| + | |||
| + | ~~~ | ||
| + | mount: périphérique de type bloc/ | ||
| + | ~~~ | ||
| + | |||
| + | ~~~bash | ||
| + | pvdisplay | ||
| + | ~~~ | ||
| + | |||
| + | ~~~ | ||
| + | Locking type -1 initialisation failed. | ||
| + | ~~~ | ||
| + | |||
| + | Exemple de commande en lien, à tester | ||
| + | ~~~bash | ||
| + | vgchange --ignorelockingfailure -P -a y | ||
| + | vgchange -a y VolGroup-1 | ||
| + | blockdev --rereadpt /dev/sda | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | |||
| + | A voir aussi | ||
| + | |||
| + | `lvm.conf` | ||
| + | ~~~ini | ||
| + | / | ||
| + | locking_type = 1 | ||
| + | locking_dir = "/ | ||
| + | ~~~ | ||
| + | |||
| + | ~~~bash | ||
| + | lvchange -p rw | ||
| + | |||
| + | lvm vgchange -ayl --ignorelockingfailure | ||
| + | lvm vgmknodes --ignorelockingfailure | ||
| + | if touch -c / >& /dev/null | ||
| + | ~~~ | ||
| + | |||
| + | |||
| + | ## Pb /dev/mapper missing LV | ||
| + | |||
| + | |||
| + | ### Solution | ||
| + | |||
| + | ~~~bash | ||
| + | vgscan --mknodes | ||
| + | ~~~ | ||
| + | |||
