IDK why my system seems to hang when I set the test_fs option.
tune2fs -E test_fs /dev/sda3 'exactly what I type' and reboot.
Do I have a dirty system?
e2fsck -yvf on an umounted partition seems to work. This system btw, was
replaced by clonezilla. I needed to resize partitions and simply
reformatted the filesystem. Everything seems to work great just this
little hangup.
I also tried removing the journal and replacing it, same thing.
tune2fs -O has_journal /dev/sda3 and e2fsck moves the journal into the
journal inode, works fine;
tune2fs -O ^has_journal /dev/sda3 and e2fsck works. But same booting
results when the test_fs flag is set.
I am grasping at straws there in adding and removing the journal. No
change there though, doesn't seem to hurt anything.
Maybe there's an error that e2fsck isn't reporting and I should ask it
to dig deeper? IDK
Does anyone have any ideas? Superblock problems?
B
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
