Monday, April 29, 2024
 Popular · Latest · Hot · Upcoming
4
rated 0 times [  4] [ 0]  / answers: 1 / hits: 1335  / 2 Years ago, mon, august 22, 2022, 11:52:35

I have three new Seagate IronWolf Pro HDDs. They are working fine:



  • I can write and read from them

  • They are passing all the tests


The one issue I have is a worrying sound they emit when idle. The sound is a repetitive "tack tack ...", each tack being separated by about 0.5 sec. The "tack" is so strong that I can feel the vibration on my desk. Again, the drives work fine, if I copy a large file to those drives, the clicking sound disappears, it seems like the drives do not know how to be idle. The noise starts maybe 1 or 2 seconds after mounting the drive.


Here is what I've been through so far to try to solve the problem:



  • Excessive head parking: The first explanation I found was that the power management on Ubuntu's side was causing excessive head parking, which could be solved via hdparm -B254 /dev/sda, but this command is not supported by my drive.



  • Forcing drive to Idle with hdparm: I tried commands like hdparm -y /dev/sda, hdparm -S0 /dev/sda. Each time the clicking sound stops for a sec when registering the command and then immediately resumes.



  • Deactivate SMART monitoring: I've found some record of drive monitoring causing some noise issue, so I deactivated it, without success.



  • Upgrade firmware: I thought about upgrading the firmware but I already have the latest firmware it seems.



  • Deactivate EPC / Idle_a / Idle_b: Using Seagate's tool called SeaChest, I can modify the power settings of a given drive. So far I've tried to disable the different idle modes, disable EPC, without success.




I have another smaller desktop with the same OS (Ubuntu 20.04), but a different Seagate drive (Seagate Exos instead of Seagate IronWolf). This other drive works as intended, so it seems the problem might be in the compatibility between Ubuntu and Ironwolf drives.


Any idea if this is a known issue and if there is a way to fix this? I can't believe this idle sound is a good thing for the drive.


EDIT 1:


I've reproduced the same behavior on Ubuntu 18, on the same system where my Seagate Exos is currently running smoothly.


I've added some rubber pads to the HDDs support frame and now I barely hear the sound. I'm still not entirely sure this is normal. I don't understand why the Seagate Exos is super silent but the IronWolf Pro aren't. I tried to contact Seagate, but I couldn't reach them for some reason.


EDIT 2:


I could still distinguish the periodic clicking noise so I ended up writing a stupid python script to keep writing stuff to disk:


import time

if __name__ == "__main__":
while True:
with open("./stupid_file.txt", "w") as fs:
for _ in range(1000000):
fs.write("This is the last time I'm buying an IronWolf HDD.
")
time.sleep(0.001)


Which I run where I've mounted my drive: python3 dumb_script.py


I can still hear some faint clicking but at least now it is not periodic... I'm still interested in case anyone can confirm this clicking is normal or not.


EDIT 3:


The clicking completely stopped, even without running the script. I have no idea why but all is fine now. Could it be just an initialization phase of the hard drive?


SOLUTION:


@Levente was right, this was due to the lazy init of ext4, see his answer for the solution.


More From » sound

 Answers
3

Here is a possible explanation, and a viable approach to take about it:




"Could it be just an initialization phase of the hard drive?" — right, I believe it's called ext4 filesystem ("lazy") initialization. When you format a disk for ext4 filesystem, the default behavior is that the initial formatting happens fast, but then the initial journaling needs to get completed later, throughout idle times; it can last a few hours (or who knows how long...).


But it's possible to initiate an ext4 filesystem in such way that the initialization happens up front: the process will take longer that way, but no subsequent "lazy" process will be necessary afterwards.


Identification of the process:


I don't remember how the journaling process was called, but I have at least found now that I have identified the culprit with iotop (and web-searched it later, to find about the laziness and its countermeasures):


sudo apt install iotop
sudo iotop -o

Update: from this article, I have learned that the process might be called ext4lazyinit.


Stop being lazy:


So when I found my brand new disk lazy-initing, I did not wait for that to finish; rather, following unmounting the partition, I have re-created the filesystem on it anew, as per the arguments presented below:


sudo mkfs -t ext4 -L some_label -E lazy_itable_init=0,lazy_journal_init=0 /dev/sdxX

(For the record, this destroys all data on the partition that you had already copied onto it.)


[#1575] Monday, August 22, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
eanda

Total Points: 439
Total Questions: 116
Total Answers: 105

Location: Armenia
Member since Sat, Dec 31, 2022
1 Year ago
eanda questions
Tue, Nov 22, 22, 15:24, 1 Year ago
Sat, Oct 16, 21, 23:48, 3 Years ago
Sun, Jul 3, 22, 09:38, 2 Years ago
Thu, Feb 3, 22, 14:33, 2 Years ago
;