Tag: raid

Dell EMC Unity: Dynamic pools minimum drives count on creation wizard (User correctable)

Dell Community Leave a comment

Article Number: 503066 Article Version: 4 Article Type: How To



Unity 300,Unity 350F,Unity 400,Unity 400F,Unity 450F,Unity 500,Unity 500F,Unity 550F,Unity 600,Unity 600F,Unity All Flash,Unity Family

On Dynamic Pool creation wizard, there is a minimum number of drives that need to be selected to create the Pool. This number directly depends on the RAID type selected, and a warning will be provided if the minimum drive count is not satisfied. The table below shows the relationship between the RAID type, the RAID width, and the minimum number of drives to create the Pool. This table only shows the smallest RAID widths supported, and the minimum number of drives it takes to create them. As an example, the smallest RAID 5 RAID width the system supports is a 4+1. The smallest Dynamic Pool created with the RAID 5 4+1 configuration is 6 drives. The minimum drive count includes the number of drives specified in the RAID width, plus an extra drive to satisfy the spare space requirements.

User-added image

Related:

Dell Optiplex 7060 storage drivers in DeployAnywhere

Symantec Community Leave a comment
I need a solution

I have recently received two sizes of Dell’s Optiplex 7060; Small Form Factor and Micro Form Factor. I have a Windows 10 Ent. x64 Image from Build 1709 used. I uploaded all the required drivers for the 7060; by the way the hardware for these two sizes are identical. They use the same storage driver, RAID ON is the default and preferred setting we want to use. So far the Micro is working with raid on, but the small form factor blue screens before mini-setup with INACCESSBLE_BOOT_DEVICE. For troubleshooting I performed a manual install of WIndows 10, added the RAID ON (iastorav.inf) driver before partitioning so the sdd can be accessible. I did this on both form factors of the 7060 exactly the same storage drive with raid on and they worked as they should; so they both have the same storage hardware. But when it domes to deploy anywhere scanning and delivering the appropriate drivers, the micro form factor will work with raid on, but small form factor must be switched to ahci. Looking for a solution to why this is not working in a uniform manor since hardware is the same between the two.

0

Related:

Any RAID setting for Unity System Drive?

Dell Community Leave a comment

Since Unity reserved first four drives as System Drive. I have a question: is any RAID setting for the System Drive?

“The first four drives of the DPE are known as system drives, and contain data used by the operating environment. While they can be

used in Pools to hold user data, the entire formatted capacity of the system drives will not be available as space is reserved for the

system. These drives should not be moved within the DPE or relocated to another enclosure, and should be replaced immediately in

the event of a fault. A system drive cannot be used as a hot spare for a non-system drive. For this reason, the minimum number of

drives in a system is 5: system drives configured in a RAID 1/0 (1+1 or 2+2) configuration with a non-system drive hot spare.”

Many thanks

Related:

Dell EMC Unity: Cannot expand storage pool; not enough drives (customer correctable)

Dell Community Leave a comment

Article Number: 502863 Article Version: 3 Article Type: Break Fix



Unity Family

User has added new drives to Unity array and is attempting to expand storage pool. He cannot since it says that he does not have enough drives available.

Unity provides for two storage pool architectures; Dynamic Pools or Traditional Pools.

Dynamic Pools can be expanded with as little as one or two drives at a time.

However, to expand Traditional Pools, you must have a minimum number of drives based on the RAID type in use.

RAID 5 5

RAID 6 6

RAID 1/0 2

User added 3 drives to array. He now has a total of 4 drives available. (In my customer’s case; these quantities may vary depending on your customer’s RAID type).

User was using Traditional Pools and therefore did not have minimum number of drives to expand (customer in my case was using RAID 5).

To determine if customer is using Traditional or Dynamic Pools….

1.In Unisphere, in the upper right, click on the Settings button (looks like a gear).

2.In the Settings window, click on the Storage Configuration tab on the left.

3.If you’re using OE code 4.2, you should only have the Drives sub menu under the Storage Configuration tab. It will list how many drives you have of each type/size and on the far right, it will show how many are configured as part of a dynamic pool and how many are configured as part of a traditional pool.

User-added image

For more info regarding Dynamic Pools vs. Traditional Pools please see Dell EMC Unity: Dynamic Pools Overview.

Related:

Dell EMC Unity: Dynamic Pool is showing degraded state after mapped RAID rebuild is completed (User Correctable)

Dell Community Leave a comment

Article Number: 502829 Article Version: 3 Article Type: Break Fix



Unity 300,Unity 400,Unity 500,Unity 600F,Unity 600,Unity Family,Unity Hybrid

A dynamic pool shows degraded state for some time however the rebuilding of related mapped RAID has been successfully completed

.

This is due to a false rebuild state in the control path however the rebuild on date path has completed.

In most cases this issue will resolve itself several hours automatically, but the period of degraded state appears longer than expected.

Related:

Encryption solution for RAID 1 on Dell Server

Symantec Community Leave a comment
I need a solution

I have some users that have an older Dell PowerEdge T310 that was refreshed to Server 2012 R2. They don’t have the budget to step to new hardware. The server uses a SAS 6/iR RAID controller configured in mirrored mode. We’re looking for a solution that is compatible with this controller and the server OS.

I tried installing one of the products that I think is built on PGP 10.4 but the server just displayed an initializing loader message. When I used the boot menu to select the boot drive, I got the Boot Guard prompt but it blue screened with a kmode exception not handled (intelppm.sys) error after entering the passphrase. 

I had to re-install the OS to get the server going again. At this time I have not installed the encryption software. Does Symantec offer one that will work with this controller?

Thanks.

0

Related:

  • No Related Posts

Re: Replacing faulted disk .

Dell Community Leave a comment

If the two disks that failed are in the same private raid groups, then you have a double faulted pool. Hang on to the faulted disk that you replaced, you may need to recover the Pool. When you create a Pool using 4+1, you create two private raid groups using 5 disks for each raid group. As this is Raid 5, it can recover if one of the disks fail, but if two of the disks in the same raid group fail, then that’s call a double faulted raid group. In normal situations that means it can’t be fixed using the hot spare.

You should open a case with Dell EMC to see if this can be fixed (not normally, but sometimes one of the faulted disks can be coaxed back to life for a short period of time). You need to hold on to the disk that you replaced and label it from which slot you removed it from. You should also make sure you have an up-to-date backup in case it can’t be recovered.

glen

Related:

Re: Created a clone. Made a mess. Can’t delete private LUNS

Dell Community Leave a comment

Okay, just in case someone has the same issue.

Like I said, the clone wizard allocates drives and creates a raid group when you run it. Apparently on the VNX series, you don’t allocate hot spares, you just leave enough unbound drives around to cover your array. My policy is 1:30 drives.

Anyway, I was able to figure this out. I had deleted all of the clone references, but had missed one that was hard to find. I did the following in the GUI after choosing my device:

  • Go to ‘Data Protection’
  • Click on “Configure Clone Settings” link

You should see the entries there, and you can delete them. This isn’t the most obvious place, so it’s easy to miss.

Related:

  • No Related Posts

ScaleIO: MDM Disconnect and Reconnect every week on a specific day and time. No other impact . MDM node has LSI controller.

Dell Community Leave a comment

Article Number: 485402 Article Version: 2 Article Type: Break Fix



ScaleIO Family

MDM cluster goes to DEGRADED and NORMAL node around the same time

217718 20xx-06-11 04:16:52.829 MDM_CLUSTER_DEGRADED ERROR MDM cluster is now in DEGRADED mode – node ID 71b3xxxxxx06817; IP: xx.xx.x.xx:9011: is off-line.

217719 2016-06-11 04:16:55.336 MDM_CLUSTER_NORMAL INFO MDM cluster is now in NORMAL mode.

217732 2016-06-11 04:21:53.345 MDM_CLUSTER_DEGRADED ERROR MDM cluster is now in DEGRADED mode – node ID 71b3xxxxxx06817; IP: xx.xx.x.xx:9011: is off-line.

217733 20xx-06-11 04:21:54.599 MDM_CLUSTER_NORMAL INFO MDM cluster is now in NORMAL mode.

MDM host had LSI controller which had scheduled consistency check. This consistency check impacted MDM cluster connectivity.

Enabled LSI controller consistency check on each week at around 4:00 AM

Workaround:

Disable the consistency check by –

MegaCli64 -AdpCcSched -Dsbl -aALL

Check the scheduled consistency check by

MegaCli64 -AdpCcSched -Info -aALL

Related:

ScaleIO: Incorrect information in “scli –query_sds_device_info” command output

Dell Community Leave a comment

Article Number: 495101 Article Version: 5 Article Type: Break Fix



ScaleIO 2.0.1.2

Issue Description

In some cases, “scli –query_sds_device_info” can return incorrect disk data – like disk size, temperature etc.

Scenario

Issue can be experienced when Hardware Awareness commands (i.e. “–query_sds_device_info”) are used against HP RAID controllers.

Symptoms

Various disk information, like size, temperature, status etc. can be returned incorrectly.

Impact

Unable to properly monitor SDS devices on hardware level from ScaleIO perspective.

There is a bug in ScaleIO software which causes wrong disk information to be returned.

Workaround

There is no workaround.

Impacted versions

2.0.1

2.0.1.2

Fixed in version

2.0.1.3

Related: