SD Error copying /.MobileBackups

[fq360]

I've just upgraded to osx lion and have updated SD to 2.6.4

whenever i try to backup it gives the following error :

Error copying /.MobileBackups/Computer/2011-07-22-210007/Volume/Users/simon-cooper/.Trash/Install Mac OS X Lion.app/Contents/SharedSupport/InstallESD.dmg to /Volumes/superduper boot image/.MobileBackups/Computer/2011-07-22-210007/Volume/Users/simon-cooper/.Trash/Install Mac OS X Lion.app/Contents/SharedSupport/InstallESD.dmg of type 8 due to error 28
| 10:20:54 PM | Error | SDCopy: Error copying /.MobileBackups/Computer/2011-07-22-210007/Volume/Users/simon-cooper/.Trash/Install Mac OS X Lion.app/Contents/SharedSupport/InstallESD.dmg to /Volumes/superduper boot image/.MobileBackups/Computer/2011-07-22-210007/Volume/Users/simon-cooper/.Trash/Install Mac OS X Lion.app/Contents/SharedSupport/InstallESD.dmg of type 8 due to error 28: No space left on device

[dnanian]

This is damage to the source volume. Boot to your recovery volume, use Disk Utility to repair the source (internal) drive with the right-hand repair button (not repair permissions), then boot back and give it another try.

[fq360]

how can this be problem with source volume. my MacBook is only 1 week old! has new install of osx lion?
I normally save my SD backup on same volume as time machine. I thought this may be the issue so I plugged external drive into time machine but still same issue
I know lion has backup feature which runs along side time machine to backup whilst on the move, and then copy back to time machine once connected at home again. could this be the issue?

[fq360]

Also why is SD trying to copy my trash?

[dnanian]

Trust me. Do the repair as suggested.

We're not copying your trash in this situation, as such. We're copying your snapshot, and Time Machine copied your trash.

[fq360]

ok will do so. I thought SD was supposed to not copy the mobilebackups

[dnanian]

Why would we not copy that folder? I thought it was probably a good idea to copy the folder, since it's where local snapshots are stored...

[fq360]

I have done repair as advised but still same. been into local apple store spk with genius who advised issue with SD diagnostics showed drive ok

[dnanian]

The genius is wrong. We've had a number of people report this issue, and a repair with Disk Utility has fixed it.

Unfortunately, under Lion, some of the file copy calls are always returning an invalid error when they encounter problems. That error is interpreted as "Disk Full", even when it's not. We reported this to Apple, but we don't know when they're going to fix it.

But if you repair the drive - not permissions, and not verify, but repair with the right-hand buttons - this file should be fixed. If not, you can exclude .MobileBackups if you'd like, using the the steps in the User's Guide. (But that shouldn't be necessary.)

[fq360]

i switched off time machine and proceeded to backup which completed successfully, i have now switched it back on and will try another backup later this week to test, i didn't need the backups so wasn't bothered about losing them, but at least now i have a complete backup.

what is the best way to test the backup to see if it boots ok

thanks

[fq360]

forgot to post after i repaired the disk this was the outcome:

Verifying and repairing partition map for “TOSHIBA MK5065GSXF Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Updating Windows boot.ini files as required
The partition map appears to be OK

but still i had the error in copying

[dnanian]

That looks like a verify, not a repair. Did you start up from the recovery partition and actually repair?

[fq360]

no repair from the disk utility

[fq360]

i booted into recovery partition and repaired using disk until, it came back as bit block error 104.... should be 105.... so repaired orphaned file or something, also my backup didn't show as bootable, it wasn't selectable as bootable image,

I've checked my time machine partition which is showing as mac os journaled, case sensitive, could that be the issue with the image not showing as bootable as my image is stored alongside my TM

thanks again

[dnanian]

OK. So now you have done what I suggested and it did find an error. Good. Did you repeat the copy successfully? Does it show up as bootable in the startup disk preference pane?