Reply
Highlighted
Aspirant

RAIDiator 4.1.8 - T5 Issues w/Lion

Not sure where to post this since the thread with the beta link is locked:

I installed the RAIDiator 4.1.8 T5 firmware update and I still an having issues with using my ReadyNasDuo as a Time Machine backup location.

I am getting this error "The network backup disk does not support the required AFP features. Open Time Machine preferences to select a different backup disk."

I am happy though that you guys seem on the ball and are rapidly trying to get a fix readied, thanks!
Message 1 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

I can authenticate with the beta but Time Machine fails for me as does mounting a share via AFP. The text of the error dialog in both cases says "Something wrong with the volume's CNID DB, using temporary CNID DB instead. Check server messages for details. Switching to read-only mode." For AFP it does indeed mount read-only and that does seem functional. TM is of course non-functional in this scenario.

Hoping for another quick beta :-) Thanks for getting this one out quickly. I did d/l log files from my Duo if you need them. I am running 511 Lion from a MacBook Air.
ReadyNAS Duo with 4TB (2xWD20EARS-00S8B1)
WAN Router: 2Wire (ATT Uverse) connected to Airport Express (AE is doing the LAN routing)
LAN: Cat6, D-Link 5 port Gigabit switches
Message 2 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

i also had "Something wrong with the volume's CNID DB, using temporary CNID DB instead. Check server messages for details. Switching to read-only mode." but i rebooted the readynas again and disconnected and reconnected in Finder and i am running an 8GB TM backup ok now.
I am connected using afp shares as well which didn't work at first.
Message 3 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Interesting. I did another reboot and could mount AFP r/w and copy a small file. It took a long time (20+ minutes) stuck in the preparing stage but after that a 9GB TM backup has started.
ReadyNAS Duo with 4TB (2xWD20EARS-00S8B1)
WAN Router: 2Wire (ATT Uverse) connected to Airport Express (AE is doing the LAN routing)
LAN: Cat6, D-Link 5 port Gigabit switches
Message 4 of 41
Highlighted
Prodigy

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

roadfun wrote:
Interesting. I did another reboot and could mount AFP r/w and copy a small file. It took a long time (20+ minutes) stuck in the preparing stage but after that a 9GB TM backup has started.

Yeah, that first backup after upgrade is a doozy. I think the reason it spends so much time preparing is (a) the large number of files and (b) apparently Spotlight re-indexes the BACKUP volume! Egad... but once all that shenanigans was finished, the backup proceeds normally.
Message 5 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

I think I'll wait until they release a final build. I used the trick found here
http://www.alexanderwilde.com/2011/04/os-x-lion-connection-error-with-afp-and-workaround/
This does not solve the TimeMachine issues but you can use AFP natively to transfer files until 4.1.8 becomes final.

Hint: When you perform step 2 and you connect to the NAS using AFP, click on cancel once you get the prompt for your login credentials and go to step 3.

EDIT: THANKS FOR THE UPDATE BTW! It's great that there is support with new firmware with us that are still with SPARC devices
Message 6 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

djrbx wrote:
I think I'll wait until they release a final build. I used the trick found here
http://www.alexanderwilde.com/2011/04/os-x-lion-connection-error-with-afp-and-workaround/
This does not solve the TimeMachine issues but you can use AFP natively to transfer files until 4.1.8 becomes final.

Hint: When you perform step two and you connect to the NAS using AFP, click on cancel once it asks you for your login credentials and go to step 3.


Hmmm, I didn't try this trick but I am able to see the ReadyNAS using AFP, mount it, and copy files, Time Machine still reports that it can't find the disk at all, even when it is mounted....

I'll too wait for the next beta since I don't want to muck things up re-enabling DHCAST128.

Thanks for pointing out the issue though djrbx since it looks a lot more widespread than I thought...
Message 7 of 41
Highlighted
NETGEAR Employee Retired

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Time Machine has additional requirements on Lion compared with AFP. RAIDiator 4.1.8 or later is required for Lion Time Machine support and that's not going to change.

bobready did you follow the Time Machine setup instructions here?: http://www.readynas.com/TimeMachine
Message 8 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Once I did the extra reboot, things seem to be working well. Have done several Time Machine backups without any problem.
ReadyNAS Duo with 4TB (2xWD20EARS-00S8B1)
WAN Router: 2Wire (ATT Uverse) connected to Airport Express (AE is doing the LAN routing)
LAN: Cat6, D-Link 5 port Gigabit switches
Message 9 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

mdgm wrote:
Time Machine has additional requirements on Lion compared with AFP. RAIDiator 4.1.8 or later is required for Lion Time Machine support and that's not going to change.

bobready did you follow the Time Machine setup instructions here?: [url ]http://www.readynas.com/TimeMachine [/url]


Oooooooooo.

Well, yes, I did, about a year or so ago when I first starting using the ReadyNAS as a Time Machine volume.....BUT...when I installed Lion on my MB Pro yesterday (it has been using the ReadyNAS for Time Machine since day 1) and today when I go into Time Machine prefs and I try an authenticate I used my usual (at home) user name "bob" and my usual password which did work.

I had set up a share for the user "bob" previously. This did mount the volume and the sparsebundle but TM did not work.

Once I used the default "ReadyNAS" user name and the password TM sprung to life and is now preparing the first whopper backup! Wish I had remembered to plug in the Ethernet cable.

So perhaps this is the issue all along, I had forgotten (and really why would I think otherwise?) that TM needs the ReadyNAS user and pw to work.

Thanks for this idea mdgm!
Message 10 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

roadfun wrote:
Once I did the extra reboot, things seem to be working well. Have done several Time Machine backups without any problem.


Thanks, I experienced the same issue initially and one more ReadyNAS NV+ reboot fixed it for me as well. Seems to be working at the moment.

Thanks!
Message 11 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

New beta working perfectly for me... Lion is happy with my shares, and TimeMachine has done its monster backup and is sat idling happily in the background. A happy TimeMachine makes for a happy user!

THANK YOU GUYS!!!!
Message 12 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Installed Lion, changed to 4.1.8 T5 on the NAS (Duo).
Rebooted my MBP several times, can access the NAS in the finder, but no TM support!
What can be the problem?

Can anyone help.

Thnx, RVE
Message 13 of 41
Highlighted
NETGEAR Employee Retired

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

RVE2011 you must use the instructions here: http://www.readynas.com/TimeMachine

If you want to use an ordinary share (unsupported) you need to be comfortable with manually editing the ReadyNAS config (only something advanced users should consider and even then probably not do): http://www.readynas.com/forum/viewtopic.php?f=71&t=55166

Welcome to the forum!
Message 14 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

my Lion backup completed successfully last evening. all is normal, not especially fast over airport, but it's a NV+ and 300+ GB.

one thing that i do differently than other default TM users, is i specifically mount my TMbackup directory using afp://my.readynas.ip.address/ReadyNAS vs using the built in network browser.

so, after mounting my volume, i then select it in TM prefs vs using the ReadyNAS.name/ReadyNAS auto discovery. i still see the readynas afp broadcast by hostname, i just choose to ignore it and explicitly map the device by ip address.

ymmv,

george
Message 15 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

OK... I don't know enough to know what's going on here...

My TM backup is working fine.

I can browse the ReadyNAS from the finder without any difficulty at all using the 'ReadyNAS (AFP)' connection.

But ReadyNAS (CIFS) and the plain ReadyNAS option that also appear in the finder window come back reporting 'connection failed'...

Is this normal?
Message 16 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Did you try hitting the "Connect As..." button in the Finder window for CIFS? I found I had to re-enter my authentication info. Of course, if you are using public/guest access this wouldn't apply.
ReadyNAS Duo with 4TB (2xWD20EARS-00S8B1)
WAN Router: 2Wire (ATT Uverse) connected to Airport Express (AE is doing the LAN routing)
LAN: Cat6, D-Link 5 port Gigabit switches
Message 17 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Till now i had no problem using the NAS. But the NAS doesn't show in the available shares/servers to backup using TM. No single disk is shown. The option to make a manual connection isn't highlighted. Can't use that. I connected my NAS in the finder using afp://ip-adres. This works fine. But no disk/server in TM. I made a big space on the TM some time ago to use it with TM. It worked without problems. I can't figure out more options. Simple because the rest is up-to-date. At least according to the issues i read till now.

A few moments ago i copied about 220 Mb to the NAS using the finder. No problems whatsoever. But still no TM?

Is there anyone with an idea?

Thnx, RVE
Message 18 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Roadfun...

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

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Hi folks,
I've installed the beta and still cannot get Lion to connect correctly via AFP. I can connect, login and see the shares, but when I click on a share in Finder, nothing happens. CIFS runs fine (as it did on the older version). So I'm not totally goosed. Timemachine is also not working as it uses AFP.

I've got the SSH access enabled on my Duo, so I logged in an snooped around. I ran a tail on /var/log/netatalk.log during a connection attempt and saw the following..

Jul 22 19:57:07.285861 afpd[1813] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by cormac
Jul 22 19:57:07.333737 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:07.385360 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:07.405561 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:07.413356 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:07.477324 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:07.516162 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:07.565941 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:07.616963 afpd[1813] {volume.c:2031} (I:AFPDaemon): Volume /c/home/cormac use CNID scheme dbd.
Jul 22 19:57:07.617244 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:09.395541 afpd[1813] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:09.441392 afpd[1813] {fault.c:122} (SSmiley Very Happyefault): ===============================================================
Jul 22 19:57:09.441693 afpd[1813] {fault.c:123} (SSmiley Very Happyefault): INTERNAL ERROR: Signal 11 in pid 1813 (2-2-0-p5)
Jul 22 19:57:09.441993 afpd[1813] {fault.c:124} (SSmiley Very Happyefault): ===============================================================
Jul 22 19:57:09.448707 afpd[1813] {fault.c:96} (SSmiley Very Happyefault): BACKTRACE: 1 stack frames:
Jul 22 19:57:09.448967 afpd[1813] {fault.c:102} (SSmiley Very Happyefault): #0 [(nil)]
Jul 22 19:57:09.451112 afpd[1614] {main.c:188} (I:AFPDaemon): child[1813]: killed by signal 6
Jul 22 19:57:09.540230 afpd[1814] {dsi_tcp.c:212} (ISmiley Very HappySI): AFP/TCP session from 192.168.12.15:50504
Jul 22 19:57:09.543737 afpd[1614] {server_ipc.c:231} (E:AFPDaemon): Reading IPC header failed (-1 of 14 bytes read): Resource temporarily unavailable
Jul 22 19:57:09.548346 afpd[1814] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: cormac
Jul 22 19:57:10.656523 afpd[1814] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Jul 22 19:57:10.671793 afpd[1814] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Jul 22 19:57:10.672134 afpd[1814] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by cormac
Jul 22 19:57:10.675781 afpd[1814] {auth.c:677} (N:AFPDaemon): afp_disconnect: trying primary reconnect
Jul 22 19:57:15.683036 afpd[1814] {auth.c:710} (E:AFPDaemon): afp_disconnect: primary reconnect failed
Jul 22 19:57:15.746883 afpd[1814] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 19:57:15.753336 afpd[1814] {fault.c:122} (SSmiley Very Happyefault): ===============================================================
Jul 22 19:57:15.753657 afpd[1814] {fault.c:123} (SSmiley Very Happyefault): INTERNAL ERROR: Signal 11 in pid 1814 (2-2-0-p5)
Jul 22 19:57:15.753877 afpd[1814] {fault.c:124} (SSmiley Very Happyefault): ===============================================================
Jul 22 19:57:15.754719 afpd[1814] {fault.c:96} (SSmiley Very Happyefault): BACKTRACE: 2 stack frames:
Jul 22 19:57:15.754979 afpd[1814] {fault.c:102} (SSmiley Very Happyefault): #0 /lib/libc.so.6(snprintf+0x1c) [0x201d0cd4]
Jul 22 19:57:15.755200 afpd[1814] {fault.c:102} (SSmiley Very Happyefault): #1 /usr/sbin/afpd(memcmp+0x1c) [0xa6c1c]
Jul 22 19:57:15.757284 afpd[1614] {main.c:188} (I:AFPDaemon): child[1814]: killed by signal 6

So it seems that there is SIGSEGV (signal 11) in the afpd process.. this just keeps repeating as Finder reconnects and then afpd dies again. I've performed several reboots and re-installs of the beta but the same issue each time.
Message 20 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Using 4.1.8 - T5, I have the same core dump when attaching to afp using Finder. Because of the core dump, finder more or less hangs for a couple of minutes. If I can force myself to be patient long enough, it does seem to eventually give up and recover. I can hurry that process by temporarily disabling AFP, which causes Finder to error out saying the server went away.

Strangely, Time Machine seems to work OK other than seeming rather slow in the preparation stage. I think that's a clue but so far I haven't been able to turn it into a solution.

The time machine share is the only one not listed in /etc/netatalk/AppleVolumes.default. The other shares are listed and set to the dbd CNID scheme. The ones that fail log a message like "Jul 22 21:42:16.240908 afpd[7597] {volume.c:2031} (I:AFPDaemon): Volume /c/home/blah use CNID scheme dbd.", while time machine does not.

I thought it might have to do with carrying over the CNID database from the previous version so I created a brand new share, but it exhibits the same problem. (Also I found I could not delete the share once I created it.)

I'm not quite sure what's different about Time Machine that makes it work. I tried changing the CNID scheme to cdb, but it's not supported. I also tried removing the CNID DB, and that didn't help.

Time Machine appears to use a config defined in /var/lib/timemachine/.AppleVolumes. I tried creating a share in my home directory in the same way, with and without options:tm. No luck, all still crash.

I compared the file permissions on .AppleDouble and .AppleDesktop on my home dir to the time machine directory, and found them to be in a different group. Changed it to match; no effect.

Comparing files and log content in the .AppleDB directories didn't reveal any noticeable difference.

For the moment, I'm stumped. The good news is, time machine is currently working for me and I can access my other shares using SMB. I'd still like to get AFP back in shape.
Message 21 of 41
Highlighted
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Ah, found a new clue.

I can connect and mount AFP shares fine connecting as Guest or a different user. It's only when connecting as myself that I have trouble.
Message 22 of 41
Aspirant

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

SampleX wrote:

I can browse the ReadyNAS from the finder without any difficulty at all using the 'ReadyNAS (AFP)' connection.

But ReadyNAS (CIFS) and the plain ReadyNAS option that also appear in the finder window come back reporting 'connection failed'...

Is this normal?
I'm getting disconnect messages every few (~5)minutes, which go away on their own because I'm running Bonjour Mounter, which reconnects them automatically. Still, it's pretty annoying having the window pop up so frequently over whatever I'm working on.
Message 23 of 41
Highlighted

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

Time Machine was working fine for me before the Lion upgrade and I had loads of space on the Duo. I have 2TB disks.

I've installed the 4.1.8. beta..

Now TM just hangs on preparing backup with Zero KB of 933.92Gb displaying as the Available: message

I get an email from the Duo now telling me there is no space..which is rubbish..I have 600Gb free. I can navigate to the drive and confirm that using Get Info.

Disk block limit reached on volume C for user 'ReadyNAS'.

Disk space used: 890651 MB (Limits: 840704 MB soft, 840704 MB hard)
User 'ReadyNAS' is now prevented from using additional disk space

Any ideas?
Message 24 of 41
Highlighted
NETGEAR Employee Retired

Re: RAIDiator 4.1.8 - T5 Issues w/Lion

The ReadyNAS (TM user) is using more than the quota allocated to it under Backup > Time Machine.
Message 25 of 41
Top Contributors
Discussion stats
Announcements