Hello Sylvia,
I'm running the script before loading the OS - it is being executed from within Linux's initrd.
Here is the actual script:
mdadm --remove /dev/md126
mdadm --remove /dev/md127
mdadm --stop /dev/md126
mdadm --stop /dev/md127
mdadm --zero-superblock /dev/sd[a-b]
sync && sync
rm -f /dev/md/*
dd if=/dev/zero conv=fsync of=/dev/sda bs=1M count=32
dd if=/dev/zero conv=fsync of=/dev/sdb bs=1M count=32
blockdev --rereadpt /dev/sda
blockdev --rereadpt /dev/sdb
export IMSM_NO_PLATFORM=1
mdadm --create /dev/md/imsm --force --raid-devices=2 --spare-devices=0 --metadata=imsm --assume-clean /dev/sd[a-b]
mdadm --create /dev/md/System --force --raid-devices=2 --spare-devices=0 --level=1 --assume-clean /dev/md/imsm
As I have mentioned in my first post, the script works fine and it can create RAID that can utilize the whole capacity of the underlying drives. However, when I create RAID on the same server and the same drivers, but I use the "Intel SCU Option ROM" to create it, the size of the RAID volume is 5% smaller than the capacity of the drives. Please see below:
Intel(R) Rapid Storage Technology enterprise - SCU Option ROM - 3.5.0.1005
Copyright(C) 2003-12 Intel Corporation. All Rights Reserved.**********************************[ MAIN MENU ]*********************************
* 1. Create RAID Volume 3. Reset Disks to Non-RAID *
* 2. Delete RAID Volume 4. Exit *
***************************[ DISK/VOLUME INFORMATION ]**************************
* RAID Volumes: *
* ID Name Level Strip Size Status Bootable*
* 0 System RAID1(Mirror) N/A 884.9GB Normal Yes *
* *
* Physical Devices: *
* ID Device Model Serial # Size Type/Status(Vol ID) *
* 4 ST91000640NS 9XG2W6CW 931.5GB Member Disk(0) *
* 5 ST91000640NS 9XG30KBR 931.5GB Member Disk(0) *
* *
* *
* *
* *
********************************************************************************
[**]-Select [ESC]-Exit [ENTER]-Select Menu
What is this 5% used for? Is it necessary or recommended to create RAID volume slightly smaller than then physical drive, or is the volume created by the mdadm command without specifying the "--size" parameter correct.
Thank you very much for your reply.
Regards,
PK