You are not logged in.
I use smartmontools to check out my hdd's SMART system from time to time. Recently, I discovered some warning flags that physical corruption was present on my newest disk. I read the badblockshowto on the smartmontools website and determined that the errors begin (thankfully) in the middle of a shared NTFS partition. I booted into Windows XP and ran the m$ scanner (scan for and attempt recovery of bad sectors) tool. After 90 min or so, it finished with a pretty non-descript box that more or less said the process was finished without displaying any log file detailing just how many bad sectors it locked out and which files were affected.
Does anyone have any experience detecting bad sectors/blocks on NTFS partitions under Linux?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I downloaded and used the SeaTools package from Seagate (It covers modern Maxtors now too + their own drives). I found that, over all, it is slower to detect & run tests than Western Digital's. But it gave me an idea of which drive was toast and why, as opposed to Windows tools which just said there was a huge delayed write error. *rolls eyes* Big help eh? It's logs are also pretty useless but you can check them in the "computer management" section, storage module under the Control Panel.
I hope that helps. Oh also, IIRC the Seatools & WD's tools will also be download-able as ISO's if you suspect windows is making things worse. Worst case, go get the Ultimate Boot-CD. It has everything you need (literally, for any brand of hard drive it has a tool).
Offline
SeaTools sucks. The short test told me to run the long test. The long test crashed such that keyboard/mouse wouldn't respond. Long story short, I RMA'ed the drive and am expecting a replacement today (only cost me $22 and that covered 2-day shipping and return shipping). I have all my stuff backed-up, but hopefully, I can rsync the partitions to the replacement with minimal data loss. After all, the bad sectors could be on free space.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
1) Mount NTFS system
2) Create a tarball of the contents on another partition
3) Wipe the NTFS partition and run badblocks over it
4) Recreate partition
5) Extract the tarball back to the fresh partition
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
@fukawi2 - The partition in question is enormous... I don't have enough free space to do it.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Is it all used though? Tar will only take what's used, so even if it's 500gb with only 20gb used, youll only need ~20gb to back it up.
Other than that, I'm not sure what to do about it.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
True.. thanks for the suggestion.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline