Prev: Trouble loading page
Next: Ultramax fan replacement - getting rid of the hard-covers?
From: eastender on 11 Dec 2009 12:55
In article <ncd4i5tdub16trs2l6fj9o6ja28mkcu3qc(a)4ax.com>,
Jaimie Vandenbergh <jaimie(a)sometimes.sessile.org> wrote:


> You can always go for an over-the-top installation, and re-import users and
> apps etc from the TM backup using the Migration Assistant that pops up
> at the end of installation.


OK - I bit the bullet and reinstalled Snow Leopard on the faulty
partition with the TM backup in place. It works fine now but I had to:

- Run all the SL updaters
- Reimport lots of fonts from the backup that were in the system library
(and which I messed with in the first place and caused the problems - it
was a proof that came back from a repro house with no Zapf Dingbats in
that triggered my activity....)
- Reinstall Microsoft Office - for some reason this did not survive. And
installed two massive updaters.

Everything else works fine so far but I'd like to know why the restore
was assessed as bootable but wouldn't.

E.
From: eastender on 11 Dec 2009 13:47
In article <nospam-521ED0.17553111122009(a)news.virginmedia.com>,
eastender <nospam(a)nospam.com> wrote:

Oh and Time Machine is starting backup from scratch - all 190GB of it.

E.
From: Chris Ridd on 11 Dec 2009 14:26
On 2009-12-11 17:55:31 +0000, eastender said:

> Everything else works fine so far but I'd like to know why the restore
> was assessed as bootable but wouldn't.

I suppose it just checks a few common files/directories are present and
plausible-looking. And your machine *did* boot up to a point...

--
Chris

From: eastender on 11 Dec 2009 15:13
In article <7ofkmhF3pgohuU1(a)mid.individual.net>,
Chris Ridd <chrisridd(a)mac.com> wrote:

> I suppose it just checks a few common files/directories are present and
> plausible-looking. And your machine *did* boot up to a point...

Indeed, up to a point, Lord Copper. But up to a point don't get no work
done. Having moved my production machine from a G5 with Superduper
backup (which boots perfectly) to the Mini I sort of assumed Time
Machine would now be robust enough to keep me running. But of course
even if it had worked it takes a long time and I presume you can't boot
from the backup drive as you have all those linked folders.

E.
From: Jaimie Vandenbergh on 11 Dec 2009 16:57
On Fri, 11 Dec 2009 20:13:32 +0000, eastender <nospam(a)nospam.com>
wrote:

>In article <7ofkmhF3pgohuU1(a)mid.individual.net>,
> Chris Ridd <chrisridd(a)mac.com> wrote:
>
>> I suppose it just checks a few common files/directories are present and
>> plausible-looking. And your machine *did* boot up to a point...
>
>Indeed, up to a point, Lord Copper. But up to a point don't get no work
>done. Having moved my production machine from a G5 with Superduper
>backup (which boots perfectly) to the Mini I sort of assumed Time
>Machine would now be robust enough to keep me running. But of course
>even if it had worked it takes a long time and I presume you can't boot
>from the backup drive as you have all those linked folders.

That's correct, it's there as a repository that the OSX DVD can
retrieve the system from (or not...), and it's not bootable.

I keep a spare USB hard drive around with a handy emergency install of
SL, and take a Carbon Copy Cloner clone before doing anything dubious
like OS major version upgrades.

Otherwise TM does indeed do okay for me - I've used it for retrievals
of anything up to whole user folders from the backup, and it's always
worked fine.

In a tiny note of similarity, the only time I've had the OS smash
itself enough not to boot has been due to fonts. That was 10.5.3 ->
10.5.4 or thereabouts, using the combined update.

Cheers - Jaimie
--
Power corrupts, but intermittent power corrupts absolutely
-- Jeff Bell, asr
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Trouble loading page
Next: Ultramax fan replacement - getting rid of the hard-covers?