Sample Header Ad - 728x90

How to resolve e2fsck Superblock problem?

4 votes
3 answers
74977 views
I have a problem like this question https://unix.stackexchange.com/questions/404019/how-disk-became-suddenly-write-protected-in-spite-configuration-is-read-write And I used these commands to resolve that ` umount /dev/sdb1 e2fsck /dev/sdb1 mount /dev/sdb1 ` but ~# e2fsck /dev/sdb1 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/sdb1 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/sdb1 contains a ufs file system additional commands to help you to know additional details ~#nano /etc/fstab UUID=###951671### /DATA ufs defaults 1 2 mkdir /DATA mount /DATA ~# ls -lat | grep DATA drwxr-xr-x 5 root root 1024 May 26 11:37 DATA ~# df -h | grep sd /dev/sda1 276G 8.7G 254G 4% / **/dev/sdb1 197G 102G 80G 57% /DATA** ~# lsblk -f | grep sd sda ├─sda1 ext4 ###-c0fb-42ce-9c78-### 253.2G 3% / ├─sda2 └─sda5 swap ###-27b4-485b-98b3-### [SWAP] sdb └─sdb1 ufs ###951671### 79.3G 52% /DATA ~:/DATA# ls ls: reading directory '.': Input/output error ~:/DATA# mount -o rw,remount /dev/sdb1 mount: /DATA: mount point not mounted or bad option. ~# umount /DATA ~# e2fsck /DATA e2fsck 1.44.5 (15-Dec-2018) e2fsck: Is a directory while trying to open /DATA 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 ~# mount /DATA mount: /DATA: WARNING: device write-protected, mounted read-only. At all, I would like to access to this hard /dev/sdb1 in /DATA folder How can I resolve this problem?
Asked by Red Science (341 rep)
Oct 14, 2019, 12:31 PM
Last activity: Apr 24, 2020, 03:54 AM