I've been trying to backup the root partition of my F33 installation. To that end, I'm running a C7 live CD. C7 won't mount the partition. tune2fs likes it, but [root@localhost mnt]# mount /dev/sda5 /mnt/a5 mount: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so. [root@localhost mnt]# dmesg | tail -n 15 [ 123.848185] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts [ 123.856904] SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts [ 146.541654] Bluetooth: Core ver 2.16 [ 146.541737] NET: Registered protocol family 31 [ 146.541739] Bluetooth: HCI device and connection manager initialized [ 146.541750] Bluetooth: HCI socket layer initialized [ 146.541753] Bluetooth: L2CAP socket layer initialized [ 146.541760] Bluetooth: SCO socket layer initialized [ 146.548524] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 146.548529] Bluetooth: BNEP filters: protocol multicast [ 146.548540] Bluetooth: BNEP socket layer initialized [ 300.961319] JBD2: Unrecognised features on journal [ 300.961325] EXT4-fs (sda5): error loading journal ====== WHY? [ 361.930877] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 361.931025] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready [root@localhost mnt]# mount -t ext2 /dev/sda5 /mnt/a5 mount: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
No idea why the journal should be a problem. I used gnome to do the reboot. I can boot back into F33.
How do I figure out what is going on? What can I do about it?