How to fix Bad magic number in super-block - fstab It is helpful to use fdisk -l on target disk to compare (with start, end and number of sectors) and select correctly the good (unproblematic) partitions to avoid deleting them in the process
Resize2fs bad magic number in super-block while trying to open: How to fix Resize2fs bad magic number in super-block while trying to open: learn how to fix this common error with step-by-step instructions and screenshots This error occurs when the file system metadata is corrupted To fix it, you can use the fsck command to check and repair the file system
Xen lvm resize2fs: Bad magic number in super-block You can do the fdisk, e2fsck and resize2fs all on the host system You just need to pass the dev vm-disks-testes to fdisk, and use dev cm--disks--testes--home1 for the other commands
Bad magic number in super-block error - Super User Re-create your dev sda2 using its original start and end sector values Be sure these are exactly the same as they were before Check that the re-created dev sda2 is accessible Back up your important data from dev sda2 Re-evaluate whether you really need to move the start of the partition
resize2fs Bad magic number in super-block while trying open This post will help you to fix the error "resize2fs Bad magic number in super-block while trying open" If you are interested in learning, Request you to go through the below recommended tutorial