V440 hardware raid failure ( boot disk)

we use raidctl -c c1t0d0 c1t1d0 RAID Volume 'c0t0d0' created ,by if c1t0d0 disk failure , how to replace HDD

Perhaps follow the guidance that is in the V440's manuals?
http://docs.sun.com/app/docs/coll/v440

Similar Messages

  • Mirrored Raid as boot disk?

    I have a flat panel iMac (PPC) that I would like to have a bit more reliable. Due to the number of files I have on this machine, it is currently configured to boot from an external Firewire drive. Recently, I have added a second external firewire drive of the same size, and am considering a Mirrored raid configuration for this system. I am primarily interested in reliability, not increasing the performance of the system, hence the mirrored, rather than stripped, raid configuration.
    It is clear from other postings on the web that a stripped raid requires a) reformatting the drives, losing all data, and b) cannot be used as a boot drive, which is mandatory in this case.
    Therefore my questions:
    1) Can I create a mirrored RAID using Disk Utility without data loss? One drive is newly formatted, the other is full of data.
    2) Can this RAID be used to boot an early flat panel iMac?

    Hi Eric Hildum;
    1) No.
    2) Probably yes. Practically no because it is going to cause you more problems then it is worth running both disk ins a RAID over a single Firewire channel.
    Don't forget that Raid is not a valid backup solution. Any data on the RAID array should also be backed up for it's protection.
    Personally for the home user, I think a good backup solution beats RAID. Usually there are less problems with backup then RAID.
    Allan

  • Moving boot disk to raid 0

    Hi Guys,
    I have the following volumes on my MacPro
    1. Boot Disk - 465.3 GB, 200GB used
    2. Raid 0 volume - 436.2 GB
    How easy is it for me to move the boot disk data to the raid 0 volume and then boot from the raid 0 partition.
    Also I have heard that if you have a raid 0 boot disk that the firmware updates can fail, is this still true.
    Thanks for any help
    Andy

    Quicken Data files are actually packages, which can contain alias to the volume. Once I stripped the aliases from the data file, no problems, but for the longest time (years) everytime I cloned and used a different volume I'd run into trouble.
    LittleSnitch hard codes the volume name, but also WHERE on the volume, an application is located. Very annoying.
    So it may be plist or preference, but it could also be writing an alias to data file, or even back to the application package itself.
    You would think at some point during testing especially, a light bulb would go off and realize there is a better way to code (unless it really is deliberate and trying to tie a program to only a single volume type system, which the Mac doesn't need to be).
    Feedback the vendor. However, unless you do a lot of moving stuff around (like during testing) it is a "once only" event. If you name the new RAID boot volume with same name, might not even matter.
    I do a lot of backup and restores during the course of a week, SuperDuper works well, not 200% perfect maybe, but works.
    I keep my boot volume, though, free of my home account. That resides on another volume and can last for years. The boot volume gets changed more often. And I think having "home account" (but not /Users) not be on the boot drive makes it easy and avoids some of these problems even.

  • System configuration & services data on boot disk or external volume?

    Assuming a RAID 1 boot disk using 2 large capacity hard disks on a Xserve, which system configuration and services data shall one store on the boot disk and an external volume?
    I am thinking of keeping DNS records and Open Directory data on the boot disk while mail store, web documents and user data in an external volume. What about database file such as MySQL?
    What is the normal and/or best practice in this matter?

    nope. doesn't matter a damm if you put the content on a secondary drive (as long as its plugged in when you want to use it!) ... the benefit of having it on a secondary drive would be to free up space on your system disc, if necessary (useful on a laptop, but means carrying around an extra portable drive for ths content) ... don't use your media drive though, better to save that for your projects captured/imported media only.
    cheers
    Andy

  • Hardware raid boot disks on m5000

    Is it possible to configure a raid 1 on boot disks to this machine?
    The M5000 has the LSI 1064 controller and it seems to be possible..
    After booting from dvd (boot cdrom -s):
    # raidctl -c -r 1 c0t0d0 c0t1d0
    Creating RAID volume will destroy all data on spare space of member disks,
    proceed (yes/no)? y
    Operation not support with volume of this level.
    The controller is in GOOD state...
    # raidctl -S
    0 "LSI_1064"
    0.0.0 GOOD
    0.1.0 GOOD
    3 "LSI_1064"
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c0t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0
    1. c0t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0
    Any ideas?
    Many thanks,
    Mauro.

    I configured mirror boot disk using Solaris Volume Manager...

  • My hardware RAID 1 only showing up in disk utility and not finder.

    Last week I finally was able to take my early 2011 iMac in to have my Seagate 1TB hard drive replaced for the recall.
    Late 2010 model iMac
    OS X 10.6.8
    OWC Mercury Elite Pro 4TB x 4TB Hardware RAID
    When I took it in the RAID 1 was working just fine. When I finally got the iMac back and booted everything up the RAID 1 was getting the dialog box that read "The disk you inserted was not readable by this computer."
    I have tried going into disk utility to see if I can verify the disk and then saw it is coming up as two different volumes... Along with those two different volumes, I can not go to click verify as it is greyed out.
    I contacted OWC and they said they have never heard of this and had two solutions, to try a software like diskwarrior, or if that didnt work I can take the drives out and try another external dock to see if it is the RAID hardware.
    If anyone has any ideas as to what could help with this situation that would be great as I was under the impression (and told by a number of other people) that having a RAID 1 as my backup was good and should not need anything else. I just want to be able to get all the data off then I will rebuild it or send it into OWC.
    Thanks!!!!

    So a fault in the Hardware Raid controller could make it not read properly? I am planning on having a good backup set up after this!
    As for the screenshot, the original was not set up with the SoftRaid. When I got the computer back I installed that to see if that may pick it up and make it at least readable to save the data on it. The two in question are the highlighted 4TB drives, which befor also read as one drive as it was set up in the OWC enclosure as a hardware raid.

  • Hardware RAID on V440 - RAIDCTL reports strange size.

    Got 4 disks in my system. Solaris installed on disk2. Others not used.
    So, did :- raidctl -c c1t2d0 c1t3d0
    Now it looks like t3 has disappeared now when I do format (as expected). Output of raidctl is-
    bash-3.00# raidctl
    Controller: 1
    Volume:c1t2d0
    Disk: 0.0.0
    Disk: 0.1.0
    Disk: 0.2.0
    Disk: 0.3.0
    Controller: 2
    However, the strange thing is if I do raidctl -l c1t2do its reporting the volume size as 744Mb
    raidctl -l c1t2d0
    Volume Size Stripe Status Cache RAID
    Sub Size Level
    Disk
    c1t2d0 744.9M N/A SYNC OFF RAID1
    0.2.0 744.9M GOOD
    0.3.0 744.9M GOOD
    Since both disk are 146Gb I assume the volume size would 146Gb?
    Also, since these two disks are now mirrored (or will be when the sync completes), if I get a disk failure what happens?
    At the moment boot-disk is set to disk2. Will this still work if say physical disk2 fails but the mirror disk3 is still up? Or would I then need to boot from disk3?
    Alternatively, could I remove a faulty disk2, replace disk3 int disk2 slot and still boot disk2?

    Hi,
    Weather the server is up and running now .
    If it is up and running then just change the parameters of boot-disk to disk3.
    Why because if suppose the server reboots it will not come up . So do this first .
    Before doing this just check weather you have a bootblk in the both disks.
    if not just install it
    * installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk <path of the disk3>*
    If this has not installed the server will try to come up but will still staying at OK prompt.

  • Best protocol for dual booting on a hardware RAID 0 array?

    Hi folks. I would like to dual boot Windows 7 and Arch. I'll append the specs. I have a Terrabyte to split evenly between the two drives - each is 500G. Unless someone can come up with a reason and convince me otherwise, I want to do away with the RAID array. There's no redundancy anyhow and the speed I would lose breaking the array is negligible, therefore irrelevant.
    My issue is that I have a RAID 0 hardware array with Intel Rapid Storage Technology as the controller. The computer did NOT come with a Windows disk, but rather a recovery partition. It is my understanding that if I break the array, I will lose the recovery partition and will not be able to reinstall Windows - which I need. IF....the recovery partition can be unphased by breaking the array and I can use it to reinstall Windows, I would prefer that since I may need to recover Windows in the future. It's not a deal breaker if I can't keep the recovery partition, since I have the Windows key.
    Is this the ideal protocol?:
    1. Backup - I plan on using Alienware Respawn or Clonezilla to backup to a CD and will also backup to an external drive.
    2. Break array, but do not alter BIOS to AHCI - leave as RAID.
    3. Restore Windows on one drive.
    4. Install Arch on second drive.
    5. Configure GRUB.
    6. Smoke stogie or alternatively weep because I turned my computer into a brick.
    At which stage does the partitioning come in? Before or after breaking the array? Is there a better method, than the one I listed. I have spent days scouring Google and the forums and while it's easy to find info on breaking a hardware RAID, there isn't much on doing this with the recovery partition and Alienware Respawn aspects involved. Any help would be appreciated. Please don't kill me or shred my diameter.
    ==================================================================================
    Specs:
    Processor: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz 1.73 Ghz: 8 Intel(R) Core (TM) i7 CPU q740 @ 1.73GHz
    Installed Memory: 8.00 GB RAM
    64 Bit Operating System
    Alienware M17X10
    Windows 7 Home Premium
    Performance Options: DEP turned on. Virtual Memory: 8180 MB
    Architecture: AMD64 Intel64 Family 6 Model 30 Stepping 5, GenuineIntel
    Computer: ACPI x64-based PC
    Display Adapters: 2 ATI Mobility Radeon HD 5800 Series
    DVD/CD-ROOM: HL-DT-ST DVDRWBD CA10N
    IDE ATA/ATAPI controllers: Ricoh PCIe Memory Stick Host Controller, Ricoh PCIe SD/MMC Host Controller, and Ricoh PCIe xD-Picture Card Controller
    IEEE 1394 Bus host controllers: Ricoh 1394 OHCI Compliant Host Controller
    Imaging devices: Integrated Webcam
    Mice; 3 HID-Compliant Mouse and Synaptics PS/2 Port Toch Pad
    Monitor: Generic PnP Monitor
    Sound, video and game controllers: AMD High Definition Audio Device and High Definition Audio Device
    Storage Controllers: Intel(R) Mobile Express Chipset SATA RAID Controller

    I think the big thing will be backing up. I don't know anything about the two programs you would use, but I know that if I dd copy the disks, I would have to change the size of the partitions to match the size of the new partitions. IE: I have Arch installed on a RAID0 of 32GB each, and if I wanted to break my RAID and install on just one disk, I would have to shrink the size of my dd'ed copy to match the smaller drive.
    Otherwise, it looks like you have the right idea, or at least the right direction.

  • System won't boot from Windiws XP boot disk after setting up RAID 0 array???

    After connecting my two Western Digital Raptor on SATA ports 1 and 2, and finally being able to launch the Bios option ROM "Intel SATA Raid manager" (had some problems associated with an LSI 4i megaRAID adapter in a pci slot), I was able to put the two disks in RAID 0. After exiting the Raid manager, the DMI pool was updated, and I was expecting the computer to boot from the XP installation boot disk in the optical drive. Instead I got the message: "Disc boot failure. Insert system disc and press enter.". This is very strange, as I installed XP earlier with the Raptors functioning as IDE drives without a problem (so IDE was selected in the BIOS for SATA drives instad of SATA as in this case). As a result I am unable to install Windows XP (professional).
    My system configuration: 
    Motherboard: Platinum power up edition
    Bios version: W72461MSv7.3
    CPU: Intel Core2Duo 6700
    Memory: Corsair, 2 GB in matched pair DDR 2, now on 2 volts
    Harddrives: 2 western digital raptors of 150 GB in RAID 0
    Optical drives: LITE-ON DVD-rewriter and reader from same brand (also DVD)
    PSU: Corsair 620 Watt
    Now removed: LSI Megaraid 4i adapter (pci) with 4 Samsung spinpoint harddrives of 4 in raid 5
    XP professional
    Boot sequence: CDROM, floppy and harddisk in this order
    BIOS settings:
    USB keybooard and mouse disabled
    JMB361 option rom disabled (not using it)
    Onboard lan boot rom disabled (not using it)
    Sata mode set to RAID
    All other settings "optimal" using F7 in BIOS
    Usinf F11 during startup doesn't help: the CDROM is not displayed in SATA mode, only floppy and harddisk.
    Using Microsoft XP professional boot floppy's did'nt help either. System restarted after loading first floppy (ther are 6 in total), and no result.
    Any suggestions would be greatly appreciated...
    Hans

    so your problem is TWICE as important, and you start another thread.
    https://forum-en.msi.com/index.php?topic=104173.0

  • Can't set up Raid-1 on boot disk

    System 2 days old:
    I have sucessfully loaded windows xp/pro twice with no raid.
    When I try to set up the raid-1 for my boot disk all goes well untill I get to
    windows setup (Press F6 to load 3rd party . . . )
    After pressing F6 I get the option to load the RAID drivers (flopy disk with MP)
    When selecting either of the two options for loading off the flopy I get the following
    error:
    file nvata.bus.sys caused an unexpected error (4096) at line
    2108 in d:\xpspi\base\boot\setup\oemdisk.c
    Press any key to continue
    Any ideas I would really like to run these two SG 120s RAID-1 please advise.

    Officially, yes, you need to off-load to a backup, configure the RAID-1, and reload onto the mirrorset.
    If you're feeling lucky, you can potentially [activate RAID-1 without the archive|http://www.afp548.com/article.php?story=20040827122302975]; on-line. Search for (other) discussions of using the DiskUtil tool and enabling disk mirroring for various of the previous discussions.
    But if something goes wrong with the on-line conversion, a bug or a power drop-out or a disk glitch or or... ?
    RAID-0 is striping; two disks together presented as one bigger disk; targets I/O performance.
    RAID-1 is mirroring; two disks together presented as one; targets reliability.
    RAID-0 and RAID-1 (and the other RAID levels) can be hardware-based or software based.
    The Mac Mini Server uses software-based RAID.
    And for completeness, neither RAID-0 nor RAID-1 is an archival strategy.
    As for the other question, do you have one disk showing, or two? If two, you're not running RAID-1. All of the Mac Mini Server boxes I've seen have arrived not configured for RAID-1. They've arrived as two single disks; as what the RAID folks tend to call JBOD; Just a Bunch Of Disks.

  • Xserve G5 won't boot off Hardware RAID partition

    I'm running an Xserve G5, 2.0 GHz single processor, OS X Server 10.4.5 with an Apple Hardware RAID card with 3 500GB drive modules in a RAID 5. The RAID is partitioned into two partitions, one for the system and one for data. After installing a video card, the Xserve will not boot off of the system partition on the RAID. It will boot just fine off a clone of that exact partition on a firewire drive, which is how I have it functioning at the moment. I have tried erasing the system partition on the RAID and re-installing the Server software but whenever I try to boot it it gives me the flashing folder Icon. I have tried resetting the NVRAM as well as restoring the functional backup of the system to no avail.
    Any ideas? (I have run disk utility, DiskWarrior, repaired permissions etc.) I also checked the status of the RAID and it is in optimal condition. The data partition seems to be just fine and the system partition seems normal when booted from the external drive.
    Xserve, Dual 2.7 G5, G4 Powerbook, many others   Mac OS X (10.4.5)  

    Harry, I just saw your post. I went through the same pain last fall, and it WAS resolved through Apple Support, but you aren't going to like the solution. Simply as background, during the pre-deployment testing of our Xserve, we were having problems with the Apple BTO SCSI card (really, an LSI Logic 22320) and swapped it out with an ATTO UL4D. Something in the card removal/replacement caused our Apple Hardware RAID card to go into the same mode as yours, where it would work fine as a RAID 5 (two LUNs, 50 GB and 417 GB, over 3x250 GB ADMs) but would not boot. Apple Support and I concluded that something had become corrupted in the firmware or boot code on the Apple Hardware RAID card, but they did not have a file to use to flash it, so they swapped out the card under our support contract, and that fixed it. I still believe that, if I had had a file to flash the card with using the megaraid command, that the original card would have been fixed. FYI the new card has Firmware Version: A131, BIOS Version G117, the old card had Firmware Version: A130, BIOS Version G117. Completely unrelated to this, I've had a RADAR bug report (RADAR #4350243) open since last November that the Apple Hardware RAID card fails to fully flush its write caches on graceful power down. I've got a test case that is 100% reproducible, causes mystery garbage blocks from space. I'd suggest that you turn the write caches off on all LUNs on your Apple Hardware RAID card as a workaround until this is fixed. LSI Logic (the Apple Hardware RAID card is a rebranded LSI Logic card) found and fixed this bug on a later firmware rev from Apple's version. No update is available yet from Apple.
    Xserve G5 Mac OS X (10.4.6)
    Xserve G5   Mac OS X (10.4.6)  

  • Neo4 K8N Plat SLI - Boot Disk Failure :(

    Having installed Windows XP Proffesional, I installed the graphics card drivers and was asked if I wanted to restart. I went ahead and restarted, and was confronted with the "boot disk failure..." error message.
    I eventually decided to reinstall Windows but when the "press any key to boot from CD" message came up, in an act of defiance, I decided that I wouldn't press any key at all.
    I was suprised to see Windows load up.
    Booting without the Windows CD in the drive results in the error. With the CD in the drive it boots - what could be causing this? The mobo, the HDs, the OS?

    The Samsung ... yes, that's a sad story ... 
    I'm one of the people who believes that two disks in a SATA Raid don't nessecarely have to be the same brand. It even haves some pro's to not use the same types of disks, but that's another topic. They should, however, be the same size of course. I used one Samsung spinpoint (120GB) and a Western Digital Caviar (120GB) in a Raid-0 array. On the Dutch forum this array is known as "RAID-UI"  . It worked pretty well, no crashes, pretty fast data transfers ... but then, one day, I had a hickup using Ghost. I saw: Creating image of C: 23% complete ... And it stood there for a very long time. After that, Ghost shut down giving an I/O error. I investigated the error and becam aware that there were disk errors on C: (one partition of two on the SATA RAID-UI). I had the whole lot repaired using CHKDSK and everything seemed OK again.
    I looked in the VIA Raid tool and saw a difference in size between "capacity" and "real capacity" of about 0.064MB on the Samsung. Well, nothing to cry about yet. But I kept on getting disk errors and I kept on having to run CHKDSK. After a week I lost over 25MB and every day I lost more to bad clusters. Knowing that two striped disks have to be the same size, I started to wonder when this raid would crash. But, since I don't like the idea of suddenly loosing a 220GB disk array, I decided to throw out both the Samsung and the WD. (The WD is in another PC). I bought two Seagate disks and didn't go back to Samsung, because of the terrible answer I got from Samsung Holland.
    I mailed them about the broken disk and asked for a replacement (disk is about 13 months old and there's a two year waranty). They simply refused to give me a replacement. They stated that I probably messed around with the disk, cause of the bad clusters. Stupid anser, to my opinion. The disk simply died from one day to the other.
    Note that this disk has always hung right behind an inlet fan! So it never got hot.
    I'm very happy with the seagates now. They're more quiet and ... FASTER! I get data-transfers of about 94-96MB/s, while with the other array the max was about 88MB/s.

  • Booting from external SATA firewire800 hardware RAID array

    Just a quick post to update on a new toy and how it's being used.
    Recently obtained a hardware RAID array which contains 5 drives at 250 GB each. Currenly setup as RAID 5, providing 1TB of storage.
    After formating via DISk image I did a drive restore from my normal boot disk to the new array.
    I changed the startup options to boot from the array.
    So basically I am running my system from this new device.....I may later reconfig the array to 0+1 with a floating spare.
    Cost of the box was 500. New and unused off ebay.

    ..

  • Hard drive failure (why can't I start up with boot disk)?

    Running OS 10.4.6. I was getting flashing question mark at startup. Tried starting with Disk Warrior holding down "C" key. Got Apple logo, but then screen frooze with horizontal lines across screen.
    Rebooted, held mouse to eject disk. Tried TechTool Pro disk. Would not boot from that either (got circle with slash logo I think).
    Finally was able to boot with Tiger install disk.
    Ran disk utility from Tiger disk. My internal hard drive showed up in red letters and said "failing"
    OK.....I can understand that.....I guess my hard drive crashed (on my 2 year old Powerbook...oh well)
    But, why can't I start up with any of my boot disks (Disk Warrior, TechTool) only the Tiger install disk. Also the Panther and Jaguar disks will NOT start it...only the Tiger disk works. One more thing I'm wondering....I connected my external firewire drive that has a boot partition on it that I have started up with in the past....and it won't boot my laptop either.
    Any ideas? Thanks for any insight. Guess I'll head to the genius bar tomorrow. At least my extended warranty is still good (I think).
    Powerbook G4 17 1.5 ghz   Mac OS X (10.4.6)  

    Here is what the outcome was:
    I took my Powerbook into Apple Genius bar (still under 3 yr. AppleCare), he determined that my hard drive had crashed. He shipped it for me to be repaired.
    It came back with a message attached saying that the source of the problem was my 3rd party RAM, which was a 1 GB module. The note said that the memory had been removed...and that in some cases like this the removed memory will be sent back to the customer and will be in the box somewhere. I checked and it wasn't there. The "Get Info" for my system said I was now running on 512 mb instead of the usual 1.5 GB. The note said that this 3rd party RAM had caused the hard drive to fail, so the hard drive had been replaced.
    I ordered a new 1GB RAM module from Apple for $300, didn't want to take a chance on 3rd party again. But....when it arrived, I went to install it....and my 1GB 3rd party module was in the slot....it just wasn't pushed all the way in I guess. I pushed it in firmly, closed up the computer, started it, and the "Info" read 1.5 GB again. I ended up removing the 512mb module and replacing that with the new 1GB one I bought from Apple. So now I have 2GB of memory and and extra 512 that I can't use. It has been running fine ever since (more than 2 months)
    Can bad RAM really make a hard drive go bad?
    I wonder why they said they had removed the RAM, but it actually had not been removed (at least not completely)
    Powerbook G4 17 1.5 ghz   Mac OS X (10.4.7)  

  • Best Practice???  Change from internal boot disk to external disk

    I have a mini running 10.5.6 server and it currently boots off it's internal disk. I was hoping to get some feedback/input from others on a good process to convert the system from it's internal boot disk to an external boot disk (firewire).
    I wanted minimum downtime during the conversion and I of course, want a complete snapshot on the new boot disk. Lastly, I do not have a local keyboard and console on the system although I could connect one if it seemed to be much easier that way.
    In general, I am thinking of the following:
    1) Boot into the Leopard Server CD.
    2) Use diskutility to Restore from the internal boot disk to the new external boot disk.
    3) Choose the new boot disk as the startup disk.
    4) Reboot onto new disk.
    Is diskutility the best bet?? Meaning will it work this way if the drives are different sizes??
    Should I try to clone the disk from the internal boot disk (assuming I shutoff services first) using SuperDuper or Carbon Copy Cloner?? But I believe they do not copy over all logfiles, etc..
    Or does anyone have a quick overview of a methodology which they have done in the past or just are suggesting might be a better process than the ones I described??
    In Summary:
    1) From the CD, clone using diskutil and change boot disk
    2) From the running OS, clone using SuperDuper or CCC and than reboot onto new disk
    3) Something else??
    Thank you in advance.

    For cloning the machine you have the approach fine. Disk Utility is fine and booting from the CD is the best method. Simply use the restore method.
    But why on earth would you want to boot from an external Firewire drive? First, there is the issue of speed. You have a mini, let's assume it is a one generation back Intel. It has an internal SATA drive on a 1.5 Gbps connection. You want to move that to a 400 Mbps Firewire bus? Next, beyond the speed issues, you have a persistence issue. You are taking the boot volume and moving into to a transitory bus. One of Firewire's greatest strengths is easy connection/disconnection. Persistence is not a strong point.
    Next, if your plan is to move the boot volume to some form of a Firewire RAID, then you are even penalizing yourself more. The mini has one FireWire port. If you are using two devices and creating a mirror RAID, then you need to daisy chain. Talk about points of failure, asynchronous startup time, bus blocking, etc. Not wise.
    Plus, I can not count how many external firewire devices have burnt up in the effort to have small footprints. Lacie and the "let's put a drive in a metal case with no fan" approach = melted drive. Western Digital and Lacie with the "let's make a completely un-reusable external power brick that either breaks in a small breeze or falls out when the heavy guy walks by the server" approach.
    If you are looking at a Firewire RAID enclosure, then you are missing the objective of speed as you are limited by the 400 bus. It is nice to say that you have a four drive SATA 2 RAID case running a RAID 5, but you are defeating the purpose of why you bought the raid. The RAID 5 can provide an exponential increase in I/O performance. But that goes out the window because of the slow bus.
    If your argument is that "this is a server and my bottleneck is Ethernet," that too does not hold up. You are likely running on a gigabyte network.
    For system details check out http://developer.apple.com/documentation/HardwareDrivers/Conceptual/Macmini_0602 /Articles/architecture.html.
    Take this with a grain of salt. You caught me on a grumpy day as yesterday I dealt with a melted external firewire drive.
    My advice is buy real server class hardware. What is you objective? Drive redundancy? Capacity? A mini is a great dev server. Not a production server. This is your data. Presumably the data that makes your business function. Don't trust it to a single platter. And don't trust it to a consumer level, disposable system. I am not trying to malign the mini. It is a fine machine for its role. Its role however is not to be a production file server. Now as a web server, we are talking a different situation.
    Ok, I am rambling. Hope this helps in some way.

Maybe you are looking for