Error 45 Time Machine Buffalo
Contents |
phone outage and cannot be reached at this time. We will update this message when service has been restored. We are sorry for any inconvenience. Technical Support chat and email are still available. Home Help Search Login Register Buffalo Forums » unraid 6 time machine Products » Storage » Linkstation Pro and Time Machine Error (Snow Leopard) « previous next »
Crashplan
Print Pages: 1 [2] Author Topic: Linkstation Pro and Time Machine Error (Snow Leopard) (Read 7034 times) 1inhiding Calf Posts: 1 Re: Linkstation backblaze Pro and Time Machine Error (Snow Leopard) « Reply #15 on: June 20, 2010, 10:34:10 AM » I had this problem, and it was infuriating - but for me it ended up being a simple fix - my network computer name had two spaces in it - instead of entering the computer name as john doe's macbook (with spaces in it), I ended up using john_doe and dropping the "macbook" or "imac" extension from the network name. The key was using the underscore...Hope this works for y'all. (Buffalo if you're reading this, this is not listed in your setup documentation anywhere...) -Geoff Logged dodosea Calf Posts: 2 Re: Linkstation Pro and Time Machine Error (Snow Leopard) « Reply #16 on: June 20, 2010, 08:32:19 PM » I'll try it.Thank you.!~~ Logged dodosea Calf Posts: 2 Re: Linkstation Pro and Time Machine Error (Snow Leopard) « Reply #17 on: June 20, 2010, 11:40:02 PM » It still not work when I changed my network ID.But I read a solution from here: http://www.macosxhints.com/article.php?story=20090905212640957You can try it ,I did nothing but copy a files (com.apple.TimeMachine.MachineID.plist.)include my mac's UUID into the Time machine diskimage,My timemachine was running!~~~~~The key was telling your mac what's your UUID....Hope this works for y'all. Logged takio Calf Posts: 1 Re: Linkstation Pro and Time Machine Error (Snow Leopard) « Reply #18 on: July 28, 2010, 09:18:32 AM » I even ipgraded firmware to 1.33 and still getting error message 45 after awhile. Logged Snoopy007 Calf Posts: 4 Re: Linkstation Pro and Time Machine Error (Snow Leopard) « Reply #19 on: August 21, 2010, 10:09:03 AM » My Link Station Pro LS-XHL is running firmware version: 1.10 and I am running SL 10.6.4 on my MacPro and I am also receiving the above mentioned error. After much searching on this forum and implementing the workaround solutions suggested above I still receive this same error. So far I have tried the manual solution of creating the sparshbundle file and also tried to remove all and add access restrictions to the target backup folder to see if this made any difference. Still no success. Wou
Top level of indirection About Me Index Catch CATCH Forum Appearances Login Subscribe level of indirection RSS Twitter « Stackoverflow DevDays London | Main | Code formatting in C++ Part Two » SaturdayOct102009 Using a networked drive for Time Machine backups (on aMac) Saturday, October 10, 2009 at 8:13PM You'll find similar information to this around the web, but I find it fiddly enough to piece together reliably, and I need it often enough, that I thought I'd blog about http://forums.buffalotech.com/index.php?topic=3017.15 it. That way it at least gives me a single place to look. Maybe it will help others too. Much of the specifcs, especially the hdiutil command line and the ifconfig trick, I sourced from this thread in the ReadyNAS forums. Note that the advice is by no means specific to ReadyNAS drives (I have a Thecus NAS myself). Many http://www.levelofindirection.com/journal/2009/10/10/using-a-networked-drive-for-time-machine-backups-on-a-mac.html?currentPage=9 thanks to btaroli in that thread for the insight. Time Machine Time Machine is Apple's easy-to-use backup system, baked into OS X (as of Leopard). Unfortunately it doesn't allow you to back-up to a networked drive out of the box. Enabling this ability is pretty easy. Early on there were some reliability issues - which were largely due to the fact that Time Machine created a disk image (more specifically, a sparse bundle) on the network drive, and this was prone to corruption if the network connection was disrupted during a backup. I don't know if all the issues here have been entirely resolved now, but it does seem more reliable. Apple's own Time Capsule, which has been specifically designed to work with Time Machine, uses this same method, so it is no longer an entirely unsupported technique. Enabling Time Machine for network drives So how do you enable backing up to network drives? Open a terminal window and paste the following in (then hit return, of course): defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1 Mounted network dr
Comments RSS WordPress.org Buffalo Time Machine Error 45 If this restoration caused a trouble, you can always undo this particular System Restore. The main issue is with the hardware of one's process not being compatible, or having challenges; http://www.msnx.net/buffalo-time-machine-error-45/ as well as 2nd issue is the fact that you've some sort of computer software issue. http://www.garth.org/archives/2011,08,27,169,fix-time-machine-sparsebundle-nas-based-backup-errors.html The blue display screen is definitely one from the worst difficulties anyone could experience. Now Type net stop winmgmt and hit Enter. You can also start System Restore with just a command, which might be helpful if Windows seven does not start correctly but the Command Prompt is still available. Most Blue Screens of Demise are components or driver related so updated drivers time machine could repair the cause in the STOP mistake. There is no restrict on the number of RAM that the personal computer might have whether it is a 64-bit operating system, but commonly 4GB memory is plenty of. If so, you will find a really good chance that the change you made brought about the BSOD. If a driver you've installed is causing Windows to blue screen, it shouldn't do so in safe manner. If your method recently started error 45 time blue-screening, use System Restore to roll its method computer software back to a previous state. New and a lot more advanced software programs are popping out which might be normally designed or intended to operate on new desktops. These glitches can be a result of both components and software package challenges, and it can be difficult to troubleshoot the dilemma. Overheating could cause important minimize within your computer's efficiency. This is the method of Home windows which basically masses up your Computer system without any in the software package or options that normal method within your system will bring. Normally, the personal computer will start up as if nothing happened. With System Restore, you can return most important Windows seven documents and configurations back for the way they used to be when your computer was doing the job properly. Before you do anything else, get started by rebooting your laptop or computer first. When Protected Mode loads up, you've got to then attempt employing your method. Make sure that the Volume Shadow Copy & Task Scheduler & Microsoft Software Shadow Copy Provider Service is Running and set on Automated. Therefore, it slows down your laptop or computer after a while. You might also reinstall and just observe the instructions properly. If This Restoration Caused A Problem, You Can Always Undo This Particular Buffalo Time Machine Error 45 System Restore. Use Procedure Restore to
backup on a NAS (as opposed to an external drive attached to a router) and it needs to be repaired. The NAS is likely a hardware product from the likes of Netgear, Synology, Buffalo or QNap - or for those of us with a home-grown backup server running FreeNAS. The error you may see is "Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you." This can be fixed by following the below. From your Mac, connect to the network share that houses the sparsebundle. At the top level of the drive are the various sparsebundles that make up your individual computer backups. Do not double click on these sparsebundles or try to repair with Disk Utility. Open Terminal and then switch to root by typing sudo su - and then enter your password. The verication that has already run has marked your sparsebundle as bad, so first we need to make it look normal. From the command line chflags -R nouchg /Volumes/{name of your network share}/{name of}.sparsebundle This may take a little while. Now type hdiutil attach -nomount -noverify -noautofsck /Volumes/{name of your network share/{name of}.sparsebundle You will then see something like /dev/diskx Apple_partition_scheme
/dev/diskxs1 Apple_partition_map
/dev/diskxs2 Apple_HFSX Where x is the disk id for the external disk. You are interested in the one labeled Apple_HFSX or Apple_HFS. It might be 2, 3, 4 or higher. At this point, I have found that the filesystem check is already happening. You can check for activity by tail'ing the fsck_hfs.log tail -f /var/log/fsck_hfs.log If fsck is going then in my experience it will be able to repair the sparsebundle. Go away for a few hours and let it chug away. When it is done, you will either see ‘The Volume was repaired successfully' or ‘The Volume could not be repaired' If the latter you can run disk repair again: fsck_hfs -drfy /dev/diskxs2 (Optionally if you have the available RAM, you can set a RAM cache in the command above to help speed up this command like so: fsck_hfs -drfy -c 750 /dev/diskxs2 This will use 750MB of RAM - feel free to change this amount to best fit your