On Sat, Oct 19, 2019 at 5:30 AM George R Goffe via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
I have a 2TB HDD with a possibly major problem. I have cleared the data from it and have tried to run "mke2fs -t ext4 -j /dev/sdc1" but after 24 hours it had just finished the 0xaa phase and started reading when the drive seemingly dropped ready and was re-assigned as a new device to /dev/sdf. Argh. I did get an ended message with an ending block number. I'd like to restart at that point in time and continue the media check. I don't see anything in the mke2fs man page though.
Has anyone seen or heard of a way to do this?
Why did it take that long? Even on large drives mke2fs (or mkfs, mkfs.ext4) should take seconds to maybe a minute, not 24 hours. I think that's your primary problem. The whole drive isn't written to when creating any modern filesystem.
Also, journaling should be on by default for ext3/4 formats otherwise there's no real benefit over ext2.
Thanks,
Richard
_______________________________________________ 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
