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

Re: insight iq  how to  collect the information of the contents ( files) of a specific directory

My question is how to collect the information in a specific directory with the cli of insight IQ

I can collect the directories with the IIQ cli

iiq_data_export fsa export -c clustername –data-module directories -o 7318 –name <file>

output CSV:

path[directory:/ifs/],dir_cnt (count),file_cnt (count),ads_cnt,other_cnt (count),log_size_sum (bytes),phys_size_sum (bytes),log_size_sum_overflow,report_date: 1537042326

/ifs/data,4092765,123934912,0,0,1097588028518359,1332028348377088,0

/ifs/home,12,68,0,0,94902,2095104,0

/ifs/.isilon,3,22,0,0,60217,564224,0

/ifs/data/files,1,7,0,0,17907,184832,0

The –data-module directories generates an overview of the files

in the manual i can only find the data-modules option

Directories directories

File Count by Logical Size file_count_by_logical_size

File Count by Last Modified file_count_by_modified_time

File Count by Physical Size file_count_by_physical_size

Top Directories top_directories

Top Files top_files

Now i want to have an export of the directory /ifs/data/files exported to csv format

I can do report in the gui also under file system analytics with the download as csv

Can someone hint me the syntax

Thanks

Related:

  • No Related Posts

How Big is the 4.x User Layer Disk, and How Can You Change That?

By default, the User Layer is 10GB.

If you have set User Quotas on your file share, then we will size the User Layer disk to be equal to your user quote. We assume that the share is specific to layering, and the only thing a user is going to be writing to it is their User Disk. So we assume that any user-specific quota is how big you want to make the User Disk. This supersedes the default. Setting the file share quota is the standard, preferred method for setting the User Layer size.

There are three registry keys in your image which govern this behavior. If you want to modify them, you can do it with a GPO or a layer. I suspect the best place to put it is in the Platform Layer, but you could put it in the OS or App Layers too.

[HKEY_LOCAL_MACHINESoftwareUnideskUlayer]

“UseQuotaIfAvailable” String Value

Values: “True” (Default), “False”

True to enable discovery and use of quotas. False to disable.

“DefaultUserLayerSizeInGb” DWord Value

The size of the user layer in GB without quotas (E.g. 5, 10, 23, etc.)

When not specified, the default is 10.

“QuotaQuerySleepMS” DWord Value

The number of milliseconds to wait after creating the directory for the user layer before checking to see if it has a quota. This is necessary to give some quota systems time to apply the quota to the new directory (FSRM requires this).

When not specified the default is 1000.

You’ll probably never use the last one, but try it if you are sure you have set a quota and it seems to be not working.

Expanding the User Layer

If you already have a User Layer disk and you want to expand it, you just need to expand the VHD itself, and then expand the filesystem on it. PowerShell on Hyper-V servers, for instance, has a CmdLet named “resize-vhd” which will take a local filename and a total number of bytes and resize your disk. For some reason, resize-vhd is only available on Hyper-V servers, but you just need to enable the Role in your server to have access to the cmdlet. Obviously you can only do this while the user is not logged in and not using the disk. Otherwise, any third-party VHD-resizing tool will work.

Once you resize the VHD, run Disk Management and expand the filesystem in the disk to fill the extra space, and that space will be reflected when the user logs in. You can use the Attach VHD function in Disk Management to expand the filesystem after you expand it, or you can let the user log back in, run Disk Management themselves, and expand the filesystem themselves. It will be the only disk with free space at the end. The space will become immediately available.

Note: resize-vhd command can be run from Hyper-V only. You will need a Hyper-V server to run the command, or you can temporarily add Hyper-V role to a machine, then run the command.

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

Exclusions – Wildcards

I need a solution

Hi,

It’s been ages since I last needed to look at this. Microsoft have recommendations for exclusions for DFSR:

<drive>:system volume informationDFSR

$db_normal$
FileIDTable_2
SimilarityTable_2

<drive>:system volume informationDFSRdatabase_<guid>

$db_dirty$
Dfsr.db
Fsr.chk
> *.log <
> Fsr*.jrs <
Tmp.edb

<drive>:system volume informationDFSRconfig

> *.xml <

<drive>:<replicated folder>dfsrprivatestaging*

> *.frx <

These are mostly easy. What about the one inside > < brackets? Also what if the System Volume Information is on different drives between servers?

Thanks

0

Related:

  • No Related Posts

7023289: Updating Verastream Host Integrator 7.7 to use Open JDK

InstallJava

Install thedesired version of the JDK that you intend to use, into the desired directory,for example, in

install-dirAttachmateVerastreamHostIntegratorJava

Alongsidethe OEM version of Java that shipped with VHI.

Note: VHI has been tested with JDK8 binaries from AdoptOpenJDK and Azul Zulu. We do not advise moving to JDK9 or higher at this time. JDK8 is in long term support (LTS), and should be fully supported until October 2020. For stability, we recommend enterprise customers staying with LTS releases. A future version of VHI will be designed for JDK11, which is the next planned LTS release for OpenJDK.

Note: The …/jre/lib/security/cacerts file provided with AdoptOpenJDK JDK8 is empty; thus, the trust store is empty. The cacerts file must be replaced with one containing root certificates in order for VHI to operate. If necessary, you can copy cacerts from a recent version of JDK9 or JDK10 from AdoptOpenJDK, which contains a non-empty file. Compare the file size, or use keytool to look inside using the command:

keytool -list -v –keystore cacerts



(hit enter when prompted for a password).

ConfigureJava serialization filters

Thefollowing changes to the serialization filters must be configured to adhere tosecurity guidelines.

Open in atext editor:

install-dirattachmateverastreamjavanew-jdkjrelibsecurityjava.security

(where new-jdkcorresponds to the directory containing your newly installed JDK)

Copy andpaste the following text at the end of the document (insert a linefeed beforeand after):

jdk.serialFilter=!org.apache.commons.collections.functors.InvokerTransformer;*

sun.rmi.registry.registryFilter=!org.apache.commons.collections.functors.InvokerTransformer;*

sun.rmi.transport.dgcFilter=

java.rmi.server.ObjID;

java.rmi.server.UID;

java.rmi.dgc.VMID;

java.rmi.dgc.Lease;

maxdepth=2147483647;

maxarray=2147483647;

maxrefs=2147483647;

maxbytes=2147483647

Note:Current JDK versions contain security fixes that address long-standing Javaobject serialization vulnerabilities. There are serious side-effects to thosechanges which are described here:

https://dzone.com/articles/a-first-look-into-javas-new-serialization-filterin

As thearticle states, creating a whitelist, while theoretically possible, isextremely time-consuming and failure-prone, whereas creating a blacklist isprone to zero-day attacks (although it may be beneficial to add new threats tothe blacklist as we learn of them – as virus scanners do).

org.apache.commons.collections.functors.InvokerTransformeris a knownserialization attack vector. Research into finding additional classes toinclude in the blacklist for this filter is ongoing. Research is alsocontinuing on the creation of a reliable and secure whitelist for this filter.This technical note will be updated when this information is available.

Point VHIat your new JDK

Stop allVHI services

Verastream Host Emulator

Verastream Host Integrator Log Manager

Verastream Host Integrator Session Server

Verastream Host Integrator Web Server

Verastream Management Server

SeeStarting and Stopping Services in the VHI documentation: http://docs2.attachmate.com/verastream/vhi/7.7/en/index.jsp?topic=%2Fcom.attachmate.vhi.help%2Fhtml%2Fgettingstarted%2Fvhi_start_stop_services.xhtml

Create asymbolic link

Rename thedirectory containing the OEM JDK that shipped with VHI, e.g.,

Install-dirAttachmateVerastreamjavajdk1.8.0_162-64

To

Install-dirAttachmateVerastreamjavajdk1.8.0_162-64.bkp

Next,create a symbolic link (directory junction) that points to your newly installedJDK. Name this link jdk1.8.0_162-64 (or the name of the directory of the OEM JDK youare replacing) (Note: futureversions of VHI will improve the directory naming scheme to help reduceconfusion.)

Open aconsole in the …AttachmateVerastreamjava directory, and usethe command,

Windows Console: mklink /j old-jdk new-jdk(/j creates a directory junction)

Windows Power Shell: New-Item -ItemType Junction -Path old-jdk -Value new-jdk

Linux: ln -sn new-jdk old-jdk (-s := symboliclink; -n := no-dereference)

Where

new-jdkrefers to the name of the directory containing your newly installedJDK.

old-jdkrefers to the nameof the directory containing the originally installed JDK.

Thesymbolic link should point to the directory containing the bin, jre and libdirectories.

Start allVHI services

Verastream Host Emulator

Verastream Host Integrator Log Manager

Verastream Host Integrator Session Server

Verastream Host Integrator Web Server

Verastream Management Server

Verify allservices are running, and VHI operation is normal.

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