22 Posts
0
16263
Unable to boot to utility partition on VNX5300, help!
System is out of warranty and a lab system, its working but i want to reload the image on it because some configuration won't let me delete it.
I boot it up with serial cable attached, and hit ctrl-c and per "Backrev Array" solution it's supposed to do a Minisetup and reboot a few times. It never reboots it just sits at the "int13 - EXTENDED READ (4000)" and never goes further.
I rebooted it manually myself and try to start the process again but I just get this... any ideas?
ABCDabcdEFabcd << Stopping after POST >> GabcdefHabcdefIabcdefJabcdeKLabMabNabOabcPQRSTUVWabXYabZAABBCCabDDabcEEabcFFabcGGabcHHabcIIabJJabKKLLMMNNOOPPQQRRSSTTUUVVWWXX
************************************************************
* Extended POST Messages
************************************************************
INFORMATION: POST Start
INFORMATION: MCU Operating mode changed from Linux to Clariion
INFORMATION: PSB not present
************************************************************
EndTime: 10/28/2018 15:29:59
.... Storage System Failure - Contact your Service Representative ...
*******
Enclosure: 0x0008000B : Added to Table
Motherboard: 0x00130009 : Added to Table
Memory: 0x00000001
DIMM 0: 0x00000001
DIMM 1: 0x00000001
DIMM 2: 0x00000001
Mezzanine: 0x00100007
I/O Module 0: 0x00000001 : Added to Table
I/O Module 1: 0x00000001 : Added to Table
Power Supply A: 0x000B0014
Power Supply B: 0x00000001
0x00130009: MCU 0540
0x00130009: CMDAPP 0504
0x00130009: CMDTABLE 0096
0x00130009: CMDBOOT 0002
0x00130009: PLX 0305
0x000B0014: PS FW 0027
Checksum valid
Relocating Data Directory Boot Service (DDBS: Rev. 05.03)...
DDBS: K10_REBOOT_DATA: Count = 1
DDBS: K10_REBOOT_DATA: State = 0
DDBS: K10_REBOOT_DATA: ForceDegradedMode = 0
DDBS: **** WARNING: SP rebooted unexpectedly before completing MiniSetup on the Utility Partition.
DDBS: MDDE (Rev 600) on disk 1
DDBS: MDDE (Rev 600) on disk 3
DDBS: MDB read from both disks.
DDBS: Chassis and disk WWN seeds match.
DDBS: First disk is valid for boot.
DDBS: Second disk is valid for boot.
Utility Partition image (0x0040000F) located at sector LBA 0x1453D802
Disk Set: 1 3
Total Sectors: 0x013BA000
Relative Sectors: 0x00000800
Calculated mirror drive geometry:
Sectors: 63
Heads: 255
Cylinders: 1287
Capacity: 20686848 sectors
Total Sectors: 0x013BA000
Relative Sectors: 0x00000800
Calculated mirror drive geometry:
Sectors: 63
Heads: 255
Cylinders: 1287
Capacity: 20686848 sectors
Stopping USB UHCI Controller...
Stopping USB UHCI Controller...
EndTime: 10/28/2018 15:33:37
int13 - RESET (1)
int13 - CHECK EXTENSIONS PRESENT (3)
int13 - CHECK EXTENSIONS PRESENT (5)
int13 - GET DRIVE PARAMETERS (Extended) (6)
int13 - EXTENDED READ (200)
int13 - EXTENDED READ (400)
int13 - EXTENDED READ (600)
int13 - READ PARAMETERS (800)
int13 - READ PARAMETERS (802)
int13 - DRIVE TYPE (803)
int13 - CHECK EXTENSIONS PRESENT (804)
int13 - GET DRIVE PARAMETERS (Extended) (805)
int13 - READ PARAMETERS (806)
int13 - EXTENDED WRITE (846)
int13 - EXTENDED WRITE (847)
int13 - EXTENDED WRITE (848)
int13 - READ PARAMETERS (964)
int13 - DRIVE TYPE (965)
int13 - CHECK EXTENSIONS PRESENT (966)
int13 - GET DRIVE PARAMETERS (Extended) (967)
int13 - READ PARAMETERS (968)
int13 - EXTENDED WRITE (997)
int13 - EXTENDED WRITE (998)
int13 - EXTENDED WRITE (999)
int13 - EXTENDED READ (1000)
int13 - EXTENDED WRITE (1012)
int13 - EXTENDED WRITE (1013)
int13 - EXTENDED WRITE (1014)
int13 - EXTENDED READ (1200)
int13 - EXTENDED READ (1400)
int13 - EXTENDED READ (1600)
int13 - EXTENDED READ (1800)
int13 - EXTENDED READ (2000)
int13 - EXTENDED READ (2200)
int13 - EXTENDED READ (2400)
int13 - EXTENDED READ (2600)
int13 - EXTENDED READ (2800)
int13 - EXTENDED READ (3000)
int13 - EXTENDED READ (3200)
int13 - EXTENDED READ (3400)
int13 - EXTENDED READ (3600)
int13 - EXTENDED READ (3800)
int13 - EXTENDED READ (4000)
It doesn't seem to ever go past this... so I cannot move on to the next steps in the solution.
any help or experience with this would be much appreciated!
-M
cdntekkie
22 Posts
1
November 5th, 2018 10:00
The system is reimaged... SPa boots up fine now.
In the end I needed to use SPb to run the utility partition to do the reimage.
kelleg
4.5K Posts
0
October 30th, 2018 14:00
Boot issues are not easy to determine. It might be a bad image or something else.
It might be easier to help with the configuration issue. What exactly is the issue that you can't solve?
glen
DELL-Sam L
Moderator
Moderator
•
6.9K Posts
0
October 31st, 2018 09:00
Hello cdntekkie,
Are you getting this error while connected to SPA or SPB? When you get that error how long do you let it sit before you manually reboot your VNX5300?
Please let us know if you have any other questions.
cdntekkie
22 Posts
0
October 31st, 2018 12:00
I tried it with SPA only and SPB removed, and with both SPs installed. No matter what I do it always stops there at the int 4000 or 4200 line.
I left it for half a day with no change.
kelleg
4.5K Posts
1
October 31st, 2018 15:00
When you say the array is working - what do you mean - does it boot up completely so that you can see the array in Unisphere?
Once the boor process has stopped it will not continue.
What are the LEDs showing on the processor?
The SP Fault LED is 2-color (amber/blue) LED located on the air dam of the SP. During a normal boot of the Flare Partition, the following blink rates will be seen:
Blink Rate
Color
Interpretation
¼ Hz
Amber
Power up and BIOS Initialization Phase
1 Hz
Amber
Extended POST Testing Phase
4 Hz
Amber
Operating System Boot Phase – Windows has not finished starting
¼ Hz
Blue
OS booted. SP likely pingable and/or accessible via PPP. NtMirror has exported the boot partition.
1 Hz
Blue
Flare driver start in progress
4 Hz
Blue
Flare driver start completed
Off
Boot success, ready for Flare IO – This is the normal case after booting. Flare and NDUMON have started. SP should be accessible via ping, Dial-Up Networking, or Remotely Anywhere.
The following blink rates are for special cases:
Blink Rate
Color
Interpretation
2 Hz
Amber
NMI button pressed
1 – 3 – 3 - 1
Amber
Bad DIMM detected (or Bad DIMM slot on the CPU Module)
On (solid)
Amber
CPU Module needs replacement
On (solid)
Blue
SP has booted in Degraded Mode
glen
cdntekkie
22 Posts
0
November 1st, 2018 06:00
I mean that it's booted up currently into "normal" mode where I can reach it via unisphere on https, it just won't seem to boot into the utility partition so I can reimage it. Is there a way to re-install the utility partition using ndu or something? I know I just upgraded the Block OE to the latest version but I didnt do anything to the utility partition.
The end result I want is for the array to be completely reimaged from scratch, if there's some way to do that from a booted system possibly through the remotelyanywhere sessions on the SPs then that would be fine too!
cdntekkie
22 Posts
0
November 1st, 2018 10:00
Can I change the array from unified to block only without a re-image? that's my goal. I have no use for unified.
I installed the utilitypartition-x.x.x.pbu file via ndu -install and then tried again and this time it's booted into the utility partition... so it must have been missing or corrupted...
I'll await your answer on the first question though, as I have 5 arrays I want to make block from unified.
kelleg
4.5K Posts
1
November 1st, 2018 10:00
No - booting into the Utility partition is a support-only operation.
If there are no faults on the array, then there is no reason to re-image the array. Any issue that is configuration related can normally be fixed without a re-image.
glen
cdntekkie
22 Posts
0
November 2nd, 2018 07:00
SPB is reloaded now to factory defaults, but SPa was stuck still. Will be working on that today.
Encry
9 Posts
0
November 16th, 2018 01:00
How long did it take to reimage your system? did you connect via the serial port on SPB to initialize the reimage on both storage processors? i think ive seen somewhere that you do the reimage with only one SP in the system....
cdntekkie
22 Posts
0
November 16th, 2018 08:00
It takes about 45 minutes, you should only have one SP seated while reimaging. They both connect to the same vault disks so once the first one is working and you can connect to it via unisphere then you can reseat the second storage processor and itll boot up and update on its own.
cdntekkie
22 Posts
0
November 21st, 2018 06:00
it wont let me pm you for some reason, shoot me your email somehow so we can stop spamming these folks lol.
Ali_Shneba
2 Posts
0
November 15th, 2021 07:00
Hi cdntekkie
May you please send me the full procedure you done because I'm facing the exact same issue mentioned while it stuck at ( int13 - EXTENDED READ (4000).
Many Thanks for your support Mate
Ali Shneba