errado tipo fs, má opção, bad superblock ao tentar montar o volume restaurado

Question

Eu restaurei um grupo LVM de uma configuração recuperada hoje (background # 1 , # 2 ). Imagens completas foram feitas dos discos antes de emitir o seguinte comando.

[root@ursula diskissues]# vgcfgrestore -f ursula2012_restore.cfg vg_ursula2012
  Restored volume group vg_ursula2012

Então

vgchange -ay

Em seguida, adicionei uma linha a /etc/fstab , mas tento obter mount -a :

[root@ursula diskissues]# mount -a
mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg_ursula2012-lv_www,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

de dmesg:

EXT4-fs (dm-6): VFS: Can't find ext4 filesystem

Aqui está o fstab:

/dev/mapper/vg_ursula-lv_root /                       ext4    defaults        1 1
UUID=1e1f9db2-8231-407c-bc0e-18ae5066231e /boot                   ext4    defaults        1 2
/dev/mapper/vg_ursula-lv_home /home                   ext4    defaults        1 2
/dev/mapper/vg_ursula-LogVol05 /tmp                    ext4    defaults        1 2
/dev/mapper/vg_ursula-LogVol04 /usr                    ext4    defaults        1 2
/dev/mapper/vg_ursula-LogVol03 /var                    ext4    defaults        1 2
/dev/mapper/vg_ursula-lv_swap swap                    swap    defaults        0 0
/dev/mapper/vg_ursula2012-lv_www /www                    ext4    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0

pvs:

[root@ursula diskissues]# pvs
  PV         VG            Fmt  Attr PSize   PFree 
  /dev/sda5  vg_ursula     lvm2 a--  276.34g     0 
  /dev/sdb1  vg_ursula2012 lvm2 a--    1.80t     0 
  /dev/sdc1  vg_ursula2012 lvm2 a--  948.67g 18.83g

lv

[root@ursula diskissues]# lvs
  LV       VG            Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  lv_root  vg_ursula2012 -wi-a-----  50.00g                                                    
  lv_www   vg_ursula2012 -wi-a-----   2.66t                                                    
  LogVol03 vg_ursula     -wi-ao----  48.83g                                                    
  LogVol04 vg_ursula     -wi-ao----  48.83g                                                    
  LogVol05 vg_ursula     -wi-ao----  29.30g                                                    
  lv_home  vg_ursula     -wi-ao----   9.77g                                                    
  lv_root  vg_ursula     -wi-ao---- 111.74g                                                    
  lv_swap  vg_ursula     -wi-ao----  27.89g                                                    

vgscan

[root@ursula diskissues]# vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "vg_ursula2012" using metadata type lvm2
  Found volume group "vg_ursula" using metadata type lvm2

[root@ursula diskissues]# lvscan
  ACTIVE            '/dev/vg_ursula2012/lv_www' [2.66 TiB] inherit
  ACTIVE            '/dev/vg_ursula2012/lv_root' [50.00 GiB] inherit
  ACTIVE            '/dev/vg_ursula/LogVol05' [29.30 GiB] inherit
  ACTIVE            '/dev/vg_ursula/LogVol04' [48.83 GiB] inherit
  ACTIVE            '/dev/vg_ursula/LogVol03' [48.83 GiB] inherit
  ACTIVE            '/dev/vg_ursula/lv_root' [111.74 GiB] inherit
  ACTIVE            '/dev/vg_ursula/lv_home' [9.77 GiB] inherit
  ACTIVE            '/dev/vg_ursula/lv_swap' [27.89 GiB] inherit

    

Answer 1

(movido de comentários para tornar a resposta mais pesquisável)

Permitir que os erros do disco sejam corrigidos com e2fsck

e2fsck -y /dev/vg_ursula2012/lv_root
e2fsck -y /dev/vg_ursula2012/lv_www