Bonjour,
Suite a un upgrade VPS almalinux
[RESCUE] root@-----------:~ $ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 2.5G 0 disk
└─sda1 8:1 0 2.5G 0 part /
sdb 8:16 0 40G 0 disk
├─sdb1 8:17 0 1M 0 part
└─sdb2 8:18 0 40G 0 part
umount /dev/sdb2
umount: /dev/sdb2: not mounted.
Je poursuis la procédure du guide : https://docs.ovh.com/fr/vps/repartitionner-vps-suite-upgrade/#comment-reparer-les-erreurs-bad-magic-number-in-superblock
e2fsck -yf /dev/sdb2
e2fsck 1.44.5 (15-Dec-2018)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks…
e2fsck: Bad magic number in super-block while trying to open /dev/sdb2
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
/dev/sdb2 contains a xfs file system
Je tente une réparation :
dumpe2fs /dev/sdb2 | grep superblock
dumpe2fs 1.44.5 (15-Dec-2018)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb2
Couldn't find valid filesystem superblock.
Que faire ensuite ?
Merci de votre aide
Il faudrait vérifier la sauvegarde et tenter :
> xfs_repair /dev/sdb2
(Je ne connais pas xfs)