IDK why this keeps happening : May 31 14:26:28 unraid afpd: login tailee (uid 1000, gid 100) AFP3.1 I know others are backing up with TM as well without problems. I'm backing TM without problem but I only run a few basic add-ons.

Jun 4 12:13:53 unraid cnid_dbd: main: not enough arguments It has many lines about cnid, including one near the end that says: Here are some more links that may be relevant.Īlso, I have attached a copy of my syslog (while it is still attempting to unmount user shares). Perhaps Time Machine makes a call that NetAtalk doesn't understand, which causes the process to hang and which subsequently prevents safe shutdown? Since unRAID allows shares to be exported over AFP (Time Machine), this seems to be a bug (or limitation) that unRAID should attempt to fix (or work-around)? Perhaps unRAID needs to use a patched version of NetAtalk? UPDATE: Seems to indicate that NetAtalk (which unRAID uses?) might not be compatible with Time Machine calls. What is this cnid_dbd command? Why is it always still running even after all file sharing services have been stopped?ĭoes this mean that I am going to have to perform a full parity check every time I reboot, if I ever want to use my unRAID array to store Time Machine backups? AppleDB folder is accessed in a way that is not closed properly when file sharing services are stopped? But it seems that when used with Time Machine, the. Time Machine has been working correctly for the past few days. 'kill -9' put the process into uninterruptible sleep. What else can I try, besides pulling the power? The machine still responds to ping, I can still login as root over SSH, I can still access the unraid and unmenu web interfaces (but only by their IP address, not the server name). I tried running /sbin/powerdown and got a few lines of output about SMART overall-health self-assessment test resut: PASSED, and then nothing. I don't think fuser is preventing the shutdown, but I don't know what is. I closed the terminals that were running them, and they are still hanging around. kill -9 won't work on the fuser processes. A backup was started to the disk, then stopped, and the disk ejected from my Mac. cache_dirs, sabnzbd/sickbeard/couchpotato are all not running, but no matter what I try I cannot get out of the fuser process, and it's still retrying to unmount disk1. I logged in and tried to find what process is using a share with fuser (this usually works, and usually reports either cache_dirs or sabnzbd/sickbeard/couchpotato).

Softperfect ram disk unable to unmount