So about a week ago, I decided to take the plunge and upgrade from Leopard to Snow Leopard (yes I realize that Lion was just released lmfao but anyways..).
I have a late '06 MBP 17" with a 160GB HDD (145GB used) and so I'm the "clean install" kinda guy... I didn't have any External Harddrives, so I rigged my 1TB custom windows computer so TM can backup to it (creating a .sparsebundle file and connecting via ethernet). I backed up, then did a SuperDuper (I'm a nervous guy) also. Then I used disk utility from the Snow Leopard disk to "repartition" my harddrive to 1 partition and then did the install of Snow Leopard. Once it finished, I then updated (combo update from 10.6.0 -- 10.6.8 lol) and then started the LONGGG process of Migration Assistance restoring from the backup (I used Cat5e ethernet cable so I honestly don't understand what bottlenecked it).
I noticed a few problems right off the bat -- First of all, my avg. cpu usage has risen overall, the Process "kernel_task" uses 60+ (usually 70+) threads, and my computer overall is sluggish... which is quite interesting considering I did a clean install... I remember this also happening when I upgraded from Tiger to Leopard (hahaha) and I'm not quite sure how I resolved it... So I'm assuming I just reinstalled again (maybe this time I'll erase before partitioning)...
But I had to go on a week long trip to visit colleges before I could continue... which makes today the day after I got home.
My plan was to let Time machine run all night (this way my consistently revised College App Essay had no chance of disappearing
)...
But it went into this constant cycle:
Scanning 0 files ---> Scanning 1,600,000 files ---> preparing 0 files ---> 1,600,000 files ---> cleaning up (repeat) and its tellign me that last backup was August 7th, so nothing happened obviously.
I do some googling and it turns out its this weird problem requiring a "deep traversal" each time it backs up (well when I started running it a week ago -- no such problems were encountered).
And I double and triple checked the Hardware UUID's from the system profiler AND the SparseBundle Do in fact match up. And I verified the integrity of the disk image in disk utility and it showed NO problems.
So heres the system.log for whats going on:
And again and again and again literally hours before I noticed...
It shouldn't be requesting 156GB considering the UUIDs should match! and if it were the backup would fail instead of loop... right?
Also, snow leopards telling me the condition of my battery is "Replace Soon"... I'm on AC power 99% of the time, but could the battery be causing any problems???
So does anyone have any ideas? I'd rather not erase the sparsebundle and start over incase there are anything I need to restore/ it takes forever to do first backup.
THANKS
Thanks,
Robby
I have a late '06 MBP 17" with a 160GB HDD (145GB used) and so I'm the "clean install" kinda guy... I didn't have any External Harddrives, so I rigged my 1TB custom windows computer so TM can backup to it (creating a .sparsebundle file and connecting via ethernet). I backed up, then did a SuperDuper (I'm a nervous guy) also. Then I used disk utility from the Snow Leopard disk to "repartition" my harddrive to 1 partition and then did the install of Snow Leopard. Once it finished, I then updated (combo update from 10.6.0 -- 10.6.8 lol) and then started the LONGGG process of Migration Assistance restoring from the backup (I used Cat5e ethernet cable so I honestly don't understand what bottlenecked it).
I noticed a few problems right off the bat -- First of all, my avg. cpu usage has risen overall, the Process "kernel_task" uses 60+ (usually 70+) threads, and my computer overall is sluggish... which is quite interesting considering I did a clean install... I remember this also happening when I upgraded from Tiger to Leopard (hahaha) and I'm not quite sure how I resolved it... So I'm assuming I just reinstalled again (maybe this time I'll erase before partitioning)...
But I had to go on a week long trip to visit colleges before I could continue... which makes today the day after I got home.
My plan was to let Time machine run all night (this way my consistently revised College App Essay had no chance of disappearing
)...But it went into this constant cycle:
Scanning 0 files ---> Scanning 1,600,000 files ---> preparing 0 files ---> 1,600,000 files ---> cleaning up (repeat) and its tellign me that last backup was August 7th, so nothing happened obviously.
I do some googling and it turns out its this weird problem requiring a "deep traversal" each time it backs up (well when I started running it a week ago -- no such problems were encountered).
And I double and triple checked the Hardware UUID's from the system profiler AND the SparseBundle Do in fact match up. And I verified the integrity of the disk image in disk utility and it showed NO problems.
So heres the system.log for whats going on:
Code:
Aug 13 23:26:46 Rnc505-2 com.apple.backupd[862]: Starting standard backup
Aug 13 23:26:46 Rnc505-2 com.apple.backupd[862]: Attempting to mount network destination using URL: smb://rnc505@169.254.128.36/Y
Aug 13 23:26:50 Rnc505-2 com.apple.backupd[862]: Mounted network destination using URL: smb://rnc505@169.254.128.36/Y
Aug 13 23:26:51 Rnc505-2 hdiejectd[915]: running
Aug 13 23:26:52 Rnc505-2 com.apple.backupd[862]: QUICKCHECK ONLY; FILESYSTEM CLEAN
Aug 13 23:26:54 Rnc505-2 com.apple.backupd[862]: Disk image /Volumes/169.254.128.36-5/RobbyCohens Computer_0017f2cd5646.sparsebundle mounted at: /Volumes/RobbyCohen's Computer Backups
Aug 13 23:26:54 Rnc505-2 com.apple.backupd[862]: Backing up to: /Volumes/RobbyCohen's Computer Backups/Backups.backupdb
Aug 13 23:26:54 Rnc505-2 com.apple.backupd[862]: Detected system migration from: /Volumes/RobbyCohen's Computer Backups/Backups.backupdb/RobbyCohens Computer/2011-08-07-072547/Macintosh HD
Aug 13 23:26:54 Rnc505-2 com.apple.backupd[862]: Event store UUIDs don't match for volume: Macintosh HD
Aug 13 23:26:54 Rnc505-2 com.apple.backupd[862]: Node requires deep traversal:/ reason:must scan subdirs|new event db|
Aug 13 23:27:50 Rnc505-2 com.apple.launchd[1] (com.apple.netauth.sysagent[905]): Exited with exit code: 255
Aug 13 23:47:20 Rnc505-2 com.apple.backupd[862]: Compacting storage: 156.36 GB requested (including padding), 72.07 GB available before compacting
Aug 13 23:47:20 Rnc505-2 com.apple.backupd[862]: Stopping backup.
Aug 13 23:47:21 Rnc505-2 com.apple.backupd[862]: Backup canceled.
Aug 13 23:47:23 Rnc505-2 com.apple.backupd[862]: Ejected Time Machine disk image.
Aug 13 23:47:23 Rnc505-2 com.apple.backupd[862]: Compacting backup disk image to recover free space
Aug 13 23:47:32 Rnc505-2 diskimages-helper[963]: Reclaimed 0 bytes out of 72.4 GB possible.
Aug 13 23:47:33 Rnc505-2 hdiejectd[915]: quitCheck: calling exit(0)
Aug 13 23:47:33 Rnc505-2 com.apple.backupd[862]: Completed backup disk image compaction
Aug 13 23:47:33 Rnc505-2 com.apple.backupd[862]: Starting standard backup
Aug 13 23:47:33 Rnc505-2 com.apple.backupd[862]: Attempting to mount network destination using URL: smb://rnc505@169.254.128.36/Y
Aug 13 23:47:37 Rnc505-2 com.apple.backupd[862]: Mounted network destination using URL: smb://rnc505@169.254.128.36/Y
Aug 13 23:47:39 Rnc505-2 hdiejectd[978]: running
Aug 13 23:47:40 Rnc505-2 com.apple.backupd[862]: QUICKCHECK ONLY; FILESYSTEM CLEAN
Aug 13 23:47:42 Rnc505-2 com.apple.backupd[862]: Disk image /Volumes/169.254.128.36-6/RobbyCohens Computer_0017f2cd5646.sparsebundle mounted at: /Volumes/RobbyCohen's Computer Backups
Aug 13 23:47:42 Rnc505-2 com.apple.backupd[862]: Backing up to: /Volumes/RobbyCohen's Computer Backups/Backups.backupdb
Aug 13 23:47:43 Rnc505-2 com.apple.backupd[862]: Detected system migration from: /Volumes/RobbyCohen's Computer Backups/Backups.backupdb/RobbyCohens Computer/2011-08-07-072547/Macintosh HD
Aug 13 23:47:43 Rnc505-2 com.apple.backupd[862]: Event store UUIDs don't match for volume: Macintosh HD
Aug 13 23:47:43 Rnc505-2 com.apple.backupd[862]: Node requires deep traversal:/ reason:must scan subdirs|new event db|
Aug 13 23:48:37 Rnc505-2 com.apple.launchd[1] (com.apple.netauth.sysagent[966]): Exited with exit code: 255And again and again and again literally hours before I noticed...
It shouldn't be requesting 156GB considering the UUIDs should match! and if it were the backup would fail instead of loop... right?
Also, snow leopards telling me the condition of my battery is "Replace Soon"... I'm on AC power 99% of the time, but could the battery be causing any problems???
So does anyone have any ideas? I'd rather not erase the sparsebundle and start over incase there are anything I need to restore/ it takes forever to do first backup
.THANKS
Thanks,
Robby