HDD continuously writing data

[Vyky]

Hi,

last month I started to notice, that my 2013 Mac mini started to produce HDD sounds - just like continuously writing data, even if all APPs are closed, immediately after restart, etc. I dont think this is a HDD failure because of the familiar writing sound.

I did lot of research in the forums, but didnt find any help.

It looks like the kernel_task od launchd are causing it by writing SOME data, even if I dont use the computer for hours. Im desperate about finding whats wrong.

Tried to check Activity monitor, which shows this (screenshot attached). The "bytes written" from kernel and launchd are continuously growing to Gigs (the screenshot is after restart).

I triend to kill some processes, I tried to stop everything running - can I determine what is the kernel and launchd writing and somehow stop this? Or maybe another process writes?

Yeah and I dont have any memory/CPU problem (Kernel CPU around 3%)

Im a common user, not a geek, please slowly

Thanx for the help.

 

[RemarkabLee]

Investigate open files using Sloth:

http://sveinbjorn.org/sloth


Also worth running Disk Utility and check the filesystem health.

 

[Mr. Retrofire]

I did lot of research in the forums, but didnt find any help.

sudo fs_usage > ~/fs_usage_log.txt

...in a Terminal window writes the file system access data to the fs_usage_log.txt file in the current user directory. You can stop the fs_usage tool with the Command+Period keys.

Then open the fs_usage_log.txt file in BBEdit or TextWrangler. Make sure that the text editor window is wide enough!

----------

Also worth running Disk Utility and check the filesystem health.

OS X does this automatically at startup before the Finder mounts the volumes.

 

[Vyky]

Yeah, Disk utility done, Onyx cleaning done - nothing worked. Tried Sloth, but cannot determine the process either :-(

 

[Fishrrman]

Well, you could turn off Spotlight and delete the indexes.

And, if you're using Time Machine, turn it off.

 

[Vyky]

Did both, no help :-/

 

[Macman45]

Stealth network traffic? Are you by any chance on a shared or university network?

 

[Vyky]

Ok, got the file - but I cant read whats wrong... like I said, no geek

Could you check it out? I uploaded it here, cause 22Mb.

OK, reuploaded: http://www.multiupload.nl/DZ7GQCQ1AL

 

[Mr. Retrofire]

Could you check it out? I uploaded it here, cause 22Mb:

http://www.edisk.cz/stahnout-soubor/38361/fs_usage_log.txt_20.32MB.html

I cannot download the file (the download button does nothing). Can you upload a compressed version of the log file (zip or bzip2) to
http://www.multiupload.nl/
(putlocker & depositfiles are enough)
?

Thanks!

 

[Vyky]

Ok, repuloaded: http://www.multiupload.nl/DZ7GQCQ1AL

 

[Mr. Retrofire]

Ok, repuloaded: http://www.multiupload.nl/DZ7GQCQ1AL

Thanks. Next time use a compression program or the Finder "Compress" option to compress the text file. This reduces the upload and download time.

What i found:
mdworker (this is a spotlight process) analyzes your Mail sent box. If Mail opens automatically mdworker analyzes the data also automatically.

 

[RemarkabLee]

OS X does this automatically at startup before the Finder mounts the volumes.

I don't think it does, unless forced to (safe mode).

 

[Mr. Retrofire]

I don't think it does, unless forced to (safe mode).

From:
https://developer.apple.com/library/Mac/documentation/Darwin/Reference/ManPages/man8/fsck_hfs.8.html

...“The second form of fsck_hfs preens the specified file systems. It is normally started by fsck(8) run
from /etc/rc.boot during automatic reboot, when a HFS file system is detected. When preening file systems, fsck_hfs will fix common inconsistencies for file systems that were not unmounted cleanly.”
...

Journaled file systems (HFS+J) and SSDs reduce the time needed for fsck_hfs to nearly zero.

 

[RemarkabLee]

From:
https://developer.apple.com/library/Mac/documentation/Darwin/Reference/ManPages/man8/fsck_hfs.8.html


Journaled file systems (HFS+J) and SSDs reduce the time needed for fsck_hfs to nearly zero.

The article mentions there are 3 forms of this command, with increasing functionality. So you are correct to say it does run at boot, but a normal boot would usually execute the first and/or second form and not a full filesystem check that the third form provides. Safe mode will however, use the third form.

When preening file systems, fsck_hfs will fix common inconsistencies for file systems that were not unmounted cleanly. If more serious problems are found, fsck_hfs does not try to fix them, indicates that it was not successful, and exits.