Add network drive to mac startup
Unfortunately, this naming convention only allows me to have five pieces of hardware on my network at once. I'll be damned if I'm calling anything Scrappy.
So this script will run whenever you double-click it instead of opening the editor again , be sure to save it as an Application note the "File Format" option below. So let's give that a try. Eject your networked Volume and double-click on the script application you've just created. The volume should re-appear, as if by magic if Clarke's quote is accurate. We're nearly there! Open the Accounts dialog in System Preferences. Select the Login Items tab and authorize yourself for changes by clicking the lock icon in the bottom left hand corner.
Once you've done that, click the plus button under the login items list and select the application you created. It should now appear in the list:. Fingers crossed, your network share should be mounted every single time you log in. If you feel like it, you can do the same for other users too. In my case, I set up Dropbox on the Mini so it's files were all on the Drobo.
How to select a different startup disk
This way I had an extra local backup of my most important files, and visitors could get access if I let them without having to set up additional shares. But unfortunately, it didn't work! Every time my Mac Mini started up, I got a handy and surprisingly verbose error message from Dropbox headed "Dropbox Folder Missing" telling me my Dropbox folder had been moved or deleted.
I was a little perplexed by this, as I could clearly see the volume on my desktop. That way, you can restore everything to how it was before you began this process, if necessary. In the Users folder , you'll find your home folder, easily identified by the house icon. Select the Home folder and drag it to its new destination on another drive.
Because you're using a different drive for the destination, the operating system will copy the data rather than move it, which means the original data still will remain in its current location. You'll delete the original home folder later after you have verified that everything is working. From the list of user accounts, right-click on the account whose home folder you moved, and select Advanced Options from the pop-up menu.
Do not make any changes to Advanced Options except for those noted here. Doing so can cause quite a few unforeseen problems that could lead to data loss or the need to reinstall the operating system. In the Advanced Options sheet, click Choose , located to the right of the Home directory field. Navigate to the location you moved your home folder to, select the new home folder, and click OK.
Navigate to the location of your new Home folder, which should now display the house icon. Create a test TextEdit file by typing a few words and then saving the document. In the drop-down Save sheet, select your new Home folder as the location to store the test document. Give the test document a name, and click Save. Open a Finder window, and navigate to the old location for your home folder. This home folder should still be listed by name, but it should no longer have the house icon.
I am using external hard drive that is connected to ASUS router. Great tip! Seems like you mounted the Windows share, and not the file image, make sure you name those two things something different and try again. Looking into it some more, the only new file was the sparsebundle file which was almost Gb. Can I use your instructions to copy this file to the NAS drive, mount and then delete the original sparsebundle file on my laptop?
Will this work, please advise? Hi Justin, great tutorial, i have a question, I'm thinking in a scenario of a kernel panic for example, that you need to do a full restore of the hard drive, you think is posible to copy the sparsebundle to a USB drive, then connect that USB drive to the Mac and then do a full restore from that USB drive? Just started looking at this. I guess the downsides are things like not being able to set encryption or size restrictions individually. Can you tell me anything else that you think would cause me a problem doing it this way that i have not found yet?
Looks like your NAS supports AFP, in which case you should just ignore my instructions here and set things up the way you did. It's going to be better in every way than my steps outlined above.
- wd external format for mac?
- How to automatically mount a network drive on Mac OS X?
- picture style editor download mac.
I have been using this "hack" for a couple of months now. Starting today, I cant mount my sparsebundle anymore. Disk Utility cant repair it Guess the only easy thing to do is to buy a time capsule :P. Hi, everything goes well until i reach migration assistant. What options did you use to have it shown on it.
I just made sure I had the drive mounted when it was time to do the migration, is that not working for you? Yeah I've had all sorts of trouble with the script, am thinking about removing it from the article. Let me know if this works for you. I was able to set it up yet when I start the TimeMachine's backup it is stuck at Kb.
Do you figure any solution? I haven't run into this specific problem, and I'm not sure how to help you. If you're on WiFi, trying plugging into the router directly and see how it goes. It is a router problem. It has a usb port and supports smb shares.
How to Automatically Connect to a Network Drive at Login in OS X
When i've configured timemachine there it even crashed from time to time. Huawei quality! Thanks so much for this! Everything worked up until the point of attempting my first timemachine backup. I get a message saying something along the lines of not enough space. I was limited on how big I could make the 'TimeMachine' disk to the amount of free space on my computer not enough space for a single backup. Is there a way to make the disk larger using storage space of server I'm using?
Figured it out. I wasn't copying the correct 'file' onto the server..
Thanks again! Hope you may have seen this. I had issues with getting everything going there and found this link. Using the same steps I named the bundle and followed the steps with no issues until opening the TimeMachine utility in which it crashes with the error "Can't connect to a current time machine backup disk".
I haven't run into this specific problem yet, but for lack of a better suggestion I'd say to restart your computer and reconnect, see if the problem reoccures. Scratch that, I wasn't thinking Basically it couldn't connect to the current backup because none existed. Thanks for the guide, looks like all is working great so far Thank you for this, ZerockzZz! Justin, can you please update the article with this vital little tidbit? I seem to have gotten this to work "sort of". The TimeMachine sparsebundle was only "mounted" the first day, and then about three days later.
It won't hang around. Trying to double click on the sparsebundle out on the server doesn't do squat-- nothing happens. I'm frustrated. So, I'm feeling distinctly out of my depth. When you mention "bundle" i'm suddenly lost. There's entirely too much assumption of knowledge in nearly every single article I've pulled up to try to get help on my situation, so I'm resorting to leaving a message. I hope you can help. I was thinking that I could use your technique to get TimeMachine finally running backups off my MacBook Pro 15, but it seems like a coin toss with bad odds I have certainly found this approach to be inconsistent at times, and the problem is entirely that I can't get the partition to mount at times.
In all of these cases I have found that restarting my Mac solves the problem. It's not an ideal solution, I'd rather avoid rebooting, but it does work. Actually if they would enable smb protocol in the recovery console it could be restored in theory.
I have tested in the way just for purposes of testing as close as possible. I did my TM for 5 days to a smb connected share. It worked great. I than started working on restoring. Found out that smb is disable in the recovery console. I finally used afp to connect to the same share and I could do a complete restore without issues.
I really wish they would enable smb in the recovery console. Seems pretty short cited of a company that is promoting smb and trying to move away from afp to not enable this. How did you end up using AFP to connect? I ran everything succesfully, except the last step: reload the backed-up data via Migration assistant.
Strange behaviour, or error on my side? Cool - thanks. Being stupid and fussy I want the real one ;. I'll keep an eye on things in that case. Another thing do you know the reason why a restore can't be done during a Recovery? Is there just no option to mount the share during Recovery - I haven't actually ever done one Yeah, there's no way to mount the partition during recovery sadly. It's unlikely we'll ever find a fix for this either. Can you move other files to the drive? If not, check your permissions on the server side. Not sure what else the problem could be, what kind of error do you get?
Dunno if this might help anyone, but I found that by starting my script with a delay command helped it to mount my smb share much more consistently. The delay gives time for my laptop to actually connect to the network before giving up. I just added. It assumes seconds, apparently. You may need to extend it if you take longer to connect.
Hope this helps someone. Thank you for the tutorial! A solid backup of my wife's laptop was LONG overdue, since it has most of the pictures of my 3 year old on it! Sorry I didn't read this to begin with I thought I -HAD- read all the comments and then when you told me to read the comments I noticed there's a "load 10 more comments" at the bottom of the screen, which must be expanded several times.
I tried all passwords, none work It shouldn't be asking for your password at all, are you sure you didn't name the network share Time Machine? Thanks a million for this post! Now I can actually use SMB 3. Thanks for this post. Everything was described very clearly, and I actually got most of this to work, which is amazing because I know nothing about computer speak.
Automatically Connect to a Network Drive on Mac OS X Start Up & Login
The only issue I am having is that my NAS has a password required, so I believe I need to somehow incorporate that step into the Applescript so that I can mount at startup. Error I receive when running the script is:. There was a problem connecting to the server The share does not exist on the server. Please check the share name, and then try again. Time machine is successfully pointed to the sparse bundle on the NAS, and the size of that sparse bundle is correct, and I have already performed a backup. Any chance someone can help me with the Applescript, otherwise not a huge issue to manually mount.
I'm afraid I'm not sure how to modify the script to include a password, sorry! I've since set up Control Plane to automate mounting, check out my tutorial here:. Glad the article was helpful! I'd consider it a favour if you shared it with anyone who might be interested. When I run the script, I get the following error:. Here is the script as I ran it. Thanks for any help. Hey Joe! The first error you're seeing is because there's a space in the name of the network share — this gets weird fast.
The quick fix is to rename the share to something without a space. The second problem, I think, is because you have too many drives mounted named "TimeMachine". Again, the simplest fix is to name your sparsebundle something else entirely just to avoid confusion. Okay, I might be totally off base here, but the only way I can figure that you got that error is if you tried to point time machine at the network drive where the sparsebundle is instead of the mounted bundle itself.
That's not it, is it? I just tried the method again just to make sure and it worked for me on Yosemite. What version of OS X are you running? Justin you were correct. I named my sparsebundle and network share the same, so when I ran the command it selected the network share over the sparsebudle. Heads up for anyone else having the same issue.
Pick a different name for your bundle and network share. Thanks for the good article. Because it's unsupported, Recovery HD won't see the drive on the network. And, outside of OS X, you can't use the command to manually assign the drive. There's no way around this that I've found. Rob Nightingale. Top Deals. Email Facebook Whatsapp Pinterest Twitter.