![]() |
| ||||||||||||||||
|
Welcome to the HEXUS.community discussion forums forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and other features. By joining our free community you will have access to post topics, respond to polls and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! |
|
|||||||
Thecus.care@HEXUS Founded in 2004, Thecus brings decades of R&D expertise, sales channel development, and a strong customer focus to deliver high-quality products that meet the storage needs of individuals and large organizations alike. |
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Registered User
Join Date: Mar 2008
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
n5200 SMART Errors and RAID problems
I seem to be having major problems with the n5200 and the following drive:
=== START OF INFORMATION SECTION === Device Model: WDC WD7500AACS-00ZJB0 Serial Number: WD-WCASM0011601 Firmware Version: 01.01B01 User Capacity: 750,156,374,016 bytes SMART keeps kicking off Current_pending_sector errors on 2 or 3 disk. These are brand new disk. If i reboot the box the errors will some times go away: root@127.0.0.1:/img/www/inc/info# /usr/sbin/smartctl -A -d marvell /dev/sda smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home page ismartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 253 221 021 Pre-fail Always - 958 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 39 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 100 253 051 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 53 10 Spin_Retry_Count 0x0012 100 253 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 896 194 Temperature_Celsius 0x0022 114 110 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0010 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 051 Old_age Offline - 0 This seems to be dropping the disk from the raid 5 array which has become a MAJOR pain. I have had the NAS for the past 3 days and the entire time has been spend resyncing the array many times. IE: root@127.0.0.1:/img/www/inc/info# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid5] [raid6] [raid10] md1 : active raid5 sda2[0] sdb2[4] sdd2[3] sdc2[2] 2191836096 blocks level 5, 64k chunk, algorithm 2 [4/3] [U_UU] [====>................] recovery = 23.0% (168229120/730612032) finish=407.5min speed=22996K/sec md0 : active raid1 sdd1[3] sdc1[2] sda1[0] 1959808 blocks [5/3] [U_UU_] unused devices: <none> root@127.0.0.1:/img/www/inc/info# mdadm -D /dev/md1 /dev/md1: Version : 00.90.02 Creation Time : Thu Mar 27 03:27:08 2008 Raid Level : raid5 Array Size : 2191836096 (2090.30 GiB 2244.44 GB) Device Size : 730612032 (696.77 GiB 748.15 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Thu Mar 27 23:11:11 2008 State : clean, degraded, recovering Active Devices : 3 Working Devices : 4 Failed Devices : 0 Spare Devices : 1 Layout : left-symmetric Chunk Size : 64K Rebuild Status : 23% complete UUID : c61b5b82:0bafb41a:fd0a0572:107c955e Events : 0.633405 Number Major Minor RaidDevice State 0 8 2 0 active sync /dev/sda2 1 0 0 - removed 2 8 34 2 active sync /dev/sdc2 3 8 50 3 active sync /dev/sdd2 4 8 18 1 spare rebuilding /dev/sdb2 root@127.0.0.1:/img/www/inc/info# mdadm -D /dev/md0 /dev/md0: Version : 00.90.02 Creation Time : Thu Mar 27 21:05:13 2008 Raid Level : raid1 Array Size : 1959808 (1914.20 MiB 2006.84 MB) Device Size : 1959808 (1914.20 MiB 2006.84 MB) Raid Devices : 5 Total Devices : 3 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Thu Mar 27 21:06:54 2008 State : active, degraded Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 UUID : 1a728a1c:bf63f839:73463c1f:f64593dc Events : 0.5 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 0 0 - removed 2 8 33 2 active sync /dev/sdc1 3 8 49 3 active sync /dev/sdd1 4 0 0 - removed root@127.0.0.1:/img/www/inc/info# This has become a major nightmare to manage! Also what is up with the MD0 array as I did not build this raid1 array , is this for system usage ? per above disk /dev/hdb got kicked out, but SMART doesn't show any problems: root@127.0.0.1:/img/www/inc/info# /usr/sbin/smartctl -A -d marvell /dev/sdb smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home page is /smartmontools.sourceforge.net/]smartmontools Home Page (last updated $Date: 2008/03/23 14:11:53 $)[/url] === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 253 179 021 Pre-fail Always - 1050 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 838 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 51 10 Spin_Retry_Count 0x0012 100 100 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 846 194 Temperature_Celsius 0x0022 110 110 000 Old_age Always - 40 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 051 Old_age Offline - 0 Please Help before this little box gets tossed out the window ![]() --Jason |
|
|
|
|
|
#2 (permalink) |
|
Registered User
Join Date: Mar 2008
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
|
Re: n5200 SMART Errors and RAID problems
Hi,
I have 5 WD 1TB GP (model WD10EACS) hd's in my Thecus N5200Pro. I do not have your serious kind of problem but I do have the problem that the smart status is displayed as Warning while there are no problems when I run WD Diagnostics (green PASS). This is also mentioned about GP drives in the new HD compat. list on Thecus.com. I would like Thecus to fix this issue. I noticed however from your smartctl print outs that the version they use in the firmware is 5.33 while there is a newer (stable) version 5.36. There's something about a status code for Marvell controllers in that new version. There's also a version 5.37 but that's experimental. Maybe I go and try to run the newer (5.36) version and see if I still get the smart warning. Good luck on your issue. Hope Thecus support can help you out Regards, Roelof. |
|
|
|
![]() |
| Breadcrumb | ||||||
|
||||||
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Is data recovery possible? Intel Matrix Raid failure | mroz | Help - technical & advisory | 32 | 26-03-2008 06:30 PM |
| Can't enable LVM and Swap Disk Damage errors | bhelliom | Thecus.care@HEXUS ![]() |
1 | 25-02-2008 10:59 AM |
| n5200 - Raid 5 Degraded | skydo2007 | Thecus.care@HEXUS ![]() |
14 | 12-11-2007 09:43 AM |
| Raw Read Error Rate / CRC Errors - What does it mean? | zum | Thecus.care@HEXUS ![]() |
2 | 25-06-2007 08:04 AM |
| CHKDSK, Corruption and Consistency | Speed | Help - technical & advisory | 17 | 16-09-2006 01:13 PM |