Kaydol

Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza kaydolun.

Oturum aç

Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza giriş yapın.

Şifremi hatırlamıyorum

Şifreni mi unuttun? Lütfen e-mail adresinizi giriniz. Bir bağlantı alacaksınız ve e-posta yoluyla yeni bir şifre oluşturacaksınız.

3 ve kadim dostu 1 olan sj'yi rakamla giriniz. ( 31 )

Üzgünüz, Flood yazma yetkiniz yok, Flood girmek için giriş yapmalısınız.

Lütfen bu Floodun neden bildirilmesi gerektiğini düşündüğünüzü kısaca açıklayın.

Lütfen bu cevabın neden bildirilmesi gerektiğini kısaca açıklayın.

Please briefly explain why you feel this user should be reported.

Shucked WD140EDGZ Mostly 100% Utilization in Synology

So I’ve put three of these new 14TB drives shucked from the WD EasyStores that I picked up from BestBuy in the last few days. I only have one of these drives in this array and for some reason, it sits at 100% utilization most of the time while it is checking of parity (I just created the volume). Sometimes it goes less, but most of the time it sits at 100%, unlike the other drives as you can see in this screenshot. It seems to perform just as well, its just odd that its always at 100%. I was curious to see if it was that drive so I tore down the array, swapped it for another drive of the same exact model and it did the same thing.

It must be just how these things are in a Synology so I wanted to share this with everyone in case this is something that may be undesirable for some. I was thinking maybe a firmware issue. Not sure where to look to see if there are firmware updates for the drives – I couldn’t find anything on WDs site.

https://preview.redd.it/i0u0z1j982y71.png?width=660&format=png&auto=webp&s=357a604ac051b5b9417942bdf82fc6eca0c9a2ca

Benzer Yazılar

Yorum eklemek için giriş yapmalısınız.

3 Yorumları

  1. The read/write performance is on par with the other drives, so I wouldn’t worry much. I get this behavior on one drive or another when setting up a new array or checking parity as well.

    Rebuilding parity / expanding an array can take forever on a Synology, especially with a bunch of large drives.

  2. I was optimizing my synology pool and had to remove a drive from the pool to let it finish. It was estimating 600+ days to finish, but I removed a drive from the pool and it ended up finishing in 2 days.

  3. Well, the parity process is going to be rate-limited by one drive or the other; just happens to be this one (and that’s not by much).