Differing Raid 5 volume size on different OS's?

Hi
I have just created a new internal raid 5 set (my first)- and created the volume (fully formated)
Am running a dual boot OS system 10.5.8 and 10.6.1 and am getting different capacity readings on the raid set when booted under each OS- should i be worried or is this normal- I'm not intending on filling the drive right up.
Under OS 10.6.1 - 3.92TB
Under OS 10.5.8 - 3.56TB
The raid set was created in 10.6.1 and was expecting the usable capacity to be around these figures but assume they would be the same under 10.6 and 10.5?
Macpro early 2009 2.66ghz 12gb- Apple raid card
All software- firmware up to date
Drive bay 1: 1TB /2 partitions for OS's
Drive bay 1: 2TB raid 5 set
Drive bay 1: 2TB raid 5 set
Drive bay 1: 2TB raid 5 set
Any advice appreciated
Graeme

Snow Leopard (OSX 6) uses 1,000,000,000 bytes per GB. Earlier versions of OSX uses a power of two, which was slightly larger, so drive capacity showed a lower number in GBs. The actual number of bytes is the same.

Similar Messages

Optimizing RAID: stripe/chunk size

I'm trying to figure out how to optimize the RAID chunk/stripe size for our Oracle 8i server. For example, let's say that we have:
- 4 drives in the RAID stripe set
- 16 KB Oracle block size
- MULTIBLOCK_READ_COUNT=16
Now the big question is what the optimal setting is for the chunk/stripe size. As far as I can see, we would have two alternatives:
- case 1: stripe size = 256 KB
- case 2: stripe size = 64 KB
In case 1, all i/o would be spread out over all 4 drives. In case 2, we'd be able to isolate a lot of i/o to separate drives, so that each drive serves different i/o calls. My guess is that case 1 would work better where there's a lot of random disk i/o.
Does anyone have any thoughts or experience to share on this topic?
Thanks,
Alex Algard
WhitePages.com
null

It does not matter. Do not mix soft-raid and hard-raid. One OS i/o operation can read from one disk and number of disk. Do not forget about track-to-track seek time.
Practice is the measure of truth :)
For example, http://www.fcenter.ru/fc-articles/Technical/20000918/hi-end.gif

Drive status shown Unconfigured bad and Raid 10 volume degraded

Cisco UCS C200 M2 server one of the drive is showing Unconfigure bad and raid 10 volume degraded with long beeps and solid umber light. First I thought the hard drive is bad and replaced it with new one of same type. Did wait for rebulid for 5 days. Beep did not stop. Againg I looked in to the server and found the above status. Please refer the screen shot for more clarification of the error.
I was gong through Cisco documentation wherein I came across same type of error with bug and I am not sure its the same and is it is I did not understand the workaround I mean what to upgrade is it BIOS or firmware etc.

Mohammed,
What the bug is trying to say is that in a newer version (1.4(3c)) the behavior changes and the Physical Drive which was removed and inserted back shows the status "Missing" instead of showing up as "Unknown" under the Virtual Drive tab in CIMC as this is Unconfigured Bad drive and not part of the RAID group.
Now, the best you can do here is to monitor your system using CIMC, which is the tool we have to monitor/manage the C-Series server instead of vSphere itself.
To get rid of this behavior, you will have to enter into the WebBIOS (Control+H or C or M < Depends on what RAID controller you have), make the disk unconfig good, then make it only "online" so the disk can be part of the array again.
You may find out what is the sequence of keys you have to hit to ge to the controller during the server boot:
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C200M1/install/c200M1/RAID.html
"Watch for the prompt for your controller during verbose boot:
•The prompt for LSI controller card utility is Ctrl-H.
•The prompt for the mezzanine-style controller cards is Ctrl-C.
•The prompt for the onboard Intel ICH10R controller utility is Ctrl-M. "
Note-1: It is important you first check that the disk has no errors before you try to re-add it to the array, cause if that is the case the disk will probably fail and data loss can occur.
Note-2:Once in WebBIOS, you can also disable the beeping alarm and here is the document that shows how that can be done from WebBIOS (note that this will be the interface if you had to press Ctrl+H, otherwise it will look different) or also, you can use MegaCLI to disable the alarm, and the below link also includes the necessary command:
http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-c-series-rack-servers/116106-problem-ucs-lsi-beeps.html
In case you don't know how to set up CIMC in your C200, here is the link with images and the example, look for the C200 to get the correct steps/cabling:
http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-c200-m1-high-density-rack-mount-server/111455-setup-cimc-c-series.html
I hope this helps.
Rate ALL helpful answers
-Kenny

Extend volume - Storage Pools - iSCSI - "Extend failed" // "Error extending volume: Size Not Supported"

Hi,
I've created a storage pools of 44x 1TB SAS, my storage pool name is "DAS" with 39.1TB (35.8 TB Free Space)
I have a virtual disk named "iSCSI_DFS", Simple, Thin, 20TB with 3.05 TB Allocated
I've created volumes on that disk, NTFS, Thin, Different size.
I create iSCSI VIRTUAL DISKS on those Volumes, same size (my volumes are full)
I want to "extend" my volumes size... I click on my volume, Extend Volume, enter a new size (current is 162GB so I enter 200 and select GB) and click OK
The Volume status turn to "Extend failed" with "Error extending volume: Size Not Supported"
Can you help? I need to change my volumes size...
Thx

I also could not get my partition to extend using the new Windows Server 2012 interface. Did you try to extend volume from the "computer management", "disk management" console? Get there from Administrator Tools - Computer Management. I
was able to extend my partition only from there. You need to first make sure you have available space on the disk. I had to delete an empty volume first before I was able to extend the partition. Hope this helps. Anthony :)
Thx !!
While in the Computer Management, I realised that my Disk was "Basic" and not "Dynamics", Extending using the Disk Management suggest to switch to Dynamics, and it's now working.
The error in the Server Manager should be "Unable to Extend : Your disk is Basic" or something like.
The Disk is a virtual disk on my Storage Pools.!!!

SAPdb volume sizes

Hi,
I have 7.3.0.53 SAPdb installed in a sandbox environment and have been playing around trying to do a few different things.
1)I'd like to change either or both the data and log volume sizes.
a. Id like to be able to shrink a log down from, say 10gig to 1 gig.
b.Also can I increase individual data file sizes (as well as decrease) versus adding more or is it stuck with its original configured values.
2)The TEST db Im playing with has 10 named volumes, 2 look like theyre being used. If those 2 fill up will it automatically create a 3rd, or do I need to do that before it fills up?
3) Weve got a development db that is at 66% currently using 5 of the 10 volumes. If I have to add volumes manually when is a good time to do so? 75%? 90%? I know itll probably depend on how fast its filling up, but is there a good rule of thumb to follow?
Thanks for your time.

Hi Krishna,
I have no idea about 7.3.0.53 SAPdb, but i use MaxDB and i explain the same using MaxDB,
1. MaxDB provides a Database Manager GUI utility using which you can perform this. After connectiong to the server chooos e the instance and in the menu
Instance -> Configuration -> Volumes Now choose the data or log volume and then in the menu Action -> Properties Now perfrom your modifications here.
2. Yes it is possible to make you database add new volumes automatically by using AUTO EXTEND functionality.
You can achieve this using
 auto_extend <mode> [<percentage>]
mode : On, Off, show
percentage: This is your threshold (90 is default)
For example auto_extend on [75]
when ever your volumes size crosses 75% a new volume will be added automatically.
3. Hope the point 2 will do the trick, and you need not worry about it.
Hope this was helpful.
Thanks & Regards,
Kathirvel

Sun T3B T3+ maximum volume size (over two TeraBytes)?

I have a T3+ array that I have upgraded with 400GB FATA drives. When I did it I had firmware release 3.1.6.
The downside was that I could include only a max of 6 drives in a RAID 5, because going over 2TB (2.45TB with 7 disks) the volume so created was reported with the correct size, but then when I tried to slice it, the array was seeing only up to 184GB available for slicing. The same happened when making available the whole volume (slicing disabled) to attached hosts: only 184GB were seen.
I gather that this is because of the SCSI 2TB limit.
Now I have upgraded to firmware 3.2.6. In the meantime I have used the available space, therefore a backup required to destroy the volumes and try again with a greater than 6 (400GB) disks RAID 5 would take a long time.
Before getting the tapes out, I thought it worth asking if this limit has been overcome with this new firmware (at least to create a sliceable >2TB volume). I have seen that this new firmware includes also 300GB drives firmware updates, therefore I assume that if these drive sizes are supported, a 9 x 300 RAID 5 would be well over 2TB.

Many thanks for your replies.
I have now looked at the SCSI CDB specifications and changing the CDB from 12 bytes to 16 bytes to support greater than 2TB volumes should be quite easy, having the firmware source code.
I am afraid the only support I get is through www.sun.com and forums.
I may disagree on the 2TB limit being an improvement rather than a bug. If the array supports 300GB drives, it cannot have a 9 or 8 drives RAID 5 volume, with 300GB drives a RAID 5 volume becomes limited to 7 drives, hence I consider it a bug.
Who can we contact to lobby for this update, or at least, for Sun to release the firmware source of this EOL product?
I reckon that opening the source should be a kind of standard for 'old' (if 6 years is old enough) products, in order to give owners the choice to support their hardware themselves thus relieving Sun from the support burden (costs).

Eclipse SLI slow install of Vista 64 and no bootable raid 0 volume

I've been trying to install Vista 64 on the MSI Eclipse SLI mobo with 2x Seagate 1.5TB hdd in raid 0. Can someone please help me?
I have the following:
1) Onboard ATA Devices set for [RAID]
2) Use ctl-i to create a raid volume [RAID0] - the volume reads as not bootable
3) Vista 64 install takes a long long time and does not recognize the disk volumes even with the ICH10R SATA RAID driver.
MSI Eclipse SLI mobo BIOS v1.8
OCZ DDR3 1600 mem
i7 950

Double and triple checked both the printed manual and the downloadable 7520v1.0 manual and found nothing indicating how to get the RAID 0 volume to become bootable.
I've tried configuring RAID in two ways:
1) Setting On-Chip ATA Device to [RAID]
Creating a RAID0 Volume - Not bootable shows
- Raid volume was created but was not seen during vista 64 install as valid drives, even after driver was installed.
2) Setting On-Chip ATA Device to [AHCI]
Installing the Intel Matrix Storage Manager Driver
- Vista 64 install was good but Intel Matrix Storage Manager did not have the action for making an existing device into raid.
I could however, make the RAID0 partition size smaller (1500TB) and that would allow the drives to show as bootable. There may be a bug with the Intel ATA Driver for drive size or a bug with the Intel RAID Utility (ctl-i).

Can not boot from a RAID 5 volume

Dear Friends,
I have a Mac Pro (3 GHZ) with RAID that will not boot off of a RAID 5 volume. Here's the details:
The unit has 4 768 GB drives that I have made into one RAID 5 set. After that I broke it down into 2 two volumes one for OS (200 GB) and one for storage (the balance of the RAID). After that I copied a known good image to the OS volume.
The Start-up disk utility on the DVD sees the OS but when I boot it sits for a long time and eventually gives me what Apple calls the prohibited icon; a circle with a line-through it like Ghostbusters.
The patron table is good, and I have done this on another Mac Pro. I have tried to rebuild the RAID a few times with no luck. Ideas would be appreciated. Thanks!

My guess is that the Mac OS X system is damaged. You may need to use the Sysytem CD to perform an archive and install.
For those interested in bootable RAID cards on the Mac Pro, the Areca is the only non-Apple solution that I have found with this capability. You can read more about it here:
http://www.amug.org/amug-web/html/amug/reviews/articles/areca/1221x/
Have fun!

RAID 0 volume failed - Intel RST, W530 (wonder if it is hardware issue now)

Hi,
My laptop is about two years old. I got one of two intel RAID 0 volumes failed several months after I got this laptop. This problem has been on my laptop for a long time.
The functionality of my laptop started to become poor after this volume failed.In the beginning, windows explorer stopped working and restarted every time I opened the laptop. The windows repair tool said windows could not be repaired... So I reinstalled the OS and reset it to factory setting. However, the crashes persisted and gradually became more frequent. Many other error reports showed up. After searching for solutions, I finally did a clean windows install and used the BIOS Intel RST to repair the corrupted volume (I deleted old volumes created new ones).
Unfortunately, now, the same volume fail error appears again and the functionality of my laptop is impacted. Sometime I cannot save my excel or pdf file because program stop working, or cannot open a pdf file. I have to restart the OS.
The detail error message of Intel RST is: "your volume appears inaccessible. Try fixing any problems reported on the array disks. If this fails, review the Troubleshooting section under Help for more information. In all cases, back up any accessible data before taking action".
I'm now wondering if it is the hardware issue. If so, I'm thinking about buying an extended warranty because my orignal warranty has expired. However, I'm not sure if the warranty can cover this...
In this community, I find there are two types of extended warranty, one will start from the expiring date of the original one and the other will start from the date of purchase. I suppose I need to find the second one.
I'm also wondering the quality of the warranty. Will it take a long time to repair if I send it? or will it take a long time for them to ship?
Any idea, solution and experience in warranty / repairment would be appreciated.
Best Regards,
Haoyi
BTW, here is also my experience with Lenovo if you would like to have a look at:
I got my W530 two months after purchases... I found it was a common problem in Lenovo...
When my laptop was still in the original warranty, I contacted the lenovo customer service for repairment of the failed volume. Those people told me it was errors coming from my software. They said the repairment was not covered in the original warranty and I needed to buy a new type of warranty (related to software repairment). I had no confidence in the quality of lenovo's customer serivce... So I did not buy it.

Hi, Colonel,
Thank you for reply. I tried HD Tune, but it cannot show any information about my harddisk. It only shows Intel Raid 0 Volume, the firemware version is 1.0 and the capacity is 931.5GB. There is no other information, such as serial number, standard, supported, and buffer. I cannot choose supported features. HD Tune also cannot display the temperature of my drives. What should I do?

I replaced the battery on my RAID card, when I booted my mac pro up, I get the folder with the question mark. I used a boot USB drive to boot and when I looked in the RAID utility, my RAID 5 volumes were no longer showing, advise.

I replaced the battery on my RAID card, when I booted my mac pro up, I get the folder with the question mark. I used a boot USB drive to boot and when I looked in the RAID utility, my RAID 5 volumes were no longer showing, advise.
Ernest

Not sure if I'm following you. I have 4 hard drives installed on my Mac Pro. I had a RAID 5 configured and functional for about 5 months. My battery died on the RAID card. I replaced the battery, seated the RAID card back in the slot I removed it from. When I booted to the USB drive to look in the RAID utility, I could see the battery is charged but my volumes are not showing.
The drives don't show in disk Utility. I built the RAID with the RAID Utility and they did show there. I have a early 2008 Mac Pro, Mavricks OS running Mac Server

Time Machine - A bag of hurt with RAID 0 volumes

Here's my situation:
Mac Pro with 4 internal Hard Drives. 2 of them are in RAID 0 and they are the boot volume. The 2 others are also in RAID 0 and are used as a Time Machine volume. Both volumes have a capacity of 1TB.
I had a problem with the boot volume which forced me to erase that volume. So the next logical step was to boot from the Leopard install DVD (10.5.4) and run the Restore from Time Machine application.
But once I reached the 'Select your destination volume' step it didn't show my internal RAID 0 volume.
I tried every possible configuration but the restore application didn't want to show the internal RAID 0 volume. If I would erase the 2 volumes from the RAID 0 as 2 seperate volumes they would show up. But that wasn't what I needed since the backup was larger than the capacity of 1 seperate hard drive.
Eventually I put the 2 drives in a second Mac Pro. Started that Mac Pro in FireWire disk mode and connected it to my Mac Pro with a FireWire 800 cable. Now, the boot volume would show up in the restore application.
After 12 hours of restoring my data and having almost finished the whole process the restore application gave me an error message saying that 'An error occured, please restart'. No explanation which error had occured. Also, I wasn't able to boot from the partially restored volume.
Conclusion:
1. Apple should fix the Time Machine restore utility so that it would find internal RAID 0 volumes.
2. I still don't have a restored machine. The only possibility now is to reinstall the OS and all the applications manually and retrieve my backup data manually from the Time Machine backup.
3. I'm reverting back to CCC for making backups
David

Carolyn Thanks for quick response and advice.
Firstly I erred re the 167 re Open DNS . I did have in correct if preferences!
However...
I followed your advice and cleared all DNS except for the Open DNS ones.
That rectified the problems on the iMac.
BUT, before I can get too excited, I still have Safari NOT opening some windows on the MBP afterreverting to only Open DNS!
Specifically Macupdate, EhMac and most links from sites set up on My Yahoo.... such as New York Times, CBC, BBC etc.
eg - http://www.nytimes.com/2011/01/08/business/economy/08obama.html?exprod=myyahoo
or
http://www.cbc.ca/canada/british-columbia/story/2011/01/07/bc-highway-mudslide.h tml?ref=rss
The two above fly open on Imac but take three or more minutes on MBP!
Yet other links are open promptly
So I think it is more than just DNS.

Show volume size in Lion?

Show volume size in Lion? Snow Leopard showed the amount of space available on mounted volumes in the Finder. I can't find how to do that in Lion. Get Info works, but I'd like to see available space when I open a drive or volume/

In an active Finder window select Show Status Bsr from the View menu.

Volume size information wrong

I think I found a concerning problem freeing large spare files.
After creating and removing a handful of sparse 200GB files (VirtualBox volumes), Finder is quite wrongly showing:
Capacity: 499.42
Available: 655.65
statfs is showing something more sane:
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/disk0s2 465Gi 223Gi 242Gi 48% 58462482 63465747 48% /
inode counts seem to add up too.
neither fsck nor Disk Utilities are showing any problems with this volume. Obviously, a free count is badly wrong somewhere (does Mac OS use unmap on SSD volumes?)
So while the spare files existed, the Finder information was sane, showing a disk usage reflecting the actual allocation size (not spare file size). Upon deleting the files, the available count surpased the total volume size. I think somewhere between HFS+, SATA unmap and the SSD itself there's a potentially bad problem. My fear is at some point, used blocks are going to wrongly show up mapped into what the filesystem thinks is free space.
Had anyone else seen this?
I'll be restoring from Time Capsule as soon as I can.
OSX 10.8.5
MacBook Pro 15" Retina

HI
Yuo need ALL DISK to install
I installed this version and i didn't problems
good lock
mario

[Solved] Incorrect volume size (LVM related?)

For some reason I get incorrect volume size for my partition, when mounting.
This is the correct size.
lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/ArchRules
VG Name VolGroup00
LV UUID 25HBCU-eBIF-cgsv-7exb-XE1y-c15E-MU1BQO
LV Write Access read/write
LV Status available
# open 1
LV Size 1,84 TB
Current LE 482908
Segments 5
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
After mounting.
df -h
/dev/mapper/VolGroup00-ArchRules 917G 529G 342G 61% /mnt/ArchRules
Is this normal?
Last edited by nuxorg (2009-08-11 20:36:35)

Zariel wrote:What filesystem?
EXT4

Getting slice/volume size from kernel mode

Hi, my driver needs to be able to get a slice/volume size in LBs.
Until now, when I wanted to send IOCTLS in kernel mode I used the
cdev_ioctl function.
However I'v encountered some strange problems when using this
function for disksuite devices. The DIOCINFO IOCTL works fine, however
neither DKIOCGVTOC nor DKIOCGAPART worked. The rc is 0 but the buffers
contained random garabage. Does anyone have any idea what's wrong?
Further info:
1.On scsi or veritas volume manager devices these IOCTLS works fine, only on
devices controleld by the disksuite driver (md) am I encountering such problems.
2.The OS is solaris 8.
3.The IOCTLS work fine from user-mode for all devices types.
4.I am using cdev_ioctl as follows:
cdev_ioctl(hTargetDevice, /*The device dev_t*/
ioctlCode, /*Ioctl code*/
(intptr_t)pInputBuffer, /*The info structure*/
FKIOCTL|FREAD, /*Kernel ioctl*/
kcred, /*Root privileges*/
&ioctlRval);
Any help is appreciated.
ERAN

Hi, for other peoples information - I finally figured out the problem. It was actually a faulty RAM module which I had bought. I had upgraded from 2 to 4 gb of RAM using an approved type of RAM for my particular computer. Finally I removed one module of RAM (after doing nearly everything else under the sun including trying to reinstall the operating system and wipe the computer etc) and the computer worked fine.
Dave

Differing Raid 5 volume size on different OS's?

Similar Messages

Maybe you are looking for