I was running OpenSuse Leap 42.1 with btrfs and LVM (Logical Volume Management). Last time I've checked smartd log, I noticed there were 30 sector pending reallocation and 1 unrecoverable bad sector on hard drive. I think my hard drive got some sector corrupted and now btrfs fails some checksum and forces mount readonly. The device is successfully mounted readonly. OpenSuse dmesg reported: BTRFS: dm-1 checksum verify failed on 437944320 wanted 39F45669 found 8BF8C752 leval 0 (more 2 times) BTRFS: error (device dm-1) in btrfs_drop_snapshot:???: error=-5 IO failure BTRFS: info (device dm-1): forced readonly Now I'm on System Rescue CD and that is not reported. I've written down those log line on paper, so there may be some typo. Seemingly there is no journalctl installed on this system to check OpenSuse logs again. All the following logs are on System Rescue CD. mount -o ro,recovery /dev/mapper/vg_pupu-lv_opensuse_root /mnt/opensuse https://bpaste.net/show/263e5f7ae9d4 After mounting and umounting several times with and without "-o ro,recovery" https://bpaste.net/show/43eb64decb63 btrfs check --readonly /dev/mapper/vg_pupu-lv_opensuse_root https://bpaste.net/show/7ecf422c73a2 Would it be apropriate to run any of "btrfs check --repair /device" or "btrfs check --init-csum-tree /device" to be able to mount readwrite again? smartctl --all /dev/disk/by-id/ata-SAMSUNG_HD154UI_S1Y6JDWSC01351 https://bpaste.net/show/a6c132618974 btrfs check manpage: https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-check btrfsck page: https://btrfs.wiki.kernel.org/index.php/Btrfsck -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
