Hi

Brand new MD3200i, 12x4Tb drives. Updated to current firmware 08.20.05.60.

The wizard starts and recommends creation of a disk pool containing all 12 disks.

If this is accepted, the pool is created and status immediately changes to Needs Attention.

When selecting Needs Attention, it is reported that the disk pool is >85% capacity. Clearly this is the case, as the wizard recommends allocation of 12 disks to the pool (100%) including a preservation capacity of 2 disks.

Help states "A disk pool needs sufficient remaining capacity to successfully perfom storage array operations".

The question is why would the wizard knowingly create a 12 disk out of 12 disk pool of 100% if this immediately exceeds the 85% capacity figure? Obviously I can disable this error in the disk pool settings by disabling the Critical Warning Notification threshold, but what storage operations will I be unable to run in this 12 disk configuration? As I understand it there is already two disks worth of capacity reserved within the disk pool to deal with failures. So is the 85% warning erroneous?

Thanks in advance.

Hello,

I just took over for someone who is no longer with the company and have discovered that there is a PIN set on the control panel of my PowerVault TL2000. I can't find any documentation indicating what the PIN was set to (and my first couple dozen guesses have not panned out), so I am looking to reset the PIN to a factory default.  How do I go about accomplishing this ?

Thanks in advance for any advice you can provide...

Hi,

I have an issue when installing the MD Storage Manager Client on a Management PC from the V6 Resource DVD, This is to manage the Dell Powervault MD3620F. I have tried installing Management Station only on a PC running Windows 8.1 U1, there are no errors during the install but only the MD Configuration Utility get's installed, not the Storage Manager.

I have also tried installing this on a Host running Windows Server 2008 R2 that is connected to the PowerVault but again only the Configuration Utility is installed and there are no errors as to why the Storage Manager client has been skipped. Version 10.84.G6.54 was previously installed on this system with no issues. Are there any logs I can look at to troubleshoot why Storage Manager isn't getting installed, are there any pre-requisites I could be missing?

Cheers

3 1/2 year old Powervault MD3200I, getting following message:

Is this a repair or replace event?  Other suggestions?

Summary

Node ID: B3C1XQ1

Host IP Address:

Host ID: Out-of-Band

Event Error Code: 4011

Event occurred: Feb 28, 2015 9:15:20 AM

Event Message: Virtual Disk not on preferred path due to failover Component type: RAID Controller Module Component location: Enclosure 0, Slot 0

Priority: Warning

Simple question hopefully.  In the OpenManage software it only shows if the fans in the MD1200 are active or not. Is there a way to see the physical rotational speed of the individual four fans running inside this unit?

Note my MD1200 is attached to a Precision R5500.  If the above is possible but limited to certain operating systems, please let me know which.

Thanks.

JR

How can I tell how much deduplication is being done on a CIFS container? The OST container shows the statistics for ingested data, but the CIFS one doesn't.

Thanks.

I have a Dell 124t LTO3.

Over the course of a few months i noticed that the backups begun to fail every now and then.

Recently all backups start to fail completely, I cannot perform redirect or such.

i have a copy of the logs but cant find anything on the error codes online.

This system is out of warranty and i cannot get assistance from Dell.

Any assistance in confirming this is indeed a drive failure would be helpful.

I have the logs, see below: 

**** Hard Queue ****

Block 1, 014/016 entries @  36 bytes each, wrap @ 004, erase @ 008

0000: PC: 00001 POH: 00000:16:03 Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0001: PC: 00002 POH: 00000:02:08 Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0002: 2007-Sep-16, 13:22:42.178, Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0003: 2007-Oct-22, 11:39:05.145, Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0004: PC: 00069 POH: 00000:04:34 Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0005: 2014-May-07, 14:00:13.151, Error: ff000000, Context: 0060/00000060

      00000020:00085e64:00000000:000001d0:000000e0

0006: 2014-May-29, 13:28:57.564, Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0007: 2014-Oct-06, 11:58:40.282, Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0008: 2014-Oct-28, 16:15:47.421, Error: 023b202f, Context: 0da6/01000020

      03020043:83030005:8301fff6:020b01f4:8301ffec

0009: 2014-Oct-28, 20:15:52.883, Error: 023b202f, Context: 0da6/01000020

      03020043:83030005:8301fff6:020b01f4:8301ffec

0010: 2014-Oct-29, 09:24:34.727, Error: 073d0104, Context: 0709/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0011: 2014-Oct-29, 12:35:12.610, Error: 023e202f, Context: 0fa6/01010020

      03020043:83030009:8301fff6:020b01f4:8301ffec

0012: 2014-Oct-29, 13:46:13.094, Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

0013: 2015-Mar-04, 09:31:00.219, Error: 073d0104, Context: 012d/00000080

      ffffffff:3600ffff:381f0010:04100621:00610000

**** Soft Queue ****

Block 1, 313/350 entries @  16 bytes each, wrap @ 000, erase @ 070

0000: 2014-Oct-31, 10:06:09.508, Error: 02ca24e1, Context: 08ca/4102005a

0001: 2014-Oct-31, 10:07:10.069, Error: 02ca24e1, Context: 0bca/30010036

0002: 2014-Oct-31, 10:07:14.701, Error: 02ca24e1, Context: 0bca/31020036

0003: 2014-Oct-31, 10:07:18.597, Error: 02ca24e1, Context: 08ca/4102005a

0004: 2014-Oct-31, 10:07:35.519, Error: 02ca24e1, Context: 08ca/410201ab

0005: 2014-Oct-31, 10:07:37.844, Error: 02ca24e1, Context: 08ca/4102005a

0006: 2014-Oct-31, 10:08:37.629, Error: 02ca24e1, Context: 0bca/30010036

0007: 2014-Oct-31, 10:08:42.261, Error: 02ca24e1, Context: 0bca/31020036

0008: 2014-Oct-31, 10:08:46.156, Error: 02ca24e1, Context: 08ca/4102005a

0009: 2014-Oct-31, 10:09:03.238, Error: 02ca24e1, Context: 08ca/410201ab

0010: 2014-Oct-31, 10:09:05.562, Error: 02ca24e1, Context: 08ca/4102005a

0011: 2014-Oct-31, 10:09:58.374, Error: 02932349, Context: 0002/00000000

0012: 2014-Oct-31, 10:10:00.613, Error: 02ca24e1, Context: 08ca/4102005a

0013: 2014-Oct-31, 10:10:07.231, Error: 02932349, Context: 0003/00000000

0014: 2014-Oct-31, 10:10:10.174, Error: 02ca24e1, Context: 08ca/4102005a

0015: 2014-Oct-31, 10:10:16.815, Error: 02932349, Context: 0003/00000000

0016: 2014-Oct-31, 10:10:19.850, Error: 02ca24e1, Context: 08ca/4102005a

I have a Dell 2850 running Windows 2003 Enterprise SP1 On this I have a PERC 4/DC SCSI controller
connected to Dell Powervault 220S.This has 14 drives configured for RAID 1 giving 7 logical drives.
This system has been up since 2006 with 1 drive failing until September 2014. Since then I have
had 6 similar failures. This chronic problem is becoming predictable.

In a short space of time I lose multiple disks. First of all I will get a  redundancy lost with 2 or
3 drives failing at the same time. Then within the space of an hour I will get 3 more disks failing
with the added headache of losing both drives for a logical disk. OpenManage states that the
PERC 4/DC has failed.

Since September I have changed just about every piece of hardware. Starting with the PERC 4/DC
controller to PERC 4/Di sister board. EMM controller cards on the PV220S and with the last failure
a month ago I changed the whole PV220S chassis. I thought I had cracked it as it ran for a month
before the last failure 3/4/15. The only piece of hardware I have not changed is the Dell 2850
itself but I cannot see the server being the root cause.

After failure I normally change out the PERC 4/DC controller and checked it on another machine and
it has been OK. I find it unlikely that many drives can fail at the same time so I force the
drives online and it carries out a check on the logical drives and states they are good.
I have changed 6 drives just as a matter of course.

Searching the web I found one comment where they state that it is possible for one bad drive to cause
this but still state that drive is OK. Has anyone heard of this? The last failure stated that a drive
had been removed and re-inserted but it did not check the re-inserted disk and one second later that
disks mirror failed with 3 other disks!?

I have updated all drivers and firmware to the latest Dell revision.LSI Logic Corp. had nothing
 to assist me.

We have other servers with the same controller but they are clustered drives, I have had issues
with this controller but nothing like this. This is a stand-alone server that holds SCADA historical
data. So very limited ability to change things arounds with this Microsoft SQL database.

The first go 'round the battery sat for 4-5 months before I had time to change it, but within a few hours MDSM started reporting that it failed. We assumed that it was because of the time it sat idle. This time I installed the new battery the day after it arrived and, about 10 hours later it had failed. I looked through the logs and it was reported that the battery was fully charged within a couple of hours,only to fail 8 hours later. The RAID Controllers are at the same firmware level, 7.35.39.64, which looks like the latest/last firmware version. Is it possible that we've been sent two defective batteries? Any other ideas? Any assistance is greatly appreciated.

HI Guys,

On 7th March (2015) I got notification from My SAN with 'Degraded Physical Disk Channel'

I spoke to someone on e-mail at dell who asked me to send over a support zip file from the MDSM which I did, the engineer said someone will review it but never got back to me, or reply to my follow up emails.

Weird thing is.. manfacture date on SAN also shown 7th march (2008) so it decided to brake down on its birthday.

Tonight (sat 9th march) I decided to shut down all the Virtual Machines on all hypervisors,  i switched off the MD3000i, then the MD1000 and left it off for 5 mins.

I then switched on the MD1000 waited a few mins, then switched on the MD3000i

the management IPs 192.168.128.101/102  did not ping, I thought the SAN had died and again rebooted everything the same way as earlier, again nothing was pinging.  I then pinged the inbound IPs of 192.168.130.101/102 131.101/102  they pinged fine,  so i went to the HV's and booted up all VMs.

some hours later and I still cant ping the management IPs to get in to the MD3000i to see if that originally error has gone.  I tried adding the SAN again and used the inbound IPs (that ping) but MDSM cant connect to that either.

Sadly I cant find the console cable, some how during a few office moves in last 7 years Its probably been thrown out.

I can some how find another cable but not for a few days and I don't like the idea of this not working, I spoke to dell support tonight, but they couldn't help me as the warranty had expired.

Can anyone think of any other way I can get to the MDSM soon? if they only way is through console... can someone talk me through what to do when I am in front of the SAN connected on the cable.. is their a magic option i select to fix things? what am I looking for?

Hi,

I've a MD1000 and R510 attached via Perc 6/E (latest FW 6.3.3) to one EMM (split mode). Both EMM are powered. Second EMM is not cabled and not in use.

First 3 slots are in use with 2TB disks. Slot 3-7 (Sata) are empty and blinking amber.

I configured de MD1000 with Ctrl-R Raid 5 and 3 disks and ran initialization on the created V-group

After starting up the MD100 shows a green LED (first EMM) and a blue LED. After 1 min the empty slots starts blinking amber although no disks are present and the status LED starts also blinking amber

How can I fix the amber lights and get the status LED back into blue?

When I got this MD1000 slot 0-2 where originally SATA and 3-15 SAS slots. I replaced slot 3-7 with SATA for future usage.

Greetz Martin

Hi

We have a PV MD3600f. I have created my Disk Groups with Virtual Disks. I have linked them to the different Hosts. But I cant see them on my hosts. The servers run Windows Server 2008 R2 Datacentre. If I look in the Dell Storage Manager under Host Mappings I see that Hosts is under Unassociated Host Port Identifiers. Is that correct or do they need to be assigned to a Host Port Identifier.

Your help would be appreciated.

Regards

Kenny

I have a clean install of windows server 2012.  Install OpenManage Server Administrator 8.0.2.  Website comes up but no data.  The DSM SA DATA Manager service will not start or start manually.  Error in the logs:

Faulting application name: dsm_sa_datamgr64.exe, version: 8.0.2.1331, time stamp: 0x5446dbf1

Faulting module name: dcwfm64.dll, version: 8.0.2.1331, time stamp: 0x5446dd8f

Exception code: 0xc0000005

Fault offset: 0x0000000000002ac6

Faulting process id: 0xc4

Faulting application start time: 0x01d05aa85f712421

Faulting application path: C:\Program Files\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr64.exe

Faulting module path: C:\Program Files\Dell\SysMgt\omsa\bin\dcwfm64.dll

Report Id: 9f82c943-c69b-11e4-80bd-782bcb3aee19

Faulting package full name:

Faulting package-relative application ID:

Any thoughts on what's happening?  Note the main system is a Precision R5500 rack unit connected to a MD1200 array.

Thanks

JR

Hi, 

we have an NX3200 which was setup but wish to restore it to "out of the box".

however the system has had a local password set on the local administrator account which is not none so i cant use the system recovery options from the "repair your computer" on the F8 menu.

any help appreciated.

I received my NX3200 fully loaded, but my enterprise has a policy that the only 2012 OS authorized is the Enterprise version. I wiped out the initial install, got 2012 ENT R2 installed, but now in device manager  I have 69 unknown devices that all say Base System Device, and 6 instances that say Performance Counter. I've got all the essentials like the PERC710 Mini and NICs and my drives are all there. There are literally no drivers available from Dells site.

So 1, is there a way to get these drivers, I'm very uncomfortable operating with that many unknown devices. If not, 

2 I tried to go back to 2012 Storage R2 using the Dell OS DVD that came with the system in UEFI mode, but apparently it is not a bootable disk. How do I reload this OS, and does it have all the drivers by default. It should I guess if its a Dell DVD. Sounds like this might be my best option and I'll just have to beg forgiveness from the Enterprise admins.

Thanks for the help

I have an MD1000 split between two servers, a R710 and a PE2950. The 720 is running 2008r2 and the PE2950 is running 2003. I am looking to upgrade the 2950 to 2008.  I would like to connect both sides of the array to the R710.

Can I just connect the 2nd array to the R710 and do a Foreign import?

What will happen to shares/permissions after the import?

Thanks

Hi,

I have MD3000i Raid enclosure with 11 HDD each 300gb, two problem I have :

- Three out of 11 are keep flashing amber , I replaced these HDDs two times with same spec. but           still blinking

- The enclosure status led flashing amber ( red color)

Pls note also that the battery is expired for both controller and will be replaced soon

Any help pls? that is extermly urgent

Thanks

M

Hi,

I have an MD3000 and a MD1000 connected together and am having lots of  disk disconnects and controller errors.  Looking through the logs using MDSM I cant make out what is causing the fault.

The MD3000 has been in for a few years and was expanded with the MD1000 about a month and a half ago.  It ran fine until last week when the MD1000 appeared to disconnect briefly.  This made the virtual disk on it fail and we lost our mailserver.  Right after the event all disks and controllers were showing as optimal.

At some point both of the RAID controllers in the 3000, and the EMMs in the 1000 have failure entries in the log.  Lots of failed/degraded path errors, etc.  After last week I left all the drives out of the 1000 to see if the system would settle down, which it appeared to do.  Yesterday afternoon I pushed all the drives back in and created a disk group, but not a virtual disk.  LKate on yesterday and this morning I get a whole raft of errors and the 3000 appears to fall off the iSCSI network for tens of seconds.

Any ideas anyone?

Can I hotplug the modules in the 1000, one at a time to reseat them?  I did take controller 1 on the 3000 offline and reseat it as I thouthg that was where the errors were coming from.  Both PSU in the 3000 have been reseated too.

It's driving me mad!

Hi,

I purchased an MD3000i that I think had an expansion enclosure attached to it.

I have the MD3000i working great, but cannot clear the alarm light. Recovery Guru reports "Loss of Path Redundancy" and I cannot clear this.

I have been through the CLI guide for this SAN and cannot find a command to reset this.

All physical disks show:

DRIVE CHANNELS:

TRAY, SLOT PREFERRED CHANNEL REDUNDANT CHANNEL
0, 0 1 Physical Disk path redundancy: Lost
0, 1 1 Physical Disk path redundancy: Lost
0, 2 1 Physical Disk path redundancy: Lost
0, 3 1 Physical Disk path redundancy: Lost
0, 4 1 Physical Disk path redundancy: Lost
0, 5 1 Physical Disk path redundancy: Lost
0, 6 1 Physical Disk path redundancy: Lost
0, 7 1 Physical Disk path redundancy: Lost
0, 8 1 Physical Disk path redundancy: Lost

The RAID Controllers are upgraded to the latest FirmWare:

Firmware version:         07.35.39.64 

Can anyone help with a command that I can run to clear this.

Jim

I need someone to tell me if my approach is correct.  We have a Poweredge 2950 connected to a Powervault MD1000 with a bad slot.  We have another Powervault MD1000 that we are going to use to replace it.  Since it's the same model array, what do we have to do to transfer the drives to the new array?  I think we should power down the server and storage, disconnect the array, remove the current drives, place them in the same slot in the new array that they're in on the broken array, connect the new array, and restart.  Is this correct?