Admin Partitions | Partition ID Gets Skipped

Q: On “show ns partition” output, we sometimes see partition ID assignment is not sequential / IDs getting skipped. Is this a problem ?

A:Subject to memory availability one can create up to 511 admin partitions manually.

A partition ID is assigned to each partition upon creation and is used for internal tracking (this is not a user defined parameter).

Partition IDs are assigned from 1 to 511, however if there is an error (for any reason) during partition creation or a partition is deleted then partitioned will be skipped, these are reused later once 511 is reached.

Example:

Add partition parta … success | partition:ID1

Add partition partb … success | partition:ID2

Add partition partc… failed | partition:ID3 (Skipped)

Add partition partd… success | partition:ID4


//Assume the one below is 510th partition created it will be assigned partitionID:511

Add partition partx success | partitionID:511

//So, the actual 511th partition will now be assigned partitionID:3 as that was skipped previously

Add partition party .. will be assigned partitionID3

Q: Do these skipped partition IDs have any resource consumption until freed / reused.

A:Resources are only consumed by active partitions, skipped partition IDs do not have any bearing on resource consumption.


Example:

==

In the following output partitionID 1 to 30 and 34 is skipped (for any reason)

> show ns partition

1) Name: a

Partition ID: 31

Max BW : 10240 Kbps

Max Conn :1024 Max Mem: 700 MB

2) Name: b

Partition ID: 32

Max BW : 10240 Kbps

Max Conn :1024 Max Mem: 700 MB

3) Name: c

Partition ID: 33

Max BW : 10240 Kbps

Max Conn :1024 Max Mem: 700 MB

4) Name: d

Partition ID: 35

Max BW : 10240 Kbps

Max Conn :1024 Max Mem: 5 MB

Done

>

Now if you check using nsconmsg you can see memory use is only by the active partitions, no memory is in use for skipped partition IDs (1-30 or 34)

> shell

Copyright (c) 1992-2013 The FreeBSD Project.

Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

The Regents of the University of California. All rights reserved.

root@ns# nsconmsg -d finalstatswt0 -K /var/nslog/newnslog -g mem_cur_usedsize | grep partition

3 0 3193912 mem_cur_usedsize partition_ctx(a) (PART-31)

5 0 3193912 mem_cur_usedsize partition_ctx(b) (PART-32)

7 0 3193912 mem_cur_usedsize partition_ctx(c) (PART-33)

9 0 3193912 mem_cur_usedsize partition_ctx(d) (PART-35)

root@ns#

Related:

  • No Related Posts

Reserved and recovery getting drive letters

I need a solution

So win 10 creates two hidden partitions when you install it, a 499 reserved and 500 mb recovery, these don’t have drive letters which is great, but when I capture the image and then redeploy it I’m getting three drives C: E and F, C is the main one and e and f are the drives above. Is there anyway to keep these drives from getting letters after ghost restores them? We use Altiris 8.5 but that forum is pretty much dead and the 1st level support person I had said I need to delete those partitions from my win 10 image but that seems risky from what I have read and if we do in place upgrades down the road.

0

Related:

  • No Related Posts

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: