RN104 Full factory reset creating shares produces 1002030001 - Commit failed.

I've just given my ReadyNAS 104 a full factory reset and reinitialised the drives and a raid... which went fine, but trying to create shares produces commit errors, yet they are created.... just with terrible permissions (set to read/write for everyone including guests) and any edits also produces errors.

I've skimmed the logs and I don't see any BTRFS errors, but I did spot this in systemd-journal:

Jan 23 09:59:44 readynasd[2280]: Failed to create daap apps cache dir. rc = 1
Jan 23 09:59:45 dbus[2085]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Jan 23 09:59:45 dbus[2085]: [system] Successfully activated service 'org.opensuse.Snapper'
Jan 23 09:59:45 snapperd[3788]: Snapper create-config
Jan 23 09:59:45 snapperd[3788]: config_name:0 subvolume:/Stuff/Test fstype:btrfs template_name:default
Jan 23 09:59:45 readynasd[2280]: Snapper SetConfig successfully.
Jan 23 09:59:45 readynasd[2280]: Failed to create daap apps cache dir. rc = 1
Jan 23 09:59:45 readynasd[2280]: rndb_daap_service_export() ==> 1 (2ms)
Jan 23 09:59:45 readynasd[2280]: rndb_export() ==> 1 (196ms)
Jan 23 09:59:45 readynasd[2280]: share.c:963:process_add_share Failed to commit_dba. category = 3, ret_val = 1
Jan 23 09:59:45 readynasd[2280]: Error in commitdba status=1
Jan 23 09:59:48 readynasd[2280]: ERROR: Radar: Maximum iteration exceeded
Jan 23 10:01:46 dbus[2085]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Jan 23 10:01:46 dbus[2085]: [system] Successfully activated service 'org.opensuse.Snapper'
Jan 23 10:01:47 rnutil[3923]: Failed to get tier from /dev/md0 : 25
Jan 23 10:01:47 readynasd[2280]: Error: Connection failure: Connection refused

Am I looking at yet another factory reset? And if I do that and this occurs again... then what?