[PLUGIN] netatalk - AFP for UNRAID (Support Topic)

[Rysz]

netatalk - AFP for UNRAID (6.10+)

A plugin that integrates the legacy AFP file sharing protocol into newer UNRAID versions.

 

The Apple Filing Protocol (AFP), formerly AppleTalk Filing Protocol, is a proprietary network protocol, and part of the Apple File Service (AFS), that offers file services for macOS, classic Mac OS, and Apple IIs. In OS X 10.8 Mountain Lion and earlier, AFP was the primary protocol for file services. Netatalk is a freely-available Open Source AFP fileserver, this plugin provides an integration of such a server into UNRAID.

 

AFP was earlier removed from UNRAID - it is no longer being developed by Apple and is considered fussy and deprecated, however some people with outdated computers might have no other means to access their fileserver, while others might even prefer it over NFS or SMB for other reasons. This plugin for UNRAID was developed to let any such users finally update their outdated UNRAID servers without losing their beloved AFP file-serving capabilities or it might possibly draw back some users to UNRAID who couldn't live without AFP and switched elsewhere.

 

For obvious reasons this plugin is still considered EXPERIMENTAL and is not officially endorsed by LimeTech.

Please do report any issues or feedback you have in this topic, it'll help with the development of the plugin!

 

How to install?

https://raw.githubusercontent.com/desertwitch/nAFP-unRAID/main/plugin/nafp.plg

(via UNRAID Web GUI: Plugins ➔ Install Plugin ➔ Enter URL ➔ Install)

... and hopefully coming soon to Community Applications. 🙂

 

How does it work?

After installation AFP is disabled by default and waiting for your configuration.

All necessary steps to configure and use the plugin are explained in the GUI (Settings ➔ AFP).

 

How to contribute?

https://github.com/desertwitch/nAFP-unRAID

... and of most importantly - please do test and report back here!

 

Why do you have to revive this godforsaken protocol, just let it rest at last?!

I, too, have a few old Apple devices that can only speak AFP... unfortunately! 🤪

 

 

 

Edited September 1 by Rysz

[symptomatic-beating8996]

Hey There!

This is a (in theory) godsend for some stuff I'm working on!

That said, when I launch the plugin and configure the share per instructions, and restart the array, I run into issues on the client side. This is both in OS 9 and OS 10.0. 

Specifically, it asks which volumes I want to mount, and provides no options. My afp.conf file looks like as follows (share name is DerperThought).

 

Quote

; START OF DO NOT CHANGE SECTION

[Global]
log level = default:warn
zeroconf = no
vol preset = doNotChange
vol dbpath = /mnt/user/system/nafp

[doNotChange]
cnid scheme = dbd
cnid dev = no
search db = no
unix priv = yes
umask = 000
file perm = 666
directory perm = 777

; END OF DO NOT CHANGE SECTION

; START OF DEFINE USER SHARES HERE SECTION

; [share]
; path = /mnt/user/DerperThought
; time machine = no

; END OF DEFINE USER SHARES HERE SECTION

 

[Rysz]

9 hours ago, symptomatic-beating8996 said:

Hey There!

This is a (in theory) godsend for some stuff I'm working on!

That said, when I launch the plugin and configure the share per instructions, and restart the array, I run into issues on the client side. This is both in OS 9 and OS 10.0. 

Specifically, it asks which volumes I want to mount, and provides no options. My afp.conf file looks like as follows (share name is DerperThought).

 

 

 

Hey - thanks for testing and writing here! 🙂

You need to remove the ; and space at the beginning of the line, that's only for commenting in the configuration files.

 

So for your share to become enabled the share section needs to look like this:

; START OF DEFINE USER SHARES HERE SECTION

[share]
path = /mnt/user/DerperThought
time machine = no

; END OF DEFINE USER SHARES HERE SECTION

The above example would create a share called share linking to /mnt/user/DerperThought

 

You could also (probably easier) name the share DerperThought too, then it'd look like this:

; START OF DEFINE USER SHARES HERE SECTION

[DerperThought]
path = /mnt/user/DerperThought
time machine = no

; END OF DEFINE USER SHARES HERE SECTION

 

Please let me know if it works now, you'll need to restart AFP or better your array for the changes to become active.

 

Edited September 2 by Rysz

[symptomatic-beating8996]

*facepalm* It's always the obvious thing isnt it

You're amazing! Everything is working -swimmingly- and you have no idea how many problems you just solved!

[FredrikJL]

Hi!

 

Love this plugin, since the timemachine support for SMB is not really great, depending on how old/new your MacBook is. 

 

I'm getting a lot of these in my syslog. 

facility: 	daemon
appname: 	afpd
level: 		error

 

ad_header_read_ea("/mnt/user/timemachine-schibsted/{hostname}.sparsebundle/."): invalid metadata EA this is now being treated as a fatal error. if you see this log entry, please file a bug ticket with your upstream vendor and attach the generated core file.

 

They don't seem to intervene with the functionality when running TM-backups, but they sure are annoying as they're level: ERROR and I sometimes get hundreds of them. Ideas?

This github issue is potentially provides some clarity on the subject. Invalid metadata EA errors #236

 

Tl;dr

There is one suggestion HERE

Quote

Site note: One potential workaround is to disable the ad to ea on-the-fly conversion in netatalk3. The afp.conf option is:

convert appledouble = no

This option worked perfectly for me, I was having issues with my time machine share. Thank you!

 

 

I have yet to try this suggestion myself, but will update in this thread as I learn more. 

[FredrikJL]

16 minutes ago, FredrikJL said:

Hi!

 

Love this plugin, since the timemachine support for SMB is not really great, depending on how old/new your MacBook is. 

 

I'm getting a lot of these in my syslog. 

facility: 	daemon
appname: 	afpd
level: 		error

 

ad_header_read_ea("/mnt/user/timemachine-schibsted/{hostname}.sparsebundle/."): invalid metadata EA this is now being treated as a fatal error. if you see this log entry, please file a bug ticket with your upstream vendor and attach the generated core file.

 

They don't seem to intervene with the functionality when running TM-backups, but they sure are annoying as they're level: ERROR and I sometimes get hundreds of them. Ideas?

This github issue is potentially provides some clarity on the subject. Invalid metadata EA errors #236

 

Tl;dr

There is one suggestion HERE

 

I have yet to try this suggestion myself, but will update in this thread as I learn more. 

 

And a quick update on this. Setting the parameter as suggested solved the problem above. 

[sharename]
 path = /mnt/user/path
 time machine = yes
 valid users = username
 
 # THIS IS THE THING!
 convert appledouble = no

 

Edited September 28 by FredrikJL

[Rysz]

55 minutes ago, FredrikJL said:

 

And a quick update on this. Setting the parameter as suggested solved the problem above. 

[sharename]
 path = /mnt/user/path
 time machine = yes
 valid users = username
 
 # THIS IS THE THING!
 convert appledouble = no

 

 

Thanks for the information, this is useful and interesting.

I'll see if it's worth including in the default configuration and if so if there could be negative consequences.

[FredrikJL]

Problem seems to be now that it solves the issue for my older (2016) Macbook, but the problem seems to persist for the new M1 MacBook, for some reason. I'll keep track of it for a bit and tinker a bit more as well.

[Rysz]

On 9/29/2023 at 12:20 PM, FredrikJL said:

Problem seems to be now that it solves the issue for my older (2016) Macbook, but the problem seems to persist for the new M1 MacBook, for some reason. I'll keep track of it for a bit and tinker a bit more as well.

 

I've just compiled a new package and updated the plugin to use that, which includes the latest netatalk version (3.1.17) where this issue should be fixed regardless of the "convert appledouble" workaround (I suggest attemping to remove that workaround from the configuration now).

 

Please update and let me know if the problem is now resolved for you either with or without the workaround.

 

Edited October 1 by Rysz

[FredrikJL]

On 10/1/2023 at 11:41 AM, Rysz said:

 

I've just compiled a new package and updated the plugin to use that, which includes the latest netatalk version (3.1.17) where this issue should be fixed regardless of the "convert appledouble" workaround (I suggest attemping to remove that workaround from the configuration now).

 

Please update and let me know if the problem is now resolved for you either with or without the workaround.

 

Checking in on this one again. The problem seems to be gone now and haven't appeared for more than a week.  Thanks for the update!