Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Install Tiger on improperly set up RAID drive' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Install Tiger on improperly set up RAID drive
Authored by: dcoyle on May 04, '05 08:47:36PM

The particular issue was that Panther had absolutely no problem with the RAID setup created by following the earlier hint. There was nothing to repair as far as Panther was concerned. After creating a RAID pair, I checked several times to see if there was any problem and never saw a reason to worry.

The Tiger software is apparently much less forgiving and expects a "by the numbers" RAID set. By the way, I don't in any way mean to impugn the originator of the post I followed. There were sufficient warnings and it seemed to work just dandy under Panther.

I know you're just trying to make me feel worse by pointing out that I wasn't buying myself much by getting into this jam in the first place. Please see my reply to diamondsw. But thank you sincerely for your input.



[ Reply to This | # ]
10.4: Install Tiger on improperly set up RAID drive
Authored by: rufo on May 05, '05 09:23:11AM

Eh, my intention wasn't to make you feel worse, although I had a rough morning yesterday and was kind of in a cranky mood, so I may have come off that way. My apologies. :-)

You still could've set the other drive as a single volume RAID and rebuilt the mirror though... in the Tiger installer you can drop to the command line and probably run diutil from there (although I haven't actually seen if it has diutil), and then right from there you can head into Disk Utility, wipe the extra drive and rebuild the mirror.

I still think not having any sort of traditional backup is a Bad Idea though. You can be extremely careful and choosy about what sort of software you run and still lose data due to some freak accident - just look at the one iTunes installer package that erased data on any secondary hard drives that had a space in the name because of two missing quote characters. And it doesn't take a freak accident to cause directory damage, just a misplaced power surge or kernel panic. (I don't trust journaling fully since as I said, one of my biggest directory corruptions came while it was turned on... I do believe it prevents most damage but I'm uncertain of it's real capabilities.)

Still, if you want to run without a Real Backup™, fine by me, and if you happen to have all of your important data on a server somewhere or you just don't care if your data is lost then seriously, that's great - just don't complain if something *does* happen. :-)



[ Reply to This | # ]