[SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

surrealistic · 2018-07-28 16:35:18

Hi there!

I've tried to reinstall Arch for a couple of times last months because I have an issue with my partitions. That issue is that once I starts Windows, that "breaks" my Arch partition.

If I try to start my Arch partition after having used Windows 10 partition I get this message:

fsck.ext4: Superblock checksum does not match superblock while trying to open /dev/sdb2
/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 <device>
or
    e2fsck -b 32768 <device>

ERROR: fsck failed on '/dev/sdb2'
[          1.948707] EXT4-fs (sdb2): VFS: Found ext4 filesystem with invalid superblock checksum.
mount: /new_root: cannot mount; probably corrupted filesystem on /dev/sdb2.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off

I can fix it temporarily with

sudo fsck.ext4 -v /dev/sdb2

until I start Windows 10 partition Arch partition what makes it fail again with the same message.

Do you know why this is happening or how can I fix it definitively?

Thanks!!

Last edited by surrealistic (2018-07-31 09:42:48)

seth · 2018-07-28 21:19:13

https://wiki.archlinux.org/index.php/Du … t_Start-Up ?

surrealistic · 2018-07-29 11:12:32

I've tried to disable Windows 10 fast startup and I already have ntfs-3g installed but it's still the same, if I start Windows 10 once I'm back to Arch partition it's with the invalid superblock checksum again.

seth · 2018-07-29 12:17:09

If it's not an inconsistent state throug cross-hibernation: what business does windows have actvely writing to a partition containing a filesystem it doesn't support?
Do you run any backup / restore programs on windows (maybe vendor specific tools)?
What's the output of "file -s /dev/sdb2" when this happens as well as the general partition layout, "fdisk -l /dev/sda; fdisk -l /dev/sdb"?

surrealistic · 2018-07-29 13:18:44

I've checked if Windows is running any kind of backup software or I have any default backup configuration instead but I haven't found any backup/restoring programs.

Here is the output of "file -s /dev/sdb2":

/dev/sdb2: Linux rev 1.0 ext4 filesystem data, UUID=231375b5-346f-4e8b-aac4-5c96e93cfaae, volume name "ArchLinux" (extents) (64bit) (large files) (huge files)

And the output of "fdisk -l /dev/sda; fdisk -l /dev/sdb":

Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 78EF742C-49D2-441D-901C-1CCFF12514A2

Device         Start       End   Sectors   Size Type
/dev/sda1       2048    534527    532480   260M EFI System
/dev/sda2     534528    567295     32768    16M Microsoft reserved
/dev/sda3     567296 248304845 247737550 118.1G Microsoft basic data
/dev/sda4  248305664 250068991   1763328   861M Windows recovery environment
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 36124C5A-7CB4-4AA0-8DE3-F9FD9F55EAE1

Device          Start        End    Sectors   Size Type
/dev/sdb1        2048 1339123711 1339121664 638.6G Microsoft basic data
/dev/sdb2  1339123712 1953525134  614401423   293G Linux filesystem

seth · 2018-07-29 13:25:57

Is the "file" output from when there was an invalid superblock?
Did you repartition sdb using gparted or so? How big does windows believe sdb1 to be, resp. what's the opinion of "ntfsinfo -m /dev/sdb1"?

surrealistic · 2018-07-29 23:57:24

seth wrote:

Is the "file" output from when there was an invalid superblock?

Yes, I ran "file" command before fix the partition.

seth wrote:

Did you repartition sdb using gparted or so?

I think so, I don't remember how I did because I did it like 7 months ago, but I'm pretty sure I used gparted for that. I had a previous installation with Arch Linux and I didn't have this issue, though.

"ntfsinfo -m /dev/sdb1" output:

Volume Information 
	Name of device: /dev/sdb1
	Device state: 11
	Volume Name: DATA
	Volume State: 91
	Volume Flags: 0x0000
	Volume Version: 3.1
	Sector Size: 512
	Cluster Size: 4096
	Index Block Size: 4096
	Volume Size in Clusters: 167390207
MFT Information 
	MFT Record Size: 1024
	MFT Zone Multiplier: 0
	MFT Data Position: 24
	MFT Zone Start: 786432
	MFT Zone End: 21710207
	MFT Zone Position: 786432
	Current Position in First Data Zone: 21710207
	Current Position in Second Data Zone: 0
	Allocated clusters 50752 (0.0%)
	LCN of Data Attribute for FILE_MFT: 786432
	FILE_MFTMirr Size: 4
	LCN of Data Attribute for File_MFTMirr: 2
	Size of Attribute Definition Table: 2560
	Number of Attached Extent Inodes: 0
FILE_Bitmap Information 
	FILE_Bitmap MFT Record Number: 6
	State of FILE_Bitmap Inode: 80
	Length of Attribute List: 0
	Number of Attached Extent Inodes: 0
FILE_Bitmap Data Attribute Information
	Decompressed Runlist: not done yet
	Base Inode: 6
	Attribute Types: not done yet
	Attribute Name Length: 0
	Attribute State: 3
	Attribute Allocated Size: 20926464
	Attribute Data Size: 20923776
	Attribute Initialized Size: 20923776
	Attribute Compressed Size: 0
	Compression Block Size: 0
	Compression Block Size Bits: 0
	Compression Block Clusters: 0
	Free Clusters: 54373473 (32.5%)

seth · 2018-07-30 05:32:38

Nope.
Asked google and the first dozen answers say that merely installing (no need to mount or access) https://sourceforge.net/projects/ext2fsd/ will corrupt newer ext4 superblocks. Rings a bell?

surrealistic · 2018-07-30 09:03:15

Thank you seth! I just checked and it seems that ext2fsd is corrupting ext4 superblocks and it was fixed in ext2fsd 0.69 version, I just checked my Windows 10 partition and I installed ext2fsd 0.68 in January. I'll try to uninstall it and install the latest version of ext2fsd or just uninstall it.

surrealistic · 2018-07-31 09:19:00

I've tried to uninstall ext2fsd 0.68 and Arch partition hasn't been corrupted anymore.
So that issue was caused because of ext2fsd 0.68 version, it's supposed that ext2fsd 0.69 version has that issue fixed.

Thank you so much for your help seth!

Arch Linux

#1 2018-07-28 16:35:18

[SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#2 2018-07-28 21:19:13

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#3 2018-07-29 11:12:32

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#4 2018-07-29 12:17:09

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#5 2018-07-29 13:18:44

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#6 2018-07-29 13:25:57

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#7 2018-07-29 23:57:24

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#8 2018-07-30 05:32:38

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#9 2018-07-30 09:03:15

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

#10 2018-07-31 09:19:00

Re: [SOLVED]Superblock checksum does not describe a valid ext4 filesystem.

Board footer