Outils pour utilisateurs

Outils du site


blog

Pb LVM

Erreur Device /dev/sda excluded by a filter.

Device /dev/sda excluded by a filter.
Solutions

Solutions

dd if=/dev/zero of=/dev/sda count=1 bs=512

Ou (à tester)

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   VSize    VFree
  vg_data   1   1   0 wz--n- <931.51g 930.55g
  vgos      1   4   0 wz--n- <237.52g  79.82g

# lsblk
NAME             MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                8:0    0 931.5G  0 disk
└─sda1             8:1    0 931.5G  0 part
  └─vg_data-data 254:5    0   976M  0 lvm       
nvme0n1          259:0    0 238.5G  0 disk          
├─nvme0n1p1      259:1    0   488M  0 part /boot
├─nvme0n1p2      259:2    0   488M  0 part /boot/efi
└─nvme0n1p3      259:3    0 237.5G  0 part       
  ├─vgos-root    254:0    0  46.6G  0 lvm  /   
  ├─vgos-swap    254:1    0  15.3G  0 lvm  [SWAP]
  ├─vgos-var     254:2    0  55.9G  0 lvm  /var
  └─vgos-home    254:3    0    40G  0 lvm  /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   VSize    VFree
  vg_data   1   1   0 wz--n- <931.51g 930.55g
  vgos      1   4   0 wz--n- <237.52g  79.82g

Erreur Locking type -1 initialisation failed

Solution
  • Vérifier si /var n'est pas monté en lecture seul (voir locking_dir dans lvm.conf)
  • Utiliser l'option --ignorelockingfailure

Exemple 1

vgchange --ignorelockingfailure -P -a y

Exemple 2

pvs --config 'global { locking_dir = "/tmp" } 

Err Device mismatch detected

Source : https://documentation.commvault.com/commvault/v11_sp16/article?p=31713.htm

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.

pvchange -f --uuid pv_name --config "global {activation=0}"

List all the volume groups:

vgs -o vg_name,vg_uuid,pv_name --noheadings

Run the following commands to change the UUIDs and rename each of the volume groups listed in step 3 and activate the changed configuration:

vgchange --uuid vg_name --config "global {activation=0}"
vgrename old_vg_name new_vg_name
vgchange -ay new_vg_name
Autres RO FS
touch /plop
touch: ne peut faire un touch sur `/plop': Système de fichiers accessible en lecture seulement
blockdev --setrw /dev/sda
mount -o remount,rw /
mount: périphérique de type bloc/dev/VolGroup00/LogVol00 est protégé en écriture, on le monte en lecture seulement
pvdisplay
  Locking type -1 initialisation failed.

Exemple de commande en lien, à tester

vgchange --ignorelockingfailure -P -a y
vgchange -a y VolGroup-1
blockdev --rereadpt /dev/sda

A voir aussi

lvm.conf

/etc/lvm/lvm.conf
locking_type = 1
locking_dir = "/var/lock/lvm"
lvchange -p rw
 
lvm vgchange -ayl --ignorelockingfailure
lvm vgmknodes --ignorelockingfailure
if touch -c / >& /dev/null

Pb /dev/mapper missing LV

Solution
vgscan --mknodes
2025/03/24 15:06

Pb LibVirt Failed to start network default Unable to create bridge virbr0 Le fichier existe

Pb

virsh # net-start default
error: Failed to start network default
error: Unable to create bridge virbr0: Le fichier existe

Solution

ifconfig virbr0 down
brctl delbr virbr0
virsh net-start default
2025/03/24 15:06

Pb LibVirt DNSMasq DNS port 53 (TCP/UDP)

$ sudo lsof -i UDP:53
COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dnsmasq 3461 nobody    6u  IPv4  27341      0t0  UDP poste1.local:domain 
$ ps -p 3461 -f
UID        PID  PPID  C STIME TTY          TIME CMD
nobody    3461     1  0 11:00 ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper

/var/lib/libvirt/dnsmasq/default.conf

##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
##    virsh net-edit default
## or other application using the libvirt API.
##
## dnsmasq conf file created by libvirt
strict-order
pid-file=/var/run/libvirt/network/default.pid
except-interface=lo
bind-dynamic
interface=virbr0
dhcp-range=192.168.122.2,192.168.122.254
dhcp-no-override
dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases
dhcp-lease-max=253
dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
virsh -c qemu:///system net-edit default
2025/03/24 15:06

Pb LIBATA NCQ SSD TRIM

Voir :

Voir aussi :

Kernel parameter

libata.force=noncq
libata.force=noncq,3.0Gbps
libata.noacpi
# cat /sys/block/sda/queue/scheduler
noop deadline [cfq]

Source : https://www.systutorials.com/241496/whats-wrong-with-the-messages-like-unrecovdata-10b8b-badcrc-and-failed-command-read-fpdma-queued-on-linux/

# ls -l /sys/class/block/ | grep ata4
lrwxrwxrwx 1 root root 0 May  5 15:04 sdd -> ../../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd
lrwxrwxrwx 1 root root 0 May  5 15:04 sdd1 -> ../../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd/sdd1

Pb

/var/log/kern.log

2018-08-22T12:21:26.568 pc01 err kernel:[149221.594110] ata1.00: exception Emask 0x10 SAct 0x7fe00fff SErr 0x800100 action 0x6 frozen
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594154] ata1.00: irq_stat 0x08000000, interface fatal error
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594182] ata1: SError: { UnrecovData LinkSeq }
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594206] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594232] ata1.00: cmd 61/08:00:60:10:ee/00:00:0b:00:00/40 tag 0 ncq dma 4096 out
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594232]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594297] ata1.00: status: { DRDY }
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594313] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594339] ata1.00: cmd 61/08:08:08:20:ee/00:00:0b:00:00/40 tag 1 ncq dma 4096 out
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594339]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594404] ata1.00: status: { DRDY }
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594420] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594446] ata1.00: cmd 61/08:10:58:10:2a/00:00:0d:00:00/40 tag 2 ncq dma 4096 out
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594446]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594511] ata1.00: status: { DRDY }

/var/log/kern.log

2018-08-22T12:21:26.608 pc01 err kernel:[149221.638355] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.612 pc01 err kernel:[149221.639183] ata1.00: cmd 61/08:e8:80:10:ea/00:00:0b:00:00/40 tag 29 ncq dma 4096 out
2018-08-22T12:21:26.612 pc01 err kernel:[149221.639183]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.612 pc01 err kernel:[149221.640861] ata1.00: status: { DRDY }
2018-08-22T12:21:26.612 pc01 err kernel:[149221.641699] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.612 pc01 err kernel:[149221.642567] ata1.00: cmd 61/08:f0:10:11:eb/00:00:0b:00:00/40 tag 30 ncq dma 4096 out
2018-08-22T12:21:26.612 pc01 err kernel:[149221.642567]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.616 pc01 err kernel:[149221.644228] ata1.00: status: { DRDY }
2018-08-22T12:21:26.616 pc01 info kernel:[149221.645070] ata1: hard resetting link
2018-08-22T12:21:26.932 pc01 info kernel:[149221.959364] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2018-08-22T12:21:26.932 pc01 info kernel:[149221.960960] ata1.00: configured for UDMA/133
2018-08-22T12:21:26.932 pc01 info kernel:[149221.961024] ata1: EH complete
2025/03/24 15:06

Pb lang qwerty boot cryptsetup

Voir

Cryptsetup me demande la passphrase au boot, mais rien ne marche.

Je jette un œil sur une image d'un clavier yankee, youpi !

Après le boot, toujours pareille,

J'aurais pu aussi tenter de booter sur un ancien noyau.

loadkeys fr ne fonctionne pas. La commande loadkeys n'est pas présente

Je test

Source :

apt-get install console-data
dpkg-reconfigure console-data
dpkg-reconfigure keyboard-configuration
systemctl restart keyboard-setup
update-initramfs -u

/etc/initramfs-tools/initramfs.conf

KEYMAP=y

En ce qui me concerne ça venait du paquet console-setup ou kdb que j'avais désinstallé

apt-get install console-setup
loadkeys fr
update-initramfs -u
2025/03/24 15:06
blog.txt · Dernière modification : de 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki