Re: 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

Related:

  • No Related Posts

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

Related:

  • No Related Posts

XenServer on SDX does not get upgraded to 12.1.0-105

In case of Single bundle upgrade failure, the Dom0 partition disk space Use% gets stuck at 100%.

This is sticky condition and can only be corrected by rebooting the SDX appliance.

Once the system reboot is complete, the disk Use% should drop back to normal.

A check can be performed by the df / command as described in previous section.

Loss of space can be attributed to the amount of logs accumulated in the /var/log directory on the file system.

Bringing down the Use% to 72% will allow the SBU to succeed, the following steps have to be performed –

1> Reboot the system to get it out of 100% sticky mode

2> Run the following command on XS/Dom0 console to cap the log rotate to 200 Mb instead of 500 Mb

sed -i.bak ‘s/500/200/’ /opt/xensource/bin/delete_old_logs_by_space

3> Wait for minute or so for log rotate to kick in an do the necessary clean up and reduce the accumulated logs to around 200 Mb.

4> Verify that the XS/Dom0 partition available disk space Use% is less than 72% for upgrade to succeed.

5> Run the SBU again.

Related:

Cyberattackers are Knocking; Secure the Front Door with BIOS Verification

EMC logo


illustration - digital padlock

As Advanced Persistent Threats Rise, Dell’s BIOS Verification Approach Is the Secure Way Forward Everyone can relate to the experience of booting up a computer – hitting the power button, hearing the startup sound, and ultimately seeing the home screen appear. But even some tech professionals may not be aware of what’s happening under the surface. When the CPU is booted up, the first thing it does is communicate with the flash memory on the motherboard to fetch a piece of code called the Basic Input Output System (BIOS). The BIOS’s job is to initialize the motherboard components, chipset and … READ MORE



ENCLOSURE:https://blog.dellemc.com/uploads/2018/05/Dell-BIOs-blog-600×356.jpg

Update your feed preferences


   

   


   


   

submit to reddit
   

Related:

PCI Attached SD Cards Inserted During Active ICA Sessions Are Not Redirected

What difference does this make when inserting an SD Card during an existing Citrix session?

Citrix monitors the USB Bus all during the session. Changes, as determined by policy, are redirected to the existing session.

The PCI bus, (or PCIe Bus) is not monitored. Additions or removals to the PCI Bus are not redirected to an existing session.

SD Cards can be attached to the USB bus or the PCI bus. Newer hardware uses the faster PCI Bus for the built-in SD Card reader.

Related:

NetScaler Displays “Unable to load a kernel” When Booting After a Firmware Upgrade

Note: Please contact your NetScaler Admin or Citrix Support Contact for the below mentioned steps.

OK prompt shown is from the FreeBSD Bootloader.

The most likely cause of this issue is that the NetScaler kernel file is missing from /flash. Because the firmware upgrade was installed from /var, a copy of the kernel file will exist on the hard drive. To resolve this issue, you can attempt to temporarily boot from the copy of the kernel file that resides in /var. Once booted, you can reinstall the NetScaler firmware using the standard procedure.

  1. Determine the device name of the /var partition on the hard drive, by referring to CTX124609.

  2. You can display the available devices using the following command from the OK prompt:​​​

    lsdev -v

  3. The FreeBSD bootloader uses a different naming convention than the actual operating system. To determine the proper naming convention for the bootloader, use the following procedure:

    1. Determine which physical drive contains /var. If lsdev -v shows 2 disk drives, disk0 will be flash and disk1 will be the hard drive. If only 1 drive is listed, disk0 will be the hard drive/SSD and there is no separate flash drive. You are interested in the hard drive.

    2. From CTX124609, determine the device name for the /var partition.

    3. The naming convention for the bootloader is in the form of disk{n}d1{part}:

    4. For example, on an MPX-8200, the device name for the /var partition is /dev/ad4s1e. lsdev -v shows that there is only one disk drive (disk0). This means that the proper name for the /var partition is disk0s1e:

  4. The NetScaler kernel file is named ns-{version}-{build}.gz. For instance, ns-10.5-55.8.gz.

  5. Use the ls command to locate the NetScaler kernel file on the /var partition of the hard drive. Note that there is no cd command, so you must specify the entire path as part of the command.

    For instance:

    ls disk0s1e:/nsinstall/<firmware folder name>/ns-10.5-55.8-nc

  6. Once you locate a suitable NetScaler kernel file to load, load it as follows (leave off the .gz extension)

    set currdev=disk0s1e:

    unload

    load disk0s1e:/nsinstall/<firmware folder name>/ns-10.5-55.8

  7. If the kernel loads successfully, try to boot the kernel by typing boot at OK prompt.

  8. After the NetScaler boots, re-run the firmware upgrade procedure and prior to rebooting again, verify that /flash contains the proper kernel file.

Related: