Nezil Posted September 11, 2011 Share Posted September 11, 2011 I'm also getting this error, and have been since at least beta12, maybe longer. It didn't click with me that this might be responsible for the web UI lockup that I tend to see after a few days of the server running. Two sys logs attached, both from 12, rather than 12a I'm afraid, though I don't think 12a has done anything to influence this. For reference, my setup is as follows: Case: Lian Li PC-P50B Motherboard: Foxconn H67MP CPU: Intel i3 2100 RAM: 2 x 2GB Samsung PC3-10600 Controller: Supermicro AOC-SASLP-MV8, Biostar DC3SA 2 Port SATA III PSU: Antec Neo Eco 520 Drive Racks: Icydock 5in3 x 3 HDDs: 15 Green Drives - 2TB EARS x 2, EVDS x 2, EADS x 2; 1TB EAVS x 3, EADS x 6. Edit: I should add that the BLK error on the latest syslog (named just syslog) has not caused any obvious issues so far, web UI is still working. Edit 2: Got a new BLK_EH_NOT_HANDLED error overnight, Web UI hasn't worked since; new syslog attached ([email protected]). I'm going to update to 12a at this point, and see if it improves things at all. syslog.zip [email protected] [email protected] Quote Link to comment
darkside40 Posted September 12, 2011 Share Posted September 12, 2011 Sadly, Beta 12a not working for me…. Same problems as I had with beta10. Loose my eth0. Flip back to Beta12 and all works fine When in Beta12, ifconfig gets me: eth0 Link encap:Ethernet HWaddr 5c:d9:98:4a:14:7f inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10081 errors:0 dropped:0 overruns:0 frame:0 TX packets:9716 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1828686 (1.7 MiB) TX bytes:2006905 (1.9 MiB) Interrupt:19 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:460 errors:0 dropped:0 overruns:0 frame:0 TX packets:460 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:72585 (70.8 KiB) TX bytes:72585 (70.8 KiB) When in Beta12a , eth0 simply doesn’t show – and I can’t “see” unRaid from my Mac or PC workstation Modprobe r8168 returns “FATAL: Module r8168 not found” in 12 and no response in 12a (but eth0 remains lost) logfile attached Network card is Dlink DGE-528T (card was on recommended list when I built my server) Any chance that network access will be fixed for Beta13? Looking through your syslog it seems that unRaid loads the r8168 Module which seems to be for PCIe NIC's, but yours is a PCI card so in my opinion teh r8169 Module would be the right choice. Are you able to remove the r8168 module and then loading r8169, both must included in 12a. Quote Link to comment
mikejp Posted September 12, 2011 Share Posted September 12, 2011 Good Morning, I got up this morning & checked my server, as I started a parity check before bed. I discovered the following error repeating itself at the end of my syslog: Sep 11 21:31:10 Tower2 kernel: kworker/0:1: page allocation failure: order:4, mode:0x4020 Sep 11 21:31:10 Tower2 kernel: Pid: 0, comm: kworker/0:1 Not tainted 3.0.3-unRAID #7 Sep 11 21:31:10 Tower2 kernel: Call Trace: Sep 11 21:31:10 Tower2 kernel: [<c105f857>] warn_alloc_failed+0xb2/0xc4 Sep 11 21:31:10 Tower2 kernel: [<c105ffc2>] __alloc_pages_nodemask+0x456/0x47f Sep 11 21:31:10 Tower2 kernel: [<c106003f>] __get_free_pages+0xf/0x21 Sep 11 21:31:10 Tower2 kernel: [<c107d6cd>] __kmalloc+0x28/0xff Sep 11 21:31:10 Tower2 kernel: [<c128e974>] pskb_expand_head+0xcb/0x1f0 Sep 11 21:31:10 Tower2 kernel: [<c128ee08>] __pskb_pull_tail+0x41/0x21f Sep 11 21:31:10 Tower2 kernel: [<c1295b6c>] dev_hard_start_xmit+0x204/0x31c Sep 11 21:31:10 Tower2 kernel: [<c12a4466>] sch_direct_xmit+0x50/0x137 Sep 11 21:31:10 Tower2 kernel: [<c1295d82>] dev_queue_xmit+0xfe/0x274 Sep 11 21:31:10 Tower2 kernel: [<c12b0127>] ip_finish_output+0x227/0x262 Sep 11 21:31:10 Tower2 kernel: [<c12b01c6>] ip_output+0x64/0x68 Sep 11 21:31:10 Tower2 kernel: [<c12adf4d>] ip_local_out+0x57/0x5b Sep 11 21:31:10 Tower2 kernel: [<c12afb5a>] ip_queue_xmit+0x2a5/0x2f2 Sep 11 21:31:10 Tower2 kernel: [<c12beee8>] tcp_transmit_skb+0x4d7/0x50d Sep 11 21:31:10 Tower2 kernel: [<c12c11f7>] tcp_write_xmit+0x2f9/0x3d7 Sep 11 21:31:10 Tower2 kernel: [<c12c1319>] __tcp_push_pending_frames+0x18/0x6f Sep 11 21:31:10 Tower2 kernel: [<c12bdfc9>] tcp_rcv_established+0x501/0x578 Sep 11 21:31:10 Tower2 kernel: [<c12c33b5>] tcp_v4_do_rcv+0x46/0x137 Sep 11 21:31:10 Tower2 kernel: [<c12c386c>] tcp_v4_rcv+0x3c6/0x647 Sep 11 21:31:10 Tower2 kernel: [<c12ac081>] ip_local_deliver_finish+0x93/0x158 Sep 11 21:31:10 Tower2 kernel: [<c12ac172>] ip_local_deliver+0x2c/0x2f Sep 11 21:31:10 Tower2 kernel: [<c12abd8b>] ip_rcv_finish+0x263/0x28b Sep 11 21:31:10 Tower2 kernel: [<c12abfbb>] ip_rcv+0x208/0x23b Sep 11 21:31:10 Tower2 kernel: [<c1293604>] __netif_receive_skb+0x234/0x25a Sep 11 21:31:10 Tower2 kernel: [<c1294a5f>] netif_receive_skb+0x5d/0x63 Sep 11 21:31:10 Tower2 kernel: [<c1294b1c>] napi_skb_finish+0x1e/0x34 Sep 11 21:31:10 Tower2 kernel: [<c1294f4c>] napi_gro_receive+0xc7/0xcf Sep 11 21:31:10 Tower2 kernel: [<c128f0ee>] ? __alloc_skb+0x53/0xf1 Sep 11 21:31:10 Tower2 kernel: [<f84d5651>] e1000_receive_skb+0x36/0x3b [e1000] Sep 11 21:31:10 Tower2 kernel: [<f84d5d79>] e1000_clean_rx_irq+0x291/0x32c [e1000] Sep 11 21:31:10 Tower2 kernel: [<f84d8926>] e1000_clean+0x3c/0x18f [e1000] Sep 11 21:31:10 Tower2 kernel: [<c1295022>] net_rx_action+0x59/0x12a Sep 11 21:31:10 Tower2 kernel: [<c102ccce>] __do_softirq+0x6b/0xe5 Sep 11 21:31:10 Tower2 kernel: [<c102cc63>] ? irq_enter+0x3c/0x3c Sep 11 21:31:10 Tower2 kernel: <IRQ> [<c102cb21>] ? irq_exit+0x32/0x53 Sep 11 21:31:10 Tower2 kernel: [<c100360b>] ? do_IRQ+0x7c/0x90 Sep 11 21:31:10 Tower2 kernel: [<c130b8a9>] ? common_interrupt+0x29/0x30 Sep 11 21:31:10 Tower2 kernel: [<c1007e14>] ? default_idle+0x2e/0x43 Sep 11 21:31:10 Tower2 kernel: [<c1001a60>] ? cpu_idle+0x3a/0x52 Sep 11 21:31:10 Tower2 kernel: [<c1306753>] ? start_secondary+0xad/0xaf Sep 11 21:31:10 Tower2 kernel: Mem-Info: Sep 11 21:31:10 Tower2 kernel: DMA per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: Normal per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 186, btch: 31 usd: 23 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 186, btch: 31 usd: 177 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 186, btch: 31 usd: 154 Sep 11 21:31:10 Tower2 kernel: HighMem per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 186, btch: 31 usd: 121 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 186, btch: 31 usd: 133 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 186, btch: 31 usd: 146 Sep 11 21:31:10 Tower2 kernel: active_anon:3358 inactive_anon:41 isolated_anon:0 Sep 11 21:31:10 Tower2 kernel: active_file:63400 inactive_file:1029066 isolated_file:0 Sep 11 21:31:10 Tower2 kernel: unevictable:49651 dirty:0 writeback:0 unstable:0 Sep 11 21:31:10 Tower2 kernel: free:850106 slab_reclaimable:27057 slab_unreclaimable:4848 Sep 11 21:31:10 Tower2 kernel: mapped:2150 shmem:62 pagetables:158 bounce:0 Sep 11 21:31:10 Tower2 kernel: DMA free:3692kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:2316kB inactive_file:2484kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15776kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:4364kB slab_unreclaimable:3016kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 869 8104 8104 Sep 11 21:31:10 Tower2 kernel: Normal free:78328kB min:3736kB low:4668kB high:5604kB active_anon:0kB inactive_anon:0kB active_file:220896kB inactive_file:220976kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:890008kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:103864kB slab_unreclaimable:16376kB kernel_stack:784kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 0 57884 57884 Sep 11 21:31:10 Tower2 kernel: HighMem free:3318404kB min:512kB low:8288kB high:16068kB active_anon:13432kB inactive_anon:164kB active_file:30388kB inactive_file:3892804kB unevictable:198604kB isolated(anon):0kB isolated(file):0kB present:7409192kB mlocked:0kB dirty:0kB writeback:0kB mapped:8596kB shmem:248kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:632kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 0 0 0 Sep 11 21:31:10 Tower2 kernel: DMA: 173*4kB 131*8kB 68*16kB 27*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3692kB Sep 11 21:31:10 Tower2 kernel: Normal: 10172*4kB 4562*8kB 70*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 78304kB Sep 11 21:31:10 Tower2 kernel: HighMem: 14893*4kB 104434*8kB 76666*16kB 30467*32kB 3245*64kB 68*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 1*4096kB = 3318404kB Sep 11 21:31:10 Tower2 kernel: 1142214 total pagecache pages Sep 11 21:31:10 Tower2 kernel: 0 pages in swap cache Sep 11 21:31:10 Tower2 kernel: Swap cache stats: add 0, delete 0, find 0/0 Sep 11 21:31:10 Tower2 kernel: Free swap = 0kB Sep 11 21:31:10 Tower2 kernel: Total swap = 0kB Sep 11 21:31:10 Tower2 kernel: 2228208 pages RAM Sep 11 21:31:10 Tower2 kernel: 1999874 pages HighMem Sep 11 21:31:10 Tower2 kernel: 150938 pages reserved Sep 11 21:31:10 Tower2 kernel: 1017284 pages shared Sep 11 21:31:10 Tower2 kernel: 211216 pages non-shared Sep 11 21:31:32 Tower2 kernel: kworker/0:1: page allocation failure: order:4, mode:0x4020 Would someone please look over the attached syslog, & maybe give me a clue as to what happened & how to fix it?? Thanks... syslog-2011-09-12.zip Quote Link to comment
Sledgehamma Posted September 12, 2011 Share Posted September 12, 2011 So here are not so many pronlems, especially with the realtek nic I, assume a RC1 ist just around the corner. Am I right? Quote Link to comment
JackBauer Posted September 12, 2011 Share Posted September 12, 2011 So here are not so many pronlems, especially with the realtek nic I, assume a RC1 ist just around the corner. Am I right? I tend to doubt it. There appear to be substantial issues remaining. (Not a substantial number necessarily - but serious issues, such as the SAS-MV8 issue. It now seems to be happening on a number of people's machines so the power supply reasoning is looking less certain.) Quote Link to comment
prostuff1 Posted September 12, 2011 Share Posted September 12, 2011 So here are not so many pronlems, especially with the realtek nic I, assume a RC1 ist just around the corner. Am I right? I tend to doubt it. There appear to be substantial issues remaining. (Not a substantial number necessarily - but serious issues, such as the SAS-MV8 issue. It now seems to be happening on a number of people's machines so the power supply reasoning is looking less certain.) What he said. Quote Link to comment
mbryanr Posted September 12, 2011 Share Posted September 12, 2011 Most of this is over my head...but this looks a reason for the sluggish system response when it gets the BLK_EH_NOT_HANDLED error: Looks like it wouldn't eliminate the error, only the memory leak. https://lists.open-fcoe.org/pipermail/devel/2010-November/010794.html This is the original code: http://fxr.watson.org/fxr/ident?v=linux-2.6;im=bigexcerpts;i=FC 3626 /* the blk_end_sync_io() doesn't check the error */ 3627 if (done) 3628 return BLK_EH_NOT_HANDLED; More info http://www.spinics.net/lists/linux-scsi/msg42860.html References to the error in the driver are significant in various mailing lists and forums. Quote Link to comment
SSD Posted September 12, 2011 Share Posted September 12, 2011 I had a problem and received very frequent "BLK_EH_NOT_HANDLED" errors on a SASLP attached Seagate LP drive a while back. All it really tells you is that something happened that the driver was not expecting, and the driver is returning this catch all error code saying that whatever it was, it didn't do anything in response. So it may be something important - or it may be something trivial - depends on what gave rise to the triggering condition. In my case it was a failing disk. This error logged over and over again, and the driver kept saying it didn't handle it. When I put the disk on a different controller, the other driver "handled" the error and I got a more specific reporting of what was going wrong without the endless "not handled" log entries. Quote Link to comment
mav3r1ck Posted September 12, 2011 Share Posted September 12, 2011 I've upgraded from 5.0b7 to 5.0b8, and I can't get to the web interface. I logged on to the server, and ran the emhttp command by hand and get a segmentation fault. It is on the network, as I can telnet to it. here's what's in the syslog for that Jul 7 19:20:32 Tower emhttp: unRAID System Management Utility version 5.0-beta8 Jul 7 19:20:32 Tower emhttp: Copyright (C) 2005-2011, Lime Technology, LLC Jul 7 19:20:32 Tower emhttp: Plus key detected, GUID: 0781-5406-0000-060512030038 Jul 7 19:20:32 Tower emhttp: rdevName.22 not found Jul 7 19:20:33 Tower emhttp: diskFsStatus.1 not found Jul 7 19:20:33 Tower kernel: emhttp[5598]: segfault at 0 ip b75ac760 sp bfc50c80 error 4 in libc-2.11.1.so[b7533000+15c000] Looks to be a problem with 'Plus' key - I'll fix it ASAP and post -beta8a. Hello Tom, I have the same issue running b12a for my PRO key... Sep 11 21:03:19 Goliath emhttp: Copyright © 2005-2011, Lime Technology, LLC Sep 11 21:03:19 Goliath emhttp: Pro key detected, GUID: 13FE-XXXX-XXXX-XXXXXXXXXXXX Sep 11 21:03:19 Goliath emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults Sep 11 21:03:19 Goliath emhttp: rdevName.22 not found Sep 11 21:03:20 Goliath emhttp: diskFsStatus.1 not found Sep 11 21:03:20 Goliath kernel: emhttp[13311]: segfault at 0 ip b74a6760 sp bf8961b0 error 4 in libc-2.11.1.so[b742d000+15c000] As you say above 'looks like a problem with the PLUS key' Thanks for your quick response Quote Link to comment
Joe L. Posted September 12, 2011 Share Posted September 12, 2011 Good Morning, I got up this morning & checked my server, as I started a parity check before bed. I discovered the following error repeating itself at the end of my syslog: Sep 11 21:31:10 Tower2 kernel: kworker/0:1: page allocation failure: order:4, mode:0x4020 Sep 11 21:31:10 Tower2 kernel: Pid: 0, comm: kworker/0:1 Not tainted 3.0.3-unRAID #7 Sep 11 21:31:10 Tower2 kernel: Call Trace: Sep 11 21:31:10 Tower2 kernel: [<c105f857>] warn_alloc_failed+0xb2/0xc4 Sep 11 21:31:10 Tower2 kernel: [<c105ffc2>] __alloc_pages_nodemask+0x456/0x47f Sep 11 21:31:10 Tower2 kernel: [<c106003f>] __get_free_pages+0xf/0x21 Sep 11 21:31:10 Tower2 kernel: [<c107d6cd>] __kmalloc+0x28/0xff Sep 11 21:31:10 Tower2 kernel: [<c128e974>] pskb_expand_head+0xcb/0x1f0 Sep 11 21:31:10 Tower2 kernel: [<c128ee08>] __pskb_pull_tail+0x41/0x21f Sep 11 21:31:10 Tower2 kernel: [<c1295b6c>] dev_hard_start_xmit+0x204/0x31c Sep 11 21:31:10 Tower2 kernel: [<c12a4466>] sch_direct_xmit+0x50/0x137 Sep 11 21:31:10 Tower2 kernel: [<c1295d82>] dev_queue_xmit+0xfe/0x274 Sep 11 21:31:10 Tower2 kernel: [<c12b0127>] ip_finish_output+0x227/0x262 Sep 11 21:31:10 Tower2 kernel: [<c12b01c6>] ip_output+0x64/0x68 Sep 11 21:31:10 Tower2 kernel: [<c12adf4d>] ip_local_out+0x57/0x5b Sep 11 21:31:10 Tower2 kernel: [<c12afb5a>] ip_queue_xmit+0x2a5/0x2f2 Sep 11 21:31:10 Tower2 kernel: [<c12beee8>] tcp_transmit_skb+0x4d7/0x50d Sep 11 21:31:10 Tower2 kernel: [<c12c11f7>] tcp_write_xmit+0x2f9/0x3d7 Sep 11 21:31:10 Tower2 kernel: [<c12c1319>] __tcp_push_pending_frames+0x18/0x6f Sep 11 21:31:10 Tower2 kernel: [<c12bdfc9>] tcp_rcv_established+0x501/0x578 Sep 11 21:31:10 Tower2 kernel: [<c12c33b5>] tcp_v4_do_rcv+0x46/0x137 Sep 11 21:31:10 Tower2 kernel: [<c12c386c>] tcp_v4_rcv+0x3c6/0x647 Sep 11 21:31:10 Tower2 kernel: [<c12ac081>] ip_local_deliver_finish+0x93/0x158 Sep 11 21:31:10 Tower2 kernel: [<c12ac172>] ip_local_deliver+0x2c/0x2f Sep 11 21:31:10 Tower2 kernel: [<c12abd8b>] ip_rcv_finish+0x263/0x28b Sep 11 21:31:10 Tower2 kernel: [<c12abfbb>] ip_rcv+0x208/0x23b Sep 11 21:31:10 Tower2 kernel: [<c1293604>] __netif_receive_skb+0x234/0x25a Sep 11 21:31:10 Tower2 kernel: [<c1294a5f>] netif_receive_skb+0x5d/0x63 Sep 11 21:31:10 Tower2 kernel: [<c1294b1c>] napi_skb_finish+0x1e/0x34 Sep 11 21:31:10 Tower2 kernel: [<c1294f4c>] napi_gro_receive+0xc7/0xcf Sep 11 21:31:10 Tower2 kernel: [<c128f0ee>] ? __alloc_skb+0x53/0xf1 Sep 11 21:31:10 Tower2 kernel: [<f84d5651>] e1000_receive_skb+0x36/0x3b [e1000] Sep 11 21:31:10 Tower2 kernel: [<f84d5d79>] e1000_clean_rx_irq+0x291/0x32c [e1000] Sep 11 21:31:10 Tower2 kernel: [<f84d8926>] e1000_clean+0x3c/0x18f [e1000] Sep 11 21:31:10 Tower2 kernel: [<c1295022>] net_rx_action+0x59/0x12a Sep 11 21:31:10 Tower2 kernel: [<c102ccce>] __do_softirq+0x6b/0xe5 Sep 11 21:31:10 Tower2 kernel: [<c102cc63>] ? irq_enter+0x3c/0x3c Sep 11 21:31:10 Tower2 kernel: <IRQ> [<c102cb21>] ? irq_exit+0x32/0x53 Sep 11 21:31:10 Tower2 kernel: [<c100360b>] ? do_IRQ+0x7c/0x90 Sep 11 21:31:10 Tower2 kernel: [<c130b8a9>] ? common_interrupt+0x29/0x30 Sep 11 21:31:10 Tower2 kernel: [<c1007e14>] ? default_idle+0x2e/0x43 Sep 11 21:31:10 Tower2 kernel: [<c1001a60>] ? cpu_idle+0x3a/0x52 Sep 11 21:31:10 Tower2 kernel: [<c1306753>] ? start_secondary+0xad/0xaf Sep 11 21:31:10 Tower2 kernel: Mem-Info: Sep 11 21:31:10 Tower2 kernel: DMA per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: Normal per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 186, btch: 31 usd: 23 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 186, btch: 31 usd: 177 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 186, btch: 31 usd: 154 Sep 11 21:31:10 Tower2 kernel: HighMem per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 186, btch: 31 usd: 121 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 186, btch: 31 usd: 133 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 186, btch: 31 usd: 146 Sep 11 21:31:10 Tower2 kernel: active_anon:3358 inactive_anon:41 isolated_anon:0 Sep 11 21:31:10 Tower2 kernel: active_file:63400 inactive_file:1029066 isolated_file:0 Sep 11 21:31:10 Tower2 kernel: unevictable:49651 dirty:0 writeback:0 unstable:0 Sep 11 21:31:10 Tower2 kernel: free:850106 slab_reclaimable:27057 slab_unreclaimable:4848 Sep 11 21:31:10 Tower2 kernel: mapped:2150 shmem:62 pagetables:158 bounce:0 Sep 11 21:31:10 Tower2 kernel: DMA free:3692kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:2316kB inactive_file:2484kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15776kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:4364kB slab_unreclaimable:3016kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 869 8104 8104 Sep 11 21:31:10 Tower2 kernel: Normal free:78328kB min:3736kB low:4668kB high:5604kB active_anon:0kB inactive_anon:0kB active_file:220896kB inactive_file:220976kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:890008kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:103864kB slab_unreclaimable:16376kB kernel_stack:784kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 0 57884 57884 Sep 11 21:31:10 Tower2 kernel: HighMem free:3318404kB min:512kB low:8288kB high:16068kB active_anon:13432kB inactive_anon:164kB active_file:30388kB inactive_file:3892804kB unevictable:198604kB isolated(anon):0kB isolated(file):0kB present:7409192kB mlocked:0kB dirty:0kB writeback:0kB mapped:8596kB shmem:248kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:632kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 0 0 0 Sep 11 21:31:10 Tower2 kernel: DMA: 173*4kB 131*8kB 68*16kB 27*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3692kB Sep 11 21:31:10 Tower2 kernel: Normal: 10172*4kB 4562*8kB 70*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 78304kB Sep 11 21:31:10 Tower2 kernel: HighMem: 14893*4kB 104434*8kB 76666*16kB 30467*32kB 3245*64kB 68*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 1*4096kB = 3318404kB Sep 11 21:31:10 Tower2 kernel: 1142214 total pagecache pages Sep 11 21:31:10 Tower2 kernel: 0 pages in swap cache Sep 11 21:31:10 Tower2 kernel: Swap cache stats: add 0, delete 0, find 0/0 Sep 11 21:31:10 Tower2 kernel: Free swap = 0kB Sep 11 21:31:10 Tower2 kernel: Total swap = 0kB Sep 11 21:31:10 Tower2 kernel: 2228208 pages RAM Sep 11 21:31:10 Tower2 kernel: 1999874 pages HighMem Sep 11 21:31:10 Tower2 kernel: 150938 pages reserved Sep 11 21:31:10 Tower2 kernel: 1017284 pages shared Sep 11 21:31:10 Tower2 kernel: 211216 pages non-shared Sep 11 21:31:32 Tower2 kernel: kworker/0:1: page allocation failure: order:4, mode:0x4020 Would someone please look over the attached syslog, & maybe give me a clue as to what happened & how to fix it?? Thanks... page allocation failure's typically indicate you've run out of memory. Quote Link to comment
mikejp Posted September 12, 2011 Share Posted September 12, 2011 Good Morning, I got up this morning & checked my server, as I started a parity check before bed. I discovered the following error repeating itself at the end of my syslog: Sep 11 21:31:10 Tower2 kernel: kworker/0:1: page allocation failure: order:4, mode:0x4020 Sep 11 21:31:10 Tower2 kernel: Pid: 0, comm: kworker/0:1 Not tainted 3.0.3-unRAID #7 Sep 11 21:31:10 Tower2 kernel: Call Trace: Sep 11 21:31:10 Tower2 kernel: [<c105f857>] warn_alloc_failed+0xb2/0xc4 Sep 11 21:31:10 Tower2 kernel: [<c105ffc2>] __alloc_pages_nodemask+0x456/0x47f Sep 11 21:31:10 Tower2 kernel: [<c106003f>] __get_free_pages+0xf/0x21 Sep 11 21:31:10 Tower2 kernel: [<c107d6cd>] __kmalloc+0x28/0xff Sep 11 21:31:10 Tower2 kernel: [<c128e974>] pskb_expand_head+0xcb/0x1f0 Sep 11 21:31:10 Tower2 kernel: [<c128ee08>] __pskb_pull_tail+0x41/0x21f Sep 11 21:31:10 Tower2 kernel: [<c1295b6c>] dev_hard_start_xmit+0x204/0x31c Sep 11 21:31:10 Tower2 kernel: [<c12a4466>] sch_direct_xmit+0x50/0x137 Sep 11 21:31:10 Tower2 kernel: [<c1295d82>] dev_queue_xmit+0xfe/0x274 Sep 11 21:31:10 Tower2 kernel: [<c12b0127>] ip_finish_output+0x227/0x262 Sep 11 21:31:10 Tower2 kernel: [<c12b01c6>] ip_output+0x64/0x68 Sep 11 21:31:10 Tower2 kernel: [<c12adf4d>] ip_local_out+0x57/0x5b Sep 11 21:31:10 Tower2 kernel: [<c12afb5a>] ip_queue_xmit+0x2a5/0x2f2 Sep 11 21:31:10 Tower2 kernel: [<c12beee8>] tcp_transmit_skb+0x4d7/0x50d Sep 11 21:31:10 Tower2 kernel: [<c12c11f7>] tcp_write_xmit+0x2f9/0x3d7 Sep 11 21:31:10 Tower2 kernel: [<c12c1319>] __tcp_push_pending_frames+0x18/0x6f Sep 11 21:31:10 Tower2 kernel: [<c12bdfc9>] tcp_rcv_established+0x501/0x578 Sep 11 21:31:10 Tower2 kernel: [<c12c33b5>] tcp_v4_do_rcv+0x46/0x137 Sep 11 21:31:10 Tower2 kernel: [<c12c386c>] tcp_v4_rcv+0x3c6/0x647 Sep 11 21:31:10 Tower2 kernel: [<c12ac081>] ip_local_deliver_finish+0x93/0x158 Sep 11 21:31:10 Tower2 kernel: [<c12ac172>] ip_local_deliver+0x2c/0x2f Sep 11 21:31:10 Tower2 kernel: [<c12abd8b>] ip_rcv_finish+0x263/0x28b Sep 11 21:31:10 Tower2 kernel: [<c12abfbb>] ip_rcv+0x208/0x23b Sep 11 21:31:10 Tower2 kernel: [<c1293604>] __netif_receive_skb+0x234/0x25a Sep 11 21:31:10 Tower2 kernel: [<c1294a5f>] netif_receive_skb+0x5d/0x63 Sep 11 21:31:10 Tower2 kernel: [<c1294b1c>] napi_skb_finish+0x1e/0x34 Sep 11 21:31:10 Tower2 kernel: [<c1294f4c>] napi_gro_receive+0xc7/0xcf Sep 11 21:31:10 Tower2 kernel: [<c128f0ee>] ? __alloc_skb+0x53/0xf1 Sep 11 21:31:10 Tower2 kernel: [<f84d5651>] e1000_receive_skb+0x36/0x3b [e1000] Sep 11 21:31:10 Tower2 kernel: [<f84d5d79>] e1000_clean_rx_irq+0x291/0x32c [e1000] Sep 11 21:31:10 Tower2 kernel: [<f84d8926>] e1000_clean+0x3c/0x18f [e1000] Sep 11 21:31:10 Tower2 kernel: [<c1295022>] net_rx_action+0x59/0x12a Sep 11 21:31:10 Tower2 kernel: [<c102ccce>] __do_softirq+0x6b/0xe5 Sep 11 21:31:10 Tower2 kernel: [<c102cc63>] ? irq_enter+0x3c/0x3c Sep 11 21:31:10 Tower2 kernel: <IRQ> [<c102cb21>] ? irq_exit+0x32/0x53 Sep 11 21:31:10 Tower2 kernel: [<c100360b>] ? do_IRQ+0x7c/0x90 Sep 11 21:31:10 Tower2 kernel: [<c130b8a9>] ? common_interrupt+0x29/0x30 Sep 11 21:31:10 Tower2 kernel: [<c1007e14>] ? default_idle+0x2e/0x43 Sep 11 21:31:10 Tower2 kernel: [<c1001a60>] ? cpu_idle+0x3a/0x52 Sep 11 21:31:10 Tower2 kernel: [<c1306753>] ? start_secondary+0xad/0xaf Sep 11 21:31:10 Tower2 kernel: Mem-Info: Sep 11 21:31:10 Tower2 kernel: DMA per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 0, btch: 1 usd: 0 Sep 11 21:31:10 Tower2 kernel: Normal per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 186, btch: 31 usd: 23 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 186, btch: 31 usd: 177 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 186, btch: 31 usd: 154 Sep 11 21:31:10 Tower2 kernel: HighMem per-cpu: Sep 11 21:31:10 Tower2 kernel: CPU 0: hi: 186, btch: 31 usd: 121 Sep 11 21:31:10 Tower2 kernel: CPU 1: hi: 186, btch: 31 usd: 133 Sep 11 21:31:10 Tower2 kernel: CPU 2: hi: 186, btch: 31 usd: 146 Sep 11 21:31:10 Tower2 kernel: active_anon:3358 inactive_anon:41 isolated_anon:0 Sep 11 21:31:10 Tower2 kernel: active_file:63400 inactive_file:1029066 isolated_file:0 Sep 11 21:31:10 Tower2 kernel: unevictable:49651 dirty:0 writeback:0 unstable:0 Sep 11 21:31:10 Tower2 kernel: free:850106 slab_reclaimable:27057 slab_unreclaimable:4848 Sep 11 21:31:10 Tower2 kernel: mapped:2150 shmem:62 pagetables:158 bounce:0 Sep 11 21:31:10 Tower2 kernel: DMA free:3692kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:2316kB inactive_file:2484kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15776kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:4364kB slab_unreclaimable:3016kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 869 8104 8104 Sep 11 21:31:10 Tower2 kernel: Normal free:78328kB min:3736kB low:4668kB high:5604kB active_anon:0kB inactive_anon:0kB active_file:220896kB inactive_file:220976kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:890008kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:103864kB slab_unreclaimable:16376kB kernel_stack:784kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 0 57884 57884 Sep 11 21:31:10 Tower2 kernel: HighMem free:3318404kB min:512kB low:8288kB high:16068kB active_anon:13432kB inactive_anon:164kB active_file:30388kB inactive_file:3892804kB unevictable:198604kB isolated(anon):0kB isolated(file):0kB present:7409192kB mlocked:0kB dirty:0kB writeback:0kB mapped:8596kB shmem:248kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:632kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Sep 11 21:31:10 Tower2 kernel: lowmem_reserve[]: 0 0 0 0 Sep 11 21:31:10 Tower2 kernel: DMA: 173*4kB 131*8kB 68*16kB 27*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3692kB Sep 11 21:31:10 Tower2 kernel: Normal: 10172*4kB 4562*8kB 70*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 78304kB Sep 11 21:31:10 Tower2 kernel: HighMem: 14893*4kB 104434*8kB 76666*16kB 30467*32kB 3245*64kB 68*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 1*4096kB = 3318404kB Sep 11 21:31:10 Tower2 kernel: 1142214 total pagecache pages Sep 11 21:31:10 Tower2 kernel: 0 pages in swap cache Sep 11 21:31:10 Tower2 kernel: Swap cache stats: add 0, delete 0, find 0/0 Sep 11 21:31:10 Tower2 kernel: Free swap = 0kB Sep 11 21:31:10 Tower2 kernel: Total swap = 0kB Sep 11 21:31:10 Tower2 kernel: 2228208 pages RAM Sep 11 21:31:10 Tower2 kernel: 1999874 pages HighMem Sep 11 21:31:10 Tower2 kernel: 150938 pages reserved Sep 11 21:31:10 Tower2 kernel: 1017284 pages shared Sep 11 21:31:10 Tower2 kernel: 211216 pages non-shared Sep 11 21:31:32 Tower2 kernel: kworker/0:1: page allocation failure: order:4, mode:0x4020 Would someone please look over the attached syslog, & maybe give me a clue as to what happened & how to fix it?? Thanks... page allocation failure's typically indicate you've run out of memory. Thanks for the response JoeL... I've been playing around with the "Tunables" on the Disk Settings page... probably got over zealous with my "tuning" With 8GB of ram, I didn't think I would run into a memory shortage. Are there any "magic numbers" that help here? Thanks again Quote Link to comment
numanuma Posted September 12, 2011 Share Posted September 12, 2011 I was just about to shutdown my unraid 5 b12 box when i saw a red indicator next to disk2, checking the log shows this error Sep 12 16:33:47 Tower last message repeated 3 times Sep 12 16:33:49 Tower emhttp: mdcmd: write: Input/output error Sep 12 16:33:49 Tower kernel: mdcmd (4233): spindown 2 Sep 12 16:33:49 Tower kernel: md: disk2: ATA_OP e0 ioctl error: -5 Sep 12 16:33:55 Tower emhttp: Spinning up all drives... Sep 12 16:33:55 Tower kernel: mdcmd (4234): spinup 0 Sep 12 16:33:55 Tower kernel: mdcmd (4235): spinup 1 Sep 12 16:33:55 Tower kernel: mdcmd (4236): spinup 2 Sep 12 16:33:55 Tower kernel: md: disk2: ATA_OP e3 ioctl error: -5 Sep 12 16:33:56 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO What's happened to my hitachi drive? I've still yet to preclear it to sector 64, would that fix it? thanks! Quote Link to comment
Joe L. Posted September 12, 2011 Share Posted September 12, 2011 If it is red, a "write" to it failed at some point in the past. See the wiki for how to re-construct the drive that is no longer up-to-date (since the write failed) The disk may have failed, or you might have a loose cable, or something else entirely. Quote Link to comment
generalz Posted September 12, 2011 Share Posted September 12, 2011 If it is red, a "write" to it failed at some point in the past. See the wiki for how to re-construct the drive that is no longer up-to-date (since the write failed) The disk may have failed, or you might have a loose cable, or something else entirely. or in my case spin downs are causing the similar problem. "md: disk2: ATA_OP e0 ioctl error: -22" http://lime-technology.com/forum/index.php?topic=15221.0 Quote Link to comment
davekeel Posted September 12, 2011 Share Posted September 12, 2011 Sadly, Beta 12a not working for me…. Same problems as I had with beta10. Loose my eth0. Flip back to Beta12 and all works fine When in Beta12, ifconfig gets me: eth0 Link encap:Ethernet HWaddr 5c:d9:98:4a:14:7f inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10081 errors:0 dropped:0 overruns:0 frame:0 TX packets:9716 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1828686 (1.7 MiB) TX bytes:2006905 (1.9 MiB) Interrupt:19 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:460 errors:0 dropped:0 overruns:0 frame:0 TX packets:460 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:72585 (70.8 KiB) TX bytes:72585 (70.8 KiB) When in Beta12a , eth0 simply doesn’t show – and I can’t “see” unRaid from my Mac or PC workstation Modprobe r8168 returns “FATAL: Module r8168 not found” in 12 and no response in 12a (but eth0 remains lost) logfile attached Network card is Dlink DGE-528T (card was on recommended list when I built my server) Any chance that network access will be fixed for Beta13? Looking through your syslog it seems that unRaid loads the r8168 Module which seems to be for PCIe NIC's, but yours is a PCI card so in my opinion teh r8169 Module would be the right choice. Are you able to remove the r8168 module and then loading r8169, both must included in 12a. Thanks for feedback - but not sure I quite understand. Re "remove the R8168 module" .. do you mean for me to remove this from the unRaid package? (in which case I would not know where to start to do this.. will need a bit of help/advice) or do you mean for me to remove the card (in which case I can't really do this easily .. its a big job due to the size/location of my server .. if I am going to access and strip down the server then I'd probably rather simply replace the PCI NIC card with one that you guys tell me will work!) Sorry to be a bit dense - but don't quite understand your advice. Thanks Quote Link to comment
Auggie Posted September 12, 2011 Share Posted September 12, 2011 Anyhow, I let it build parity on the new drive, then when completed immediately performed a Parity Check (correction enabled). Got 406 errors. That's not good. Its in the process of performing a second Parity Check, but I had just thought about the fact that I was able to still access my server during the actual parity build as well as parity check and I'm not sure I was able to do this under version 4 but now I'm wondering if accessing the shares while parity build/check was in progress should not have been allowed. That should definitely work and not cause any parity issues, but I will labor to try and reproduce this tomorrow on Labor Day. Don't happen to still have the syslog do you? During this second Parity Check I'm definitely not going to access the shares whatsoever (I hadn't stopped the array before commencing the second Parity Check) and see if any errors result. Try both ways please, and if you see sync errors please capture the system log. A follow up on this issue: I didn't want to spend another 3+ days trying to recreate errors when upgrading a parity drive to 3TB, but I went ahead and ran the server while performing intensive disk operations, to include SMB read/writes, NFS read/writes (there appears to be a bug preventing me from doing a file transfer to a user share via NFS, but I can modify and delete existing files) and even command line transfers; many times concurrently. I moved around roughly 3-4TB of data and then performed a Parity Check with no errors. I then proceeded to upgrade two of my data disks to 3TB, but never once allowing access to the server during this process. Performed Parity Checks after data was rebuilt on each drive and after everything was done, there were zero errors to report. So at this time, there appears to be some bugs in the parity drive rebuild and/or parity check while file/folder read/writes are occurring simultaneously as I have encountered no issues otherwise. Quote Link to comment
capler Posted September 12, 2011 Share Posted September 12, 2011 So I need reports from you guys using Realtek chips - as if I have to ask Just tried beta12a after using beta12. Unfortunately my write speed has dropped significantly with this release [EDIT: I've checked and my wiring is not at fault]. Now I'm getting a write speed of only 8 MB/s max when transferring a 1.5Gb file. I'm guessing it's because of the new Realtek driver in this release. My network card is Gigabit capable (and speed was indeed Gigabit on release 12). My NIC is a PCI Tenda Gigabit TEL9901G which utilises a Realtek r8169 chip. Ok, it's conclusive - the problem is with this release afterall - see my findings report below. My Gigabit NIC is still only getting 100MB/s and I've noticed that WOL isn't working either which means I can't automatically save energy using the S3 scripts because the server no longer wakes when I send a magic packet. After conducting various hardware tests, I've localised the problem down to this beta12a release. The issue is not the cabling (tried 4, all connected to different switch ports) or my Switch (tried power-cycling it), or my PCI slot (I've tried 3). My Findings: The only thing I've changed is the bzroot and bzimage files between boots... beta12a - no gigabit (100Mb/s is my max speed) and WOL doesn't work beta12 - gigabit speed & WOL working beta11 - gigabit speed & WOL working beta10 - this NIC doesn't work at all with any drivers beta9 - gigabit speed & WOL working beta6a - gigabit speed & WOL working Syslog & ethtool & ifconfig & lsmod reports attached for all above betas. One related thing I've noticed with beta12a: it appears to try to make a Gigabit connection when unraid is booted (I notice the Gigabit light on the NIC blinks just a few times, see the the sequential "eth0: link up" and "eth0: link down" messages in the syslog) before falling back to a permanent 100Mb/s speed. syslogs.zip ethtool_ifconfig_lsmod_reports.zip Quote Link to comment
Shigo_Naito Posted September 12, 2011 Share Posted September 12, 2011 Can somone please help me with my upgrade from 5b6a to 5b12a. I replaced the correct files on the flash and the webgui loaded. The problem is that unraid sees all my WD 2tb drives as unknown formats. I have included the first part of my vary large syslog, at the end of the first part it looks like command keep on reapeating and continus throw most of the last part of the sys log. Any help would be wonderful. System_Log1.txt Quote Link to comment
dgaschk Posted September 12, 2011 Share Posted September 12, 2011 Can somone please help me with my upgrade from 5b6a to 5b12a. I replaced the correct files on the flash and the webgui loaded. The problem is that unraid sees all my WD 2tb drives as unknown formats. I have included the first part of my vary large syslog, at the end of the first part it looks like command keep on reapeating and continus throw most of the last part of the sys log. Any help would be wonderful. Zip the entire syslog. Quote Link to comment
Shigo_Naito Posted September 12, 2011 Share Posted September 12, 2011 Here it is System_Log.zip Quote Link to comment
PeterB Posted September 13, 2011 Share Posted September 13, 2011 I am experiencing a problem which I can characterize by copying a directory containing a set of .flac files from a disk share on the unRAID server, to a local disk on an Ubuntu desktop. The full set of 50 files is about 1.4GB. When I perform the copy, it hangs after a few megabytes - not always in the same place. I guess that the problem is much more general than this, but these are the circumstances where I first encountered the problem. Playing the same set of files, via SqueezeBoxServer running on the unRAID server, does not cause any apparent problem. Accessing and playing large video files (mainly .mkv and .iso) from my Popcorn media players does not exhibit any problem either. At first, I suspected that my data may be corrupt, but I don't believe that this is the case. If I revert to beta11, the copy completes perfectly. What's more intriguing is that non-exhaustive testing seems to indicate that if I upgrade the unRAID server to b12 or b12a, without rebooting the Ubuntu client, then the copy will complete. However, after rebooting the client, when using b12 or b12a the copy fails again. When the copy fails, the Nautilus file manager running on the Ubuntu client locks up, requiring a reboot of the client. I am using nfs almost exclusively - the only time I use smb is to access the unRAID flash drive from Ubuntu. I can see nothing in the logfiles which would seem to relate to the failed copy. I attach logfiles from a succesful b11 copy, and a failed b12a copy. syslogb11.zip syslogb12afail.zip Quote Link to comment
dgaschk Posted September 13, 2011 Share Posted September 13, 2011 Try requesting various versions of NFS at the client. Quote Link to comment
PeterB Posted September 13, 2011 Share Posted September 13, 2011 Try requesting various versions of NFS at the client. I discovered, a long time ago, that unRAID only supports nfs3, not nfs4 - although the only indication was frequent log messages about version 4 not being recognised. I did try re-enabling nfs4 with unRAID b12, wondering whether version 4 support had been introduced with the v3 kernel. However, the log messages returned, so I went back to forcing nfs3 on the client. No, I am convinced that something else has changed (possibly nfs related) in the latest version of unRAID - but it doesn't appear to be anything to do with support of the various versions of nfs. Quote Link to comment
greybeard Posted September 13, 2011 Share Posted September 13, 2011 So at this time, there appears to be some bugs in the parity drive rebuild and/or parity check while file/folder read/writes are occurring simultaneously as I have encountered no issues otherwise. Do you have any 2 TB Samsung F4 HD204UI drives in your array? If so, has the firmware been updated? Could be completely unrelated but is something to check. Quote Link to comment
Shigo_Naito Posted September 13, 2011 Share Posted September 13, 2011 Can somone please help me with my upgrade from 5b6a to 5b12a. I replaced the correct files on the flash and the webgui loaded. The problem is that unraid sees all my WD 2tb drives as unknown formats. I have included the first part of my vary large syslog, at the end of the first part it looks like command keep on reapeating and continus throw most of the last part of the sys log. Any help would be wonderful. Any Ideas? Additional Info: Supermicro MBD-X8SIL-F-O with an i3 and 4gb of Kingston memory Supermicro AOC-SASLP-MV8 SAS card Corsair Professional Series HX750 System_Log.zip Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.