March 29, 201016 yr I'm having difficulties writing to one of the Disk 2 in my array. The 3 other disks no problem. When writing to disk 2, throughput will slow to a standstill, like less than 0.1% network utilization in task manager on XP. I have not had even one parity sync ever on any of my disks during operation or routine parity checks. I figured I should still try to run a filesystem check on Disk 2, the output is below. Does not seem to indicate any problem. Any ides as to what could be wrong here ? root@FileServer:~# reiserfsck /dev/md2 reiserfsck 3.6.19 (2003 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Mon Mar 29 01:42:26 2010 ########### Replaying journal.. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 479774 Internal nodes 2877 Directories 473 Other files 7792 Data block pointers 484775763 (177416 of them are zero) Safe links 0 ########### reiserfsck finished at Mon Mar 29 01:57:01 2010 ########### root@FileServer:~# syslog_2010-03-28.txt
March 29, 201016 yr Do you think all these oom (out-of-memory) errors might have anything to do with your problems? Mar 29 01:23:56 FileServer kernel: reiserfsck invoked oom-killer: gfp_mask=0x280da, order=0, oomkilladj=0 Mar 29 01:23:56 FileServer kernel: Pid: 19862, comm: reiserfsck Not tainted 2.6.31.12-unRAID #1 Mar 29 01:23:56 FileServer kernel: Call Trace: Mar 29 01:23:56 FileServer kernel: [<c1047d7a>] oom_kill_process+0x5e/0x1ce Mar 29 01:23:56 FileServer kernel: [<c1048066>] ? badness+0x15a/0x191 Mar 29 01:23:56 FileServer kernel: [<c10480ce>] __out_of_memory+0x31/0x10c Mar 29 01:23:56 FileServer kernel: [<c1048207>] out_of_memory+0x5e/0x83 Mar 29 01:23:56 FileServer kernel: [<c104a0e2>] __alloc_pages_nodemask+0x380/0x43d Mar 29 01:23:56 FileServer kernel: [<c1055d16>] handle_mm_fault+0x1d7/0x88e Mar 29 01:23:56 FileServer kernel: [<c128e6e4>] ? schedule+0x620/0x67a Mar 29 01:23:56 FileServer kernel: [<c10270b1>] ? __do_softirq+0xf0/0xf8 Mar 29 01:23:56 FileServer kernel: [<c1016f80>] do_page_fault+0x17c/0x1e4 Mar 29 01:23:56 FileServer kernel: [<c1016e04>] ? do_page_fault+0x0/0x1e4 Mar 29 01:23:56 FileServer kernel: [<c128fd6e>] error_code+0x66/0x6c Mar 29 01:23:56 FileServer kernel: [<c1016e04>] ? do_page_fault+0x0/0x1e4 Mar 29 01:23:56 FileServer kernel: Mem-Info: Mar 29 01:23:56 FileServer kernel: DMA per-cpu: Mar 29 01:23:56 FileServer kernel: CPU 0: hi: 0, btch: 1 usd: 0 Mar 29 01:23:56 FileServer kernel: Normal per-cpu: Mar 29 01:23:56 FileServer kernel: CPU 0: hi: 186, btch: 31 usd: 181 Mar 29 01:23:56 FileServer kernel: Active_anon:35702 active_file:61 inactive_anon:19981 Mar 29 01:23:56 FileServer kernel: inactive_file:105 unevictable:58924 dirty:0 writeback:0 unstable:0 Mar 29 01:23:56 FileServer kernel: free:2522 slab:3593 mapped:1017 pagetables:271 bounce:0 Mar 29 01:23:56 FileServer kernel: DMA free:2204kB min:248kB low:308kB high:372kB active_anon:11996kB inactive_anon:1312kB active_file:60kB inactive_file:64kB unevictable:8kB present:15804kB pages_scanned:54 all_unreclaimable? no Mar 29 01:23:56 FileServer kernel: lowmem_reserve[]: 0 491 491 491 Mar 29 01:23:56 FileServer kernel: Normal free:7884kB min:7940kB low:9924kB high:11908kB active_anon:130812kB inactive_anon:78612kB active_file:184kB inactive_file:356kB unevictable:235688kB present:503172kB pages_scanned:544 all_unreclaimable? no Mar 29 01:23:56 FileServer kernel: lowmem_reserve[]: 0 0 0 0 Mar 29 01:23:56 FileServer kernel: DMA: 551*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2204kB Mar 29 01:23:56 FileServer kernel: Normal: 937*4kB 5*8kB 2*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 7884kB Mar 29 01:23:56 FileServer kernel: 59099 total pagecache pages Mar 29 01:23:56 FileServer kernel: 0 pages in swap cache Mar 29 01:23:56 FileServer kernel: Swap cache stats: add 0, delete 0, find 0/0 Mar 29 01:23:56 FileServer kernel: Free swap = 0kB Mar 29 01:23:56 FileServer kernel: Total swap = 0kB Mar 29 01:23:56 FileServer kernel: 130864 pages RAM Mar 29 01:23:56 FileServer kernel: 0 pages HighMem Mar 29 01:23:56 FileServer kernel: 2301 pages reserved Mar 29 01:23:56 FileServer kernel: 6728 pages shared Mar 29 01:23:56 FileServer kernel: 124481 pages non-shared Mar 29 01:23:56 FileServer kernel: Out of memory: kill process 19862 (reiserfsck) score 2834 or a child Mar 29 01:23:56 FileServer kernel: Killed process 19862 (reiserfsck) Mar 29 01:25:51 FileServer kernel: reiserfsck invoked oom-killer: gfp_mask=0x201d0, order=0, oomkilladj=0 Mar 29 01:25:51 FileServer kernel: Pid: 19602, comm: reiserfsck Not tainted 2.6.31.12-unRAID #1 Mar 29 01:25:51 FileServer kernel: Call Trace: Mar 29 01:25:51 FileServer kernel: [<c1047d7a>] oom_kill_process+0x5e/0x1ce Mar 29 01:25:51 FileServer kernel: [<c1048066>] ? badness+0x15a/0x191 Mar 29 01:25:51 FileServer kernel: [<c10480ce>] __out_of_memory+0x31/0x10c Mar 29 01:25:51 FileServer kernel: [<c1048207>] out_of_memory+0x5e/0x83 Mar 29 01:25:51 FileServer kernel: [<c104a0e2>] __alloc_pages_nodemask+0x380/0x43d Mar 29 01:25:51 FileServer kernel: [<c104bd1a>] __do_page_cache_readahead+0x8e/0x169 Mar 29 01:25:51 FileServer kernel: [<c104bfc7>] ondemand_readahead+0xff/0x15a Mar 29 01:25:51 FileServer kernel: [<c104c096>] page_cache_sync_readahead+0x16/0x1b Mar 29 01:25:51 FileServer kernel: [<c1046f37>] generic_file_aio_read+0x21c/0x51a Mar 29 01:25:51 FileServer kernel: [<c101b5ad>] ? __wake_up_common+0x35/0x5b Mar 29 01:25:51 FileServer kernel: [<c1067ace>] do_sync_read+0xbb/0xf9 Mar 29 01:25:51 FileServer kernel: [<c10326a5>] ? autoremove_wake_function+0x0/0x30 Mar 29 01:25:51 FileServer kernel: [<c128edbc>] ? mutex_lock+0xe/0x28 Mar 29 01:25:51 FileServer kernel: [<c1067a13>] ? do_sync_read+0x0/0xf9 Mar 29 01:25:51 FileServer kernel: [<c1068146>] vfs_read+0x8a/0x114 Mar 29 01:25:51 FileServer kernel: [<c10684dd>] sys_read+0x3b/0x60 Mar 29 01:25:51 FileServer kernel: [<c1002975>] syscall_call+0x7/0xb Mar 29 01:25:51 FileServer kernel: Mem-Info: Mar 29 01:25:51 FileServer kernel: DMA per-cpu: Mar 29 01:25:51 FileServer kernel: CPU 0: hi: 0, btch: 1 usd: 0 Mar 29 01:25:51 FileServer kernel: Normal per-cpu: Mar 29 01:25:51 FileServer kernel: CPU 0: hi: 186, btch: 31 usd: 170 Mar 29 01:25:51 FileServer kernel: Active_anon:36322 active_file:20 inactive_anon:19450 Mar 29 01:25:51 FileServer kernel: inactive_file:0 unevictable:58922 dirty:0 writeback:0 unstable:0 Mar 29 01:25:51 FileServer kernel: free:2643 slab:3530 mapped:1011 pagetables:271 bounce:0 Mar 29 01:25:51 FileServer kernel: DMA free:2324kB min:248kB low:308kB high:372kB active_anon:10484kB inactive_anon:2888kB active_file:0kB inactive_file:0kB unevictable:8kB present:15804kB pages_scanned:0 all_unreclaimable? no Mar 29 01:25:51 FileServer kernel: lowmem_reserve[]: 0 491 491 491 Mar 29 01:25:51 FileServer kernel: Normal free:8248kB min:7940kB low:9924kB high:11908kB active_anon:134804kB inactive_anon:74912kB active_file:80kB inactive_file:0kB unevictable:235680kB present:503172kB pages_scanned:436 all_unreclaimable? no Mar 29 01:25:51 FileServer kernel: lowmem_reserve[]: 0 0 0 0 Mar 29 01:25:51 FileServer kernel: DMA: 577*4kB 3*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2332kB Mar 29 01:25:51 FileServer kernel: Normal: 1012*4kB 13*8kB 2*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 8248kB Mar 29 01:25:51 FileServer kernel: 58968 total pagecache pages Mar 29 01:25:51 FileServer kernel: 0 pages in swap cache Mar 29 01:25:51 FileServer kernel: Swap cache stats: add 0, delete 0, find 0/0 Mar 29 01:25:51 FileServer kernel: Free swap = 0kB Mar 29 01:25:51 FileServer kernel: Total swap = 0kB Mar 29 01:25:51 FileServer kernel: 130864 pages RAM Mar 29 01:25:51 FileServer kernel: 0 pages HighMem Mar 29 01:25:51 FileServer kernel: 2301 pages reserved Mar 29 01:25:51 FileServer kernel: 6626 pages shared Mar 29 01:25:51 FileServer kernel: 124498 pages non-shared Mar 29 01:25:51 FileServer kernel: Out of memory: kill process 19921 (reiserfsck) score 2834 or a child Mar 29 01:25:51 FileServer kernel: Killed process 19921 (reiserfsck) Mar 29 01:28:10 FileServer kernel: dd invoked oom-killer: gfp_mask=0x201d0, order=0, oomkilladj=0 Mar 29 01:28:10 FileServer kernel: Pid: 20158, comm: dd Not tainted 2.6.31.12-unRAID #1 Mar 29 01:28:10 FileServer kernel: Call Trace: Mar 29 01:28:10 FileServer kernel: [<c1047d7a>] oom_kill_process+0x5e/0x1ce Mar 29 01:28:10 FileServer kernel: [<c1048066>] ? badness+0x15a/0x191 Mar 29 01:28:10 FileServer kernel: [<c10480ce>] __out_of_memory+0x31/0x10c Mar 29 01:28:10 FileServer kernel: [<c1048207>] out_of_memory+0x5e/0x83 Mar 29 01:28:10 FileServer kernel: [<c104a0e2>] __alloc_pages_nodemask+0x380/0x43d Mar 29 01:28:10 FileServer kernel: [<c104bd1a>] __do_page_cache_readahead+0x8e/0x169 Mar 29 01:28:10 FileServer kernel: [<c104be0c>] ra_submit+0x17/0x1c Mar 29 01:28:10 FileServer kernel: [<c104c016>] ondemand_readahead+0x14e/0x15a Mar 29 01:28:10 FileServer kernel: [<c104c096>] page_cache_sync_readahead+0x16/0x1b Mar 29 01:28:10 FileServer kernel: [<c1046f37>] generic_file_aio_read+0x21c/0x51a Mar 29 01:28:10 FileServer kernel: [<c1067ace>] do_sync_read+0xbb/0xf9 Mar 29 01:28:10 FileServer kernel: [<c10861b1>] ? block_ioctl+0x2c/0x34 Mar 29 01:28:10 FileServer kernel: [<c10326a5>] ? autoremove_wake_function+0x0/0x30 Mar 29 01:28:10 FileServer kernel: [<c10721a3>] ? do_vfs_ioctl+0x474/0x4a8 Mar 29 01:28:10 FileServer kernel: [<c128edbc>] ? mutex_lock+0xe/0x28 Mar 29 01:28:10 FileServer kernel: [<c1067a13>] ? do_sync_read+0x0/0xf9 Mar 29 01:28:10 FileServer kernel: [<c1068146>] vfs_read+0x8a/0x114 Mar 29 01:28:10 FileServer kernel: [<c10684dd>] sys_read+0x3b/0x60 Mar 29 01:28:10 FileServer kernel: [<c1002975>] syscall_call+0x7/0xb Mar 29 01:28:10 FileServer kernel: Mem-Info: Mar 29 01:28:10 FileServer kernel: DMA per-cpu: Mar 29 01:28:10 FileServer kernel: CPU 0: hi: 0, btch: 1 usd: 0 Mar 29 01:28:10 FileServer kernel: Normal per-cpu: Mar 29 01:28:10 FileServer kernel: CPU 0: hi: 186, btch: 31 usd: 178 Mar 29 01:28:10 FileServer kernel: Active_anon:34449 active_file:30 inactive_anon:21248 Mar 29 01:28:10 FileServer kernel: inactive_file:4 unevictable:58924 dirty:0 writeback:0 unstable:0 Mar 29 01:28:10 FileServer kernel: free:2587 slab:3542 mapped:1017 pagetables:283 bounce:0 Mar 29 01:28:10 FileServer kernel: DMA free:2248kB min:248kB low:308kB high:372kB active_anon:10920kB inactive_anon:2408kB active_file:0kB inactive_file:16kB unevictable:8kB present:15804kB pages_scanned:33 all_unreclaimable? no Mar 29 01:28:10 FileServer kernel: lowmem_reserve[]: 0 491 491 491 Mar 29 01:28:10 FileServer kernel: Normal free:8100kB min:7940kB low:9924kB high:11908kB active_anon:126876kB inactive_anon:82584kB active_file:120kB inactive_file:0kB unevictable:235688kB present:503172kB pages_scanned:114 all_unreclaimable? no Mar 29 01:28:10 FileServer kernel: lowmem_reserve[]: 0 0 0 0 Mar 29 01:28:10 FileServer kernel: DMA: 563*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2252kB Mar 29 01:28:10 FileServer kernel: Normal: 999*4kB 3*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 8100kB Mar 29 01:28:10 FileServer kernel: 58980 total pagecache pages Mar 29 01:28:10 FileServer kernel: 0 pages in swap cache Mar 29 01:28:10 FileServer kernel: Swap cache stats: add 0, delete 0, find 0/0 Mar 29 01:28:10 FileServer kernel: Free swap = 0kB Mar 29 01:28:10 FileServer kernel: Total swap = 0kB Mar 29 01:28:10 FileServer kernel: 130864 pages RAM Mar 29 01:28:10 FileServer kernel: 0 pages HighMem Mar 29 01:28:10 FileServer kernel: 2301 pages reserved Mar 29 01:28:10 FileServer kernel: 6835 pages shared Mar 29 01:28:10 FileServer kernel: 124535 pages non-shared Mar 29 01:28:10 FileServer kernel: Out of memory: kill process 20004 (reiserfsck) score 2866 or a child Mar 29 01:28:10 FileServer kernel: Killed process 20004 (reiserfsck) Mar 29 01:28:10 FileServer kernel: reiserfsck: page allocation failure. order:0, mode:0x201d0 Mar 29 01:28:10 FileServer kernel: Pid: 20004, comm: reiserfsck Not tainted 2.6.31.12-unRAID #1 Mar 29 01:28:10 FileServer kernel: Call Trace: Mar 29 01:28:10 FileServer kernel: [<c104a16b>] __alloc_pages_nodemask+0x409/0x43d Mar 29 01:28:10 FileServer kernel: [<c104bd1a>] __do_page_cache_readahead+0x8e/0x169 Mar 29 01:28:10 FileServer kernel: [<c104be0c>] ra_submit+0x17/0x1c Mar 29 01:28:10 FileServer kernel: [<c104c016>] ondemand_readahead+0x14e/0x15a Mar 29 01:28:10 FileServer kernel: [<c104c075>] page_cache_async_readahead+0x53/0x5e Mar 29 01:28:10 FileServer kernel: [<c1046f67>] generic_file_aio_read+0x24c/0x51a Mar 29 01:28:10 FileServer kernel: [<c101b5ad>] ? __wake_up_common+0x35/0x5b Mar 29 01:28:10 FileServer kernel: [<c1067ace>] do_sync_read+0xbb/0xf9 Mar 29 01:28:10 FileServer kernel: [<c10326a5>] ? autoremove_wake_function+0x0/0x30 Mar 29 01:28:10 FileServer kernel: [<c128edbc>] ? mutex_lock+0xe/0x28 Mar 29 01:28:10 FileServer kernel: [<c1067a13>] ? do_sync_read+0x0/0xf9 Mar 29 01:28:10 FileServer kernel: [<c1068146>] vfs_read+0x8a/0x114 Mar 29 01:28:10 FileServer kernel: [<c10684dd>] sys_read+0x3b/0x60 Mar 29 01:28:10 FileServer kernel: [<c1002975>] syscall_call+0x7/0xb Mar 29 01:28:10 FileServer kernel: Mem-Info: Mar 29 01:28:10 FileServer kernel: DMA per-cpu: Mar 29 01:28:10 FileServer kernel: CPU 0: hi: 0, btch: 1 usd: 0 Mar 29 01:28:10 FileServer kernel: Normal per-cpu: Mar 29 01:28:10 FileServer kernel: CPU 0: hi: 186, btch: 31 usd: 173 Mar 29 01:28:10 FileServer kernel: Active_anon:34495 active_file:30 inactive_anon:21283 Mar 29 01:28:10 FileServer kernel: inactive_file:4 unevictable:58924 dirty:0 writeback:0 unstable:0 Mar 29 01:28:10 FileServer kernel: free:2516 slab:3535 mapped:1017 pagetables:283 bounce:0 Mar 29 01:28:10 FileServer kernel: DMA free:2212kB min:248kB low:308kB high:372kB active_anon:10968kB inactive_anon:2408kB active_file:0kB inactive_file:16kB unevictable:8kB present:15804kB pages_scanned:42 all_unreclaimable? no Mar 29 01:28:10 FileServer kernel: lowmem_reserve[]: 0 491 491 491 Mar 29 01:28:10 FileServer kernel: Normal free:7852kB min:7940kB low:9924kB high:11908kB active_anon:127012kB inactive_anon:82724kB active_file:120kB inactive_file:0kB unevictable:235688kB present:503172kB pages_scanned:315 all_unreclaimable? no Mar 29 01:28:10 FileServer kernel: lowmem_reserve[]: 0 0 0 0 Mar 29 01:28:10 FileServer kernel: DMA: 553*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2212kB Mar 29 01:28:10 FileServer kernel: Normal: 937*4kB 3*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 7852kB Mar 29 01:28:10 FileServer kernel: 58980 total pagecache pages Mar 29 01:28:10 FileServer kernel: 0 pages in swap cache Mar 29 01:28:10 FileServer kernel: Swap cache stats: add 0, delete 0, find 0/0 Mar 29 01:28:10 FileServer kernel: Free swap = 0kB Mar 29 01:28:10 FileServer kernel: Total swap = 0kB Mar 29 01:28:10 FileServer kernel: 130864 pages RAM Mar 29 01:28:10 FileServer kernel: 0 pages HighMem Mar 29 01:28:10 FileServer kernel: 2301 pages reserved Mar 29 01:28:10 FileServer kernel: 6831 pages shared Mar 29 01:28:10 FileServer kernel: 124614 pages non-shared
March 29, 201016 yr Author Looking at the log, the first oom came when the reiserfsch command failed to run 3 at a time while at the same time preclearing another drive. I was able to complete the reiserfsck when doing just one disk at a time, so I guess my answer will be no, I don't think that is it directly.
March 30, 201016 yr does it go fast for like a minute then start to slow down? what about reading from the share does that slow down? because i have a problem similar to yours i only have 1 drive so i cant test if its just this one. Only way i found to fix my problem so far was to run 4.4.2. For me it would work fine if i read files but if i tried to transfer a file it would slow all the way.
March 30, 201016 yr Author I had good read speeds. Slow writes was almost immediate. But my problem has gone away after I rebooted it last night. With the reboot, I disabled the sabnzbd addon. Another possible cause for the problems disappearance is the filesystemcheck. Idunno.
April 4, 201016 yr Author Problem is back. I stopped running Sabnzbd for now, but the problem popped up anyways. I didn't see those same out of memory errors, but there is some other stuff going on: Apr 4 05:34:38 FileServer kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Apr 4 05:34:38 FileServer kernel: ata4.00: BMDMA2 stat 0xd0009 Apr 4 05:34:38 FileServer kernel: ata4: SError: { BadCRC } Apr 4 05:34:38 FileServer kernel: ata4.00: cmd 25/00:00:87:8c:40/00:04:82:00:00/e0 tag 0 dma 524288 in Apr 4 05:34:38 FileServer kernel: res 41/04:ef:87:8c:40/00:03:82:00:00/f0 Emask 0x1 (device error) Apr 4 05:34:38 FileServer kernel: ata4.00: status: { DRDY ERR } Apr 4 05:34:38 FileServer kernel: ata4.00: error: { ABRT } Apr 4 05:34:38 FileServer kernel: ata4.00: configured for UDMA/100 Apr 4 05:34:38 FileServer kernel: ata4: EH complete Apr 4 06:40:49 FileServer kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Apr 4 06:40:49 FileServer kernel: ata4.00: BMDMA2 stat 0xd0009 Apr 4 06:40:49 FileServer kernel: ata4: SError: { BadCRC } Apr 4 06:40:49 FileServer kernel: ata4.00: cmd 25/00:00:0f:8e:56/00:04:b2:00:00/e0 tag 0 dma 524288 in Apr 4 06:40:49 FileServer kernel: res 41/04:ef:0f:8e:56/00:03:b2:00:00/f0 Emask 0x1 (device error) Apr 4 06:40:49 FileServer kernel: ata4.00: status: { DRDY ERR } Apr 4 06:40:49 FileServer kernel: ata4.00: error: { ABRT } Apr 4 06:40:49 FileServer kernel: ata4.00: configured for UDMA/100 Apr 4 06:40:49 FileServer kernel: ata4: EH complete I see no sync errors for any of my disks in the web interface, and have never had a sync error on my parity check. Almost complete syslog attached (I cut away a lot of duplicate file messages to keep the size under 128k - the full syslog was 330k). Any help appreciated! syslog.txt
April 5, 201016 yr Bad CRC is an indication of the Cyclic Redundancy Check failing. If a disk is reporting this, it is either a un-readable sector (usually reported as a media error in a SMART report) or a bad/noisy cable between the disk and the disk controller. It could also be a noisy power supply causing the communications errors too.
April 5, 201016 yr Author I resisted the urge to open the box and mess arround with cables jut yet. Full SMART report attached. How can I have 7 pending sectors when there are no reallocated sectors ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 155 145 021 Pre-fail Always - 9250 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 79 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 588 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 19 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 6688 194 Temperature_Celsius 0x0022 130 113 000 Old_age Always - 22 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 7 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 Do I risk anything by running the SMART tests ? smart_wd20eads-2_2010-04-04.txt
April 5, 201016 yr A sector is marked as "pending re-allocation" when an attempt to read it fails. It cannot be re-allocated until it is next written. (because the disks does not know what should be in the re-allocated sector. If it knew, it would be able to read the sector marked for re-allocation, and it would not need re-allocation.) Therefore, you have not attempted to write those 7 sectors pending re-allocation since the read of them failed. Joe L.
April 5, 201016 yr Author Joe, any idea how this relates to the slow write performance of the drive ? What would you do in my place ?
April 5, 201016 yr Joe, any idea how this relates to the slow write performance of the drive ? What would you do in my place ? I would not wait for a sale on a replacement drive. I'd get a new drive and put it in place. My time is worth more to me than the disk itself. Then, once the data on the drive is rebuilt onto a replacement and parity protection is again in effect for the array, I can take my time with the old disk. The drive went off-line because a write to it failed. It went off-line a second time during the reconstruction. You did not show the actual disk error preceding all the write_stripe errors, but unless you find a loose cable (either SATA or POWER), you really need to think it is the drive, or the disk controller port. The drive is most likely. As far as the cables not being touched in months... It gives it months to vibrate loose, or for the temperature to heat/cool enough for it to work itself loose. It can happen. It is at least worth a check. Joe L.
April 5, 201016 yr Author Actually, the drive never went offline. In the webinterface it shows green, 0 (zero) errors. I last did a parity check 1.st of the month (with your script, thanks). I had no sync errors. Does that change anything ? Also, I don't quite know what you mean by "You did not show the actual disk error preceding all the write_stripe errors", I am not sure if you got more out of reading the log than I did or if You might be mixing this up with another case.
April 5, 201016 yr I think I am mixing up two different cases. Sorry. The other person has a disk that has gone off-line twice. Joe L.
April 5, 201016 yr Your errors are BadCRC Apr 4 05:34:38 FileServer kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Apr 4 05:34:38 FileServer kernel: ata4.00: BMDMA2 stat 0xd0009 Apr 4 05:34:38 FileServer kernel: ata4: SError: { BadCRC } Apr 4 05:34:38 FileServer kernel: ata4.00: cmd 25/00:00:87:8c:40/00:04:82:00:00/e0 tag 0 dma 524288 in Apr 4 05:34:38 FileServer kernel: res 41/04:ef:87:8c:40/00:03:82:00:00/f0 Emask 0x1 (device error) Apr 4 05:34:38 FileServer kernel: ata4.00: status: { DRDY ERR } Most likely bad SATA cable, loose cable/cable connection, poor quality cable picking up noise from nearby cables, marginal power supply, bad disk, bad disk controller port (probably in that order) Joe L.
April 9, 201016 yr Author OK, so first off I am baffled as to why unRAID would not display these badcrc errors on the webadmin page. Sureley, a badcrc in the controller-to-disk communication is a bad sign and should be highlighted IMHO. But anyway, I took the thing apart. Did every cable in that box with cable ties resulting in a neat and nice looking case where the SATA cables are not tangled up with the power cables, and I discarded the molex-sata adapter used for the problem disk. Also swapped the data cable and controller-port with another disk to see if the problem would move to another disk. The badcrc errors are gone from the log now. I also ran a long SMART-test finding no errors, resulting in 0 reallocated sectors. The disk does still have 8 pending sectors, though. Guess the write of some files might have failed due to intermittent power connection. I crc-checked my files (I have crc on everything I have transfered to the unRAID server) and only found crc-errors in 3 4.7GB ISO files the files I was trying to transfer when this problem first occoured. But the basic problem remains. Did some more systematic troubleshooting and found that writing smaller files (up to 700 MB) is no problem. Even writing a 4.7GB ISO file to the root of the disk is no problem. The real problem seems to be writing a (any) 4.7GB file (or larger) to the directory where I keep arround 20 other 4.7GB ISO files. When I try to write the ISO to that same dir, the transfer freezes up and results in an error "the network location no longer avaliable" (or something to that effect). I tried from two different client computers (both Win XP-32bit). What is up with that
April 9, 201016 yr The real problem seems to be writing a (any) 4.7GB file (or larger) to the directory where I keep arround 20 other 4.7GB ISO files. When I try to write the ISO to that same dir, the transfer freezes up and results in an error "the network location no longer avaliable" (or something to that effect). I tried from two different client computers (both Win XP-32bit). What is up with that I tried to reproduce that problem and I couldn't. (XP32sp3 over samba to unRAID 4.5.3) Copied a single 7GB file back and forth a few times, both with UNC paths and with a mapped network drive, worked equally well. I am puzzled by your problem.
Archived
This topic is now archived and is closed to further replies.