Hi everyone,

Need some help on my issue below.

We have PowerVault MD3200 and MD1200 as extension. Disk used is Seagate 600GB SAS.

Earlier, there was unreadable sector error on the system. From log, it shows physical disk 1,3 was a culprit. I had marked this disk as failed and use option Replace in MDSM to replace this disk with our unassigned disk at 1,11. Now Recover Guru does not report any unreadable sector.

But, the virtual disk still shows as degraded although reconstruction already finished after some 1 hour +. Then, we hit another issue when physical disk at 1,3 was failed and our virtual disk goes to failed state. The problem is when failed disk happen, our spare disk does not take over. I try to manually fail the disk after revive it back but spare disk still silent.

Basically, we hit two problems here and I would like to know what action can I take in order to resolve this issue

1. Virtual disk goes to degraded state after reconstruction finish before another failed disk happen. How to ensure virtual disk goes to optimal state?

2. Failed disk happen and spare disk does not take over, resulting in my virtual disk goes to failed state.

Thank you

I have two MD3000i arrays that seem to be experiencing slot failures.  The symptom starts as a disk showing impending failure in one specific slot.  Normal replacement with a new disk works fine, but during the copyback process, the new disk starts to show impending, or actual failure.  These same "failing" disks work fine in any other slot.  In one array, the failing slot is #3, in the other it is #6. Any ideas what might be the cause of this?  Could it simply be a dirty connector?

When a hard drive fails we see the light flash amber on front of the unit but an email is received. The test email works just fine. Additionally when the bad drive is pulled and the new one put in you get the critical emails for those events. But I don't get an email when a drive has failed. Everything works fine on an MD3000 we have in the same situation and the email settings are set the same way. But for some reason the MD3000i emails for a hard drive bad isn't sent.

There are two options for setting up SNMP for the storage arrays. There are SNMP alert notifications originating from the Event Monitor, and SNMP alert notifications originating from the storage array (depending on your RAID controller module model)

Both SNMP agent locations can be configured in the MDSM GUI. When trying to do this with SMcli, the command looks like this:

SMcli -a trap:public, 123.45.67.891 123.45.67.892

Not included in any documention that i've read is that the SMcli command only sets up SNMP alert notifications originating from the Event Monitor.

Is there a way to setup SNMP alert notifications originating from the storage array without having to use the MDSM GUI? With SMcli it is possible to check the current SNMP configuration with "show storageArray;". I need a way to set those settings on the RAID controller without having to use the GUI (so that it can be a part of automated provisioning).

We have an MD3000 storage array that did something very weird about a month ago.  We have two servers attached to it via HBA adapters.   The servers lost connectivity to the array and our servers disconnected.    Once we rebooted our servers, everything appeared to be fine.  The only errors showing were sector error on a disk.  But when pulling the support information it was referring to disks that had failed 4 months prior.  

Then last week the MD3000 just crashed.   Totally down.  Could not get onto the unit at all.  Flashing Red lights...  the works...   It was in a constant reboot.  One controller would attempt to come up, crash, and then the other controller would do the same.   If we pulled the drives all out of the array we were then able to consistently ping the controllers.   But could never get access to the MDSM.

Our vendor shipped us a replacement unit and we moved all the drives over 1 for 1 along with the controllers.   The result was the same.  Constant reboots.   We were initially thinking that the backplane was the issue.   Next we tried plugging the drives into another unit with new controllers.    The unit did the same thing that time as well.  

We then found an article that talked about putting 2 new drives into the array and powering it up.   We were then able to see the drives in the array and also access MDSM.   From there we put in the remaining drives 1 by 1.   System stayed up the entire time.   We then installed Disk 1 and finally Disk 0.  The system was able to see all 10 drives we had in the system.   However, it did NOT see our Disk Groups!   

How can we get the controllers to read the "foreign config" off of the drives and import it to the controllers so we can access our data?

Is there some type of recovery command we can run?   I see recovery data in the MDSM folder structure on my server...   Is there a way to import that original config in?

HELP!!!!

Thanks,

RIch

Okay so before i start, yes i have seen the tech spec saying that the md1200 needs a h800 to run

However:

can you run an MD1200 on a Perc6E using the following cable?

Okay so ive seen the tech spec that says you need a h800 to run an md1200

however 

is it possible to run it on a perc6E using the following cable:

www.amazon.com/.../ref=wms_ohs_product

Here are this week's top-rated support articles based on accuracy, usefulness, & ease of understanding:

• Identify your PowerEdge server's generation, processor, & more just by its model number
• How to configure iDRAC and systems management options on PowerEdge servers
• Managing multiple servers with OpenManage & OpenManage Essentials
• How to export RAID controller logs with OpenManage
• Understanding chassis diagnostic indicators & hard drive carrier LEDs 

Hello, we have an MD3200i with 12 500GB drives in Raid 5.  We have bought 4  1TB drives because we want to increase our size. We have 2 Pools, each with 1/2 of the total space available. We do not need to retain the data in Pool B but the data in Pool A is sensitive and needs to be intact. How can we remove the drives in Pool B, add the 4 1TB drives to it without losing Pool A? 

Any help is appreciated.

Hello - 

I am fairly new to the DAS environment and have been playing around with it for several month.  Most of the items I have come across I can get thorugh with a little reading (ok, sometimes more than a little), but overall it is fairly simple.  The one item that just keeps stumping me is the Reconfigure function in OMSA.  I currently have Raid6 setup with 4 drives, and would like to expand that to 6 drives.  When I go in  to the Virtual Disk and select reconfigure, I get an error

<Name> Reconfigure Error, Possible reasons include:

-Not enough physical disk space.

-The virtual disk has reached the maximum number of physical disks supported that can be reconfigured at this time.

-Reconfiguration or resizing is not supported at this time.

-Invalid configuration. For information about reconfiguring virtual disks or resizing CacheCade(s), see the Online Help and the Storage Controller documentation."

Everything I read indicates that I should be able to expand the volume and reconfigure the array to add the new drives.  I have tried this with both drives that are the same size, and drives that are larger than the existing drives.

Any help would be appreciated. 

Hello,

I have a few MD3200i EMM's with the same problem. For some reason they are showing a product ID of MD36xxf instead of the correct MD32xxi.

I know that these are 3200i EMM's because they have the same part number as the other 2 MD3200i EMM's that I have: DP/N 0770D8.

It's not a huge deal at the moment as it really has no bearing on performance just an odd label that I would prefer to change back to the correct one and I can't seem to find anything about this odd situation on the net.

Thanks for any help anyone can give me.

Is there any problem with temporarily having 2 different backup media servers connected to the DR4100 we have been backing up to for a couple of years?

I'm running BE 2014 on a 2008 server and am trying to migrate to a new 2012 server. I went through Veritas' BE migration steps, but I could not get the DR to show up as storage on the new server, even working with a Veritas tech. I blew away the new installation and plan to reinstall from scratch again. I want to connect to the DR before migrating the job data and catalogs (in fact, I may just migrate the catalogs and create the jobs from scratch). As long as I don't have any jobs running on either, can I have both servers connected without affecting the backup data?

Hi

I am adding Dell TL 2000 to smantic backup exe but I can not see the cariages/Media to Lable it.

TL is connectivity with host through SAS cables. on host windows 2012 R2 is installed.

I can see the Tape drives in device manager but I can't see "Media changers..." in device manager.

I updated the driver as well . Please guide me in this regards asap.

I have PowerVault MD 3200 and I expanded it by PowerVault MD1200

When I connect MD 1200 it doesn't show up on Storage Manager and I get error message in Event log says that"Physical physical disk has unsupported capacity" message is repeated by each slot no.

My MD1200 consist of 12 Dell Hard Disks (SAS  12Gbps - 512e - RPM 7.2K - 6 TB)

Much appreciated your assist...

Hello,

in our company we have an MD3000i. Contained disks were configured in RAID6 and were exposing 2 separate LUNs used by 3 servers machines through iSCSI.

After a power loss we were not able to see the logical volumes anymore.

Management ports were answering to ping but not reachable using the MDSM utility.

After a long search we found the original serial cable in its original box and managed to connect it using hyperterminal running on an old windows XP laptop (115200:8:N:1:N).

We found that on both controllers the starpup was failing due to a firwmare failure.

When we send a break signal we the system ask us to press an uppercase 'S' to enter service interface. Unfortunately after pressing 'S'  we have no result.

We also tried to swap the two controllers master <-> slave but the result was the same.

Is there any way to upload the firmware on one controller using the serial cable or the management port in the described situation?

Can you please help us? Any contribute is for sure precious.

Best regards

Francesco

here follows a log trace of one of the controllers:

Current date: 01/19/17 time: 03:46:04

Send <BREAK> for Service Interface or baud rate change
01/19/17-12:59:48 (GMT) (tRAID): NOTE: Set Powerup State
01/19/17-12:59:48 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
01/19/17-12:59:48 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
01/19/17-12:59:48 (GMT) (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBas
e = 0x0
01/19/17-12:59:48 (GMT) (tRAID): NOTE: Turning on tray summary fault LED
01/19/17-12:59:50 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
01/19/17-12:59:50 (GMT) (tRAID): NOTE: lost persistent dq data because buffer w
as modified or size changed.
01/19/17-12:59:54 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
01/19/17-12:59:56 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-63-00
01/19/17-13:00:00 (GMT) (tNetCfgInit): NOTE: Network Ready
01/19/17-13:00:04 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:00:04 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:00:14 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
01/19/17-13:00:14 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
01/19/17-13:00:14 (GMT) (tRAID): WARN: No attempt made to open Inter-Controller
Communication Channels
01/19/17-13:00:14 (GMT) (tRAID): NOTE: LockMgr Role is Master
01/19/17-13:00:14 (GMT) (tRAID): WARN: FBM:validateSubModel: Exception - Alt co
ntroller not ready
01/19/17-13:00:14 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawne
d
01/19/17-13:00:15 (GMT) (tRAID): NOTE: spmEarlyData: No data available
01/19/17-13:00:15 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version:
0116-e05c
01/19/17-13:00:15 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi =
x5a4badb4 Low = x1925ed10
01/19/17-13:00:20 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Ti
me: 30 seconds
01/19/17-13:00:20 (GMT) (tRAID): NOTE: WWN baseName 0008a4ba-db1925ed (valid==>
SigMatch)
01/19/17-13:00:20 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
01/19/17-13:00:20 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
01/19/17-13:00:21 (GMT) (tRAID): WARN: BID: initialize(): Power latched!
01/19/17-13:00:31 (GMT) (tRAID): NOTE: ACS: Icon ping to alternate failed: -2,
resp: 0
01/19/17-13:00:31 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm
Mode: 0, Status: 0
01/19/17-13:00:31 (GMT) (tRAID): WARN: ACS: autoCodeSync(): Skipped since alt n
ot communicating.
01/19/17-13:00:31 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization
Phase Complete
01/19/17-13:00:31 (GMT) (tRAID): NOTE: Caught IconSendInfeasibleException Error
in iop::requestAltIopDelay
01/19/17-13:00:31 (GMT) (tRAID): NOTE: CheckInMonitor: Check-in failed (IconSen
dInfeasibleException Error)
01/19/17-13:00:32 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage
updated successfully
01/19/17-13:00:32 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 r
ecords.
01/19/17-13:00:32 (GMT) (tRAID): WARN: Received IconSendInfeasibleException Err
or adding small edr records from alt controller
01/19/17-13:00:32 (GMT) (tRAID): WARN: spm: unable to exchange features, assumi
ng none
01/19/17-13:00:32 (GMT) (tRAID): NOTE: SPM acquireObjects exception: IconSendIn
feasibleException Error
01/19/17-13:00:32 (GMT) (tRAID): NOTE: DBRead 0.196 secs
01/19/17-13:00:33 (GMT) (tRAID): NOTE: sas: Peering Disabled (Alt Unavailable)
01/19/17-13:00:33 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0
01/19/17-13:01:01 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:01:01 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:01:01 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:01:01 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:01:01 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:01:01 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:01:01 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:01:01 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:01:03 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0
01/19/17-13:01:30 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:01:30 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:01:31 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:0 Qlogic coredump file write failed.fclose returned -1

01/19/17-13:01:31 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:01:31 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:01:31 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:01:31 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:01:32 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0
01/19/17-13:01:59 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:01:59 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:02:00 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:02:00 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:02:00 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:02:00 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:02:00 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:02:00 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:02:01 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0
01/19/17-13:02:28 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:02:28 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:02:29 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:02:29 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:02:29 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:02:29 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:02:29 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:02:29 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:02:30 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0
01/19/17-13:02:39 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumAc
tivePhys:0 numActivePhys:1
01/19/17-13:02:39 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: IOCPort: chan:0, FAILE
D to DEGRADED
01/19/17-13:02:39 (GMT) (tSasEvtWkr): WARN: sasIocPhyUp: Initializing Channel 0
: Attached SAS Address: 5a4badb41a459a10
01/19/17-13:02:41 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumAc
tivePhys:1 numActivePhys:2
01/19/17-13:02:41 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: IOCPort: chan:0, DEGRA
DED to OPTIMAL
01/19/17-13:02:58 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:02:58 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:02:58 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:02:58 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:02:58 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:02:58 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:02:58 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:02:58 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:02:59 (GMT) (tRAID): WARN: QLStartAdapter: ControllerErrorCount exc
eeds threshold.
01/19/17-13:02:59 (GMT) (tRAID): ERROR: QLInitializeDevice: QLStartAdapter faile
d
01/19/17-13:02:59 (GMT) (tRAID): ERROR: QLAddDevice: controller/device/chip init
ialization failed.
01/19/17-13:02:59 (GMT) (tRAID): ERROR: qlgEnableHostInterface: QLInitializeDevi
ce failed.
01/19/17-13:02:59 (GMT) (tRAID): NOTE: ****************************************
****************************************
01/19/17-13:03:00 (GMT) (tRAID): NOTE: QLogic Target Application, Version 2.0
1.08 6-13-2005 (W2K)
01/19/17-13:03:00 (GMT) (tRAID): NOTE: iSCSI Target Application
01/19/17-13:03:00 (GMT) (tRAID): NOTE: ***************************************
*****************************************

Exception: Data Abort
-=<###>=-
Attaching interface lo0... done

Adding 9767 symbols for standalone.
Error
01/19/17-13:03:13 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00

WARNING: Restart by watchdog time out

Current date: 01/19/17 time: 03:49:46

Send <BREAK> for Service Interface or baud rate change
01/19/17-13:03:30 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
01/19/17-13:03:30 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
01/19/17-13:03:30 (GMT) (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBas
e = 0x0
01/19/17-13:03:30 (GMT) (tRAID): NOTE: Turning on tray summary fault LED
01/19/17-13:03:32 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
01/19/17-13:03:35 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
01/19/17-13:03:38 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-63-00
01/19/17-13:03:42 (GMT) (tNetCfgInit): NOTE: Network Ready
01/19/17-13:03:47 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:03:47 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:03:48 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:03:48 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:03:48 (GMT) (tSasCfg016): NOTE: Alt Controller path up - chan:1 phy
:18 itn:1
01/19/17-13:03:48 (GMT) (tSasCfg021): NOTE: Alt Controller path up - chan:0 phy
:16 itn:2
01/19/17-13:03:57 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
01/19/17-13:03:58 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
01/19/17-13:03:58 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels
Opened
01/19/17-13:03:58 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawne
d
01/19/17-13:03:58 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHand
le: x2b, SAS Address: 5a4badb41a459a00
01/19/17-13:03:58 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHand
le: x1a, SAS Address: 5a4badb41a459a01
01/19/17-13:03:58 (GMT) (tRAID): NOTE: LockMgr Role is Slave
01/19/17-13:03:58 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version:
0116-e05c
01/19/17-13:03:58 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi =
x5a4badb4 Low = x1925ed10
01/19/17-13:03:58 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
01/19/17-13:04:02 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Ti
me: 30 seconds
01/19/17-13:04:02 (GMT) (tRAID): NOTE: WWN baseName 0006a4ba-db1a459a (valid==>
BaseFromAlt)
01/19/17-13:04:02 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a
channel to become ready
01/19/17-13:04:03 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms fo
r a channel to become ready
01/19/17-13:04:03 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
01/19/17-13:04:03 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
01/19/17-13:04:16 (GMT) (iacTask1): NOTE: ACS: Acs Needed on Alt: No, StateCode
: 3, ReasonCode = 2
01/19/17-13:04:16 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm
Mode: 0, Status: 1
01/19/17-13:04:16 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization
Phase Complete
01/19/17-13:04:18 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - Wide
Port: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
01/19/17-13:04:18 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - Wide
Port: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
01/19/17-13:04:18 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - Wide
Port: #0 - Alt Controller, chan:0 encl:0, subExp:255, OPTIMAL to DEGRADED
01/19/17-13:04:18 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - Wide
Port: #0 - Alt Controller, chan:0 encl:0, subExp:255, DEGRADED to FAILED
01/19/17-13:04:18 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1,
devHandle: x1a, I/O: 0, SAS Address: 5a4badb41a459a01
01/19/17-13:04:18 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send E
ventAck: event: 00000018, eventContext: 0002001a
01/19/17-13:04:18 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - Se
ndEventAck for host: 2
01/19/17-13:04:18 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0,
devHandle: x2b, I/O: 0, SAS Address: 5a4badb41a459a00
01/19/17-13:04:18 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send E
ventAck: event: 00000018, eventContext: 0002002b
01/19/17-13:04:18 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - Se
ndEventAck for host: 1
01/19/17-13:04:20 (GMT) (tHckReset): NOTE: LockMgr Role is Master
01/19/17-13:04:26 (GMT) (tRAID): NOTE: Scsicon error status fe received.
01/19/17-13:04:26 (GMT) (tRAID): WARN: sendTaskLockMsg: Error or Infeasible mes
sage status=fffffffd
01/19/17-13:04:26 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:04:26 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage
updated successfully
01/19/17-13:04:26 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 r
ecords.
01/19/17-13:04:26 (GMT) (tRAID): WARN: Received IconSendInfeasibleException Err
or adding small edr records from alt controller
01/19/17-13:04:27 (GMT) (tRAID): WARN: spm: unable to exchange features, assumi
ng none
01/19/17-13:04:27 (GMT) (tRAID): NOTE: SPM acquireObjects exception: IconSendIn
feasibleException Error
01/19/17-13:04:27 (GMT) (tRAID): NOTE: DBRead 0.167 secs
01/19/17-13:04:27 (GMT) (tRAID): NOTE: sas: SOD Bad Check-in: IconSendInfeasibl
eException Error
01/19/17-13:04:28 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 03208a80 4c0c8 bytes , result 0
01/19/17-13:04:53 (GMT) (tSasEvtWkr): NOTE: sasLinkUp: expDevHandle:x9 - WidePo
rt: #1 - Alt Controller, chan:1 encl:0, subExp:255, FAILED to DEGRADED
01/19/17-13:04:53 (GMT) (tSasEvtWkr): NOTE: sasLinkUp: expDevHandle:x9 - WidePo
rt: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to OPTIMAL
01/19/17-13:04:53 (GMT) (tSasEvtWkr): NOTE: sasLinkUp: expDevHandle:xa - WidePo
rt: #0 - Alt Controller, chan:0 encl:0, subExp:255, FAILED to DEGRADED
01/19/17-13:04:53 (GMT) (tSasEvtWkr): NOTE: sasLinkUp: expDevHandle:xa - WidePo
rt: #0 - Alt Controller, chan:0 encl:0, subExp:255, DEGRADED to OPTIMAL
01/19/17-13:04:54 (GMT) (tSasCfg037): NOTE: Alt Controller path up - chan:1 phy
:18 itn:1
01/19/17-13:04:54 (GMT) (tSasCfg038): NOTE: Alt Controller path up - chan:0 phy
:16 itn:2
01/19/17-13:04:55 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:04:55 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:04:56 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:04:56 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:04:56 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:04:56 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:04:56 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:04:56 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:04:57 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 03208a80 4c0c8 bytes , result 0
01/19/17-13:05:08 (GMT) (IOSched): NOTE: Connect Initiator: 1 - channel: 0,dev
Handle: x2b, SAS Address: 5a4badb41a459a00
01/19/17-13:05:08 (GMT) (iconMgr4): WARN: sasNetworkManager::healthCheckEvent -
Unknown Event (-3)
01/19/17-13:05:08 (GMT) (IOSched): NOTE: Connect Initiator: 2 - channel: 1,dev
Handle: x1a, SAS Address: 5a4badb41a459a01
01/19/17-13:05:08 (GMT) (iconMgr4): NOTE: CheckInMonitor: Check-in failed (NoUn
marshalFuncException Error)
01/19/17-13:05:08 (GMT) (iacTask3): NOTE: fbm:altValidateSubModelID: Sub-Model
IDs Validated
01/19/17-13:05:24 (GMT) (iacTask1): NOTE: ACS: Acs Needed on Alt: No, StateCode
: 3, ReasonCode = 2
01/19/17-13:05:24 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:05:24 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:05:25 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:05:25 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:05:25 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:05:25 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:05:25 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:05:25 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:05:27 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 03208a80 4c0c8 bytes , result 0
01/19/17-13:05:54 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:05:54 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:05:55 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:05:55 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:05:55 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:05:55 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:05:55 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:05:55 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:05:56 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 03208a80 4c0c8 bytes , result 0
01/19/17-13:06:23 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:06:23 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:06:24 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:06:24 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:06:24 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:06:24 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:06:24 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:06:24 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:06:25 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image
03.00.01.47 from 03208a80 4c0c8 bytes , result 0
01/19/17-13:06:52 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion
timeout
01/19/17-13:06:52 (GMT) (tRAID): WARN: QLMailboxCommand: command completion tim
eout, cmd = 0x69
01/19/17-13:06:53 (GMT) (tRAID): NOTE: Qlogic coredump file written to '1WDYM4J
:/tmp/QLogic_Coredump_port_0_1WDYM4J',rc 204E50, expected 204E50
01/19/17-13:06:53 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose
returned -1

01/19/17-13:06:53 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
01/19/17-13:06:53 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail
ed. Stat f000
01/19/17-13:06:53 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State
4543
01/19/17-13:06:53 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
01/19/17-13:06:54 (GMT) (tRAID): WARN: QLStartAdapter: ControllerErrorCount exc
eeds threshold.
01/19/17-13:06:54 (GMT) (tRAID): ERROR: QLInitializeDevice: QLStartAdapter faile
d
01/19/17-13:06:54 (GMT) (tRAID): ERROR: QLAddDevice: controller/device/chip init
ialization failed.
01/19/17-13:06:54 (GMT) (tRAID): ERROR: qlgEnableHostInterface: QLInitializeDevi
ce failed.
01/19/17-13:06:54 (GMT) (tRAID): NOTE: ****************************************
****************************************
01/19/17-13:06:54 (GMT) (tRAID): NOTE: QLogic Target Application, Version 2.0
1.08 6-13-2005 (W2K)
01/19/17-13:06:54 (GMT) (tRAID): NOTE: iSCSI Target Application
01/19/17-13:06:54 (GMT) (tRAID): NOTE: ***************************************
*****************************************

Exception: Data Abort
cpsr: 60000013 pc: 0x0020eb94 semTake
-=<###>=-
Attaching interface lo0... done

Adding 9767 symbols for standalone.
Error
01/19/17-13:07:45 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00

WARNING: Reset by alternate controller

Current date: 01/19/17 time: 03:54:18

Send <BREAK> for Service Interface or baud rate change
01/19/17-13:08:02 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
01/19/17-13:08:02 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
01/19/17-13:08:02 (GMT) (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBas
e = 0x0
01/19/17-13:08:02 (GMT) (tRAID): NOTE: Turning on tray summary fault LED
01/19/17-13:08:04 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
01/19/17-13:08:07 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
01/19/17-13:08:10 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-63-00
01/19/17-13:08:14 (GMT) (tNetCfgInit): NOTE: Network Ready
01/19/17-13:08:19 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:08:19 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:08:20 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:08:20 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumAc
tivePhys:2 numActivePhys:2
01/19/17-13:08:20 (GMT) (tSasCfg016): NOTE: Alt Controller path up - chan:1 phy
:18 itn:1
01/19/17-13:08:20 (GMT) (tSasCfg021): NOTE: Alt Controller path up - chan:0 phy
:16 itn:2
01/19/17-13:08:29 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
01/19/17-13:08:30 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
01/19/17-13:08:30 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels
Opened
01/19/17-13:08:30 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawne
d
01/19/17-13:08:30 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version:
0116-e05c
01/19/17-13:08:30 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi =
x5a4badb4 Low = x1925ed10
01/19/17-13:08:35 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Ti
me: 30 seconds
01/19/17-13:09:14 (GMT) (tRAID): NOTE: Scsicon error status fe received.
01/19/17-13:09:59 (GMT) (tRAID): NOTE: Scsicon error status fe received.
01/19/17-13:10:01 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:10:44 (GMT) (tRAID): NOTE: Scsicon error status fe received.
01/19/17-13:10:44 (GMT) (tRAID): NOTE: LockMgr Role is Master
01/19/17-13:10:47 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:11:29 (GMT) (tRAID): WARN: FBM:validateSubModel: Exception - Alt co
ntroller not ready
01/19/17-13:11:29 (GMT) (IonTask): NOTE: Scsicon error status fe received.
01/19/17-13:11:33 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:12:14 (GMT) (tRAID): NOTE: Scsicon error status fe received.
01/19/17-13:12:19 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:12:59 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
01/19/17-13:13:05 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:13:44 (GMT) (tRAID): NOTE: Scsicon error status fe received.
01/19/17-13:13:51 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:14:14 (GMT) (tRAID): NOTE: WWN baseName 0006a4ba-db1a459a (valid==>
SigMatch)
01/19/17-13:14:14 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
01/19/17-13:14:14 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
01/19/17-13:14:37 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:15:23 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:16:09 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:16:55 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:17:41 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:18:27 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:19:13 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:19:59 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:20:45 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:21:05 (GMT) (ssmEvent): NOTE: Scsicon error status fe received.
01/19/17-13:21:31 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:21:50 (GMT) (ssmEvent): NOTE: Scsicon error status fe received.
01/19/17-13:22:17 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:23:03 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:23:49 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:24:35 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:25:21 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:26:07 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:26:53 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:27:19 (GMT) (ssmEvent): NOTE: Scsicon error status fe received.
01/19/17-13:27:39 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:28:04 (GMT) (ssmEvent): NOTE: Scsicon error status fe received.
01/19/17-13:28:25 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:29:11 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:29:57 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:30:43 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:31:29 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:32:15 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:33:01 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:33:32 (GMT) (ssmEvent): NOTE: Scsicon error status fe received.
01/19/17-13:33:47 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:34:17 (GMT) (ssmEvent): NOTE: Scsicon error status fe received.
01/19/17-13:34:33 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:35:19 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.

01/19/17-13:36:05 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:36:51 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:37:37 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:38:23 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:39:09 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:39:45 (GMT) (ssmSpin): NOTE: Scsicon error status fe received.
01/19/17-13:39:55 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:40:30 (GMT) (ssmSpin): NOTE: Scsicon error status fe received.
01/19/17-13:40:41 (GMT) (IOSched): NOTE: eventDataAlloc calling flushEvents: si
ze: 12
01/19/17-13:40:41 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
01/19/17-13:41:25 (GMT) (IOSched): NOTE: eventDataAlloc calling flushEvents: si
ze: 12
01/19/17-13:41:27 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.

I not sure whats going on and Support doesn't appear to know exactly what is going on either.

I have a MD3820i, brand spanking new. I'm trying to configure the MGMT ports on it, but am unable to do so.

I have server connected via the console cable. I can get to the Service Interface just fine. I can configure my settings just fine. However the unit will not accept my default gateway. It will take the setting that I am putting there, I can save it , reboot the controller and when it comes back online, every setting I setup is present, except the DFGW has reverted to 0.0.0.0. 

I am not using the CLI, or the Management Software, as the device will not discover, because my server, and the unit technically cannot communicate with one another, even though I have them on the same VLAN. 

I've tried enabling/disabling IPv4, IPv6, various settings within the IPv6 setup, tried DHCP (even though there isn't one)

The last tech I was working with, was trying to get in with a special login, but kept setting the terminal session to 115200, which appeared to encode the display making it impossible to get into the unit at all.

I think I may have a unit with bunk FW on it, but has anyone encountered this issue or even anything close to it?

We have a server that is no longer being used but we must maintain access to the records on it for 7 years. It was running CentOS 5.6. It was last backed up in 2014 using the RD1000. The server had a failed HDD and we had to rebuild it. This is the first time I have even seen this server, so I can't explain the lack of raid configs and other such protections. At this point, I have replaced the HDD and reinstalled CentOs 5. I tried to access the RD1000, which does show up in GUI but is not able to be mounted. fdisk -l shows the drive but says the partition table is missing so it cannot be mounted. I tried all 5 back up disks we have stored, all of which were used Monday through Friday for back ups in 2014 and have been in storage since. It seems unlikely that all five backups have gone bad, but I also don't know how they did the back ups so they could have been doing them wrong the whole time. 

 I am mostly a novice with Linux but am learning quickly. Anything anyone can offer to help I would appreciate it. 

Hi,

I've an old PowerVault 124T tape library added to a Windows Server 2012 R2 machine, the drive is showing up ok in device manager, but the medium changer is not. Has anyone come across this issue before and have a fix for it?

I saw a similar issue with an IBM TS3200 before and the library mode needed to be changed from sequential to random, but I don't see the option for this on the GUI (front panel or web interface).

Thanks in advance for any help.

C

Hi everyone,

 I would like to connect my SAS PowerVault directly to the Vmware host 5.1.

Will I be able to use it from a single windows VM ? 

I would like to setup Veeam and use the autoloader for backups. 

The idea is to assign the hardware to a single VM (yes I know I will not be able to vmotion it) and use it. 

I will appreciate any comment / support. 

Cheers, Dan

Here are this week's top-rated support articles based on accuracy, usefulness, & ease of understanding:

• Safety precautions to take while replacing parts in your Dell system 
• Obtaining logs from your PowerEdge M1000E Chassis Management Controller (CMC)
• How to gather logs in Windows Server using DSET 3.7
• Installing OpenManage Server Administrator (OMSA) on VMware to collect logs
• Resolve PowerEdge CMOS battery status showing as "unknown" in OMSA 7.x