The Linux Cafe is for Linux gurus, novices and the curious alike! And it entails far more than you might think. Operating systems such as Chrome OS, Android, WearOS, Tizen and many others. In fact, unless you're specifically running a Windows-based machine, chances are you're running Linux in some form or fashion. From your computer to your tablet to your smartphone and right down to your favorite wearables, chances are they have the Linux kernel at their core. So come, join us, and see the world of Linux through new eyes!
515 messages in 298 discussions
Latest Oct-13 by MEDDLY
46 messages in 32 discussions
Latest 6:15 AM by The Chief (BowWave)
219 messages in 134 discussions
Latest Nov-26 by 1776 (MRCROSSROADS)
213 messages in 122 discussions
Latest Nov-25 by 1776 (MRCROSSROADS)
133 messages in 52 discussions
Latest Nov-8 by 1776 (MRCROSSROADS)
298 messages in 129 discussions
Latest Oct-30 by 1776 (MRCROSSROADS)
1411 messages in 293 discussions
687 messages in 252 discussions
15 messages in 10 discussions
48 messages in 28 discussions
180 messages in 94 discussions
509 messages in 166 discussions
886 messages in 424 discussions
305 messages in 140 discussions
737 messages in 312 discussions
I normally run 'badblocks' directly instead of using the 'fsck [-c]'. Afterwards, one can check the 'filesystem' -- tree, counts, etc. with 'fsck'. Knowing enough about 'badblocks', one can check (over-write, zero) every bit on a drive or partition as well as exercise, initial, wipe hardware.
I have never heard of badblocks. :-/
I've used badblocks but it fails.
Time to start going SSD all around anyway. :-D
In all seriousness, how do you know 'it fails'? What parms/options, etc.?