Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
FWIW, I did it! I realized that I had an appropriate drive to clone the SSD from…
#11
rjmacs wrote:
[quote=Black]
What's "done?"
He's got part of an outdated backup installed and still has to figure out how he's going to be able to access most of his files.

Who pissed in your cornflakes this morning? Can't we have a little moment here? :damnyou:

Sorry, I'm finding this forum's approach to helping Gene unusually brain-dead. The way he ended up accomplishing this is going to be a mess to get working.
Reply
#12
Clone your SSD now...just in case you need to reformat.
Reply
#13
wowzer wrote:
Clone your SSD now...just in case you need to reformat.
I would wipe the SSD and re-clone from his current main 1TB drive, with some sort of systematic )=as simple as possible) approach to determining which sub-folders not to bring over.
Reply
#14
Black wrote:
[quote=rjmacs]
[quote=Black]
What's "done?"
He's got part of an outdated backup installed and still has to figure out how he's going to be able to access most of his files.
gure out how he's going to be able to access most of his files.
Who pissed in your cornflakes this morning? Can't we have a little moment here? :damnyou:

Sorry, I'm finding this forum's approach to helping Gene unusually brain-dead. The way he ended up accomplishing this is going to be a mess to get working.
I really hate to say this, Black, but it seems to me that you left your statement unfinished. I'm happy to have the SSD set up as a bootable drive, at last, but...

...you infer that there's a problem with the way that I got it done.

How is it a problem? What issues will I have that I wouldn't have if I had done the install another way?

Over the years, I've appreciated your suggestions, so for me and for some of our other friends who basically suggested the method that I ended up using, please clarify your seemingly negative pronouncement with an more detailed explanation.

I, for one, want to make sure that what I ended up doing to get the SSD up and running, isn't going to bite me in the tush, later on.

As you say, I do still have to "figure out how he's going to to be able to access most of his files." So, where's the explanation? If you see a problem with what I've done to clone the SSD, please don't leave me hanging. Fill in the answer.

I'm sure that not only will I be grateful, but no doubt others will be as well.

Rather than being seen as a "party pooper" the explanation would turn your statement into a welcome contribution.

I always appreciate the fact that you and all my other forum friends take the time to send their thoughts to me.

Immediately helpful or not, these thoughts seem to guide me to a successful conclusion.

I find that many things in life that are frustrating work out just fine, given a little time and lots of input. The more to choose from, the easier and better the solution.

So, Black, please don't leave me hanging. Please fill in the blanks!

Your friend,

GeneL
Reply
#15
If this were me. And it was last year sometime. I would do a fresh install of the OS on the SSD. Then I would install all the apps I KNOW I will need immediately. Keeping in mind, I will be installing them in the future as needed. Keeps unnecessary cruft from transferring from the old drive. Then I would tell iTunes to use my larger HDD as the repository of all my music and make sure it "moves" everything there. In addition to the iTunes folder, I would have a photos folder as well as my "projects" folder.

That's it. The only thing extra required is a blank HDD to transfer the larger files to from the original HDD.

Was it instant gratification? No. It took a good bit to make sure I had reinstalled all the apps I needed. But it was also nice to know that I didn't move a bunch of apps (and their support files) that I hadn't used in years over to my current drive.

Furthermore, I kept my original backup (the source from which all this sprang) for a while so I could refer back to it if I needed some pref files or some Application Support files.
Reply
#16
bazookaman wrote:
If this were me. And it was last year sometime. I would do a fresh install of the OS on the SSD. Then I would install all the apps I KNOW I will need immediately. Keeping in mind, I will be installing them in the future as needed. Keeps unnecessary cruft from transferring from the old drive…

Yep, that's the procedure I used when I moved from my steam-powered 1937 Apple McIntosh confuser to my new Late 2012 iMac w/ Fusion drive.

It was a prolonged and painstaking process but my new system is super clean, reliable, and fast.
Reply
#17
To set the record straight, I had recently done a fresh install of Lion to the original Apple drive that I cloned. Because I so rarely used it, it had most, if not all of my mainly used apps installed and not a lot more.

I'm thinking that it was the perfect candidate for making a clone to the SSD.

It would have been great if I had thought of it sooner, but it didn't come to mind until after I struggled for awhile. Seems to have ended well, though.

Now, I do need more suggestions about how to bring the SSD up to speed with a clean connection to any and all the files that are still on the 1TB internal drive that has been my main "working" drive, until now.

From what I've seen, the end result should make it seem as if all my files are stored on the SSD, even though they are actually on another drive.

One question comes to my mind. Should I change the drive, which is now a "slave" by removing the OS and treat it just like a folder? I'm not sure how I'd do that.

How I set up this function is the balance of this project and that is where I need guidance.

May I have more gruel, I mean guidance, PLEASE!

I may have to hit the lottery in order to buy all the margaritas that I'm offering in thanks for the very kind support that everyone has given me.

Thanks again!

GeneL


bazookaman wrote:
If this were me. And it was last year sometime. I would do a fresh install of the OS on the SSD. Then I would install all the apps I KNOW I will need immediately. Keeping in mind, I will be installing them in the future as needed. Keeps unnecessary cruft from transferring from the old drive.

That's it.

The only thing extra required is a blank HDD to transfer the larger files to from the original HDD. This puzzles me. I have four internal drives, two of which are 1TB and have been used as my main drive and backup. They have everything on them that I've been using over time. So, why would I need a blank hard drive and why have to transfer anything from my original drive, since it's right there in my Mac Pro?

Was it instant gratification? No. It took a good bit to make sure I had reinstalled all the apps I needed. But it was also nice to know that I didn't move a bunch of apps (and their support files) that I hadn't used in years over to my current drive.

Furthermore, I kept my original backup (the source from which all this sprang) for a while so I could refer back to it if I needed some pref files or some Application Support files.
Reply
#18
GeneL wrote:
One question comes to my mind. Should I change the drive, which is now a "slave" by removing the OS and treat it just like a folder?

HELL no.

It's handy to have a spare boot drive, the items in the Library folder may prove valuable as you accommodate the move to the SSD and the OS, itself, takes up little drive-space.
Reply
#19
Okay! Thanks.

I'm still looking for the method to use to complete the install. How do I best create the links to the "old" drive.

I did see the tips about iTunes and that I can link to the iPhoto library by holding down the option key when I open iPhoto on the SSD. That's right isn't it.

What concerns me are the several inferences that it's more complicated than it appears to create the linkage between the SSD and the files on the old drive. It seems that if I don't do it the"right" way, it will create problems.

I'm in the dark about this, so please, someone enlighten me.
Reply
#20
My concern would be that Gene's landlocked, and can't surf the waves of Mavericks, and beyond, on that old tower. A new Mini will probably be in his future anyway, so this bunch of hoop-jumping is basically a practice run; it doesn't have to be perfect, it just has to give him that wonderful SSD experience that is continually praised amongst these parts. Whether all the apps and files are set up completely properly really doesn't matter. As long as enough of them are, he gets the SSD wow factor, which ought to be considered a success given the scope of his project.

'zook nailed THE solution, anything else is just part of an extended learning experience, which will hopefully be beneficial at some point in the future as additions to Gene's toolkit. If he gets it working, for now, whether it's 100% proper or not, and sleeps better, it is a win. Perfection awaits Gene on his future Mini... and he has something to look forward to; I'm pretty sure none of us here would wish for anyone to really be stuck on Lion forever.
==
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)