Software RAID 1 - test

I have created Mirror like this:
/dev/md/dsk/d0  /dev/md/rdsk/d0 /       ufs     1       no      -
/dev/md/dsk/d4  /dev/md/rdsk/d4 /export/home    ufs     2       yes     -
/dev/md/dsk/d1  /dev/md/rdsk/d1 /opt    ufs     2       yes     -
/dev/md/dsk/d3  /dev/md/rdsk/d3 /opt2 ufs     2       yes     -disk0 = c0t0d0
disk1 = c0t1d0
What I want to do is:
1. Power off system; Remove disk1 (c0t1d0) - will the system boot up (I expect not)?
2. No mater what is a result of point 1 if later I will P plugg disk1 back again - will the system boot normally with any errors ?

czezz wrote:
I have created Mirror like this:
/dev/md/dsk/d0  /dev/md/rdsk/d0 /       ufs     1       no      -
/dev/md/dsk/d4  /dev/md/rdsk/d4 /export/home    ufs     2       yes     -
/dev/md/dsk/d1  /dev/md/rdsk/d1 /opt    ufs     2       yes     -
/dev/md/dsk/d3  /dev/md/rdsk/d3 /opt2 ufs     2       yes     -disk0 = c0t0d0
disk1 = c0t1d0
What I want to do is:
1. Power off system; Remove disk1 (c0t1d0) - will the system boot up (I expect not)?Depends on what you mean by "boot". SVM has a requirement that more than 50% of replicas need to be online for full boot capability. If exactly 50% are gone, then the system will stop at a maintenance prompt. You'd need to delete the unavailble replicas to continue booting.
However, losing a drive right when you boot should be a rare event. You can do all the work before the reboot as long as you're properly monitoring and notice when the drive disappears.
2. No mater what is a result of point 1 if later I will P plugg disk1 back again - will the system boot normally with any errors ?Assuming the replicas are still valid, yes. Otherwise you'd still need to go in and refresh the replicas on the disk. If you did boot all the way up, then the mirror on disk 1 will be stale as well. You'll have to reattach the disk1 mirrors with 'metareplace' to resync everything.
Darren

Similar Messages

  • RAID test on 8-core with real world tasks gives 9% gain?

    Here are my results from testing the software RAID set up on my new (July 2009) Mac Pro. As you will see, although my 8-core (Octo) tested twice as fast as my new (March 2009) MacBook 2.4 GHz, the software RAID set up only gave me a 9% increase at best.
    Specs:
    Mac Pro 2x 2.26 GHz Quad-core Intel Xeon, 8 GB 1066 MHz DDR3, 4x 1TB 7200 Apple Drives.
    MacBook 2.4 GHz Intel Core 2 Duo, 4 GB 1067 MHz DDR3
    Both running OS X 10.5.7
    Canon Vixia HG20 HD video camera shooting in 1440 x 1080 resolution at “XP+” AVCHD format, 16:9 (wonderful camera)
    The tests. (These are close to my real world “work flow” jobs that I would have to wait on when using my G5.)
    Test A: import 5:00 of video into iMovie at 960x540 with thumbnails
    Test B: render and export with Sepia applied to MPEG-4 at 960x540 (a 140 MB file) in iMovie
    Test C: in QuickTime resize this MPEG-4 file to iPod size .m4v at 640x360 resolution
    Results:
    Control: MacBook as shipped
    Test A: 4:16 (four minutes, sixteen seconds)
    Test B: 13:28
    Test C: 4:21
    Control: Mac Pro as shipped (no RAID)
    Test A: 1:50
    Test B: 7:14
    Test C: 2:22
    Mac Pro config 1
    RAID 0 (no RAID on the boot drive, three 1TB drives striped)
    Test A: 1:44
    Test B: 7:02
    Test C: 2:23
    Mac Pro config 2
    RAID 10 (drives 1 and 2 mirrored, drives 3 and 4 mirrored, then both mirrors striped)
    Test A: 1:40
    Test B: 7:09
    Test C: 2:23
    My question: Why am I not seeing an increase in speed on these tasks? Any ideas?
    David
    Notes:
    I took this to the Apple store and they were expecting 30 to 50 per cent increase with the software RAID. They don’t know why I didn’t see it on my tests.
    I am using iMovie and QuickTime because I just got the Adobe CS4 and ran out of cash. And it is fine for my live music videos. Soon I will get Final Cut Studio.
    I set up the RAID with Disk Utility without trouble. (It crashed once but reopened and set up just fine.) If I check back it shows the RAID set up working.
    Activity Monitor reported “disk activity” peaks at about 8 MB/sec on both QuickTime and iMovie tasks. The CPU number (percent?) on QT was 470 (5 cores involved?) and iMovie was 294 (3 cores involved?).
    Console reported the same error for iMovie and QT:
    7/27/09 11:05:35 AM iMovie[1715] Error loading /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: dlopen(/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHD Audio, 262): Symbol not found: _keymgr_get_per_threaddata
    Referenced from: /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio
    Expected in: /usr/lib/libSystem.B.dylib

    The memory controllers, one for each cpu, means that you need at least 2 x 2GB on each bank. If that is how Apple set it up, that is minimal and the only thing I would do now with RAM is add another 2 x 2GB. That's all. And get you into triple channel bandwidth.
    It could be the make and model of your hard drives. If they are seagate then more info would help. And not all drives are equal when it comes to RAID.
    Are you new to RAID or something you've been doing? seems you had enough to build 0+1 and do some testing. Though not pleased, even if it works now, that it didn't take the one time.
    Drives - and RAIDs - improve over the first week or two - which, before commiting good data to them - is the best time to torture, run them ragged, use Speedtools to break them in, loosen up the heads, scan for media errors, and run ZoneBench (and with 1TB, partition each drive into 1/4ths).
    If Drive A is not identical to B, then they may deal with an array even worse. And no two drives are purly identical, some vary more than others, and some are best used in hardware RAID controller environments.
    Memory: buying in groups of three. okay. But then adding 4 x 4GB? So bank A with 4 x 2GB and B with twice as much memory. On Mac Pro, 4 DIMMs on a bank you get 70% bandwidth, it drops down from tri-channel to dual-channel mode.
    I studied how to build or put together a PC for over six months, but then learned more in the month (or two) after I bought all the parts, found what didn't work, learned my own short-comings, and ended up building TWO - one for testing, other for backup system. And three motherboards (the best 'rated' also had more trouble with BIOS and fans, the cheap one was great, the Intel board that reviewers didn't seem to "gork" actually has been the best and easiest to use and update BIOS). Hands on wins 3:1 versus trying to learn by reading for me, hands-on is what I need to learn. Or take car or sailboat out for drive, spin, see how it fares in rough weather.
    I buy an Apple system bare bones, stock, or less, then do all the upgrades on my own, when I can afford to, gradually over months, year.
    Each cpu needs to be fed. So they each need at least 3 x 1GB RAM. And they need raw data fed to RAM and cpu from disk drives. And your mix of programs will each behave differently. Which is why you see Barefeats test with Pro Apps, CINEBENCH, and other apps or tools.
    What did you read or do in the past that led you to think you need RAID setup, and for how it would affect performance?
    Photoshop Guides to Performance:
    http://homepage.mac.com/boots911/.Public/PhotoshopAccelerationBasics2.4W.pdf
    http://kb2.adobe.com/cps/401/kb401089.html
    http://www.macgurus.com/guides/storageaccelguide.php
    4-core vs 8-core
    http://www.barefeats.com/nehal08.html
    http://www.barefeats.com/nehal03.html

  • Software RAID Failure - my experience and solution

    I just wanted to share this information with the iCloud community.
    I searched a bit and did not find much information that was useful with regard to my software RAID issue.
    I have 27 inch Mid 2011 iMac with SSD and Hard drive which has been great.
    I added an external hard drive (I think if I mention any brand name the moderator will delete this post) which includes an nice aluminum case with two 3 TB hard drives within it, and it has a big blue light on the front and is connected via Thunderbolt. This unit is about 2 years old and I have it configured in a 3 TB mirrored RAID (RAID 1) via a software RAID configured via Mac OS Disk Utility. 
    I had at one point a minor glitch which was fixed using another piece of software (again if I mention a brand the moderator will delete this post) which is like a 'Harddrive Fighter' or similar type name LOL.   So otherwise that RAID has served me well as a site for my Time Machine back up and Aperture Vault, etc.  (I created a 1.5 TB Sparse bundle for Time Machine so that the backup would not use the entire 3 TBs)
    I recently purchased a second aluminum block of drives, and set that up as a 4 TB RAID 1.
    Each of the two RAIDs are set with the option of “Automatically rebuild RAID mirror sets” checked.
    I put only about 400 gb on the new RAID to let it sit for a ‘burning in period.’
    A few days ago the monitoring software from the vendor who sells the aluminum block of drives told me I had a problem.  One of the drives had “Failed.”   The monitoring software strangely enough does not distinguish the drives so you can figure out which pair had the issue, so I assumed it was the New 8 TB model.  Long story short, it was the older 6 TB model, but that does not matter for this discussion.
    I contacted the vender and this is part of their response.
    “This is an indication that the Disk Utility application in Mac had a momentary problem communicating with the drive mechanism. As a result, it marked that drive as "failed" in the header information. Unfortunately, once this designation is applied to a drive by the OS, the Disk Utility will thereafter refuse to attempt any further operations with that disk until the incorrect "failed" marker is manually cleared off the drive.”
    That did not sound very good to me…..back up killed by a SOFTWARE GLITCH?
    “The solution is to remove the corrupted volume header, and allow the generation of a new one….This command will need to be done for each disk in the array… (using Terminal)…
    diskutil zerodisk (identifier)
    …3. After everything is finished, you should be able to exit Terminal, and go back into the Disk Utility Application to re-configure the RAID array on the device.”
    Furthermore they said.
    “If the Disk Utility has placed a flag into the RAID array header (which exists on both drives) then performing this procedure on a single drive will not correct anything.”
    And…
    “When a drive actually does fail, it typically stops appearing in the Disk Utility application altogether. In that circumstance, it will never be marked "failed" by the Disk Utility, so the header erase operation is not needed.”
    This all sounded like a bad idea to me. And what does the Vendors RAID monitor software say then?  “Disk Really Really FAILED, check for a fire.”
    As I tried to figure out which drive was actually the bad RAID pair I stumbled on a solution.
    First I noted that the OS Disk Utility did NOT show a fault in the RAID. It listed both RAIDS as “Online.’ Thus no rebuilding was needed and it did not begin the rebuild process.
    The Vendors disk monitor software saw some fault, but Mac was still able to read and write to the RAID, both disks in the mirror.  I wrote a folder to the RAID and with various rebooting steps I pulled the “Bad” drive and looked at the “Good” Drive….the folder was there…I put the Bad drive back in and pulled the Good Drive and the folder was there on the “bad” drive.  So it wrote to both drives.  AND THE VENDORS MONITORING SOFTWARE SHOWED THE PREVIOUSLY LABELED ‘BAD’ DRIVE AS ‘GOOD’ AND THE MISSING DRIVE SLOT AS ‘BAD’.
    My stumbled FIX.   I moved a bunch of files off the failed RAID to the new RAID  but before I moved the sparse bundle, a folder of 500 gigs movies and some other really big folders the DISK UTILITY WINDOW (which I still had open) now showed that the RAID had a Defect and began rebuilding the mirror set itself, out of the blue!   I don't know why this happened.  But moving about 1/2 of the data off of it perhaps did something?  Any Ideas?
    This process took a few hours as best I can tell (let it run overnight) and the next day the RAID was fine and the Vendors RAID monitor did not show a fault any longer.
    So, the Vendors RAID monitoring software reporting a “FAILED” drive without any specific error codes to look up.  Perhaps they could have more info for the user on the specific fault?  The support line of the the Vendor said with certainty “the Volume Header is corrupted” and THE ONLY FIX is to completely ZERO THE DRIVE! This was not necessary as it turns out.
    And the stick in the eye to me…..
    “I've also sometimes seen the drives get marked as "failed" by the disk utility due to a shaky connection. In some cases, swapping the ends of the Thunderbolt cable will help with this. Something to try, perhaps, if your problems come back. “
    Ya Right…..
    Mike

    Follow up.
    After going through the Zeroing process and rebuilding the RAID set three times, with various configurations, LaCie finally agreed to repair the unit under warrantee.
    I tried swapping the power supplies and thunderbolt wires, tried taking the drive out of series with the newer big brother of it.  And it still failed after a few days.
    I just wanted to share more of what I learned with regard to rebuilding the RAID sets via the Terminal.  The commands can be typed partially and a help paragraph will come up to give VERY cryptic descriptions of the proper use of the commands.
    First Under terminal you can used the command "diskutil appleRAID list" to list those drives which are in the RAID.  This gives you the ID number for each physical drive. For example:
    AppleRAID sets (1 found)
    ===============================================================================
    Name:                 LaCie RAID 3TB
    Unique ID:            84A93ADF-A7CA-4E5A-B8AE-8B4A8A6960CA
    Type:                 Mirror
    Status:               Online
    Size:                 3.0 TB (3000248991744 Bytes)
    Rebuild:              manual
    Device Node:          disk4
    #  DevNode   UUID                                  Status     Size
    0  disk3s2   D53F6A81-89F1-4FB3-86A9-8808006683C2  Online     3000248991744
    -  disk2s2   E58CA8F5-1D2C-423A-B4BE-FBAA80F85879  Spare      3000248991744
    ===============================================================================
    In my situation with the failed RAID, I had an extra disk in this with the status of Missing/Failed. 
    The command is "diskutil appleRAID remove" and the cryptic help paragraph says:
    Usage:  diskutil appleRAID remove MemberDeviceName|MemberUUID
            RAIDSetVolumePath|RAIDSetDeviceName|RAIDSetUUID
    MemberDeviceName|MemberUUID  is the number listed in the "diskutil appleRAID List" command,  and
    RAIDSetVolumePath|RAIDSetDeviceName|RAIDSetUUID is the Device Node for the RAID which here is /dev/disk4.
    I used this command to remove the third entry (missing/failed), I did not copy the terminal window text on that one, so I cannot show the list of three disks.
    I could not get to remove the disk2s2 disk listed as SPARE, as it gave an error message:
    Michaels-iMac:~ mike_aronis$ diskutil appleraid remove E58CA8F5-1D2C-423A-B4BE-FBAA80F85879 /dev/disk4
    Started RAID operation on disk4 LaCie RAID 3TB
    Removing disk from RAID
    Changing the disk type
    Can't resize the file system on the disk "disk2s2"
    Error: -69827: The partition cannot be resized
    But I was able to remove it using the graphical interface Disk Utility program using the delete key.
    I then rebuilt the RAID set by dragging the second drive back into the RAID set.
    I could not get the command: "diskutil appleRAID update AutoRebuild 1 /dev/disk4" to work, because even though it was trying to execute it HUNG.  I put the two drives into my newer LaCie 2big as my attempt at further trouble shooting the RAID (this was not suggested by LaCie tech), rebuild the RAID and now I am going to leave it setup that way for a few days before I ship it back to just see if the old drives work fine in the new RAID box (thus proving the RAID box is the problem). I tried the AutoRebuild 1 command just now and it gave an error.
    Michaels-iMac:~ mike_aronis$ diskutil appleraid update autorebuild 1 /dev/disk4
    Error updating RAID: Couldn't modify RAID (-69848)
    Michaels-iMac:~ mike_aronis$
    In my haste to rebuild the RAID set for the third or forth time as LaCie led me through the testing this and test that phase, I forgot to click the "Auto Rebuild" option in the Disk Utility program.
    Question for the more experienced:
    As I was working on this issue, I notice that each time I rebooted and did work in the Terminal (with and without the RAID plugged in to the thunderbolt connection) I notice that the list of drives would change and my main boot drive would not stay listed as drive 0!  Some times it would be drive 0, sometimes the RAID would be listed as Drive 0.  It's strange to me...I would have thought the designation for Drive0 and Drive1 would always be my two build in drives (SSD and spinning drive).
    Mike

  • Software RAID issue

    I have just installed 2-200 GB seagate hd's into my machine and set them up as a software raid 0. Also installed is the original 80 GB drive and a Hitachi 160 GB drive. The two new drives functioned long enough for me to copy all of my raw digital home video.
    Now, when I try to boot the grey Apple screen comes up and the machine hangs. When I disconnect the drives, it boots right up.
    I thought maybe my power supply was giving up the ghost until I reconnected them and successfully rebooted with Drive Genius 1.2. I rebuilt the raid set (maintaining all data) and rebooted into OSX successfully. Woohoo!
    But not so fast. Next reboot started the same thing. And now Drive Genius has no effect.
    I really dont wan't to lose the data on these drives. Is there a problem with the software raid in 10.4.7? Any ideas of other things to try? Help?!?!
    Thanks,
    Andy
    G4 1.25DP FW800   Mac OS X (10.4.7)  
    G4 1.25DP FW800   Mac OS X (10.4.7)  

    Possibly a couple things that "aren't quite right" with your setup.
    SoftRAID 3.5 supports mirror for boot drive, but not with stripped.
    The two IDE buses are not identical, making for some slight problems with RAID on the two.
    You really can't RAID if both drives are together in one drive cage on the same IDE bus.
    You need a PCI controller to RAID in MDD. Most people at this point in time opt for Serial ATA drives and controller. If you want a bootable SATA drive...
    http://www.firmtek.com/seritek
    If you must boot from stripped RAID (not always a good idea and may not offer much actually in real world performance, check www.barefeats.com for some tests for one).
    A dedicated boot drive for OS/Apps and use other drives for media, data, scratch, even for /users.
    Two ATA drives on the same bus, have to share the bus, contend for I/O.
    You can create a stripe raid with Disk Utility and boot.
    I assume that you read the SoftRAID QuickStart and Manual which really are helpful. There are a number of sites etc that can go into more about RAID.

  • Apple software RAID 0 not spinning down while not in use

    I have a G-Tech G-RAID w/ Thunderbolt, 8TB external enclosure.  It has two 4TB fujitsu drives in it, set up as RAID 0 with Apple's Disk Utility v13 (426) that ships with 10.8 Mountain Lion.  This is attached to a very cleanly installed Mid 2011 Mac Mini, which is acting as a media server.  There is basically no 3rd party software on it, because it's acting as a NFS filer server for streaming digital players around the house.
    However, I have the G-RAID set to spin down when possible in energy saver, and it's not.  It never spins down.  I have 4 external drives on this media server, ranging from USB to FW800 to the Thunderbolt drive, all from different manufacturers, and different sizes and models.  All the other drives spin down after 10 minutes.
    Not only is the checkbox "Put hard disks to sleep when possible" checked in Energy Saver, but a
    pmset -g
    reveals that the "disksleep" is set to 10 (min).
    In frustration, I have tried a lot of things including (but not limited to) removing all other hard drives and hardware, starting up with shift held (safe boot) and removing any software at all that I thought would be keeping the drive "alive."
    Finally I decided to start monitoring the drive with fs_usage, to see if I could suss out what is keeping this one drive alive.
    "fs_usage | grep DISKNAME" reveals that SystemUIServer is accessing the drive every minute, about seven times in a clump.  Considering that SystemUIServer is the peice of software that controls the little menu add-ons to the right of the menubar, I have spend a great deal of time trying to figure out what would use SystemUIServer that is accessing this drive.
    Now it's true that this drive is set up as a time machine drive, but I have disabled time machine, and spotlight, and still I get the same SystemUIServer accesses every minute.  Here is a fs_usage dump:
    orion:~ seanb$ sudo fs_usage | grep Betelgeuse
    Password:
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000029   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000011   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000017   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000008   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:53:16  statfs64          /Volumes/Betelgeuse     0.000017   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000025   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000007   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000011   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000011   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000009   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:54:17  statfs64          /Volumes/Betelgeuse     0.000014   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000062   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000013   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000024   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000009   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:55:17  statfs64          /Volumes/Betelgeuse     0.000014   SystemUIServ
    As you can see, it's the same seven drive accesses every minute.  This is NOT occuring with any of my other drives.  Now, here comes my wild conjecture.  Is this something the system does because they are RAID slices?  Do OS X software RAID slices check themselves every minute? This seems to be preventing them from sleeping.
    Any help would be appreciated, I'm going nuts here.
    Sean

    The second column in your fs_usage report says that iStat Menus is what is accessing your disk (Istat64).  Disable iStat Menus and I bet your issue will go away.  I know there is a module in iStat Menus to monitor drive space, but if I recall correctly, even if that module is disabled, iStat has a habit of checking drives anyhow.  I remember hearing people getting rid of istat menus in order to allow their HDs to sleep propely.
    In fact, and easy way to test this would be to reboot your Mac with the shift key held down until you see your desktop load up.  This will prevent 3rd party add-ons from loading like iStat Menus. Let me know if that works.
    Unfortunatrly this is not the problem I am having, as I've booted with shift, and I still see the  "getattrlist" accesses in my fs_usage report.
    EDIT: stupid font made your report look like iStat when it was Lstat.  So what I said about iStat Menus is probably incorrect.  But using the shift key to boot could still lead you to the correct anwer.  I'm doing testing on my end as well. Let you know if I see anything that pertains to your issue.  (I got an Lstat entry in my fs_usage when I open the drive during testing, but I have not beeing getting them an regular intervals like you do.  I would still guess that you have 3rd party software that is checking on drives periodically, and that holding shift might suss that out.)
    Message was edited by: Cheule

  • Software Raid Inconsistent on a mac pro

    My software raid 0 array is sometimes slow, sometimes fast.  Using the Blackmagic disk speed test utility, it sometimes gets 97MB/s read speed, and sometimes 150MB/s read speed.  I ensure nothing else is running in the background between tests.  Another test I do is to duplicate a folder containing 1 gig of files.  Sometimes it takes twice as long to duplicate it.  Early 2008 Mac Pro, 8 cores, 8 gig mem, raid 0 is two 750gig Caviars (using the 4th internal bay for time machine) Disk utility reports all is clean.  Lion 10.7.1.  Rebuild array?  ideas?

    Mac OS X runs with main memory massively over-committed. Because of this, it often has to return to the Boot Drive to get a few pages of this or that. This activity moves the read/write heads ways from the data area on the data drive and kills RAID performance.
    If you have not done so already, you should consider creating a separate Boot Drive containing System, Library, Applications, and the hidden unix files including Paging/Swap. Move all User files off that drive, except one Admin User used only for Administration, not daily work.

  • Looking for opinions on Apple's software RAID in Disk Utility

    I'm thinking about making a stripped RAID (RAID 0) with Apple's software RAID in Disk Utility. How reliable is it, and will I see a huge speed improvement over just having two independent drives. This RAID will also be my boot drive. Is that a good idea or should I have a separate drive for that function?

    It depends. And seeing you don't have a lot of exposure to RAID, it depends, you still need even more to regularly backup, and depends on the drives to some extent. RAIDs are great for some things, and the sustained reads and writes look good in some simple benchmarks, but for most users, they are better off with a really good fast 10K Raptor or something as a dedicated OS/apps boot drive.
    http://www.barefeats.com/quad07.html
    They did some earlier tests on RAID for boot drive, which you might want to look into.

  • TS4284 Disk Utility may not be able to verify or repair permissions on a software RAID set

    Disk Utility may not be able to verify or repair permissions on a software RAID set
    Symptoms
    When Lion is installed on a software RAID set, Disk Utility may not be able to verify or repair volume permissions. The process appears to start but immediately stops.
    Resolution
    Use the command line tool diskutil to verify and/or repair permissions on a software RAID volume. Note: The user running these commands must have administrative privileges.
    https://support.apple.com/kb/TS4284
    How does a bug like this survive testing?

    "How does a bug like this survive testing?"
    Exactly.

  • I have some questions regarding setting up a software RAID 0 on a Mac Pro

    I have some questions regarding setting up a software RAID 0 on a Mac pro (early 2009).
    These questions might seem stupid to many of you, but, as my last, in fact my one and only, computer before the Mac Pro was a IICX/4/80 running System 7.5, I am a complete novice regarding this particular matter.
    A few days ago I installed a WD3000HLFS VelociRaptor 300GB in bay 1, and moved the original 640GB HD to bay 2. I now have 2 bootable internal drives, and currently I am using the VR300 as my startup disk. Instead of cloning from the original drive, I have reinstalled the Mac OS, and all my applications & software onto the VR300. Everything is backed up onto a WD SE II 2TB external drive, using Time Machine. The original 640GB has an eDrive partition, which was created some time ago using TechTool Pro 5.
    The system will be used primarily for photo editing, digital imaging, and to produce colour prints up to A2 size. Some of the image files, from scanned imports of film negatives & transparencies, will be 40MB or larger. Next year I hope to buy a high resolution full frame digital SLR, which will also generate large files.
    Currently I am using Apple's bundled iPhoto, Aperture 2, Photoshop Elements 8, Silverfast Ai, ColorMunki Photo, EZcolor and other applications/software. I will also be using Photoshop CS5, when it becomes available, and I will probably change over to Lightroom 3, which is currently in Beta, because I have had problems with Aperture, which, until recent upgrades (HD, RAM & graphics card) to my system, would not even load images for print. All I had was a blank preview page, and a constant, frozen "loading" message - the symbol underneath remained static, instead of revolving!
    It is now possible to print images from within Aperture 2, but I am not happy with the colour fidelity, whereas it is possible to produce excellent, natural colour prints using its "minnow" sibling, iPhoto!
    My intention is to buy another 3 VR300s to form a 4 drive Raid 0 array for optimum performance, and to store the original 640GB drive as an emergency bootable back-up. I would have ordered the additional VR300s already, but for the fact that there appears to have been a run on them, and currently they are out of stock at all, but the more expensive, UK resellers.
    I should be most grateful to receive advice regarding the following questions:
    QUESTION 1:
    I have had a look at the RAID setting up facility in Disk Utility and it states: "To create a RAID set, drag disks or partitions into the list below".
    If I install another 3 VR300s, can I drag all 4 of them into the "list below" box, without any risk of losing everything I have already installed on the existing VR300?
    Or would I have to reinstall the OS, applications and software again?
    I mention this, because one of the applications, Personal accountz, has a label on its CD wallet stating that the Licence Key can only be used once, and I have already used it when I installed it on the existing VR300.
    QUESTION 2:
    I understand that the failure of just one drive will result in all the data in a Raid 0 array being lost.
    Does this mean that I would not be able to boot up from the 4 drive array in that scenario?
    Even so, it would be worth the risk to gain the optimum performance provide by Raid 0 over the other RAID setup options, and, in addition to the SE II, I will probably back up all my image files onto a portable drive as an additional precaution.
    QUESTION 3:
    Is it possible to create an eDrive partition, using TechTool Pro 5, on the VR300 in bay !?
    Or would this not be of any use anyway, in the event of a single drive failure?
    QUESTION 4:
    Would there be a significant increase in performance using a 4 x VR300 drive RAID 0 array, compared to only 2 or 3 drives?
    QUESTION 5:
    If I used a 3 x VR300 RAID 0 array, and installed either a cloned VR300 or the original 640GB HD in bay 4, and I left the Startup Disk in System Preferences unlocked, would the system boot up automatically from the 4th. drive in the event of a single drive failure in the 3 drive RAID 0 array which had been selected for startup?
    Apologies if these seem stupid questions, but I am trying to determine the best option without foregoing optimum performance.

    Well said.
    Steps to set up RAID
    Setting up a RAID array in Mac OS X is part of the installation process. This procedure assumes that you have already installed Mac OS 10.1 and the hard drive subsystem (two hard drives and a PCI controller card, for example) that RAID will be implemented on. Follow these steps:
    1. Open Disk Utility (/Applications/Utilities).
    2. When the disks appear in the pane on the left, select the disks you wish to be in the array and drag them to the disk panel.
    3. Choose Stripe or Mirror from the RAID Scheme pop-up menu.
    4. Name the RAID set.
    5. Choose a volume format. The size of the array will be automatically determined based on what you selected.
    6. Click Create.
    Recovering from a hard drive failure on a mirrored array
    1. Open Disk Utility in (/Applications/Utilities).
    2. Click the RAID tab. If an issue has occurred, a dialog box will appear that describes it.
    3. If an issue with the disk is indicated, click Rebuild.
    4. If Rebuild does not work, shut down the computer and replace the damaged hard disk.
    5. Repeat steps 1 and 2.
    6. Drag the icon of the new disk on top of that of the removed disk.
    7. Click Rebuild.
    http://support.apple.com/kb/HT2559
    Drive A + B = VOLUME ONE
    Drive C + D = VOLUME TWO
    What you put on those volumes is of course up to you and easy to do.
    A system really only needs to be backed up "as needed" like before you add or update or install anything.
    /Users can be backed up hourly, daily, weekly schedule
    Media files as needed.
    Things that hurt performance:
    Page outs
    Spotlight - disable this for boot drive and 'scratch'
    SCRATCH: Temporary space; erased between projects and steps.
    http://en.wikipedia.org/wiki/StandardRAIDlevels
    (normally I'd link to Wikipedia but I can't load right now)
    Disk drives are the slowest component, so tackling that has always made sense. Easy way to make a difference. More RAM only if it will be of value and used. Same with more/faster processors, or graphic card.
    To help understand and configure your 2009 Nehalem Mac Pro:
    http://arstechnica.com/apple/reviews/2009/04/266ghz-8-core-mac-pro-review.ars/1
    http://macperformanceguide.com/
    http://www.macgurus.com/guides/storageaccelguide.php
    http://www.macintouch.com/readerreports/harddrives/index.html
    http://macperformanceguide.com/OptimizingPhotoshop-Configuration.html
    http://kb2.adobe.com/cps/404/kb404440.html

  • Software raid won't boot after updating to "mdadm" in mkinitcpio.conf

    After a power outage I've discovetred the config I was using (with raid in mkinitcpio.conf) no longer works, it's mdadm now - that's fine.  I've updated that and re-run mkinitcpio successfully, however my system is unable to boot from the root filesystem /dev/md2 like so:
    Waiting for 10 seconds for device /dev/md2 ...
    Root device '/dev/md2' doesn't exist. Attempting to create it.
    ERROR: Unable to determine major/minor number of root device '/dev/md2'.
    You are being dropped to a recovery shell
        Type 'exit' to try and continue booting
    /bin/sh: can't access tty; job control turned off
    [ramfs /]#
    As far as I can see from reading various threads and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM I'm doing the right things now (although I'm not using lvm at all, which makes the installation document a little confusing).
    I think I've included all the appropriate bits of config here that should be working.  I assume I've missed something fundamental - any ideas?
    menu.lst:
    # (0) Arch Linux
    title  Arch Linux  [/boot/vmlinuz26]
    root   (hd0,0)
    kernel /vmlinuz26 root=/dev/md2 ro
    initrd /kernel26.img
    mkinitcpio.conf:
    HOOKS="base udev autodetect pata scsi mdadm sata filesystems"
    fstab:
    /dev/md1 /boot ext3 defaults 0 1
    /dev/md2 / ext3 defaults 0 1
    mdadm.conf
    ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=7ae70fa6:9f54ba0a:21
    47a9fe:d45dbc0c
    ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=20560268:8a089af7:e6
    043406:dbdabe38
    Thanks!

    Hi magec, that's quite helfpul - I've certainly got further.
    Before I was doing this to set up the chroot (which is what is suggested in the wiki article about setting up software raid):
    mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
    mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
    mount /dev/md2 /mnt
    mount /dev/md1 /mnt/boot
    mount -o bind /dev /mnt/dev
    mount -t proc none /mnt/proc
    chroot /mnt /bin/bash
    But based on your suggestion it's working better
    mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
    mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
    mount /dev/md2 /mnt
    mount /dev/md1 /mnt/boot
    mount -t proc none /mnt/proc
    mount -t sysfs none /mnt/sys
    mount -n -t ramfs none /mnt/dev
    cp -Rp /dev/* /mnt/dev
    chroot /mnt /bin/bash
    The boot is now getting further, but now I'm getting:
    md: md2 stopped.
    md: bind<sdb2>
    md: bind<sda2>
    raid1: raid set md2 active with 2 out of 2 mirrors
    md2: detected capacity change from 0 to 32218349568
    mdadm: /dev/md2 has been started with 2 drives.
    md2: Waiting 10 seconds for device /dev/md2 ...
    unknown partition table
    mount: mounting /dev/md2 on /new_root failed: No such device
    ERROR: Failed to mount the real root device.
    Bailing out, you are on your own. Good luck.
    /bin/sh: can't access tty; job contol turned off
    [ramfs /]#
    The bit that really confuses me is this:
    [ramfs /]# cat /proc/mdstat
    Personalities : [raid1]
    md2 : active raid1 sda2[0] sdb2[1]
    31463232 blocks [2/2] [UU]
    md1 : active raid1 sda1[0] sdb1[1]
    208704 blocks [2/2] [UU]
    unused devices: <none>
    [ramfs /]# mount /dev/md2 /new_root
    mount: mounting /dev/md2 on /new_root failed: No such file or directory
    [ramfs /]# ls /dev/md2
    /dev/md2
    [ramfs /]#
    So the array is up, the device node is there but it can't be mounted?  Very strange.
    Last edited by chas (2010-05-02 11:24:09)

  • Can you move a software raid 1 from one mac to another

    I have a 2 disc software raid 1 on my powermac and I want to move it to my mac pro. Does anyone know if I can do this?

    It appears that in Mac OS X 10.4, and again in the transition to 10.7, RAID format may have undergone dramatic changes. If you are trying to move a RAID array across those boundaries, you may not have the best results moving the drives directly.

  • [Solved] Move Software RAID 5 Array From NAS To Arch

    Edit: I probably never had a problem at all, the error in dmesg probably just scared me, because after I disconnected it I noticed that /dev/d127 was 8.1 TB, the exact size of my RAID array node in my NAS which was /dev/md0, I just overlooked it. I reconnected it to my pc and mounted /dev/md127 to /mnt/raid and got this wonderful sight!
    [bran@ra ~]$ ls /mnt/raid
    data lost+found meta sys
    [bran@ra ~]$ ls /mnt/raid/data/
    data ftproot module _NAS_Media _NAS_Piczza_ _NAS_Recycle_RAID _P2P_DownLoad_ stackable _SYS_TMP TV USBHDD
    download htdocs Movies _NAS_NFS_Exports_ NAS_Public nzbget-downloads PLEX_CONFIG sys tmp USBCopy
    I bought a Thecus N4520 a few months ago and it's ok but programs crash a lot and they're hard to debug, apps have to be updated manually and the whole thing is moderately underpowered. I'm trying to move the software RAID 5 array from the NAS to my desktop, the kernel seems to detect that there is a RAID array but all these drives aren't part of it. I'm pretty new to RAID and I'm just getting my feet wet with it.
    When I try to assemble the RAID array, it just tells me that it isn't an md array. How can I get it to build my array?
    [bran@ra ~]$ sudo mdadm --assemble /dev/sdb /dev/sdc /dev/sdd /dev/sde
    mdadm: device /dev/sdb exists but is not an md array.
    Found this little chunk of info in dmesg, it says that the md devices have unknown partition tables.
    [ 3.262225] md: raid1 personality registered for level 1
    [ 3.262483] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    [ 3.262508] iTCO_wdt: Found a Patsburg TCO device (Version=2, TCOBASE=0x0460)
    [ 3.262585] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 3.262933] md/raid1:md126: active with 4 out of 4 mirrors
    [ 3.262961] md126: detected capacity change from 0 to 536850432
    [ 3.263272] RAID1 conf printout:
    [ 3.263274] --- wd:4 rd:4
    [ 3.263276] disk 0, wo:0, o:1, dev:sdc3
    [ 3.263276] disk 1, wo:0, o:1, dev:sdb3
    [ 3.263277] disk 2, wo:0, o:1, dev:sdd3
    [ 3.263278] disk 3, wo:0, o:1, dev:sde3
    [ 3.263501] md: bind<sde4>
    [ 3.264810] md: bind<sdb2>
    [ 3.268262] async_tx: api initialized (async)
    [ 3.272632] md: raid6 personality registered for level 6
    [ 3.272636] md: raid5 personality registered for level 5
    [ 3.272637] md: raid4 personality registered for level 4
    [ 3.272905] md/raid:md127: device sdb2 operational as raid disk 1
    [ 3.272908] md/raid:md127: device sde2 operational as raid disk 3
    [ 3.272910] md/raid:md127: device sdd2 operational as raid disk 2
    [ 3.272911] md/raid:md127: device sdc2 operational as raid disk 0
    [ 3.273211] md/raid:md127: allocated 0kB
    [ 3.273241] md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2
    [ 3.273243] RAID conf printout:
    [ 3.273244] --- level:5 rd:4 wd:4
    [ 3.273245] disk 0, o:1, dev:sdc2
    [ 3.273246] disk 1, o:1, dev:sdb2
    [ 3.273247] disk 2, o:1, dev:sdd2
    [ 3.273248] disk 3, o:1, dev:sde2
    [ 3.273273] md127: detected capacity change from 0 to 8929230716928
    [ 3.273322] RAID conf printout:
    [ 3.273326] --- level:5 rd:4 wd:4
    [ 3.273329] disk 0, o:1, dev:sdc2
    [ 3.273331] disk 1, o:1, dev:sdb2
    [ 3.273332] disk 2, o:1, dev:sdd2
    [ 3.273360] disk 3, o:1, dev:sde2
    [ 3.283617] md126: unknown partition table
    [ 3.309239] md127: unknown partition table
    [ 3.312660] md: bind<sdb4>
    [ 3.318291] md/raid1:md124: not clean -- starting background reconstruction
    [ 3.318296] md/raid1:md124: active with 4 out of 4 mirrors
    [ 3.318333] md124: detected capacity change from 0 to 10736291840
    [ 3.318385] RAID1 conf printout:
    [ 3.318391] --- wd:4 rd:4
    [ 3.318395] disk 0, wo:0, o:1, dev:sdc4
    [ 3.318398] disk 1, wo:0, o:1, dev:sdb4
    [ 3.318402] disk 2, wo:0, o:1, dev:sdd4
    [ 3.318405] disk 3, wo:0, o:1, dev:sde4
    [ 3.319890] md124: unknown partition table
    [ 3.323462] md: bind<sde1>
    [ 3.338094] md/raid1:md125: active with 4 out of 4 mirrors
    [ 3.338225] md125: detected capacity change from 0 to 2146414592
    [ 3.338253] RAID1 conf printout:
    [ 3.338258] --- wd:4 rd:4
    [ 3.338262] disk 0, wo:0, o:1, dev:sdc1
    [ 3.338266] disk 1, wo:0, o:1, dev:sdb1
    [ 3.338268] disk 2, wo:0, o:1, dev:sdd1
    [ 3.338271] disk 3, wo:0, o:1, dev:sde1
    Here's my full dmesg
    mdadm.conf
    # The designation "partitions" will scan all partitions found in /proc/partitions
    DEVICE partitions
    ARRAY /dev/md127 metadata=1.2 name=(none):0 UUID=d1d14afc:23490940:a0f7f996:d7b87dfb
    ARRAY /dev/md126 metadata=1.2 name=(none):50 UUID=d43d5dd6:9446766e:1a7486f4:b811e16d
    ARRAY /dev/md125 metadata=1.2 name=(none):10 UUID=f502437a:d27d335a:d11578d5:6e119d58
    ARRAY /dev/md124 metadata=1.2 name=(none):70 UUID=ea980643:5c1b79e8:64f1b4cb:2462799b
    Last edited by brando56894 (2014-04-21 22:51:01)

    Sorry I numbered them to show the flow of information, this was also just a place for me to store info as I worked through it. I managed to get it to work by creating a partition that takes up the whole drive and is actually 22 GB larger than all the other drives (since I found out that the had root, swap and home partitions that are no longer needed).
    I should be able to resize the other partitions without a problem, correct? They're EXT4. Should I unmount the raid array and do them individually, remount the array, let it sync and do the next? Or just unmount the array, resize all of them, mount it and let it sync?

  • Adding A New Drive To A Software RAID 5 Array

    Edit 3: Just mounted the partitions and I can delete them because they contain nothing special. Is it safe to expand the 2nd partition of each drive to fill up the left over 22 GB?
    Edit 2: I just deleted all the partitions off of my new drive and created one partition, then added it to the array and it works just fine. My next question is, can I delete all the smaller partitions and expand /dev/sd[x]2 to reclaim all the space (about 70 GB)?
    One of my drives failed and Western Digital sent me a new drive, except it was an external drive instead of an internal drive, so I cracked it open and the label looked different. Turns out it's just refurbished and it's the same model as my other drives (WD Caviar Green 3 TB).
    I've read through the wiki article on Software RAID and created the partitions exactly the same as my other drives, but while creating the main 2.7 TB partition it says that the ending sector is out of range when it isn't. I'm new to all this so I have no idea what to do. From what I've read there normally aren't this many partitions per disk, correct? I also have md124, md125 and md126 for the other partitions. md127 is for the 2.7 TB partitions. I took the array out of my Thecus N4520. I have a 3 TB external drive and a 1TB internal, along with another 500 GB drive. Would I be better off at destroying the RAID set and creating a fresh RAID 5 set, considering I'm losing about 90 GB if I don't need the smaller partitions.
    /dev/sdc
    Disk /dev/sdc: 5860533168 sectors, 2.7 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 00636413-FB4D-408D-BC7F-EBAF880FBE6D
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860533134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 43941 sectors (21.5 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 41945088 46139375 2.0 GiB FD00
    2 47187968 5860491263 2.7 TiB FD00 THECUS
    3 46139392 47187951 512.0 MiB FD00
    4 2048 20973559 10.0 GiB FD00 i686-THECUS
    5 20973568 41945071 10.0 GiB FD00
    /dev/sdd
    Disk /dev/sdd: 5860533168 sectors, 2.7 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): C5900FF4-95A1-44BD-8A36-E1150E4FC458
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860533134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 43941 sectors (21.5 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 41945088 46139375 2.0 GiB FD00
    2 47187968 5860491263 2.7 TiB FD00 THECUS
    3 46139392 47187951 512.0 MiB FD00
    4 2048 20973559 10.0 GiB FD00 i686-THECUS
    5 20973568 41945071 10.0 GiB FD00
    /dev/sde
    Disk /dev/sde: 5860533168 sectors, 2.7 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 2B5527AC-9D53-4506-B31F-28736A0435BD
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860533134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 43941 sectors (21.5 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 41945088 46139375 2.0 GiB FD00
    2 47187968 5860491263 2.7 TiB FD00 THECUS
    3 46139392 47187951 512.0 MiB FD00
    4 2048 20973559 10.0 GiB FD00 i686-THECUS
    5 20973568 41945071 10.0 GiB FD00
    new drive: /dev/sdf
    Disk /dev/sdf: 5860467633 sectors, 2.7 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 93F9EF48-998D-4EF9-B5B7-936D4D3C7030
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860467599
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 5813281700 sectors (2.7 TiB)
    Number Start (sector) End (sector) Size Code Name
    1 41945088 46139375 2.0 GiB FD00 Linux RAID
    2 47187968 47187969 1024 bytes FD00 Linux RAID
    3 46139392 47187951 512.0 MiB FD00 Linux RAID
    4 2048 20973559 10.0 GiB FD00 Linux RAID
    5 20973568 41945071 10.0 GiB FD00 Linux RAID
    when I type in 5860491263 as the end sector gdisk does nothing, just wants more input. If I type +2.7T it accepts it, but really it just creates a partition that's 1KB in size!
    I am able to create a 2.7 TB partition with an end sector of 5860467599, this won't screw anything up will it?
    Edit 1: just tried it and got this
    [root@ra /home/bran]# mdadm --add /dev/md127 /dev/sdf2
    mdadm: /dev/sdf2 not large enough to join array
    [root@ra /home/bran]# fdisk -l /dev/sdf
    Disk /dev/sdf: 2.7 TiB, 3000559428096 bytes, 5860467633 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 93F9EF48-998D-4EF9-B5B7-936D4D3C7030
    Device Start End Size Type
    /dev/sdf1 41945088 46139375 2G Linux RAID
    /dev/sdf2 47187968 5860467599 2.7T Linux RAID
    /dev/sdf3 46139392 47187951 512M Linux RAID
    /dev/sdf4 2048 20973559 10G Linux RAID
    /dev/sdf5 20973568 41945071 10G Linux RAID
    Last edited by brando56894 (2014-04-28 00:47:29)

    Sorry I numbered them to show the flow of information, this was also just a place for me to store info as I worked through it. I managed to get it to work by creating a partition that takes up the whole drive and is actually 22 GB larger than all the other drives (since I found out that the had root, swap and home partitions that are no longer needed).
    I should be able to resize the other partitions without a problem, correct? They're EXT4. Should I unmount the raid array and do them individually, remount the array, let it sync and do the next? Or just unmount the array, resize all of them, mount it and let it sync?

  • Need help with formatting a software RAID 5 array with xfs

    Hi,
    i'm tying to format a software RAID 5 array, using the xfs filesystem with the following command:
    # mkfs.xfs -v -m 0.5 -b 4096 -E stride=64,stripe-width=128 /dev/md0
    but all I get is the attached error message. It works fine when I use the ext4 filesystem. Any ideas?
    Thanks!
    http://i.imgur.com/cooLBwH.png
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

    Sorry I numbered them to show the flow of information, this was also just a place for me to store info as I worked through it. I managed to get it to work by creating a partition that takes up the whole drive and is actually 22 GB larger than all the other drives (since I found out that the had root, swap and home partitions that are no longer needed).
    I should be able to resize the other partitions without a problem, correct? They're EXT4. Should I unmount the raid array and do them individually, remount the array, let it sync and do the next? Or just unmount the array, resize all of them, mount it and let it sync?

  • I'm running 10.5.8 on a MacBook Pro and need to update to Java 7 in order to take a software assessment test for a potential job. The Java app will only upgrade from 10.6 or higher. What can I do?

    I'm running 10.5.8 on a MacBook Pro and need to update to Java 7 to take software assessment tests online for a potential job. What can I do?

    Apple Java for Mac OS X 10.5 Update 10
    Apple Java for Mac OS X 10.6 Update 17
    Apple Java 2013-005
    I would suggest you upgrade your computer's OS minimally to Snow Leopard 10.6.8.
    Upgrading to Snow Leopard
    You can purchase Snow Leopard through the Apple Store: Mac OS X 10.6 Snow Leopard - Apple Store (U.S.). The price is $19.99 plus tax. You will be sent physical media by mail after placing your order.
    After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store. Access to the App Store enables you to download Mountain Lion if your computer meets the requirements.
         Snow Leopard General Requirements
           1. Mac computer with an Intel processor
           2. 1GB of memory
           3. 5GB of available disk space
           4. DVD drive for installation
           5. Some features require a compatible Internet service provider;
               fees may apply.
           6. Some features require Apple’s iCloud services; fees and
               terms apply.
    Upgrading from Snow Leopard to Lion or Mountain Lion
    You can upgrade to Mountain Lion from Lion or directly from Snow Leopard. Mountain Lion can be downloaded from the Mac App Store for $19.99.
    If you sign into the App Store and try to purchase Mountain Lion but the App Store says your computer is not compatible then you may still be able to upgrade to Lion per the following information.
    A. Upgrading to Mountain Lion
    To upgrade to Mountain Lion you must have Snow Leopard 10.6.8 or Lion installed. Purchase and download Mountain Lion from the App Store. Sign in using your Apple ID. Mountain Lion is $19.99 plus tax. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
         OS X Mountain Lion - System Requirements
           Macs that can be upgraded to OS X Mountain Lion
             1. iMac (Mid 2007 or newer) - Model Identifier 7,1 or later
             2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) - Model Identifier 5,1 or later
             3. MacBook Pro (Mid/Late 2007 or newer) - Model Identifier 3,1 or later
             4. MacBook Air (Late 2008 or newer) - Model Identifier 2,1 or later
             5. Mac mini (Early 2009 or newer) - Model Identifier 3,1 or later
             6. Mac Pro (Early 2008 or newer) - Model Identifier 3,1 or later
             7. Xserve (Early 2009) - Model Identifier 3,1 or later
    To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
         Are my applications compatible?
             See App Compatibility Table - RoaringApps.
         For a complete How-To introduction from Apple see Upgrade to OS X Mountain Lion.
    B. Upgrading to Lion
    If your computer does not meet the requirements to install Mountain Lion, it may still meet the requirements to install Lion.
    You can purchase Lion by contacting Customer Service: Contacting Apple for support and service - this includes international calling numbers. The cost is $19.99 (as it was before) plus tax.  It's a download. You will get an email containing a redemption code that you then use at the Mac App Store to download Lion. Save a copy of that installer to your Downloads folder because the installer deletes itself at the end of the installation.
         Lion System Requirements
           1. Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7,
               or Xeon processor
           2. 2GB of memory
           3. OS X v10.6.6 or later (v10.6.8 recommended)
           4. 7GB of available space
           5. Some features require an Apple ID; terms apply.

  • Installing grub2 1.99rc1 on Linux Software RAID (/dev/md[0-x])

    Hello!
    In the last days I tried to install Archlinux x64 on my server. This server consists of 4 SATA drives. I'm using Linux software Raid with the following configuration:
    mdadm --create --verbose /dev/md0 --auto=yes --level=10 --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
    mdadm --create --verbose /dev/md1 --auto=yes --level=10 --raid-devices=4 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2
    mdadm --create --verbose /dev/md2 --auto=yes --level=0 --raid-devices=4 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
    md0 --> / including /boot
    md1 --> /data (my storage partiton)
    md2 --> my swap partion
    In the last step of the installer I don't installed grub and leave the installer without installing a bootloader.
    I mounted the /dev folder to /mnt/dev and chrooted in my new system:
    chroot /mnt bash
    In my new system I installed the new grub2 bootloader with:
    pacman -S grub2-bios
    In the next step I tried to install the bootloader to the MBR with the following command:
    grub_bios-install --boot-directory=/boot --no-floppy --recheck /dev/md0
    But I get the following error:
    /sbin/grub-probe: error: no such disk.
    Auto-detection of a filesystem of /dev/md0 failed.
    Please report this together with the output of "/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <[email protected]>
    I also tried to install the grub2 directly on my discs with the following command:
    grub_bios-install --boot-directory=/boot --no-floppy --recheck /dev/sda
    But the error is the same as above.
    Following the instruction of the error message I executed the following command:
    /sbin/grub-probe --device-map="/boot/grub/device.map
    I get a large debug output:
    /sbin/grub-probe: info: scanning hd3,msdos2 for LVM.
    /sbin/grub-probe: info: the size of hd3 is 3907029168.
    /sbin/grub-probe: info: no LVM signature found
    /sbin/grub-probe: info: scanning hd3,msdos1 for LVM.
    /sbin/grub-probe: info: the size of hd3 is 3907029168.
    /sbin/grub-probe: info: no LVM signature found
    /sbin/grub-probe: info: scanning hd4 for LVM.
    /sbin/grub-probe: info: the size of hd4 is 2068992.
    /sbin/grub-probe: info: no LVM signature found
    /sbin/grub-probe: info: the size of hd4 is 2068992.
    /sbin/grub-probe: info: scanning hd4,msdos1 for LVM.
    /sbin/grub-probe: info: the size of hd4 is 2068992.
    /sbin/grub-probe: info: no LVM signature found
    /sbin/grub-probe: info: changing current directory to /dev.
    /sbin/grub-probe: info: opening md0.
    /sbin/grub-probe: error: no such disk.
    There is a tutorial for installing grub2 at ArchLinux in the wiki:
    https://wiki.archlinux.org/index.php/Grub2
    But I can't find any solution for my problem.
    Does anybody know a solution for this problem?
    Thanks for help
    Best regards,
    Flasher
    Last edited by Flasher (2011-03-03 20:13:13)

    hbswn wrote:Maybe it cannot handle the new mdadm format. Here the other partitions have version 0.90. Only the failing md0 has version 1.2:
    I'm sure it is the cause of the problem. But not new format. The old one (0.90) is incompatible with grub2.
    I hit the same problem and today I managed to fix it.
    What I did: I copied /boot to tmp directory, destroyed /dev/md0 (my /boot) with metadata 0.90, created new /dev/md0 (metadata 1.2), copied back /boot content.
    After that, grub_bios-install /dev/sda && grub_bios-install /dev/sdb finished without any errors.

Maybe you are looking for

  • Cover Flow won't work on Windows XP Computer

    I have a Windows XP computer (Wanting to get a Mac as soon as I can buy one) and when I was on iTunes I have been trying to use the cover flow option, and it keeps saying "Cover Flow will not work on this computer" and I was wondering if there was an

  • Getting error 114 and how to fix this

    Hi, I have a backup server and took snapshot of PeopleSoft app and oracle client. But when I try to start PSNTSRVR, it doesn't come up at all. Also tried executing PTPEMAIN via command prompt and then it threw error 114. This is second time that it h

  • HT4059 How do you highlight and make notes on a PDF book?  I can do so on my ePub books, but not PDF. Is there a trick?

    How do you highlight and make notes on a PDF book?  I can do so on my ePub books, but not PDF. Is there a trick?  I would like to avoid a second app for this.

  • Deleting large amounts of data

    All, I have several tables that have about 1 million plus rows of historical data that is no longer needed and I am considering deleting the data. I have heard that deleting the data will actually slow down performance as it will mess up the indexing

  • ITunes freezes whilst trying to download duplicate episodes

    I use home sharing. On one PC (not the PC i used to purchase the episodes) there are 2 episodes of a TV series that have already downloaded but have duplicates in the library which have not downloaded.  iTunes is trying to download these duplicates.