Unsolved

This post is more than 5 years old

1 Rookie

 • 

8 Posts

30651

May 13th, 2015 07:00

MD3000i Boot loop

Hello,

I have a MD3000i dual controller device with local drives attached.

Two days a go the all device crashed (VMFS on vmware was disconnected)

one i was next to the device ive noticed that only the mgmt ports have link, but the iscsi once dont have.

unfortunately at the moment, i dont have a console cable.

after some investigation i noticed that both the controllers got into a reboot loop, the control would come up, ill have a ping to the MGMT ip, but shortly after itll boot and i will lost ping and vice versa.

i tried all the usual solutions: disconnect one of the controllers, replace their places, disconnect cables etc

after reading this thread: en.community.dell.com/.../19487284

i tried to perform the solution suggested.

I inserted two new drives into the enclosure, and the system booted!

The problem is, that anytime I’m trying to insert anyone of our old data drives to the enclosure the system crash and getting into a reboot cycle again.

I tried to upgrade one of the controller firmware, but then it didn’t recognized the data drive at all (Marked as incompatible, and no HD firmware was founded for them), after that I downgrade the firmware gradually until our current firmware version - 07.35.31.60, with no luck, either the system is marking the drives as incompatible, or it starting to reboot itself.

Please help,

Yuval

May 13th, 2015 11:00

Hello, yuyudodo.

I'm afraid from what I've read here, it sounds like either you have a corrupted dacstore on the disks, or a corrupted database on the controllers. Either way, we wouldn't be able to tell without a serial cable or a support bundle. I would see what you could do to obtain a serial cable, and we can send you instructions on grabbing a "serial capture".

But, without the "serial capture", my best guess is a corrupt dacstore or corrupted metaData.

1 Rookie

 • 

8 Posts

May 13th, 2015 12:00

Hey Daniel,

I tired replace to an alternative controllers\Enclousre, but the error still occur when im trying to insert one of my old data drives (any of them)

Please see a support package included i took from the controller while it was booting without any drives.

1 Attachment

1 Rookie

 • 

8 Posts

May 13th, 2015 13:00

Link to Files: (Forum wont let me upload zip)

https://www.sendspace.com/file/yw9l9t

1 Rookie

 • 

8 Posts

May 13th, 2015 13:00

Hey Daniel,

I tired replace to an alternative controllers\Enclousre, but the error still occur when im trying to insert one of my old data drives (any of them)

Please see a support package included i took from the controller while it was booting without any drives.

May 13th, 2015 15:00

I'm having trouble with that link. I sent you an email, and you can reply with the bundle.

Again, it doesn't sound like there's much we can do from here, but I'll take a look.

1 Rookie

 • 

8 Posts

May 13th, 2015 19:00

Here is the eaxct error code from the console:

05/14/15-01:41:00 (GMT) (ssmSpin): ASSERT: Assertion failed: driveRoleState, file vdmDrive.cc, line 133

05/14/15-01:41:00 (GMT) (IOSched): NOTE:  QLDoInterruptServiceRoutine: TOE/FW has reset adapter.  CSR 00008708 AS 2 AF 800001

NOTE:  I2C transaction returned 0x0423fe00

1 Rookie

 • 

8 Posts

May 13th, 2015 21:00

Once trying with the latest firmware, that's the input im getting while inserting one of the data drives:

05/14/15-02:27:51 (GMT) (ssmSpin): WARN:  Drive constructor - invalid role state

05/14/15-02:27:51 (GMT) (ssmSpin): ERROR: DriveSerializer: Caught Drive Persistence Exception

05/14/15-02:27:51 (GMT) (ssmSpin): WARN:  Caught Drive Persistence Exception in SubRecInterface::constSrIter::operator*

05/14/15-02:27:51 (GMT) (ssmSpin): WARN:  Caught Drive Persistence Exception in DriveMgr::readDrives

05/14/15-02:27:51 (GMT) (ssmSpin): WARN:  Drive 0x10002 will be marked incompatible as DSM detected error: 12

05/14/15-02:27:51 (GMT) (ssmSpin): WARN:  Incompatible Drive having WRONG Cause

05/14/15-02:28:23 (GMT) (ssmEvent): WARN:  Incompatible Drive having WRONG Cause

0 events found

No Events found!

Top