7 ms·
Looking beyond the obvious problem here, just curious why the admin ran chkdsk /f for no reason, then did it on 6 more systems after observing it caused ntfs fa
by magoon 6y ago
Looking beyond the obvious problem here, just curious why the admin ran chkdsk /f for no reason, then did it on 6 more systems after observing it caused ntfs failure.
- astronautjones 6y ago"i, also, like to live dangerously"
- andreareina 6y agohttps://m.xkcd.com/242/ https://m.xkcd.com/242/ maybe. One hopes the reporter had backups (or was testing on disposable systems) before trying to reproduce a data-loss condition.
- mormegil 6y agoXKCD has a mobile version?! You learn something new every day!
- FriendlyNormie 6y agoWho cares? Go suck Randall’s dick you dumb faggot.
- emayljames 6y agoI'd say admin has had issues with users hard resetting the PC's and corrupting data, albeit slowly, and so runs chkdsk before it gets real bad.
- diegoperini 6y agoI'd do the same and for me, the reason would probably be trust.
- tzs 6y agoHe didn’t. It’s a very slow command. He started it in parallel on several. He only found that there was a problem when the ones started earlier finished and rebooted. By then it was too late for 7 machines but he was able to stop it on the rest.