Eşyalarını Tamir Et Topluluk Mağaza

Early 2011 Model: A1278 / 2.3 GHz i5 or 2.7 GHz i7 processor

782 Soru Tümünü görüntüle

Seçenekler

HDD constantly writing data?

Hey everyone, having a strange problem. I recently upgraded to 16 GB of RAM, and I’m not sure if this problem is directly correlated to that. My HDD has been writing/reading data like crazy since I upgraded, specifically spotlight, racking up GB’s of data written in less than half an hour, mdworker processes and mds_stores were using a crazy amount of CPU but then it would settle down after a while.

So, I disabled spotlight through the terminal since I don’t really use it anyways and most of the huge reading/writing stopped, but I still feel the HDD starting and stopping at a pretty steady rate, and in activity monitor I see the process “launchd” slowly writing data usually at a rate of up to 500 KB, and my storage space slowly dwindles.

So is this because I upgraded the RAM so there are larger cache’s and such? I have no idea what I’m talking about really, I have used a bunch of different terminal actions to spit out a bunch of code trying to isolate what is in launchd, the sloth program to try and identify which part of launchd is writing bytes, cocktail program to try and fix any indexing issues. Or is the process “launchd” constantly writing data a normal thing?

I should mention the computer isn’t slow, its as fast as it was before I switched the RAM. DriveDX tells me the drive is alright, it gives me three warnings (Start/Stop count, G-Sense Error Rate, Load Cycle count), so I am not convinced this is my drive going bad. I also notice my sleepimage file is pretty big, almost 10 GB’s, and the process “coresymbolicationd” is bigger than I ever remember. Last bit of info is I removed my broken optical drive recently and left it empty, it may just be coincidence but it seems to coincide with this event, though I can’t imagine removing a broken optical drive affects the HDD writing data. Am I looking at doing a clean OS reinstall?

Thanks for any answers/advice, let me know if I should provide any logs and instructions on how to get said logs, or any other information to get a better solution!

Bu soruyu yanıtla Ben de bu sorunu yaşıyorum

Bu iyi bir soru mu?

Evet Hayır
Puan 0
Yorum Ekle

2 Cevap

Filtre ölçütü:
En Faydalı En Yeni En eski
En Yararlı Yanıt

Seçenekler

Sounds like the encrypt may have gotten turned on. Look in System Preferences > Security & Privacy > FileVault and see if it is turned on.

Bu yanıt yardımcı oldu mu?

Evet Hayır
Puan 2

7 Yorum:

@mayer unfortunately not, if only it were that simple. I removed some unnecessary third party launch agents and launch daemons late last night, shut it down over night and it seems to be behaving slightly (maybe) better this morning, still writing data consistently when the laptop is running but it seems at a slower rate (still racking up MBs every few minutes). I guess a good question is if the "launchd" process should be writing any data at all, is that abnormal or normal? I have read a lot of people have issues with the "launchd" CPU usage but its normal for me, and others have this strange issue where it writes a lot of data. From what I gather the "launchd" process runs all the daemons so I have been trying to isolate where all the data is going, logs maybe?

Edit: definitely not logs as far as I can tell from both the /Library and /private log folders.

tarafından

I could also be Spotlight indexing your contents.

tarafından

@mayer I turned off spotlight yesterday because the mds_stores and mdworker processes were using a huge amount of CPU out of nowhere. I've been looking at the system logs looking for anything irregular,

"Mar 29 14:27:16 users-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit"

Does this mean anything? I am seeing it a lot in the system log. I'm going to try a safe boot start later and see if the problems persist to tell me if should just reinstall High Sierra

Edit: a little googling tells me a novice like me won't get anything from looking at the Console log and that line of code is normal. I am very befuddled, maybe I just never noticed this before I messed with it so I am being paranoid.

tarafından

DirtyJetsamMemoryLimi means something is using up to much RAM

tarafından

@mayer hmmm thats interesting as I just upgraded from 4 GB to 16 GB of RAM and activity monitor tells me I am only using 4 GB of memory with 3 GB of cached memory. Kernel_task is using about 950 MB of memory but everything else under 200 MB. I suppose putting the 4GB back in is another test I can do over the weekend along with a safe mode boot, though that seems unrelated to the HDD constantly writing data. It definitely seems to be affecting the "System" part of the storage as the "System" keeps getting larger. Its not affecting my computer speed but I am very curious as to what is going on, my only guess is that launchd is encountering an error and is stuck in a loop, but I cant find anything online along those lines of thinking.

tarafından

2 tane daha yorum göster

Yorum Ekle

Seçenekler

This series tends to have HD SATA cable breakdown. I would recommend replacing it with the better MacBook Pro 13" Unibody (Mid 2012) Hard Drive Cable. Even still I would place a strip of electricians tape on the uppercase to help to protect it from the rough aluminum case. The last issue is the folding of the cable you want rounded bends not sharp bends.

MacBook Pro 13" Unibody (Mid 2012) Hard Drive Cable Görseli

Ürün

MacBook Pro 13" Unibody (Mid 2012) Hard Drive Cable

$34.99

Bu yanıt yardımcı oldu mu?

Evet Hayır
Puan 1
Yorum Ekle

Yanıtını ekle

Andy sonsuza kadar minnettar olacak.
İstatistikleri Görüntüle:

Son 24 Saat: 4

Son 7 gün: 4

Son 30 gün: 13

Her zaman: 635