Time Machine keeps and asking to rebuild it !

[cecemf]

Hi,

I have DS212+ and I one hard drive for my time Machines backup and as you know it takes days to backup all your PCs with time Machine and after few days I get this message :



It's all ready the 3rd times it doing it and restarting the time machine from scratch, very frustrating.

I did follow th eprocedure from Synology website to configure time machine on the NAs so i'm not sure if it's a fault from DSM 4.0-2228 (got the latest version) or Mac OS X 10.7.4

Does anyone experience the same issue ? Any solutions?

[relax_nl]

Fix Time Machine Sparsebundle NAS Based Backup Errors
http://www.garth.org/archives/2011,08,2 ... rrors.html

[cecemf]

Fix Time Machine Sparsebundle NAS Based Backup Errors
http://www.garth.org/archives/2011,08,2 ... rrors.html

That's a super quick reply, thank you very much will try that out tonight, seems complicated LOL

[norm0147]

I am also having similar Time Machine issue. It backs up for a month or two with no problem, then get the Rebuild message. Though it will rebuild and start over, I don't like losing the ability to go back to a previous time. I did find this site also http://www.garth.org/archives/2011,08,2 ... rrors.html However I am getting what I think some kind of mounting or pathing issue with Terminal.
For using Time machine I had created a folder named "TIMEMACHINE" on my synology DS410j. The Mac had created the file "My Computer's Name.sparsebundle" which is what is expected in the Garth post. I have tried listing the path part of the command in quotes "" and also without. (It did mention somewhere in there to do that if the sparsebundle was created with a apostrophe s, mine had done that.) I have also tried to include the NAS name in the path. No matter what I try I get "hdiutil: attach failed - No such file or directory"
By what I read on that site it sounds like if I could get it to mount and do the file repair, it would fix the problem and though maybe a tad time consuming, whenever this issue occurs a fix is possible instead of tossing a backup and starting over.

Any help or ideas on this.. Thanks

[relax_nl]

But in general – life is much easier on the command line if you go into the ‘Sharing’ panel of System Preferences and make your machine name something short with no spaces.

[cecemf]

I can't get it to work, I get this:

Code: Select all

Cedrics-iMac:~ root# chflags -R nouchg /Volumes/DiskStationMFBC/TimeMachine.sparsebundle
chflags: /Volumes/DiskStationMFBC/TimeMachine.sparsebundle: No such file or directory

DiskStationMFBC = the name of the DS212+
TimeMachine = Name of the file where the time machine backup is, is that what the .sparsebundle is supposed to be ?

[norm0147]

After logging into the root with Terminal. I had put in

hdiutil attach -nomount -noverify -noautofsck /Volumes/TIMEMACHINE/Norm's iMac.sparsebundle

This returned: attach failed - No such file or directory

I also tried:
hdiutil attach -nomount -noverify -noautofsck "/Volumes/TIMEMACHINE/Norm's iMac.sparsebundle"
hdiutil attach -nomount -noverify -noautofsck /Volumes/SynologyNAS/TIMEMACHINE/Norm's iMac.sparsebundle
hdiutil attach -nomount -noverify -noautofsck "/Volumes/SynologyNAS/TIMEMACHINE/Norm's iMac.sparsebundle"
They all give me the "No such file or directory"

My Synology is named SynologyNAS, and my sparsebundle is in a folder on the Synology named: TIMEMACHINE, and the sparsebundle the Mac created is in the directory TIMEMACHINE and named "Norm's iMac.sparsebundle"

It seems to me I am encountering some kind of pathing issue, but I am at a loss.

Again thanks for any help, it is always greatly appreciated

[relax_nl]

Try to mount on your PC the share that contains the sparse bundle, but do not double click on the bundle.
And then check into the /Volumes folder of the PC the correct path to the file.

[norm0147]

That was one of the things I tried in my numerous attempts, I did notice it had put in a "-1" after the /Volumes/TIMEMACHINE-1
But that also errored with No such file or directory.

I did fail to mention in that Garth's procedure, step one: chflags -R nouchg /Volumes/{name of your network share}/{name of}.sparsebundle
I had tried to just list: /Volumes/TIMEMACHINE/ without putting in the sparsebundle file and it actually ran for like a half hour and unlocked the sparsebundle file. I guess because it was the only file in there it unlocked everything that would have been in that file. But then trying to move on with the hdiutil attach command, it needs a specific file listed. I was wondering if it is some form of naming issue of the sparsebundle. If I renamed the file a short unbroken name might it work, then if it works go back and rename it back to the original, or would that cause me even more problems?

[norm0147]

I took a chance and renamed the sparsebundle a short one syllable name and it took it an displayed the:

/dev/diskx Apple_partition_scheme
/dev/diskxs1 Apple_partition_map
/dev/diskxs2 Apple_HFSX

and now there is a lot of activity on the synology so I guess it is file checking/repairing. He said it can take many hours.

I will let you all know if the overall process was successful. Thanks for the help and for those experiencing the same issue I had, it did appear to be a naming issue, but as of yet I don't know if the renaming I did will cause a problem down the road.

[cecemf]

I can't get it to work, I get this:

Code: Select all

Cedrics-iMac:~ root# chflags -R nouchg /Volumes/DiskStationMFBC/TimeMachine.sparsebundle
chflags: /Volumes/DiskStationMFBC/TimeMachine.sparsebundle: No such file or directory

DiskStationMFBC = the name of the DS212+
TimeMachine = Name of the file where the time machine backup is, is that what the .sparsebundle is supposed to be ?

I'm still seating duck, any advice in what im doing wrong ?

[norm0147]

Cecemf,
I am by no means an expert, nor at this point am I sure this process will even repair the backup. But as far as trying, open Finder up and locate the sparsebundle file, right click it and pick "Get Info" check in that window you will see "Where:" where is it pathed to there? I am just guessing here, but the "DiskStationMFBC" looks like what you named the synology diskstation. I only had to list the file in which the backup was in.

My problem seemed to be the sparsebundle file had spaces and apostrophes in the name which terminal didn't like. But by what you wrote that is not an issue with yours.

[cecemf]

Cecemf,
I am by no means an expert, nor at this point am I sure this process will even repair the backup. But as far as trying, open Finder up and locate the sparsebundle file, right click it and pick "Get Info" check in that window you will see "Where:" where is it pathed to there? I am just guessing here, but the "DiskStationMFBC" looks like what you named the synology diskstation. I only had to list the file in which the backup was in.

My problem seemed to be the sparsebundle file had spaces and apostrophes in the name which terminal didn't like. But by what you wrote that is not an issue with yours.

The terminal you were using is it the DSM one or the Mac os one ?

[relax_nl]

From this

Code: Select all

Cedrics-iMac:~ root# 

I would say you were using the iMac's one, which is the correct one.

After mounting on the iMac the share containing the sparsebundle, have you checked in the /Volumes folder to see the correct path?
Moreover, the name of the sparsebundle might be causing troubles... try to rename it to something simple like TM.sparsebundle before launching the command, and once it has been repaired, rename it back to the original name.

[cecemf]

From this

Code: Select all

Cedrics-iMac:~ root# 

I would say you were using the iMac's one, which is the correct one.

After mounting on the iMac the share containing the sparsebundle, have you checked in the /Volumes folder to see the correct path?
Moreover, the name of the sparsebundle might be causing troubles... try to rename it to something simple like TM.sparsebundle before launching the command, and once it has been repaired, rename it back to the original name.

Thanks will try this.

I though using Time Machine and a NAS was meant to be simple LOL