- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- msa1000 errors with 300gb drives in raid5
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 08:38 AM
04-11-2005 08:38 AM
I get an error message that the physical drive sizes are mismatched, and may result in at least a 10% decrease in volume, and that the unit cannot be created with the parameters given.
The command I used was add unit 0 raid_level=5 data="Disk101-Disk113"
However, when I replace the 300GB drives with 146gb drives, the unit builds without a problem. So, I physically checked each 300GB drive (looking at the p/n on the label), and they all show to be 300GB. I also ran the command show all disks and it also shows them all as being 300gb.
I am able to bind (7) 300gb drives in R5, however, even though it builds the unit, I still get the error about drive size mismatch.
I brought the firmware up to 4.3.2 and still get the same errors. I tried binding each drive as an individual unit, and they all show as 300gb..so it appears that all the drives are working correctly..I just cannot get the system to bind (13) 300gb drives in R5. any ideas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 09:44 AM
04-11-2005 09:44 AM
Re: msa1000 errors with 300gb drives in raid5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 11:27 AM
04-11-2005 11:27 AM
Re: msa1000 errors with 300gb drives in raid5
Can you use the same cmd but add a size value.
size=2097151MB
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 06:30 PM
04-11-2005 06:30 PM
Re: msa1000 errors with 300gb drives in raid5
just a guess
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 11:29 PM
04-11-2005 11:29 PM
Re: msa1000 errors with 300gb drives in raid5
It could be a limit of the Array size...
13 * 300 GB RAID 5 = 3,6 TB Raw capacity...
Could this be the problem...
Regards
Dragomir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 01:36 AM
04-12-2005 01:36 AM
SolutionWhat is your environment that you are running in? What OS are you running? Also, since you are limited to 2TB logical drives on the array, you should look at splitting your array into two groups with their own logical drive. A failed drive on a 13x300gb Array will take a LONG time to rebuild 15-20min per gb rebuild time. You would be wise to split it up!
Ciao,
Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 09:26 AM
04-12-2005 09:26 AM
Re: msa1000 errors with 300gb drives in raid5
It was a size limitation of the logical volume..I split the logical partitions into 2 raid5 sets 6+1 x 2 and that worked great..anything over 2tb will not bind.
thanks again!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 09:26 AM
04-12-2005 09:26 AM