DaleWilliams

Huh... You've not been able to see the share since upgrading to 5.0? One thing that *might* be the problem is the change in user security with 5.0 ROOT can no longer see all shares...Setup a USER in unRAID to use as a 'normal user'. Be sure that its authorized with READ/WRITE in your TM share setup on unRAID. Log into UNRAID from the Mac (disconnect and then GO/Connect the shares) using your new user-id and not root. Then can you see the TM share? What I *have* done once in a similar situation is:Open the Time Machine in System Preferences. Do 'Select disk...' as if you were setting up your first TM backup...(do you see the old sparse.bundle now?) Create a new sparse.bundle on unRAID *IN my case, I reused the same name for the time machine file 'dale_timemachine'. I don't know exactly how to describe what happened, but it was as if I'd never had the problem. Somehow TM relinked and 'kept' all the old backups. This made me very uneasy...I'm used to having TM throw up on this by prompting to Overwrite or specify a new file name.* I don't know if this was a fix to TM in Mavericks, or voodoo...Your Mileage May Vary. I'm running short of ideas or suggestions that I've personally tried. After the above, what I would probably try next, is: Permissions fix on the MAC and on unRAID. Then I'd run Reiserfsck on the unRAID drive just to be sure.

If you ever replace your MB with one that incorporates true SATA, you'll find that AFP works fine with unRAID, and especially after 5.0.3. Unless you're trying to network your Mavericks machine to older Macs, I wouldn't worry about it. Apple is dropping AFP and moving to Samba. Mavericks only requires AFP for TimeMachine...and even that last bit of AFP will be gone one day.

I'm looking forward to finding out!

The .00x files are parts of a segmented file. If the segments have been successfully combined into a final file, then the segments can be deleted. In general, Apple uses these 'hidden dot files' for housekeeping. (the '.' makes them invisible by default on OS X and Windows) On your Mac you see them in a couple of places...they hold the Finder information such as a file's location on the desktop, or its 'tags'. This sort of info shouldn't actually be stored in the file. (turn on invisible files in finder, and you'll see them all over the place) They also are used when files are newly created and are still 'open' for writing. For example, to copy file 'X.txt' from DiskA to DiskB, Apple might create a file called '.X.txt' on DiskB. As data is copied, it goes to DiskB ".X.txt". When successful, the file is renamed and the '.' is removed, making it visible. Torrents and downloads often 'restart' their downloads and creating a new file. If the original download terminated abnormally, the '.'dot file is sometimes left behind by the torrent or download software. This can lead to 'extra' dot files that are no longer tied to an active finder operation, and consequently aren't cleaned up properly. *IF* the final file is complete and visible in your Finder, then any corresponding 'dot' file or folder can be safely deleted. Its also possible that the MOVER is not appropriately deleting the files with the names beginning with "__"...that's a pretty uncommon first character. Its also possible that your 'join' program (whatever you use to 'unarchive' or reassemble all the '.00x' files into a whole) is tripped up by the beginning "__" and doesn't properly delete them after rejoining. (In your joining software, there's probably a Preference setting to DELETE segments after joining. That should be ON. Still, those beginning characters may be a problem.)

Can you see the TM share in the unRAID web interface? Check your TM 'share'...is AFP enabled for the TM share? When you access the unRAID server from the web interface, go the SHARE tab, you'll see the TM share listed among the defined shares. Click on the VIEW for the TM share...the share folder should open in the browser...is the 'sparse.bundle' there? And are you logged into the unRAID server with an account that has visibility to the TM share? (and has the correct READ/WRITE setting applied on the SHARE tab?)

'...will not mount...' Where are you at when this happens? Are you in Finder at the | GO | Connect Server... | command? or are you looking at the shortcuts on the left side of a Finder window?

Parity: Parity is like a 'checksum', its an error correction mechanism...you see checksums every day. There's one built into the number on the credit card you used for lunch today. Here's a simplified concept: Assume 3 data drives + Parity. Drive 1's data = 1,2,3,4 Drive 2's data = 4,4,4,4 Drive 3's data = 9,9,8,8 Assume the parity algorithm is as follows: Add up all the data, 'by column' and write it to Parity So, column 1 has a 1, a 4 and a 9 = 14 column 2 is 2,4,9=15 column 3 is 3,4,8=15 column 4 is 4,4,8=16 Apply the algorithm to get the parity drive: So the parity drive's columns of data = 14,15,15,16 IMAGINE now that Drive 1 is crashed/borked/removed...you still have Drives, 2,3, and parity. Install a new Drive 1. Run your trusty unRAID server and it will recreate Drive 1 by taking the Parity Drive, and subtracting the values from the other Drives (Drives 2 and 3) So the new Drive 1 Column 1 Gets: 14 (from Parity) - 4 (from Drive 2) - 9 (from Drive 3) = 1 UNRAID Writes '1' in 'column 1' on Drive 1. Column 2 Gets: 15-4-9=2 UNRAID Writes '2' on 'column 2' on Drive 1. Column 3 Gets: 15-4-8=3 , etc. Column 4 Gets: 16-4-8=4 The rebuilt Drive 1 now has the data "1,2,3,4". This same algorithm works for any data drive, not just 'Drive 1', as long as you are replacing or 'error correcting' only one drive at a time. You can recreate any ONE single drive failure or replacement, but it requires the other drives work and be errorfree. That's why its important to follow the instructions for replacing/repairing drives, etc. You want to avoid situations where you have multiple broken drives...the algorithm can only recover one drive at a time. http://en.wikipedia.org/wiki/Parity_bit

FAN. Motherboards will shut down immediately if they are powered on WITHOUT a working FAN on the CPU. Check the fan connection...are there wires caught in it?...Watch the fan as you power-on...does it spin?

BIOS ? I've had the BIOS somehow corrupt itself...I never figured out how or why. (dead internal battery?) Anyway, it required that I boot with DELETE-KEY, F8, F12 or F2 (depends on BIOS). Then re-configure the BIOS to add the USB to the Boot List ahead of the hard drives, And to make sure that AHCI/SATA is enabled for the hard drives, and not ATA. ...maybe some other settings, but these are the ones I remember.

Ideally, upgrade to the paid version of unRAID to get cache drive support. There are lots of threads on how to use the cache drive for PLEX and SAB. Alternatively, this recent thread seems to setup a drive outside of unRAID which then can run PLEX (and I would assume SAB) http://lime-technology.com/forum/index.php?topic=30496.0

lionelhutz, Do you have a cache drive in your unRAID server?

Do you have multiple routers on your LAN? There's one router connected to your IP provider ( via DSL, or Cable Modem, or FIOS). Do you have other routers?

IMHO, Some nice tweaks to SMB.

I'm finding unraid, 5.0.4 and TM under Mavericks to be rock solid. No connection problems. And no longer have to manually Connect to Server/Tower in order to initiate the first TM update.

Editing the hosts file on Mac OS X (Lion, Mt Lion, Mavericks) http://osxdaily.com/2012/08/07/edit-hosts-file-mac-os-x/ OR, See the next post from dgaschk!

+1 For Mac OS X: Use either tower.local or the DNS numeric address. (I can never seem to get consistent response from 'tower.local' and am still looking to fix that. But I just setup a static port for unraid, and bookmarked the IP address.)

/RANT ON What is with these 'cloud services', anyway? Connections to GoogleDrive are breaking the Mac OS X Mavericks Finder. And now Microsoft's cloud is breaking Windows? Shouldn't 'cloud services' be transparent and not opaque? /RANT OFF sorry to go off-topic...but lately, 'disconnect from all cloud drives' has been added to my generic 'tech support checklist'.

What's this 'Microsoft account' of which you speak?

From my list of 'DOH' moments comes this concern: Windlasher, what I meant to say earlier was: 1. Open two windows on your PC - one showing the disk #1 and the unraid files you want to MOVE - one showing the other disk #2 and location to which you want to move the files. 2. Drag and drop between the two windows. You don't have to explicitly copy FROM unraid disk #1 TO your PC and then a second copy FROM your PC to unraid disk #2. You have to keep your PC running while the files are copied of course. This just uses your PC as the intermediate 'brains' of the copy. Its slower than using MC directly, but as dgaschk points out, the speed limit is probably your parity drive.

How do you define 'cache share'? 1. Is that a share that is ONLY on the cache drive? 2. Is that a share that is ENABLED to use the cache drive? 3. Is that something else entirely? (maybe post a screen shot of the cache share configuration web page?)

dgaschk, Is Settings->SMB->Local master: YES also hopeful for this, or is that for something else?

+1 or perhaps one board topic devoted to the specifics of what works in 5.0.x installation instructions. (perhaps restricted to the plug-in authors' instructions, with debate moved to separate threads?)

I agree. In several decades of this stuff, I've never needed to 'upgrade' hard drive firmware. Unless its to fix a fault that makes the drive unusable, I wouldn't mess with it. (I'd share the list of all the stuff that I have bricked while 'fixing' them, but it's just too depressing.)

I've never changed the firmware in a hard drive, perhaps someone else can help.

You use a Mac, correct? You can delete them. They exist on your Mac or PC, too, but, the '.' at the beginning of the name keeps them 'hidden'. Those 'dot files' are small 'hidden' files that are used to keep track of things. (like the position of the file on the desktop, your preferred sort order for a folder. They are also used by the finder to control things like a 'copy' or 'move'.)