-
Posts
60 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jsmontague
-
-
21 minutes ago, johnnie.black said:
That's for Seagate drives:
https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888
Im not following. the link I sent says not to read that variable for any manufacturer except seagate. all mine above are WD so that variable isn't used instead should be reading the "value" column. Is the WIKI wrong or shouldn't be followed?
-
Reading the below link it says "PLEASE completely ignore the RAW_VALUE number!" for Raw_Read_Error_Rate.
-
is that same for all manufacturers? I'm currently adding in an old Seagate drive that is showing the following 😬😬
# ATTRIBUTE NAME FLAG VALUE WORST THRESHOLD TYPE UPDATED FAILED RAW VALUE 1 Raw read error rate 0x000f 114 099 006 Pre-fail Always Never 69344592
-
which field should be 0 or close to it?
-
I checked the BIOS and have "auto" set for overclocking. Any other ideas?
M/B: ASUSTeK COMPUTER INC. Crosshair V Formula Version Rev 1.xx - s/n: MT701C041000044 BIOS: American Megatrends Inc. Version 1703. Dated: 10/17/2012 CPU: AMD Phenom™ II X6 1090T @ 3200 MHz
root@Alexandria:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to [email protected], please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 4: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 5: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms.
-
These are directly connected disks in a SC846 chassis with a stock backplane so no cables in the system outside the SAS connectors to the LSI card. They have previously lived in a windows based system with direct SATA cables to MOBO are those leftover SMART numbers from before migration? I've read up on the guide to understanding SMART so that helped me a little bit, any other guides/info to read up on you recommend? I am adding in a second parity disk so for now I think my plan will be to run them and keep a disk on standby should either give up the ghost.
-
alexandria-diagnostics-20200310-1755.zip
Not sure if the diagnostics now hold the extended SMART test data or not? I can't see anything different when I pull each drives report. Both show "passed" in the dashboard.
-
I just kicked off SMART tests on Disk1 and Disk2 will post back. Thanks!!
-
Just got my first unRAID build stood up using SC846 case and internals of my old "cold" backup storage server and disks. All my main data is on a Window Storage systems array with no redundancy so although I want to get this guy done right, I also am a little freaked out in the sheer amount of time it takes to get array up etc i'm running with no backup should a drive fail in my current server. That being said i've got my old 4TB's and a shucked 6TB installed and pool built and I just completed a parity check. Both times it finds a ton of errors but SMART test is passing on disks. Can anyone help a noob out here and tell me which disks need to go? Last thing I want is to have to remove/replace a drive or even rebuild the pool in the middle of migrating data etc. I have 2 6TB on way today and once I kill my current server plan on adding one of its 6TB as 2nd parity for N+2 drive protection.
Diag attached
New unRaid Build Errors
in General Support
Posted
Couple pronouns here maybe are causing me to not understand you so maybe i'll start over to help.
https://wiki.unraid.net/Understanding_SMART_Reports explains how to read SMART table. It says to ignore WD hard drives RAW value on the "Raw_Read_Error_Rate" field.
So if the value below "51" for example is ignored as this is a WD drive, what value do I keep my eye on for incrementing to help point to the drive failing?
SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 51