jdog09

It has been running perfect and none of the LinkUp/Down messages in the log since 7/7. If I tried the other build, usually would be hosed up before it could complete a parity check on 9TB.

It has been longer than any other after 12a release and still stable on the RealTek Issue....

uRaid 5.0rc3 can't even get through a parity check before having an upstable NIC connection.. This is a trace from rolling back to Beta 14.. Last one still works.. un 3 18:35:31 stadiumNAS kernel: ------------[ cut here ]------------ Jun 3 18:35:31 stadiumNAS kernel: WARNING: at net/core/dev.c:3827 net_rx_action+0x78/0x12a() Jun 3 18:35:31 stadiumNAS kernel: Hardware name: EP45-UD3P Jun 3 18:35:31 stadiumNAS kernel: Modules linked in: md_mod xor pata_jmicron jmicron r8169 ahci libahci i2c_i801 i2c_core [last unloaded: md_mod] Jun 3 18:35:31 stadiumNAS kernel: Pid: 1645, comm: nfsd Tainted: G W 3.1.1-unRAID #1 Jun 3 18:35:31 stadiumNAS kernel: Call Trace: Jun 3 18:35:31 stadiumNAS kernel: [] warn_slowpath_common+0x65/0x7a Jun 3 18:35:31 stadiumNAS kernel: [] ? net_rx_action+0x78/0x12a Jun 3 18:35:31 stadiumNAS kernel: [] warn_slowpath_null+0xf/0x13 Jun 3 18:35:31 stadiumNAS kernel: [] net_rx_action+0x78/0x12a Jun 3 18:35:31 stadiumNAS kernel: [] __do_softirq+0x6b/0xe5 Jun 3 18:35:31 stadiumNAS kernel: [] ? irq_enter+0x3c/0x3c Jun 3 18:35:31 stadiumNAS kernel: [] ? irq_exit+0x32/0x53 Jun 3 18:35:31 stadiumNAS kernel: [] ? do_IRQ+0x7c/0x90 Jun 3 18:35:31 stadiumNAS kernel: [] ? common_interrupt+0x29/0x30 Jun 3 18:35:31 stadiumNAS kernel: [] ? csum_partial_copy_generic+0x6c/0x100 Jun 3 18:35:31 stadiumNAS kernel: [] ? tcp_sendmsg+0x2a3/0x915 Jun 3 18:35:31 stadiumNAS kernel: [] ? inet_sendmsg+0x6f/0x78 Jun 3 18:35:31 stadiumNAS kernel: [] ? sock_sendmsg+0xa5/0xbb Jun 3 18:35:31 stadiumNAS kernel: [] ? blk_finish_plug+0xd/0x28 Jun 3 18:35:31 stadiumNAS kernel: [] ? do_sync_readv_writev+0x84/0xb7 Jun 3 18:35:31 stadiumNAS kernel: [] ? fsnotify+0x1ad/0x1c7 Jun 3 18:35:31 stadiumNAS kernel: [] ? kernel_sendmsg+0x28/0x37 Jun 3 18:35:31 stadiumNAS kernel: [] ? sock_no_sendpage+0x45/0x58 Jun 3 18:35:31 stadiumNAS kernel: [] ? tcp_sendpage+0x32/0x66 Jun 3 18:35:31 stadiumNAS kernel: [] ? do_tcp_sendpages+0x490/0x490 Jun 3 18:35:31 stadiumNAS kernel: [] ? inet_sendpage+0x82/0x9c Jun 3 18:35:31 stadiumNAS kernel: [] ? inet_dgram_connect+0x5e/0x5e Jun 3 18:35:31 stadiumNAS kernel: [] ? kernel_sendpage+0x1a/0x2d Jun 3 18:35:31 stadiumNAS kernel: [] ? svc_send_common+0x41/0xdf Jun 3 18:35:31 stadiumNAS kernel: [] ? svc_sendto+0x112/0x15f Jun 3 18:35:31 stadiumNAS kernel: [] ? nfsd_cache_update+0x88/0x10f Jun 3 18:35:31 stadiumNAS kernel: [] ? nfs3svc_encode_renameres+0x3b/0x3b Jun 3 18:35:31 stadiumNAS kernel: [] ? nfsd_cache_update+0xb3/0x10f Jun 3 18:35:31 stadiumNAS kernel: [] ? auth_domain_put+0x10/0x42 Jun 3 18:35:31 stadiumNAS kernel: [] ? svcauth_unix_release+0x15/0x4d Jun 3 18:35:31 stadiumNAS kernel: [] ? svc_authorise+0x28/0x2e Jun 3 18:35:31 stadiumNAS kernel: [] ? svc_tcp_sendto+0x32/0x83 Jun 3 18:35:31 stadiumNAS kernel: [] ? svc_send+0x53/0x88 Jun 3 18:35:31 stadiumNAS kernel: [] ? svc_process+0xff/0x112 Jun 3 18:35:31 stadiumNAS kernel: [] ? nfsd+0xd1/0x108 Jun 3 18:35:31 stadiumNAS kernel: [] ? nfsd_svc+0x131/0x131 Jun 3 18:35:31 stadiumNAS kernel: [] ? kthread+0x62/0x67 Jun 3 18:35:31 stadiumNAS kernel: [] ? kthread_worker_fn+0x10a/0x10a Jun 3 18:35:31 stadiumNAS kernel: [] ? kernel_thread_helper+0x6/0xd Jun 3 18:35:31 stadiumNAS kernel: ---[ end trace 85ce947744be7903 ]--- Jun 3 18:35:31 stadiumNAS kernel: r8169 0000:04:00.0: eth0: link up

Here is the Syslog.. Didn't even get through the parity check... A lot of R8139 Messages Unraiderro20120601.txt

I am down again too... When I get home and physically reboot, I can take a picture of stack trace on Monitor. I will open a tail -f on Syslog and let it run....

Likewise, RC14 worked like a champ... I will snap a picture of the Stack traces on the monitor next time it goes toes up... I just rebooted so it will be a few days..

Any update on the NFS issue? I have used Unraid for a couple of years as a NFS store for VMWare and XenCenter. I can't keep a NFS from going stale. Usually 12-24 hours something happens. I drop and remount the client (XenCenter) and I can restart my VM. The NFS mount point on Private Only.. NO SMB or AFP enabled. Private Security Rule 192.168.1.199(rw,no_root_squash) Any other ideas..

There is some type of problem with NFS Stale issues on client side. I have used VMWare and XenServer as NFS clients for the past couple of years and NFS has been flawless. Now with 5.0 it is too unstable. Anyone have any suggestions?

MTA is exchange 2007.. What are you testing with? I always received the emails from unraid_notify.. Just no body.. Subject only..

If you are going to stick with unraid_notify, please throw a \n not a \r\n after the existing one in your packaging of your tar ball.

All three addresses are set to the same Email Address....

I figure this one out... It is a problem withe unraid_notify script. I added an additional \n after subject on output creation and all is good now.

Getting this message alot... Sep 5 11:58:20 stadiumNAS unmenu[13488]: bad method - 159 174 1313 940 10 2 96 0 0 940 940159- Sep 5 11:59:01 stadiumNAS last message repeated 106 times Sep 5 12:00:07 stadiumNAS last message repeated 211 times Any ideas?

Ant, Looks like my tweak to remove AuthMethod, etc from the ssmtp.conf files works and I get an email on my internal Exchange MTA. However, on-boot I see a message generated and accepted from my MTA but no message delivered to my mailbox. I run the Configuration Test and do immediately receive the test message with Subject and Body. Next I go to Notification screen and push the test and immediately receive an email with Subject only. However I see in the log where the unraid information was collected.

Yes, I am talking about LOGIN/MD5. Since I host my own MailServer domain and Unraid is inside my FW no need to Auth. Others may have a similar request. Keep up the good work.

Works fine but I have an internal Exchange Server that doesn't have Auth turned on. I started to update all the php pages to add a "None" for Authentication type and started testing. SSMTP works fine with no-auth as long as AuthMethod is not in the conf file. Unfortunately, the design of the Web Form drives off that value and once you set it and remove from config file you cannot change it back. ;-) After I figured that out, I just decided to erase AuthMethod, AuthLogin, AuthPassword from default config file. I really like your Look and Feel and the Stats page. Nice work.

Having trouble with AFP Time Machine Created/Cleaned up/Rebooted, Upgraded and still get this error: p 3 21:13:44 stadiumNAS emhttp: shcmd (111): killall -HUP smbd Sep 3 21:13:44 stadiumNAS emhttp: shcmd (112): ps axc | grep -q rpc.mountd Sep 3 21:13:44 stadiumNAS emhttp: Restart NFS... Sep 3 21:13:44 stadiumNAS emhttp: shcmd (113): exportfs -ra |& logger Sep 3 21:13:44 stadiumNAS emhttp: Restart AFP... Sep 3 21:13:44 stadiumNAS emhttp: shcmd (114): killall -HUP afpd Sep 3 21:13:44 stadiumNAS emhttp: shcmd (115): cp /etc/avahi/services/afp.service- /etc/avahi/services/afp.service Sep 3 21:13:44 stadiumNAS avahi-daemon[5393]: Files changed, reloading. Sep 3 21:13:44 stadiumNAS avahi-daemon[5393]: Service group file /services/afp.service changed, reloading. Sep 3 21:13:44 stadiumNAS emhttp: shcmd (116): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Sep 3 21:13:44 stadiumNAS avahi-daemon[5393]: Files changed, reloading. Sep 3 21:13:44 stadiumNAS avahi-daemon[5393]: Service group file /services/smb.service changed, reloading. Sep 3 21:13:44 stadiumNAS emhttp: shcmd (117): /usr/local/sbin/emhttp_event svcs_restarted Sep 3 21:13:44 stadiumNAS emhttp_event: svcs_restarted Sep 3 21:13:45 stadiumNAS avahi-daemon[5393]: Service "stadiumNAS" (/services/afp.service) successfully established. Sep 3 21:13:45 stadiumNAS avahi-daemon[5393]: Service "stadiumNAS-SMB" (/services/smb.service) successfully established. Sep 3 21:13:45 stadiumNAS kernel: mdcmd (50): spindown 1 Sep 3 21:13:54 stadiumNAS emhttp: shcmd (118): :>/etc/samba/smb-shares.conf Sep 3 21:13:54 stadiumNAS emhttp: shcmd (119): cp /etc/exports- /etc/exports Sep 3 21:13:54 stadiumNAS emhttp: shcmd (120): cp /etc/netatalk/AppleVolumes.default- /etc/netatalk/AppleVolumes.default Sep 3 21:13:54 stadiumNAS shfs/user: duplicate object: /mnt/disk2/./.DS_Store Sep 3 21:13:54 stadiumNAS shfs/user: duplicate object: /mnt/disk3/./.DS_Store Sep 3 21:13:54 stadiumNAS shfs/user: duplicate object: /mnt/disk6/./._.DS_Store Sep 3 21:13:54 stadiumNAS shfs/user: duplicate object: /mnt/disk6/./.DS_Store Sep 3 21:13:54 stadiumNAS emhttp: shcmd (121): echo '/mnt/user/ISOLibrary -async,no_subtree_check,fsid=100 196.196.196.224/27(rw,no_root_squash)' >>/etc/exports Sep 3 21:13:54 stadiumNAS emhttp: shcmd (122): echo '/mnt/user/VMDisk2 -async,no_subtree_check,fsid=101 196.196.196.224/27(rw,no_root_squash)' >>/etc/exports Sep 3 21:13:54 stadiumNAS emhttp: Restart SMB... Sep 3 21:13:54 stadiumNAS emhttp: shcmd (123): killall -HUP smbd Sep 3 21:13:54 stadiumNAS emhttp: shcmd (124): ps axc | grep -q rpc.mountd Sep 3 21:13:54 stadiumNAS emhttp: Restart NFS... Sep 3 21:13:54 stadiumNAS emhttp: shcmd (125): exportfs -ra |& logger Sep 3 21:13:54 stadiumNAS emhttp: Restart AFP... Sep 3 21:13:54 stadiumNAS emhttp: shcmd (126): killall -HUP afpd Sep 3 21:13:54 stadiumNAS emhttp: shcmd (127): cp /etc/avahi/services/afp.service- /etc/avahi/services/afp.service Sep 3 21:13:54 stadiumNAS avahi-daemon[5393]: Files changed, reloading. Sep 3 21:13:54 stadiumNAS avahi-daemon[5393]: Service group file /services/afp.service changed, reloading. Sep 3 21:13:54 stadiumNAS emhttp: shcmd (128): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Sep 3 21:13:54 stadiumNAS avahi-daemon[5393]: Files changed, reloading. Sep 3 21:13:54 stadiumNAS avahi-daemon[5393]: Service group file /services/smb.service changed, reloading. Sep 3 21:13:54 stadiumNAS emhttp: shcmd (129): /usr/local/sbin/emhttp_event svcs_restarted Sep 3 21:13:54 stadiumNAS emhttp_event: svcs_restarted Sep 3 21:13:55 stadiumNAS avahi-daemon[5393]: Service "stadiumNAS" (/services/afp.service) successfully established. Sep 3 21:13:55 stadiumNAS avahi-daemon[5393]: Service "stadiumNAS-SMB" (/services/smb.service) successfully established. Sep 3 21:14:16 stadiumNAS afpd[5697]: dsi_stream_read: len:0, unexpected EOF Sep 3 21:14:43 stadiumNAS cnid_dbd[5725]: Set syslog logging to level: LOG_NOTE Sep 3 21:15:00 stadiumNAS afpd[5746]: dsi_stream_read: len:0, unexpected EOF

Thanks for the help... eth0 Realtek driver problems are gone with the kernel parameter. I did add manually at boot to menu loader and just wanted to confirm for permanent boot that adding to the syslinux.cfg on the same line or a separate line is correct for UnRAID. One Line default menu.c32 menu title Lime Technology LLC prompt 0 timeout 50 label unRAID OS menu default kernel bzimage append initrd=bzroot pcie_aspm=off label Memtest86+ kernel memtest Two Line default menu.c32 menu title Lime Technology LLC prompt 0 timeout 50 label unRAID OS menu default kernel bzimage append initrd=bzroot append pcie_aspm=off label Memtest86+ kernel memtest

Keep seeing issues with the r8169 driver.. Any suggestions. The AFPD error is during a Time Machine Backup.. Might be related to the stability of the eth0 connection. Aug 28 10:14:07 stadiumNAS kernel: r8169 0000:04:00.0: eth0: link up Aug 28 10:14:39 stadiumNAS last message repeated 2 times Aug 28 10:16:24 stadiumNAS last message repeated 3 times Aug 28 10:17:14 stadiumNAS kernel: ------------[ cut here ]------------ Aug 28 10:17:14 stadiumNAS kernel: WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xf8/0x17b() Aug 28 10:17:14 stadiumNAS kernel: Hardware name: EP45-UD3P Aug 28 10:17:14 stadiumNAS kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Aug 28 10:17:14 stadiumNAS kernel: Modules linked in: md_mod xor pata_jmicron i2c_i801 jmicron i2c_core r8169 ahci libahci Aug 28 10:17:14 stadiumNAS kernel: Pid: 0, comm: kworker/0:0 Not tainted 3.0.3-unRAID #3 Aug 28 10:17:14 stadiumNAS kernel: Call Trace: Aug 28 10:17:14 stadiumNAS kernel: [<c10288ac>] warn_slowpath_common+0x65/0x7a Aug 28 10:17:14 stadiumNAS kernel: [<c12c8bf6>] ? dev_watchdog+0xf8/0x17b Aug 28 10:17:14 stadiumNAS kernel: [<c1028925>] warn_slowpath_fmt+0x26/0x2a Aug 28 10:17:14 stadiumNAS kernel: [<c12c8bf6>] dev_watchdog+0xf8/0x17b Aug 28 10:17:14 stadiumNAS kernel: [<c10312ea>] run_timer_softirq+0x10a/0x182 Aug 28 10:17:14 stadiumNAS kernel: [<c12c8afe>] ? __netdev_watchdog_up+0x52/0x52 Aug 28 10:17:14 stadiumNAS kernel: [<c102ccce>] __do_softirq+0x6b/0xe5 Aug 28 10:17:14 stadiumNAS kernel: [<c102cc63>] ? irq_enter+0x3c/0x3c Aug 28 10:17:14 stadiumNAS kernel: <IRQ> [<c102cb21>] ? irq_exit+0x32/0x53 Aug 28 10:17:14 stadiumNAS kernel: [<c1015bbd>] ? smp_apic_timer_interrupt+0x6c/0x7a Aug 28 10:17:14 stadiumNAS kernel: [<c133584a>] ? apic_timer_interrupt+0x2a/0x30 Aug 28 10:17:14 stadiumNAS kernel: [<c104007b>] ? override_creds+0x1f/0x23 Aug 28 10:17:14 stadiumNAS kernel: [<c11dd604>] ? acpi_safe_halt+0x1c/0x2a Aug 28 10:17:14 stadiumNAS kernel: [<c11dd6db>] ? acpi_idle_enter_c1+0x61/0xb1 Aug 28 10:17:14 stadiumNAS kernel: [<c12985da>] ? cpuidle_idle_call+0x6b/0xa1 Aug 28 10:17:14 stadiumNAS kernel: [<c1001a60>] ? cpu_idle+0x3a/0x52 Aug 28 10:17:14 stadiumNAS kernel: [<c1331077>] ? start_secondary+0xad/0xaf Aug 28 10:17:14 stadiumNAS kernel: ---[ end trace 2eed0f0b922db24c ]--- Aug 28 10:17:14 stadiumNAS kernel: r8169 0000:04:00.0: eth0: link up Aug 28 10:17:46 stadiumNAS last message repeated 8 times Aug 28 10:18:49 stadiumNAS last message repeated 16 times Aug 28 10:19:37 stadiumNAS last message repeated 12 times Aug 28 10:19:39 stadiumNAS afpd[18263]: select: Invalid argument Aug 28 10:19:39 stadiumNAS afpd[18263]: dsi_stream_read: len:-1, Invalid argument Aug 28 10:19:39 stadiumNAS afpd[18263]: dsi_stream_receive: invalid packet, fatal Aug 28 10:19:41 stadiumNAS kernel: r8169 0000:04:00.0: eth0: link up Aug 28 10:19:59 stadiumNAS last message repeated 7 times Aug 28 10:20:09 stadiumNAS afpd[18263]: select: Invalid argument Aug 28 10:20:09 stadiumNAS afpd[18263]: dsi_stream_read: len:-1, Invalid argument Aug 28 10:20:09 stadiumNAS afpd[18263]: dsi_stream_receive: invalid packet, fatal Aug 28 10:20:10 stadiumNAS afpd[18263]: =============================================================== Aug 28 10:20:10 stadiumNAS afpd[18263]: INTERNAL ERROR: Signal 11 in pid 18263 (2-2-0-p6) Aug 28 10:20:10 stadiumNAS afpd[18263]: =============================================================== Aug 28 10:20:10 stadiumNAS afpd[18263]: BACKTRACE: 9 stack frames: Aug 28 10:20:10 stadiumNAS afpd[18263]: #0 /usr/sbin/afpd(netatalk_panic+0x2d) [0x8097dfd] Aug 28 10:20:10 stadiumNAS afpd[18263]: #1 /usr/sbin/afpd() [0x8097f6d] Aug 28 10:20:10 stadiumNAS afpd[18263]: #2 [0xb76e4400] Aug 28 10:20:10 stadiumNAS afpd[18263]: #3 /usr/sbin/afpd(dsi_writeinit+0x60) [0x8094600] Aug 28 10:20:10 stadiumNAS afpd[18263]: #4 /usr/sbin/afpd(afp_over_dsi+0x368) [0x80548f8] Aug 28 10:20:10 stadiumNAS afpd[18263]: #5 /usr/sbin/afpd() [0x8053c55] Aug 28 10:20:10 stadiumNAS afpd[18263]: #6 /usr/sbin/afpd(main+0x660) [0x8070bd0] Aug 28 10:20:10 stadiumNAS afpd[18263]: #7 /lib/libc.so.6(__libc_start_main+0xe6) [0xb72cfb86] Aug 28 10:20:10 stadiumNAS afpd[18263]: #8 /usr/sbin/afpd() [0x8053a51] Aug 28 10:20:18 stadiumNAS afpd[18618]: afp_disconnect: primary reconnect failed Aug 28 10:20:19 stadiumNAS afpd[18618]: dsi_stream_read: len:0, unexpected EOF Aug 28 10:20:26 stadiumNAS afpd[18627]: afp_disconnect: primary reconnect failed Aug 28 10:20:28 stadiumNAS afpd[18627]: dsi_stream_read: len:0, unexpected EOF Aug 28 10:20:36 stadiumNAS afpd[18636]: afp_disconnect: primary reconnect failed Aug 28 10:20:40 stadiumNAS afpd[18636]: dsi_stream_read: len:0, unexpected EOF Aug 28 10:20:47 stadiumNAS afpd[18645]: afp_disconnect: primary reconnect failed Aug 28 10:20:47 stadiumNAS afpd[18645]: dsi_stream_read: len:0, unexpected EOF

Bug: I had a password that Contain ")" and "(" The Error code was 2 from the net ads command. Only got the Beta4 to join the domain after changing my Enterprise Domain Admin password without these characters..

I am obviously having a blonde moment.. What is OP? I have figured out how to get bubbaRiad but I am curious to what OP really stands for.... Nice work by the way.. I am new to the unRaid family.. Still testing before I spend countless hours archiving my DVD and Photo Collection.