NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Thu Mar 28, 2024 8:14 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 6 posts ] 
Author Message
PostPosted: Mon Mar 01, 2010 10:08 pm 
Offline

Joined: Sun Feb 15, 2009 11:34 pm
Posts: 20
Hello all

My Naslite has been up for 50 days.. but when I went to look at the details.. I have had some errors.. I think it means one of my hard drives is on the way out.. can someone please assist me with this.

PRODUCT NASLite-2 Operating System Type


VERSION v2.61 12-2009 Operating System Version



Feb 25 22:39:29 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 22:39:29 [5] hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=952310, sector=952209
Feb 25 22:39:29 [5] hdb: possibly failed opcode: 0x25
Feb 25 22:39:29 [5] end_request: I/O error, dev hdb, sector 952209
Feb 25 22:39:31 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb 25 22:39:31 [5] hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=952310, sector=952217
Feb 25 22:39:31 [5] hdb: possibly failed opcode: 0x25

MODEL: MDT MD2500BB-00DWA0, SN# MDT-MMAEH2466643, v.15.05R15
INTERFACE: DEVICE-HDB
Server Storage Disk-1




General:
This page provides specific information pertaining to Disk-1. Hardware, filesystem and S.M.A.R.T. details are listed below.




Disk-1 Hardware Details:

MODEL: MDT MD2500BB-00DWA0, SN# MDT-MMAEH2466643, v.15.05R15
INTERFACE: DEVICE-HDB





Filesystem Details:

tune2fs 1.40.4 (31-Dec-2007)
Filesystem volume name: NASLite-SE000101
Last mounted on:
Filesystem UUID: 412e8745-0ff7-4150-9c49-4b0885085452
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super
Filesystem flags: signed directory hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 30539776
Block count: 61049008
Reserved block count: 0
Free blocks: 7380598
Free inodes: 30499729
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Last mount time: Sun Jan 10 18:09:49 2010
Last write time: Sun Jan 10 18:09:49 2010
Mount count: 3
Maximum mount count: 21
Last checked: Sun Jan 10 17:26:10 2010
Check interval: 15552000 (6 months)
Next check after: Fri Jul 9 17:26:10 2010
Reserved blocks uid: 0 (user admin)
Reserved blocks gid: 0 (group admin)
First inode: 11
Inode size: 128
Journal inode: 8
Journal backup: inode blocks






S.M.A.R.T. Status:

smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: MDT MD2500BB-00DWA0
Serial Number: MDT-MMAEH2466643
Firmware Version: 15.05R15
User Capacity: 250,059,350,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 6
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Mar 1 21:24:01 2010 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: (7599) seconds.
Offline data collection
capabilities: (0x79) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 95) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.

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 0x000b 200 001 051 Pre-fail Always In_the_past 0
3 Spin_Up_Time 0x0007 137 112 021 Pre-fail Always - 3650
4 Start_Stop_Count 0x0032 100 100 040 Old_age Always - 373
5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 4
7 Seek_Error_Rate 0x000b 100 253 051 Pre-fail Always - 0
9 Power_On_Hours 0x0032 060 060 000 Old_age Always - 29745
10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0
11 Calibration_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 372
194 Temperature_Celsius 0x0022 112 253 000 Old_age Always - 38
196 Reallocated_Event_Count 0x0032 196 196 000 Old_age Always - 4
197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 9
198 Offline_Uncorrectable 0x0012 200 200 000 Old_age Always - 16
199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0009 200 155 051 Pre-fail Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 65535 inconsistent with error log pointer 2

ATA Error Count: 65535 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 65535 occurred at disk power-on lifetime: 159 hours (6 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 55 8f 0e f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
01 00 25 00 00 08 00 00 46d+05:45:33.150 [RESERVED]
01 00 25 00 00 08 00 00 46d+05:45:33.150 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:33.150 NOP [Abort queued commands]
01 00 25 00 00 08 00 00 46d+05:45:33.150 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:33.150 NOP [Abort queued commands]

Error 65534 occurred at disk power-on lifetime: 159 hours (6 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 55 8f 0e f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
01 00 25 00 00 08 00 00 46d+05:45:31.200 [RESERVED]
01 00 25 00 00 08 00 00 46d+05:45:31.200 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:31.200 NOP [Abort queued commands]
01 00 25 00 00 08 00 00 46d+05:45:31.200 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:31.200 NOP [Abort queued commands]

Error 65533 occurred at disk power-on lifetime: 159 hours (6 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 55 8f 0e f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
01 00 25 00 00 08 00 00 46d+05:45:29.300 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:29.300 NOP [Abort queued commands]
01 00 25 00 00 08 00 00 46d+05:45:29.300 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:29.300 NOP [Abort queued commands]
01 00 25 00 00 08 00 00 46d+05:45:29.300 [RESERVED]

Error 65532 occurred at disk power-on lifetime: 159 hours (6 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 55 8f 0e f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
01 00 25 00 00 08 00 00 46d+05:45:27.350 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:27.350 NOP [Abort queued commands]
01 00 25 00 00 08 00 00 46d+05:45:27.350 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:27.350 NOP [Abort queued commands]
01 00 25 00 00 08 00 00 46d+05:45:27.350 [RESERVED]

Error 65531 occurred at disk power-on lifetime: 159 hours (6 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 55 8f 0e f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
01 00 25 00 00 08 00 00 46d+05:45:25.450 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:25.450 NOP [Abort queued commands]
01 00 25 00 00 08 00 00 46d+05:45:25.450 [RESERVED]
00 00 0e 00 00 51 8f 00 46d+05:45:25.450 NOP [Abort queued commands]
01 00 25 00 00 08 00 00 46d+05:45:25.450 [RESERVED]

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 732 283309350
# 2 Extended offline Completed: read failure 90% 732 283309350
# 3 Extended offline Completed: read failure 90% 35 283309350
# 4 Extended offline Completed: read failure 90% 35 283309350
# 5 Extended offline Completed: read failure 50% 431 193707529
# 6 Extended offline Completed: read failure 50% 588 193707529
# 7 Extended offline Completed: read failure 50% 280 193707529
# 8 Extended offline Completed: read failure 50% 891 193707529
# 9 Extended offline Completed: read failure 50% 888 193707529
#10 Extended offline Completed: read failure 20% 451 193707529
#11 Extended offline Interrupted (host reset) 90% 450 -
#12 Extended offline Interrupted (host reset) 90% 450 -
#13 Extended offline Completed: read failure 50% 256 193707529
#14 Extended offline Completed: read failure 50% 180 193707529
#15 Extended offline Completed without error 00% 1029 -
#16 Extended offline Completed without error 00% 913 -
#17 Extended offline Completed without error 00% 897 -
#18 Extended offline Completed without error 00% 895 -
#19 Extended offline Completed without error 00% 1052 -
#20 Extended offline Completed without error 00% 741 -
#21 Extended offline Completed without error 00% 671 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


Top
 Profile  
 
PostPosted: Mon Mar 01, 2010 10:35 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
Personally I might be inclined to backup the data ASAP and then run an FSCK on that volume/drive.

Mike


Top
 Profile  
 
PostPosted: Mon Mar 01, 2010 10:51 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Here's what I'd do:

1. Backup as Mike pointed out.
2. Check cables/connectors to the drive. I'd replace with a known-good cable and plug it to another known-good port just to be sure.
3. Run extended SMART on it and let it complete. You can view the status every so often by looking at the SMART stats screen.
4. Check filesystem with bad block check enabled.

SMART will generate errors if you have bad connections also, so don't assume the drive is bad until you can eliminate the cables as the cause. After you are done and the drive seems to do it's job, try loading it a bit bu moving some data to and from it and see if you can generate errors in the syslog. If not you can assume things are back to normal and keep an eye on it for a while.

BACK UP before you do any troubleshooting.


Top
 Profile  
 
PostPosted: Wed Mar 03, 2010 9:28 pm 
Offline

Joined: Sun Feb 15, 2009 11:34 pm
Posts: 20
Hello all

Thank you for your replies. I am in the process of backing up the data. I am sorry but I have run the extended smart test from Telnet... but I do not see the results on the drives html page, even if I refresh the page. Do I need to reboot Naslite to start the test?


Top
 Profile  
 
PostPosted: Thu Mar 04, 2010 5:39 am 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
No, you don't need to reboot. As long as you have some reasonable Content Update Interval, then the results will be shown on the "Server Storage Disk-x" page. But, depending on the disk manufacturer, the result may be hard to find or interpret.

On the "Disk-x" page ... first find out the current number of "Power_On_Hours". Then look near the bottom of the page for something that looks like this:
Quote:
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 3769 -


The 3769 is the number of "Power_On_Hours" of that test. There may be many test results, so that's why it is important to double check that the result matches your expectation of when a successful test completed, and that it is current, not old and irrelevant.


Top
 Profile  
 
PostPosted: Thu Mar 04, 2010 8:18 am 
Offline

Joined: Sun Feb 15, 2009 11:34 pm
Posts: 20
Thank you George

While backing up my data I got this message last night. Once / if I can back it up I will open up the box and check the cables as was mentioned.

Mar 4 05:19:25 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 4 05:19:25 [5] hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=492015, sector=491761
Mar 4 05:19:25 [5] hdb: possibly failed opcode: 0x25
Mar 4 05:19:25 [5] end_request: I/O error, dev hdb, sector 491761
Mar 4 05:19:27 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 4 05:19:27 [5] hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=492015, sector=491769
Mar 4 05:19:27 [5] hdb: possibly failed opcode: 0x25
Mar 4 05:19:29 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 4 05:19:29 [5] hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=492015, sector=491769
Mar 4 05:19:29 [5] hdb: possibly failed opcode: 0x25
Mar 4 06:03:46 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 4 06:03:46 [5] hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1192069, sector=1191865
Mar 4 06:03:46 [5] hdb: possibly failed opcode: 0x25
Mar 4 06:03:48 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 4 06:03:48 [5] hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1192069, sector=1191865
Mar 4 06:03:48 [5] hdb: possibly failed opcode: 0x25
Mar 4 06:03:51 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 4 06:03:51 [5] hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1192069, sector=1191865
Mar 4 06:03:51 [5] hdb: possibly failed opcode: 0x25
Mar 4 06:03:53 [5] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 4 06:03:53 [5] hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1192069, sector=1191865
Mar 4 06:03:53 [5] hdb: possibly failed opcode: 0x25
Mar 4 06:03:53 [2] hda: DMA disabled
Mar 4 06:03:53 [2] hdb: DMA disabled
Mar 4 06:03:53 [2] ide0: reset: success
Mar 4 06:03:55 [5] hdb: task_pio_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
Mar 4 06:03:55 [5] hdb: task_pio_intr: error=0x40 { UncorrectableError }, LBAsect=1192069, sector=1192057
Mar 4 06:03:55 [5] hdb: possibly failed opcode: 0x29
Mar 4 06:03:55 [5] end_request: I/O error, dev hdb, sector 1192057
Mar 4 06:03:56 [5] hdb: task_pio_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
Mar 4 06:03:56 [5] hdb: task_pio_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1192069, sector=1192065
Mar 4 06:03:56 [5] hdb: possibly failed opcode: 0x29
Mar 4 06:03:58 [5] hdb: task_pio_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
Mar 4 06:03:58 [5] hdb: task_pio_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1192069, sector=1192065
Mar 4 06:03:58 [5] hdb: possibly failed opcode: 0x29
Mar 4 06:04:00 [5] hdb: task_pio_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 43 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group