NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Mon Apr 29, 2024 1:42 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 4 posts ] 
Author Message
PostPosted: Sat Aug 08, 2009 2:47 am 
Offline

Joined: Sun Dec 30, 2007 5:16 pm
Posts: 13
Location: Portland, OR
Copying to any drive on the server is extremely slow all of a sudden. 3-4 Hours for 4 GB.

Would the errors indicated in the logs below cause the slow copy. My 'Linux' is extremely rudimentary!

I searched around a bit and found this SMART analysis of one of my drives showing errors. There were also errors in the syslog for the same drive.

Here's the pertinent portion of the syslog:

Aug 8 08:54:35 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
Aug 8 08:54:35 user.warn kernel: VFS: Mounted root (ext2 filesystem).
Aug 8 08:54:35 user.info kernel: Mounted devfs on /dev
Aug 8 08:54:35 user.info kernel: Freeing unused kernel memory: 540k freed
Aug 8 08:54:35 user.warn kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 8 08:54:35 user.warn kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Aug 8 08:54:35 user.warn kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 8 08:54:35 user.warn kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Aug 8 08:54:35 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Aug 8 08:54:35 user.warn kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 8 08:54:35 user.warn kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Aug 8 08:54:35 user.err kernel: ext3: No journal on filesystem on ide0(3,65)
Aug 8 08:54:35 user.err kernel: ext3: No journal on filesystem on sd(8,1)
Aug 8 08:54:35 user.err kernel: ext3: No journal on filesystem on sd(8,17)
Aug 8 08:54:35 user.info kernel: kjournald starting. Commit interval 5 seconds
Aug 8 08:54:35 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,33), internal journal
Aug 8 08:54:35 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.


Here's the SMART analysis drive characteristics:

Disk-4 Hardware Details:

MODEL: ATA ST3750840AS, v.3.AA
INTERFACE: SCSI, HOST-3, BUS-0, TARGET-0, LUN-0



Filesystem Details:


tune2fs 1.27 (8-Mar-2002)
Filesystem volume name: NASLite-SE000121
Last mounted on:
Filesystem UUID: f7d40125-3b11-4fd0-910d-eabc1d354d8b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 91586560
Block count: 183141000
Reserved block count: 0
Free blocks: 81752682
Free inodes: 91580196
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: Sat Aug 8 08:54:30 2009
Last write time: Sat Aug 8 08:54:30 2009
Mount count: 3
Maximum mount count: 38
Last checked: Thu Jul 30 16:01:51 2009
Check interval: 15552000 (6 months)
Next check after: Tue Jan 26 16:01:51 2010
Reserved blocks uid: 0 (user admin)
Reserved blocks gid: 0 (group admin)
First inode: 11
Inode size: 128
Journal UUID:
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0



Here's the SMART LOG error report:

SMART Error Log Version: 1
ATA Error Count: 19 (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 19 occurred at disk power-on lifetime: 2943 hours (122 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
-- -- -- -- -- -- --
84 51 4f f8 01 60 e0 Error: ICRC, ABRT 79 sectors at LBA = 0x006001f8 = 6291960

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 c7 01 60 e0 00 00:00:38.644 READ DMA EXT
25 03 80 47 01 60 e0 00 00:00:38.509 READ DMA EXT
25 03 80 c7 00 60 e0 00 00:00:38.427 READ DMA EXT
25 03 08 37 00 60 e0 00 00:00:40.802 READ DMA EXT
25 03 80 47 00 60 e0 00 00:00:40.784 READ DMA EXT

Error 18 occurred at disk power-on lifetime: 2943 hours (122 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
-- -- -- -- -- -- --
84 51 3f 80 00 60 e0 Error: ICRC, ABRT 63 sectors at LBA = 0x00600080 = 6291584

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 3f 00 60 e0 00 00:00:28.857 READ DMA EXT
25 03 08 37 00 60 e0 00 00:00:28.838 READ DMA EXT
35 03 08 e7 05 60 e0 00 00:00:28.419 WRITE DMA EXT
35 03 08 cf 05 60 e0 00 00:00:28.419 WRITE DMA EXT
35 03 08 ef 00 60 e0 00 00:00:28.418 WRITE DMA EXT

Error 17 occurred at disk power-on lifetime: 2920 hours (121 days + 16 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
-- -- -- -- -- -- --
84 51 0f b0 00 60 e0 Error: ICRC, ABRT 15 sectors at LBA = 0x006000b0 = 6291632

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 3f 00 60 e0 00 00:00:17.333 READ DMA EXT
25 03 08 37 00 60 e0 00 00:00:17.332 READ DMA EXT
35 03 08 3f 00 5e e0 00 00:00:17.331 WRITE DMA EXT
35 03 08 47 00 5e e0 00 00:00:17.319 WRITE DMA EXT
25 03 01 00 00 00 e0 00 00:00:17.260 READ DMA EXT

Error 16 occurred at disk power-on lifetime: 2920 hours (121 days + 16 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
-- -- -- -- -- -- --
84 51 47 00 47 00 e0 Error: ICRC, ABRT 71 sectors at LBA = 0x00004700 = 18176

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 78 cf 46 00 e0 00 03:30:14.535 READ DMA EXT
25 03 08 c7 46 00 e0 00 03:30:14.533 READ DMA EXT
35 03 80 47 7d 00 e0 00 03:30:14.531 WRITE DMA EXT
35 03 80 c7 7c 00 e0 00 03:30:14.529 WRITE DMA EXT
35 03 80 47 7c 00 e0 00 03:30:14.527 WRITE DMA EXT

Error 15 occurred at disk power-on lifetime: 2613 hours (108 days + 21 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
-- -- -- -- -- -- --
84 51 07 e2 3e 00 e0 Error: ICRC, ABRT 7 sectors at LBA = 0x00003ee2 = 16098

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 18 d1 3e 00 e0 00 00:02:32.087 READ DMA EXT
25 03 1a cf 3e 00 e0 00 00:02:32.066 READ DMA EXT
25 03 1c cd 3e 00 e0 00 00:02:01.422 READ DMA EXT
25 03 1e cb 3e 00 e0 00 00:02:01.417 READ DMA EXT
25 03 20 c9 3e 00 e0 00 00:02:01.413 READ DMA EXT

SMART Self-test log structure revision number 1

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.

System Componets
NASLite-2 HDD v2.06 10-2007
Boot HDD is Seagate 250 GB IDE
1 750 GB IDE
1 750 GB Sata II
2 1TB SATA II


Top
 Profile  
 
PostPosted: Sat Aug 08, 2009 3:24 am 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
uh, yah.

Run a file check on the drive/s from the terminal and see if that cleans up the problem.

Mike


Top
 Profile  
 
PostPosted: Sat Aug 08, 2009 12:10 pm 
Offline

Joined: Sun Dec 30, 2007 5:16 pm
Posts: 13
Location: Portland, OR
Thanks,

Now I get to show my ignorance.

How does one run a "file check from the terminal"?

I ran the "Check Disk-4 File System" from the Admin menu. No help.

The "Check and Repair Disk 4 File System" has an "*" and is not available. Don't know why!


Top
 Profile  
 
PostPosted: Sat Aug 08, 2009 1:10 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
You need to boot a live CD and run it that way.

Also, check the cables to the drive/s. This could be the cause of problems.

Mike


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

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 209 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:  
Powered by phpBB® Forum Software © phpBB Group