Unsolved

18 Posts

1568

April 30th, 2020 17:00

EqualLogic MicroSD error

I have a EqualLogic array that went through a dirty shutdown a few days ago due to a power outage.

When the array was restarted the microSD card on the main controller was corrupt.

I was able to clone a new microSD card from the second controller and get a CLI prompt.  But the array immediately went into initializing mode.

It has been doing that for almost 48 hours now.

Starting to wonder if I need to do something or if this is normal. 

4 Operator

 • 

1.5K Posts

April 30th, 2020 17:00

Hello, 

First make sure you are on the active controller.  

CLI>  means either passive controller or the array configuration isn't loading. 

What model array and what firwware? 

 Regards, 

Don 

18 Posts

April 30th, 2020 17:00


Welcome to Group Manager

Copyright 2001-2017 Dell Inc.


netmgtd:1588296110.65:rcc_util.c:1026:INFO:25.2.9:CLI: Login to account grpadmin succeeded, using local authentication. User privilege is group-admin.
netmgtd:1588296110.65:rcc_util.c:1034:AUDIT:25.7.0:CLI: Login to account grpadmin succeeded, using local authentication. User privilege is group-admin.

The storage array is still initializing. Limited commands will be available unt
il the initialization is complete. Please try again later.

18 Posts

April 30th, 2020 18:00

I am 99% sure I am connected to main controller by serial (both are type 10 controllers).  I also have 2 backup controllers but not sure on firmware and not sure if using would cause data loss.

18 Posts

April 30th, 2020 18:00

PS6010S

Last I remember was firmware 9.1.2, cannot access system so not positive.

4 Operator

 • 

1.5K Posts

April 30th, 2020 19:00

Hello, 

The firmware is in the SD card so you can swap the card from existing to a replacement to maintain correct firmware. 

 It is very unlikely to be a bad controller.  You can power down the array and swap flash card and power up with another controller. 

 But this sounds more like either a RAID/disk problem or a problem with the internal logs. 

Regards, 

Don 

18 Posts

May 1st, 2020 09:00

New type 10 controllers but still repeating this reboot:

#########################################################
#                                                       #
#          Dell (tm), Inc. Storage Array                #
#               Copyright 2001-2009                     #
#                                                       #
#             Controller Information:                   #
# Part=70-0300 Rev=A06 SN=RMS0943675G1CF4 ECO=C00       #
#                                                       #
#########################################################
Bootloader Version 2.3.5 (SWINT Rev:1)
Compiled on Mon Apr 30 17:08:16 EDT 2012
(type h for help)
Enter Ctrl-P for boot prompt
 
Executing bootcmd0 [dload sd primary/eqlstor.gz]
0X80231000/11912  0X85f08100/31424212    entrypt 80231000
 
Executing bootcmd1 [run]
cpu_online_map=ffff, userapp_cpu_map ffff
psb_os_active_mask=0, psb_os_mask=0
boot1_info: userapp_cpu_map=ffff, psb_os_cpu_map=0
            cpu_online_map = 0xffff
Jumping to the application... 0x80231000
------------------------------------------------------------
Preparing ffff bitmask of cpus to run
No network device to cleanup
count = 16, total = 16
All slave cpus (16) ack'ed userapp init
count = 4, total = 4
All slave cpus (4) ack'ed message ring init
 
Dell Inc. Storage Array
 
Copyright 2001-2016 Dell Inc.
SP:13.81:mips_pss_init.c:363:INFO:28.2.107:Control module in slot 1 with serial number RMS0943675G1CF4 is designated as active.
SP:1588358457.28:ppool_nvram.c:396:ERROR:15.4.1:NVRAM contains valid data. This is a PANIC RECOVERY due to a panic on a NetBSD processor.
SP:1588358457.28:ppool_nvram.c:188:ERROR:15.4.5:Saved CPU registers, CPU 0
 at 0000000000000000 v0 ffffffff80b73d00 v1 0000000000000000
 a0 ffffffff80b8d3e0 a1 ffffffff80b81200 a2 ffffffff80b74380 a3 ffffffff80b73d00
 t0 0000000000000840 t1 80ffc0c08080f0ff t2 c0c0c0c0c0fffc80 t3 ffffffc0c0f8c080
 t4 000000004000c001 t5 0000000000000007 t6 0000000000000007 t7 0000000000000000
 s0 ffffffff80b8d3e0 s1 ffffffff8efd3000 s2 0000000000000000 s3 0000000000000001
 s4 0000000000000000 s5 0000000051eb851f s6 0000000000000064 s7 ffffffff8e1d4680
 t8 ffffffff8344c00c t9 ffffffff80414538 k0 0000000000385fdf k1 0000000000000001
 gp ffffffff8110a6b0 sp 00000000c87af820 s8 00000000000000a2 ra ffffffff809ef8f0
SP:1588358457.28:ppool_nvram.c:206:ERROR:15.4.6:Saved CP0 registers, CPU 0
 sr 4000ff01    badva c0330e98      epc 8092eed0 errorepc bfc00000
 cause 00000008   errctl 00000000 cacheeri 00000000 cacheerd 00000000
 buserr 0000000000000000 cacheerrdpa 0000000000000000
SP:1588358457.28:ppool_nvram.c:213:ERROR:15.4.7:Saved function call stack, CPU 0
   80586ab4 809ef8f0 80904abc 8091614c 80916b7c 80930d5c 809359b4 80935e78
  808a22d4 8088f660 8088f9cc 8088fd00 8099b458 8099b770 80592434 00000000
SP:1588358457.28:eqllog_mbuf_Q.c:1100:ERROR:2.4.0:Panic recovery from CPU0 with reason 'kernel fatalassertion "!IOM_IS_INVALID_METADATA_VERSION(version)" failed: file "../../../NetBSD/src/sys/EQL/ioman/lv2/lv2_lv_log_read.cc", line 2112'.
MFS set up
Building databases...
SP:1588358464.76:emm.c:1333:INFO:28.2.6:Enclosure serial number: SHU0937898Y9856.
SP:1588358465.28:misc.c:198:WARNING:32.3.39:Enclosure/Drive 0/0 is not approved because it uses logical block size emulation.
SP:1588358465.28:pclass.c:10139:WARNING:32.3.28:The drive at enclosure 0, drive 0 [PFAIL]
[ENTRY][BIST][EQL][TWDOG][WFP][210][CM1D][MESR][SCAN][BOOT2][PROC][BOARD][SMP][IOBUS][FLASH][HT][ETH0][ETH1][ETH2]
 
And when I can login it tells me the drives are still initializing...

4 Operator

 • 

1.5K Posts

May 1st, 2020 11:00

Hello, 

 Did you replace drive 0 at some point recently? 

Enclosure/Drive 0/0 is not approved because it uses logical block size emulation.

At the CLI prompt please run   CLI>su exec raidtool   And post the output 

Regards, 

Don 

No Events found!

Top