![]() The superblock could not be read or does not describe a valid ext2/ext3/ext4įilesystem. dev/sda1: 96 files, 21764/98304 sudo fsck -v /dev/sda2Įxt2fs_open2: Bad magic number in super-blockįsck.ext2: Superblock invalid, trying backup blocks.įsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 Root directory start at cluster 2 (arbitrary size)ĭata area starts at byte 4194304 (sector 8192) Differences: (offset:original/backup)įirst FAT starts at byte 3406848 (sector 6654) There are differences between boot sector and its backup. ![]() Fs was not properly unmounted and some data may be corrupt. I/O size (minimum/optimal): 512 bytes / 512 sudo fsck -v /dev/sda1Ĭhecking we can access the last sector of the filesystemĠx41: Dirty bit is set. Sector size (logical/physical): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes The output from fsck, for what it is worth, is sudo fdisk -lĭisk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Running dmesg I saw the messages “BTRFS csum failed” and “BTRFS info (device sda5) is forced read only”. ![]() With help, I have traced it down to what seems to be a problem with a BTRFS partition. I started a thread about a system journal file being read-only, which turned out to be because openSuSE loaded read-only.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |