Discussion stats
Announcements

Reply
Highlighted

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Well it was nowhere near the limit before I upgraded to Lion and I had switched off TM beforehand so no new backups were attempted.

I don't understand why TM had loads of free space before the upgrade yet now has none.

TM is supposed to be able to delete old backups if the disk becomes full.
Message 26 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

SampleX wrote:
Roadfun...

Hitting 'Connect as' just tells me that there was a problem connecting to the server, which may not exist or is unavailable...


I am having the exact same problem as you...have you been able to figure this out yet?
Message 27 of 41
Highlighted
Aspirant

Duo works, NV+ not???

I've a strange problem: I updated my DUO and my NV+. Timemachine has never been used on the DUO, but when I activate it, Lion starts to make its backup on the DUO. I want to use the NV+ as I did before because the DUO is directly connected to the internet, while the NV+ is not. Whatever I try, TM on the NV+ is not working. I deleted al entries on the NV+ in /c/home/ReadyNAS, no change. I renamed ReadyNAS to a temp name, created a new ReadyNAS, set the owner and file permissions correctly, but when I select the NV+, it refuses any connection and reports error 2.

logfiles
the NV+ /var/log/netatalk.log reports:

Jul 23 10:51:41.242002 afpd[2017] {dsi_tcp.c:212} (ISmiley Very HappySI): AFP/TCP session from 192.168.100.111:49477
Jul 23 10:51:41.248976 afpd[2017] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: ReadyNAS
Jul 23 10:51:42.281842 afpd[2017] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Jul 23 10:51:42.297153 afpd[2017] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Jul 23 10:51:42.297473 afpd[2017] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by ReadyNAS
Jul 23 10:51:42.328355 afpd[2017] {volume.c:2129} (W:AFPDaemon): volume "timemachine" does not support Extended Attributes, using ea:ad instead
Jul 23 10:51:42.334387 afpd[2017] {auth.c:948} (N:AFPDaemon): AFP logout by ReadyNAS
Jul 23 10:51:42.335069 afpd[2017] {dsi_stream.c:397} (ESmiley Very HappySI): dsi_stream_read: len:0, unexpected EOF
Jul 23 10:51:42.335329 afpd[2017] {afp_dsi.c:498} (N:AFPDaemon): afp_over_dsi: client logged out, terminating DSI session
Jul 23 10:51:42.337373 afpd[2017] {afp_dsi.c:99} (N:AFPDaemon): AFP statistics: 0.60 KB read, 0.45 KB written
Jul 23 10:51:42.337694 afpd[2017] {dircache.c:615} (I:AFPDaemon): dircache statistics: entries: 0, lookups: 0, hits: 0, misses: 0, added: 0, removed: 0, expunged: 0, evicted: 0


on the DUO (which works), the /var/log/netatalk.log shows:Jul 23 09:57:44.506614 afpd[3692] {main.c:183} (I:AFPDaemon): child[4357]: exited 1
Jul 23 09:57:44.513267 afpd[4358] {dsi_tcp.c:212} (ISmiley Very HappySI): AFP/TCP session from 192.168.100.126:63469
Jul 23 09:57:44.525892 afpd[3692] {main.c:185} (I:AFPDaemon): child[4358]: done
Jul 23 09:57:44.627074 afpd[4359] {dsi_tcp.c:212} (ISmiley Very HappySI): AFP/TCP session from 192.168.100.126:63470
Jul 23 09:57:44.633768 afpd[4359] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: ReadyNAS
Jul 23 09:57:45.900141 afpd[4359] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Jul 23 09:57:45.915030 afpd[4359] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Jul 23 09:57:45.915371 afpd[4359] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by ReadyNAS
Jul 23 09:57:45.953808 afpd[4359] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
NAS-Netgear-Duo:/var/log#

What is wrong???
Message 28 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

hmm gets even more weird: after comparing /etc/passwd, I found a difference in the ReadyNAS definition:

on the working DUO, ReadyNAS is defined as

ReadyNAS:$1$lPjiJh8C$qZ1wCBkVszZZvQ637zrYD.:96:65534::/var/lib/timemachine:/bin/true

on the non working NV+, it is defined as:
ReadyNAS:$1$LVH/Yui8$YYO6Z7E0xkBjrAKV1k1il1:1010:100:franklee@nomail.nl:/var/lib/timemachine:/bin/true

After changing 1010:100 to 96:65534 and removing 'frank lee@nomail.nl', (probably not needed) every things works again.
The question is how did the ReadyNAS entry on the NV+ got a 'normal' user entry in passed, while on the DUO, it seems a system user???
Anyway, maybe it helps to solve some errors for you too, time machine is running now on Lion and SL
Message 29 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Not working for me at all.

It just hangs at "Connecting to server...", can't cancel or anything, have to reboot my machine or disable AFP on ReadyNAS.
When it hangs and I disable AFP, OS X comes back and says the volume is unavailable and gives me the option to ignore or disconnect.

I've tried the DHCAST128 workaround, made no apparent difference.

Ok so there's a nasty bug in afpd (4.1.8-T5) Smiley Indifferent
Jul 23 18:38:25.500075 afpd[6731] {dsi_tcp.c:212} (ISmiley Very HappySI): AFP/TCP session from 192.168.2.30:51074
Jul 23 18:38:25.513121 afpd[5651] {main.c:185} (I:AFPDaemon): child[6731]: done
Jul 23 18:38:33.231517 afpd[6732] {dsi_tcp.c:212} (ISmiley Very HappySI): AFP/TCP session from 192.168.2.30:51075
Jul 23 18:38:33.238331 afpd[6732] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: lasseoe
Jul 23 18:38:34.436648 afpd[6732] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Jul 23 18:38:34.454203 afpd[6732] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Jul 23 18:38:34.454584 afpd[6732] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by lasseoe
Jul 23 18:38:52.259914 afpd[6732] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 23 18:38:52.300856 afpd[6732] {fault.c:122} (SSmiley Very Happyefault): ===============================================================
Jul 23 18:38:52.301217 afpd[6732] {fault.c:123} (SSmiley Very Happyefault): INTERNAL ERROR: Signal 11 in pid 6732 (2-2-0-p5)
Jul 23 18:38:52.301477 afpd[6732] {fault.c:124} (SSmiley Very Happyefault): ===============================================================
Jul 23 18:38:52.309213 afpd[6732] {fault.c:96} (SSmiley Very Happyefault): BACKTRACE: 1 stack frames:
Jul 23 18:38:52.309513 afpd[6732] {fault.c:102} (SSmiley Very Happyefault): #0 [(nil)]
Jul 23 18:38:52.311898 afpd[5651] {main.c:188} (I:AFPDaemon): child[6732]: killed by signal 6
Jul 23 18:38:52.400195 afpd[6733] {dsi_tcp.c:212} (ISmiley Very HappySI): AFP/TCP session from 192.168.2.30:51076
Jul 23 18:38:52.408612 afpd[6733] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: lasseoe
Jul 23 18:38:53.609073 afpd[6733] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Jul 23 18:38:53.626808 afpd[6733] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Jul 23 18:38:53.627189 afpd[6733] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by lasseoe
Jul 23 18:38:53.629754 afpd[6733] {auth.c:677} (N:AFPDaemon): afp_disconnect: trying primary reconnect
Jul 23 18:38:53.630816 afpd[5651] {server_child.c:283} (NSmiley Very Happyefault): Reconnect: no child[6732]
Jul 23 18:38:58.633061 afpd[6733] {auth.c:710} (E:AFPDaemon): afp_disconnect: primary reconnect failed
Jul 23 18:38:58.671457 afpd[6733] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 23 18:38:58.676367 afpd[6733] {fault.c:122} (SSmiley Very Happyefault): ===============================================================
Jul 23 18:38:58.676728 afpd[6733] {fault.c:123} (SSmiley Very Happyefault): INTERNAL ERROR: Signal 11 in pid 6733 (2-2-0-p5)
Jul 23 18:38:58.676968 afpd[6733] {fault.c:124} (SSmiley Very Happyefault): ===============================================================
Jul 23 18:38:58.677930 afpd[6733] {fault.c:96} (SSmiley Very Happyefault): BACKTRACE: 2 stack frames:
Jul 23 18:38:58.678231 afpd[6733] {fault.c:102} (SSmiley Very Happyefault): #0 /lib/libc.so.6(snprintf+0x1c) [0x201d0cd4]
Jul 23 18:38:58.678491 afpd[6733] {fault.c:102} (SSmiley Very Happyefault): #1 /usr/sbin/afpd [0x9a8e5]
Jul 23 18:38:58.681117 afpd[5651] {main.c:188} (I:AFPDaemon): child[6733]: killed by signal 6
Jul 23 18:38:58.784884 afpd[6734] {dsi_tcp.c:212} (ISmiley Very HappySI): AFP/TCP session from 192.168.2.30:51077
Jul 23 18:38:58.791858 afpd[6734] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: lasseoe
Jul 23 18:38:59.970896 afpd[6734] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Jul 23 18:38:59.988491 afpd[6734] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Jul 23 18:38:59.988872 afpd[6734] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by lasseoe
Jul 23 18:38:59.991397 afpd[6734] {auth.c:677} (N:AFPDaemon): afp_disconnect: trying primary reconnect
Jul 23 18:38:59.992279 afpd[5651] {server_child.c:283} (NSmiley Very Happyefault): Reconnect: no child[6733]
Jul 23 18:39:04.993081 afpd[6734] {auth.c:710} (E:AFPDaemon): afp_disconnect: primary reconnect failed
Jul 23 18:39:05.031016 afpd[6734] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Message 30 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Some progress on the segfault in this thread:
viewtopic.php?f=28&t=55205&p=313204#p313204
Message 31 of 41
Highlighted
Guide

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

I have a good old ReadyNas 600 running the latest release running Time Machine on a current OS Mac.
My Lion-based Macbook Air will arrive next week.
Should I apply the current Beta or will there be another update before then? I've been reading the threads here and it sounds as if the cake hasn't fully baked yet. Any thoughts from the Jedis?
Message 32 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

If you are not familiar with command line, don't have SSH installed and don't have the patients to troubleshoot possible issues then I would not install any beta.

On the other hand if you like troubleshooting things and are willing to make changes to config files, then have fun.
Message 33 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

I upgraded both my iMac 27' late 2009 and MBP early 2011, both are working now, including TM. However, the 4.1.8 release is not stable, while on 4.1.7 I never had to reboot the NV+, I need to reboot it once a day. For some reason, TM is not available after a day or so, afp is acting strange (slow or not available). After a reboot, everything is running smoothly again. SMB (CIFS) however is stable, no problems, even when TM requires a reboot to make it available again.
Very strange.....

UPDATE
without any reason, everything seems to be stable again.. TM, CIFS and AFP: no problems anymore, nu clue why since I haven't changed anything, but I don't complain :-)
Message 34 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

I found out the TM function operates normally if my MB is connected by UTP.
When i use the Wifi connection, no TM is available.
Connected by UTP also the normal AFP and CFIS connection is visible, without using the 'connect server' option in the finder.

My TM functions normally now, but of course i like to use it using Wifi, except maybe the first backup after my update of Lion (because of the size).

Hopefully this helps in solving the issues with beta 4.1.8 T5

Grtz, RVE
Message 35 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Morning all

I'd just like to add that this is my experience also....connected from Macbook via ethernet to Gigabit switch to ReadyNAS Duo, running Lion and the latest beta ReadyNAS beta firmware, Time Machine backups performed overnight flawlessly...however as above, my experience prior was that over wifi both AFP and CIFS would be unstable and usable...

Cheers
Message 36 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

WHen I initially purchased my ReadyNAS Duo it was with the express intention of performing Time Machine backups to it from my OS X Snow Leopard laptop. I had similar experiences whereby on a wired connection the backup would run perfectly whereas over an 802.11g wireless connection the backups would never complete. After much debugging and searching online it transpired that the issue lay with my Linksys router, running OpenWRT. The driver for the wireless in that particular model would crap out under high-load on the 2.6.x kernel. I required other features only available in 2.6.x kernel (IPv6, mainly) so regressing to a 2.4.x kernel was not an option for me. I did some research and eventually shelled out for an 802.11n Apple Airport Extreme. Best bit of hardware I've ever bought, simple as that. My backups (up until installing Lion!) ran flawlessly and I get a steady real-world throughput of ~150Mb/s on a 300Mb/s wireless connection.

If you're running OpenWRT (or any similar linux-based wifi/router firmware) I'd look into that as a potential cause.
Message 37 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

..ok..a little further on..

after seeing a post on another thread but talking about the same issues only via wireless TM backup, i changed from wireless N freq to G and as i write the TM is progressing as normal..

..hope that helps someone...
Message 38 of 41
Highlighted
Guide

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Running a good old ReadyNas 600.
Upgraded to latest beta.
Time Machine working fine.
However Finder in Lion will not open CIFS or AFP connections to ReadyNAS by clicking on the icons on the left hand of the finder menu.
Despite what others have said - the only thing that works for me is:
In the Finder menu bar click on Go -> Connect to Server... then enter "smb://(NAS IP Address)/(Sharename)"
I did this with CIFS and AFP both enabled and AFP advertising on Bonjour and Appletalk.
Not ideal, but workable until the next test/final release of T18.
Message 39 of 41
Highlighted
Tutor

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

chankla wrote:
Running a good old ReadyNas 600.
Upgraded to latest beta.
Time Machine working fine.
However Finder in Lion will not open CIFS or AFP connections to ReadyNAS by clicking on the icons on the left hand of the finder menu.
Despite what others have said - the only thing that works for me is:
In the Finder menu bar click on Go -> Connect to Server... then enter "smb://(NAS IP Address)/(Sharename)"
I did this with CIFS and AFP both enabled and AFP advertising on Bonjour and Appletalk.
Not ideal, but workable until the next test/final release of T18.

Can you try restarting Bonjour in FrontView (Services/Discovery)?
Message 40 of 41
Highlighted
Guide

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

turning off all the services and turning them all back on seemed to make things more stable (even after an additional reboot of the entire NAS). So looks like after the upgrade people need to start and stop those services without rebooting the server. It seemed like the Lion OSX machine also needed rebooting to make AFP and CIFS work. It's stable - so trying no to mess with it too much now.
Message 41 of 41