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

BSOD after deploying sysprepped image

I need a solution

I’ve been having periodic issues deploying sysprepped images with GSS 3 (we’re currently on 3.2 RU6) but managed to get it working on Windows 10 1709 and 1803 – until today. The problem has surfaced again and I think I can trace it to GSS writing files to the wrong partition. I have a deployment task for a sysprepped image with a custom unattend file that fails randomly; sometimes on certain models, and other times on models that work 99% of the time. The result is after laying down the image, it reboots to a blue screen claiming that the registry is corrupt. When I boot the machine with a recovery USB, I open the command line and run notepad. I can see that the System Reserved drive is labelled C, and in that drive is a “windows” directory, with a “panther” subdirectory (note that they aren’t capitalized) that contains our unattend file named unattend.xml. I assume this is GSS copying our custom unnattend file to C:windowspanther – except it appears that GSS (or WinPE) thinks the reserved partition is the system drive and writes the unattend file to it, causing corruption and ultimately the blue screen on boot. Another example of this is that I have a script that will write to the WindowsSetupScriptssetupcomplete.cmd file in order to install the DAgent on first boot (for portability, since we have multiple GSS servers in our environment), except I have to specify that drive as D: for WinPE to write to the correct partition.

REM Point DAgent to correct ghost server
md D:WINDOWSSETUPSCRIPTS
ECHO msiexec /i C:DAgentdagent_x64.msi /qn server_tcp_addr=%DSSERVER% server_tcp_port=402 >> D:WINDOWSSETUPSCRIPTSsetupcomplete.cmd

Is there an easy way to mitigate this? I don’t know of a way to either force WinPE to see the correct drive letters, or to specify where to copy the unattend file since WinPE sees the System Reserve partition as the C drive.

0

Related:

  • No Related Posts

Ghost not deploying image but no logs

I need a solution

I have a decent number of machiens that ghost seems to fail at but it is not creating the ghost error logs in PE.

This is the error shown in the console

ErrorMessage: Exception has occured in File Tcube_ClientImageDeploy.cpp at Line No 978. Type of exception is ClientImageDeployException. Error Description is Child Process returned an error. The exit code from process is 3. Value of Windows error code = 183 and message is Cannot create a file when that file already exists.

I have tried gdisk64 to delete partitions in case its somethign with that and that gives me the error regardless of what gdisk64 parameter I try

gdisk64 (W) fixed disk has partitions) that extend past the end of the disk

I have also tried diskpart and get errors there too.  I know we can’t all of a sudden have 100 drive failures, so any help is appreciated as they do pass the internal computer drive tests.

0

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

Isilon OneFS 8.0: Cannot install firmware package: /var/patch/backup: is not a directory

Article Number: 500573 Article Version: 9 Article Type: Break Fix



Isilon OneFS 8.0,Isilon OneFS 8.1

During firmware package installation, installation would not complete, and output such as:

# isi upgrade patches list

Patch Name Description Status

———————————————————————————————————————————-

IsiFw_Package_v9.3.5 Package Name : IsiFw Package v9.3.5 2017-04-04 To… Installing

would show Status as Installing indefinitely.

Look at last few lines from /var/log/isi_pkg of each node, and you should see the following error:

# isi_for_array -s ‘tail -50 /var/log/isi_pkg’

………

2017-05-28T13:31:56-05:00 <3.6> node-1 isi_pkg[16306]: Starting task for request ‘INSTALL’, task ‘INSTALL_INIT’, hash ‘2693c810637d37a02ee9cb57a9d01d3d’

2017-05-28T13:31:59-05:00 <3.6> node-1 isi_pkg[16306]: Running requirements file first for IsiFw_Package_v9.3.5..

2017-05-28T13:31:59-05:00 <3.3> node-1 isi_pkg[16306]: /var/patch/backup: is not a directory.

2017-05-28T13:31:59-05:00 <3.3> node-1 isi_pkg[16306]: install_init: Task encountered unknown failures


This issue could happen for any of the firmware packages such as IsiFw_Package_v9.3.5.tar or IsiFw_Package_v10.0.1.tar

Partition mounted under /var requires at least 40% of free disk space to allow installation of large patch such as firmware package. If you don’t have enough free disk space under /var, the node would fail the installation with error:

/var/patch/backup: is not a directory

Reduce disk usage under /var. It is usually /var/log directory that would contain large files that might need to be truncated. To determine that:

1. Determine which node does not have at least 40% (Capacity should be 60% or less) free space under /var

# isi_for_array -s ‘df -h /var’

2. ssh to the node as root user that does not have enough free space under /var

# cd /var/log

# du ./* | sort -n -r | head -n 10

3. Make a backup directory within /ifs/data/Isilon_Support/ to store a backup of the files that will be truncated:

# mkdir /ifs/data/Isilon_Support/Node<node number>_VarLog_Backup

4. Copy the files that you will be truncating to the new backup directory:

# cp <filename> /ifs/data/Isilon_Support/Node<node number>_VarLog_Backup

5. The output of step 2 would give you top 10 largest files under /var/log. You can truncate the files using command:

# truncate -s 0 <filename>

6. Check partition again to make sure you have freed up at least 40% (Capacity should be 60% or less) of disk space under /var:

# isi_for_array -s ‘df -h /var’

7. Once you have freed up enough capacity, retry the failed upgrade via command:

# isi upgrade retry-last-action –nodes=<lnn of failed node>

8. Allow 30min to complete upgrade process, and check to make sure the package is showing Installed for Status:

# isi upgrade patches list

Patch Name Description Status

——————————————————————————————————————

IsiFw_Package_v10.0.1 Package Name : IsiFw Package v10.0.1 2017-05-02 T… Installed

If you don’t know if the files can be safely truncated, or if there are no large files under /var/log but /var partition is still too full, or retry-last-action does not complete patch installation, please engage Technical Support for assistance and refer this KB as reference.

Related:

  • No Related Posts

ScaleIO: Cannot install Windows 2012 on VxRack Node hardware

Article Number: 493737 Article Version: 3 Article Type: Break Fix



ScaleIO 1.32.1,ScaleIO 1.32.2,ScaleIO 1.32.3,ScaleIO 1.32.4,ScaleIO 1.32.5,ScaleIO 1.32.6,ScaleIO 2.0,ScaleIO 2.0.0,ScaleIO 2.0.0.1,ScaleIO 2.0.0.2,ScaleIO 2.0.0.3,ScaleIO 2.0.1,ScaleIO 2.0.1.1

Issue Description

Unable to install Windows 2012 R2 on VxRack Node hardware

Scenario

Customer is following the SolVe Desktop procedures to install Windows 2012 R2 on VxRack Node hardware and is failing at the “Windows Setup” screen.

Symptoms

Upon choosing which partition to install Windows to in the “Windows Setup” screen and hitting the “Next” button, an error will pop up:

“Windows cannot be installed to this disk. This computer’s hardware may not

support booting to this disk . Ensure that the disk’s controller is enabled in the

computer’s BIOS menu.”

User-added image

Impact

Cannot install Windows OS to the VxRack Node hardware, upon which ScaleIO will be installed.

Windows will not recognize the UEFI disk as bootable.

Workaround

If the SolVe Desktop procedures have been followed precisely, the workaround is to make the boot disk use legacy mode.

In the BIOS of the VxRack node, change the following settings:

  1. Advanced -> CSM Configuration -> Storage -> Legacy
  2. Boot -> Boot Mode -> Legacy
  3. Boot -> Boot Option #1 -> Hard Disk:(Bus 03 Dev 00)PCI Raid Adapter

    This can be manipulated under “Boot -> Hard Disk Drive BBS Priorities

If step #3 shows the satadom, make sure that the virtual drive has already been created. If it has, reboot the host one more time to show the hard drive correctly in step #3.

This will allow Windows to see the disk as bootable and then successfully install Windows 2012 on the hard drive.

Impacted versions

v1.32.x

v 2.0.x

Fixed in version

N/A

Related:

Unisphere for VMAX: Backups fail with Compress Data is Corrupt errors

Article Number: 501444 Article Version: 3 Article Type: Break Fix



Unisphere for VMAX 8.3,Unisphere for VMAX

Cannot perform Unisphere for VMAX backup for array.

The disk space was low on the backup partition.

None

Clear some of the older backup files, so that there was room on the partition.

The smas.log has the following entry:

<date> <time> ERROR [stderr] (EJB default - 5) psql:<install_path>/SMAS/backup/SPA/<SID>_<DATE>/<SID>_historical_backup.sql:133: ERROR: compressed data is corruptThe postgresql.log file has the following entry:<date> <time> GMT:::1(61658):spa@spa:[11792]:ERROR: compressed data is corrupt<date> <time> GMT:::1(61658):spa@spa:[11792]:STATEMENT: COPY( SELECT <arguments> FROM dwf_storagegroup ) TO '<install_path>\SMAS\backup\SPA\<SID>_<DATE>\<SID>_dwf_storagegroup.sql' DELIMITER ','; 

Related:

Converting Linux VMDK to GHO file, Error 652

I need a solution

Hi. I’m following the instructions found here to create a ghost file from a Linux virtual machine. Unfortunately I’m encountering some issues. In the command prompt, I get the message “ABORT: 62, Attempted to access an inconsistent Linux partition. Operation aborted at user request”

It’s Ubuntu 18.04, file system is ext4

Any help appreciated. Thanks.

0

Related:

Re: Symmetrix VMAX & VMAX3 Logical Structure

Hello,

Basically I wanted to confirm my understanding of the logical structure within the Symmetrix VMAX and VMAX storage arrays.

Correct me if I’m wrong, I’ll go top to bottom.

1) Disk Group – A group of identical disks in terms of technology, size, speed etc. *VMAX All-Flash has only one Disk Group.

2) RAID Group – A group of disks from the disk group that have the same RAID protection. *Question: Can I have more than on RG per DG or is it always 1:1 ?

3) Data Device (TDAT) – A logical slice of a physical disk in a particular RAID Group.

4) TDEV – A logical slice of a TDAT, smallest logical device in the storage array. *Question: I’ve read that TDEVs are comprised of Hypers which are slices of a physical disk. How does that work exactly?

Now, regarding provisioning and FAST and VP Tiers:

-A meta device is comprised of several TDEVs and provisioned to a host as a LUN. *VMAX3 does not have metas.

-A thin pool is comprised of Data Devices (TDATs). *Question: Can there be several pools per RAID GROUP or is it always 1:1?

-Are VP Tiers based on Thin Pools, meaning every thin pool is a separate VP Tier and FAST moves data between them?

Summary of all questions just in case:

1) Can I have more than on RG per DG or is it always 1:1?

2) I’ve read that TDEVs are comprised of Hypers which are slices of a physical disk. How does that work exactly and what are Hypers exactly in technical terms (I’ve seen several different explanations)?

3) Can there be several thin pools per RAID GROUP or is it always 1:1?

4) Are VP Tiers based on Thin Pools, meaning every thin pool is a separate VP Tier and FAST moves data between them?

Related: