[SOLVED] 17.1.4 - Seagate 24/7 Hdd gets klick noise

[Torsten_b]

Hi Folks,

I just want to inform you about a strange problem, the hdd gets klick noise nearly every 60 seconds, while using 17.1.4.
I've tried to switch off all params getting of smartctl, and all bios-params. I also checked the cable, and all other stuff around the mainboard (Asus Q1900M, 8GB)

Just a 'smartctl -a' every 5 to 10 seconds prevents sometimes the klick noise.

With a fresh installed Freebsd 11-release there is not this klicking noise.

smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-RELEASE-p8 amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Pipeline HD 5900.2
Device Model:     ST3160316CS
Serial Number:    5VT1YRJD
LU WWN Device Id: 5 000c50 052858c40
Firmware Version: CA12
User Capacity:    160,041,885,696 bytes [160 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5900 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
 ===

It would be nice, if someone can check this in the sourcetree.

Bye, Torsten

[bartjsmit]

Normally this is a sign that the drive is dying. Rather than the 17.1.4 install/upgrade causing the problem, it may just have been the high number of drive accesses during the install that tipped it over the edge.

Did you execute a short test (smartctl -t short) on it? How long has it been in service?

Bart...

[franco]

Hi Torsten,

Fairly certain the disk is dying. Our updates apply a few thousand files, rewrite or delete them, and the system does more things in the background than a freshly installed FreeBSD which would have almost no background jobs.


Cheers,
Franco

[Torsten_b]

Hi,

well the drive is brand new. Just take a look to the smartctl output.
I know, the klicking noise is a measuremt of dying disks. I have listen't to this klicking quite often.

But...

the klicking noise does only apear while using opnsense. I have installed plain FreeBSD 11 Release, and I also have installed pfsense. With both OS's this klinking noise didn't came up. I've checked all bios params, changed the partition layout, checked the drive software, installed the drive to an other mainboard, and so on and so on.

I did this all, because I want to know whats going on with this drive. In case the drive is broken, I could return  it to the shop.

Sounds funny, isn't it?
I really don't have any clue, why this tiny drive does this noise only with opns.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   111   100   006    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       79
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       116
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       26
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   068   067   045    Old_age   Always       -       32 (Min/Max 31/33)
194 Temperature_Celsius     0x0022   032   040   000    Old_age   Always       -       32 (0 23 0 0 0)
195 Hardware_ECC_Recovered  0x001a   063   063   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

Bye, Torsten

[weust]

Only thing I can think of to try out, is a different drive.
For testing, of course.

I can't imagine it really, but perhaps the motherboard is doing something funky in combination with it all.

[Torsten_b]

Hi weust,

Well, I tried it with different drive a few minutes ago. As expected, the testdrive a wd5000aakx doesn't make this klick noise. But this only a workaround. Btw, the motherboard is a asrock Q1900 m board, with intel baytrail soc chips, designed for very low power consuming. I've got different boards with the intel baytrail chipset from gigabyte and asrock, mostly with wd-hdds. With plain freebsd 11-release the hdd doesnt make this klicking noise.

Changing the hdd doesn't solve the problem.
I'm really interested to solve the problem. If I have any problem with a port or the kernel on freebsd, i write a bugreport to the maintainer on svn, and we find out the problem to solve it. Even if I have to compile a new patched kernel, thats no problem. But, on opns I can't inform the maintainer, cause of a closed svn.

I think, opns needs to solve the problem at all. Because I'm using a very common chipset and a 24/7 certified hdd.

My intention is to solve the problem for me and other users, to push opns forward. Even if I have to compile and reinstall all stuff more then twice, okay?

The girls an guys on opns doing a great job. Even because of this great job a tiny little problem with hardware needs to get solved.

Bye, Torsten

[weust]

Closed svn? If you mean GitHub then that's fully open?
Plus, the maintainers use these forums as well.
Or stop by in the IRC channel during the week, to discus it there.

[bartjsmit]

Hi Torsten,

I'm not quite sure what your expectations are from this forum. Allow me to recap:

1. You have a hard drive that makes a noise
2. This is a new drive which is passing all health checks
3. You cannot reproduce the issue with another drive
4. The model in question is optimised for storing video

I think that using another disk is a perfectly acceptable solution and I'm not convinced that your problem is representative for any significant fraction of the OPNsense userbase.

Bart...

[Torsten_b]

Hi all,

The problem is solved.
Thanks for your support.


Bye, Torsten