CoreOS and ChromeOS implement intentional superblock corruption that shows up as a number of symptoms:
dmesg showing: sd 8:0:0:0: [sde] Write Protect is off
fsck showing: fsck.ext4: Bad magic number in super-block while trying to open chromeos_15117.112.0_scarlet_recovery_stable-channel_mp-v7.bin
mount showing: mount -o offset=$(( 352256 * 512 )) chromeos_15117.112.0_scarlet_recovery_stable-channel_mp-v7.bin scarlet/ mount: scarlet: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.
read only mount success.
losetup --offset $(( 352256 * 512 )) /dev/loop0 chromeos_15117.112.0_scarlet_recovery_stable-channel_mp-v7.bin; dumpe2fs /dev/loop0 | grep -i features showing Filesystem features: ext_attr resize_inode dir_index filetype sparse_super large_file FEATURE_R24 FEATURE_R25 FEATURE_R26 FEATURE_R27 FEATURE_R28 FEATURE_R29 FEATURE_R30 FEATURE_R31
to correct the problem you can repair using a backup superblock (if this gets out, they'