Hi All,

 

I have been having trouble with my Time Machine Share since 5.0. I have not been able to open/mount the share with Finder

 

Recently, I tried to remove the share by first deleting all the files in the share with the rm -r command. It seemed to hang on that command while deleting the sparsebundle (after awhile there was no disk activity), So I quit that telenet session. After that I went into the webGUI and changed the export mode from yes(Timemachine) to just yes. I was then able to access the share, but after accessing it, it proceeded to freeze my entire computer (had to force restart Finder) and it caused many other problems.

 

So now when I access the server from telnet, I cannot even cd into the sparsebundle folder (from either the /mnt/user or /mnt/disk)

I can access the actual share using cd, but when i cd into the sparsebundle it "freezes"

 

HELP Please!!!! There is nothing of value in the system log, so I did not attach it.

Not much to go on here.

Are you using 5.0.4 ? (or at least 5.0.3?)

And what version of Mac OS X?

After you went to 5.0.x did you

    restart your Mac,

    then use Finder/GO/Connect to server... to reestablish links to unRAID (while using NOT ROOT, but an 'unRAID user' login and password),

    then open TM Preferences and reSelect the proper TM share?

 

How do/did you have your TM set up? Is TM restricted to ONE Hard drive ("included disks")

Have you run Reiserfsck on that drive?

 

 

How much time did you give the commands to complete. It may take several minutes or an hour depending on the size of the sparsebundle. Eventually the command line will return.

Yep.

 

unRaid 5.04

OSX Mavericks (fresh install)

 

After 5.x.x

Restarted Mac and unRaid multiple times

Disabled all plugins on unRaid

Freshly installed OSX Mavericks (not really related)

Successfully connected to all shares (except Time Machine) using bot Finder/Go/Server and when it pops up in the Finder sidebar (NOT using root) (using unraid user and password)

I didnt even try the TM app, I cannot connect to the Time Machine share using any method

 

 

my TM machine share is restricted to one hard drive with a cap of 1.5GB

I should have tried reiserfsck before, but i didnt. I am currently performing a parity check and will run reiser afterwards.

 

Also, I do know that the rm command can take a LONG time, especially when the total size is around 1.3GB. However, to my understanding (and memory), the sparsebundle has a crap ton of individual files in it, especially since I have been backing my mac up for over a year now. I waited quite a long time and I checked disk activity every once in awhile. The disk activity finally stopped, yet the command had not returned yet. I was reading that the rm command can hang up if too many files are deleted at once.

So then I aborted and restarted everything. Which leads me to my current situation.

 

As always, thank you for your help!

 

Update:

 

Reiserfsck did not return any errors

Do the other shares work?

Are you able to make a new share?

 

Do you have (or have ever had) SimpleFeatures installed?

All the other shares work.

I am able to make new shares.

 

Yes, I have had SimpleFeatures installed at some point. Could that be the problem?

Turn off both AFP and SMB and then delete the share.

Turn off both AFP and SMB and then delete the share.

and completely remove remnants of SimpleFeatures. It doesn't manage shares correctly.

http://lime-technology.com/forum/index.php?topic=28927.msg279478#msg279478

Yeah, I made sure that there was nothing in /boot/config /extra or /plugins. Nothing from simplefeatures remains.

 

Also, I tried again to delete the sparsebundle from the server using the console this time (because I cant access the share normally) and I let it run almost a FULL 24 hours from the console. It command did not return and the webGUI because inaccessible, however I could still telnet in and use shutdown -h now.

 

So it is probably not a plugin problem, and reiserfsck says that its not a directory problem...... and I cannot delete the sparsebundle (to delete the share) from either the console, telnet, or Finder. Nor can I cd into the sparsebundle to delete individual directories (as to break up the work that rm has to do) So I am at a lost at what to do.

 

Could the sparsebundle be corrupt if I had stopped the rm command halfway through (using shutdown -h now)? What options do I have to remove the file? As I understand rm -rf doesnt really make a difference since the file is not write protected.

 

 

Also just to clarify, when you use the rm command, should you always turn off AFP, SMB and should your Array be started, in maintenance mode, or stopped?

I attached a screenshot of the permission for the files on my TimeMachine share. (This is the only other thing that I can think of that might be a problem)