HPE Proliant MicroServer Gen10 - Revision history

Jeremy: /* My Model */

2025-11-21T18:05:59Z

My Model

← Older revision		Revision as of 18:05, 21 November 2025
Line 197:		Line 197:
	==My Model==		==My Model==
	My system has:		My system has:
	* CPU: AMD Opteron™ X3421 Processor (2.1-3.4GHz/4 compute cores/8 graphic cores/2MB/12-35W) -- See on [http://www.cpu-world.com/CPUs/Bulldozer/AMD-Opteron%20X3000%20series%20X3421.html cpu-world] or the [https://www.amd.com/en/opteron useless marketing page]		* CPU: AMD Opteron™ X3421 Processor (2.1-3.4GHz/4 compute cores/8 graphic cores/2MB/12-35W) -- See on [http://www.cpu-world.com/CPUs/Bulldozer/AMD-Opteron%20X3000%20series%20X3421.html cpu-world] or the [https://www.amd.com/en/opteron useless marketing page]<br>The AMD Opteron X3421 APU runs at a base clock of 2.1 GHz and can boost up to 3.4 GHz.
	** CPU Core Count - 4		** CPU Core Count - 4
	** CPU Core Frequency (Base – Max Boost) - 2.1 – 3.4 GHz		** CPU Core Frequency (Base – Max Boost) - 2.1 – 3.4 GHz

Jeremy at 19:11, 18 September 2025

2025-09-18T19:11:46Z

@@ Line 4: / Line 4: @@
 ==Overview==
+* CPU
 * Expansion bays
 ** 1 x media bay (Optional (1) DVD-RW or (1) SATA SSD)
@@ Line 14: / Line 25: @@
 ** Rear: 2 x USB 3.0 ports (not blue for whatever reason), 2 x USB 2.0 ports
 ** 1 x on-board USB 2.0 port
 * Expansion Slots
 ** 1 x PCIe3 x4 (1) (low-profile only in this chassis)

Jeremy at 19:09, 18 September 2025

2025-09-18T19:09:06Z

Show changes

Jeremy: /* Keyboard Bindings at POST */

2025-09-18T19:05:11Z

Keyboard Bindings at POST

← Older revision		Revision as of 19:05, 18 September 2025
Line 10:		Line 10:
	</pre>		</pre>
	==Keyboard Bindings at POST==		==Keyboard Bindings at POST==
	~~Broadcom NetXtreme Boot Agent~~		* F2 or DEL : Enter BIOS Setup (aka "Aptio Setup")
	~~CTRL+S for configuration menu~~		* F11 : Enter Boot Menu
			* Ctrl + S : Broadcom NetXtreme Boot Agent configuration menu
	F2 or DEL : Enter Setup		* Ctrl + M : Marvell BIOS Utility

	F11 : Enter Boot Menu

	==Issues==		==Issues==
	* Does not properly handle brownouts - Gets stuck with flashing amber power LED and won't boot properly until manually power cycled		* Does not properly handle brownouts - Gets stuck with flashing amber power LED and won't boot properly until manually power cycled

Jeremy: /* Resources */

2025-09-18T19:02:58Z

Resources

← Older revision		Revision as of 19:02, 18 September 2025
Line 44:		Line 44:
	* For apt-based distros:<pre>apt-get install alien alien firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm dpkg -i firmware-smartarray-f7c07bdbbd_3.21-2.1_amd64.deb</pre>		* For apt-based distros:<pre>apt-get install alien alien firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm dpkg -i firmware-smartarray-f7c07bdbbd_3.21-2.1_amd64.deb</pre>
	* Reboot		* Reboot

			===Accessing Marvell BIOS Utility===

			The Marvell BIOS Utility is built into the embedded Marvell storage controller ROM. Use this utility to create and manage RAID virtual disks and arrays using the drives connected to the embedded storage controller. Accessing the Marvell BIOS Utility under legacy boot mode

			Procedure:
			# Reboot the server.
			# On the POST drive information screen, press Ctrl+M.

	===Updating BIOS===		===Updating BIOS===

Jeremy: /* Issues */

2025-09-17T01:58:29Z

Issues

← Older revision		Revision as of 01:58, 17 September 2025
Line 25:		Line 25:
	* No per-drive power / activity LEDs		* No per-drive power / activity LEDs
	* No door for the drive bays, need to remove the front bezel to get to the drives		* No door for the drive bays, need to remove the front bezel to get to the drives
	* I/O errors on SATA drives and/or they drop off the bus / become inaccessible, apparently due to buggy Marvell 88SE9230 SATA controller		* <font color=red>I/O errors on SATA drives and/or they drop off the bus / become inaccessible, apparently due to buggy Marvell 88SE9230 SATA controller</font>
	** Workaround: Add 'iommu=pt' to the Linux kernel parameters		** Workaround: Add 'iommu=pt' to the Linux kernel parameters
	** See: https://forum.proxmox.com/threads/proxmox-cant-recognize-hdd-on-sata.60259/		** See: https://forum.proxmox.com/threads/proxmox-cant-recognize-hdd-on-sata.60259/

Jeremy: /* HPE Proliant MicroServer Gen10 */

2025-09-17T00:49:50Z

HPE Proliant MicroServer Gen10

← Older revision		Revision as of 00:49, 17 September 2025
Line 1:		Line 1:
	=HPE Proliant MicroServer Gen10=		=HPE Proliant MicroServer Gen10=
	[[File:873830-421 1 Supersize.jpg\|128px]]<br>		[[File:873830-421 1 Supersize.jpg\|128px]]<br>

			==POST==
			<pre>
			Version 2.18.1263. Copyright (C) 2020 American Megatrends, Inc.
			BIOS Date: 02/19/2020 11:03:31 Ver: ZA10A380
			Press <F2> or <DEL> to enter setup.
			Press <F11> to enter Boot Menu.
			</pre>
	==Keyboard Bindings at POST==		==Keyboard Bindings at POST==
	Broadcom NetXtreme Boot Agent		Broadcom NetXtreme Boot Agent

Jeremy at 19:30, 16 September 2025

2025-09-16T19:30:20Z

← Older revision		Revision as of 19:30, 16 September 2025
Line 1:		Line 1:
	=HPE Proliant MicroServer Gen10=		=HPE Proliant MicroServer Gen10=
	[[File:873830-421 1 Supersize.jpg\|128px]]<br>		[[File:873830-421 1 Supersize.jpg\|128px]]<br>
			==Keyboard Bindings at POST==
			Broadcom NetXtreme Boot Agent
			CTRL+S for configuration menu

			F2 or DEL : Enter Setup

			F11 : Enter Boot Menu

	==Issues==		==Issues==
	* Does not properly handle brownouts - Gets stuck with flashing amber power LED and won't boot properly until manually power cycled		* Does not properly handle brownouts - Gets stuck with flashing amber power LED and won't boot properly until manually power cycled

Jeremy: /* Updating Storage Controller Firmware */

2021-02-06T21:32:07Z

Updating Storage Controller Firmware

← Older revision		Revision as of 21:32, 6 February 2021
Line 24:		Line 24:
	===Updating Storage Controller Firmware===		===Updating Storage Controller Firmware===
	* Go here and find the latest version for the "Firmware \| Storage Controller" download: https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_8374214d9a3a4392878c9bba59#tab2 (e.g. [https://downloads.hpe.com/pub/softlib2/software1/sc-linux-fw-array/p164515310/v177536/rpm/RPMS/x86_64/firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm]		* Go here and find the latest version for the "Firmware \| Storage Controller" download: https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_8374214d9a3a4392878c9bba59#tab2 (e.g. [https://downloads.hpe.com/pub/softlib2/software1/sc-linux-fw-array/p164515310/v177536/rpm/RPMS/x86_64/firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm]
			* Generic method without installing a package:<pre>root@daytapod1 ~/firmware $ rpm2cpio firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm \| cpio -idmv root@daytapod1 ~/firmware $ cd usr/lib/x86_64-linux-gnu/firmware-smartarray-f7c07bdbbd-3.21-1.1 root@daytapod1 ~/firmware/usr/lib/x86_64-linux-gnu/firmware-smartarray-f7c07bdbbd-3.21-1.1 $ ./setup Supplemental Update / Online ROM Flash Component for Linux (x64) - HPE Smart Array P408i-p, P408e-p, P408i-a, P408i-c, E208i-p, E208e-p, E208i-c, E208i-a, P408i-sb, P408e-m, P204i-c, P204i-b, P816i and P416ie-m SR Gen10 (3.21), searching... ============ Summary ============ Smart Component Finished Exit Status: 3 Update not attempted. All selected devices are either up-to-date or have newer versions installed.</pre>
	* For rpm-based distros:<pre>rpm -ivh firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm</pre>		* For rpm-based distros:<pre>rpm -ivh firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm</pre>
	* For apt-based distros:<pre>apt-get install alien alien firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm dpkg -i firmware-smartarray-f7c07bdbbd_3.21-2.1_amd64.deb</pre>		* For apt-based distros:<pre>apt-get install alien alien firmware-smartarray-f7c07bdbbd-3.21-1.1.x86_64.rpm dpkg -i firmware-smartarray-f7c07bdbbd_3.21-2.1_amd64.deb</pre>

Jeremy: /* Issues */

2021-02-06T21:10:19Z

Issues

← Older revision		Revision as of 21:10, 6 February 2021
Line 13:		Line 13:
	** See: https://forum.proxmox.com/threads/proxmox-cant-recognize-hdd-on-sata.60259/		** See: https://forum.proxmox.com/threads/proxmox-cant-recognize-hdd-on-sata.60259/
	** See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239		** See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239
			** Example dmesg output:<pre> [Sat Feb 6 15:00:15 2021] perf: interrupt took too long (4082 > 3936), lowering kernel.perf_event_max_sample_rate to 49000 [Sat Feb 6 15:53:26 2021] ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen [Sat Feb 6 15:53:26 2021] ata2.00: irq_stat 0x80000040, connection status changed [Sat Feb 6 15:53:26 2021] ata2: SError: { DevExch } [Sat Feb 6 15:53:26 2021] ata2.00: failed command: FLUSH CACHE EXT [Sat Feb 6 15:53:26 2021] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 29 res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) [Sat Feb 6 15:53:26 2021] ata2.00: status: { DRDY } [Sat Feb 6 15:53:26 2021] ata2: hard resetting link [Sat Feb 6 15:53:27 2021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sat Feb 6 15:53:27 2021] ata2.00: configured for UDMA/133 [Sat Feb 6 15:53:27 2021] ata2.00: retrying FLUSH 0xea Emask 0x10 [Sat Feb 6 15:53:27 2021] ata2.00: device reported invalid CHS sector 0 [Sat Feb 6 15:53:27 2021] ata2: EH complete [Sat Feb 6 15:54:46 2021] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen [Sat Feb 6 15:54:46 2021] ata4.00: irq_stat 0x80000040, connection status changed [Sat Feb 6 15:54:46 2021] ata4: SError: { DevExch } [Sat Feb 6 15:54:46 2021] ata4.00: failed command: FLUSH CACHE EXT [Sat Feb 6 15:54:46 2021] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 28 res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) [Sat Feb 6 15:54:46 2021] ata4.00: status: { DRDY } [Sat Feb 6 15:54:46 2021] ata4: hard resetting link [Sat Feb 6 15:54:47 2021] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sat Feb 6 15:54:47 2021] ata4.00: configured for UDMA/133 [Sat Feb 6 15:54:47 2021] ata4.00: retrying FLUSH 0xea Emask 0x10 [Sat Feb 6 15:54:47 2021] ata4.00: device reported invalid CHS sector 0 [Sat Feb 6 15:54:47 2021] ata4: EH complete [Sat Feb 6 15:58:41 2021] ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen [Sat Feb 6 15:58:41 2021] ata2.00: irq_stat 0x80000040, connection status changed [Sat Feb 6 15:58:41 2021] ata2: SError: { DevExch } [Sat Feb 6 15:58:41 2021] ata2.00: failed command: FLUSH CACHE EXT [Sat Feb 6 15:58:41 2021] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 9 res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) [Sat Feb 6 15:58:41 2021] ata2.00: status: { DRDY } [Sat Feb 6 15:58:41 2021] ata2: hard resetting link [Sat Feb 6 15:58:42 2021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sat Feb 6 15:58:42 2021] ata2.00: configured for UDMA/133 [Sat Feb 6 15:58:42 2021] ata2.00: retrying FLUSH 0xea Emask 0x10 [Sat Feb 6 15:58:42 2021] ata2.00: device reported invalid CHS sector 0 [Sat Feb 6 15:58:42 2021] ata2: EH complete [Sat Feb 6 16:03:34 2021] ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen [Sat Feb 6 16:03:34 2021] ata3.00: irq_stat 0x80000040, connection status changed [Sat Feb 6 16:03:34 2021] ata3: SError: { DevExch } [Sat Feb 6 16:03:34 2021] ata3.00: failed command: FLUSH CACHE EXT [Sat Feb 6 16:03:34 2021] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 9 res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) [Sat Feb 6 16:03:34 2021] ata3.00: status: { DRDY } [Sat Feb 6 16:03:34 2021] ata3: hard resetting link [Sat Feb 6 16:03:34 2021] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sat Feb 6 16:03:34 2021] ata3.00: configured for UDMA/133 [Sat Feb 6 16:03:34 2021] ata3.00: retrying FLUSH 0xea Emask 0x10 [Sat Feb 6 16:03:34 2021] ata3.00: device reported invalid CHS sector 0 [Sat Feb 6 16:03:34 2021] ata3: EH complete [Sat Feb 6 16:05:28 2021] ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen [Sat Feb 6 16:05:28 2021] ata2.00: irq_stat 0x80000040, connection status changed [Sat Feb 6 16:05:28 2021] ata2: SError: { DevExch } [Sat Feb 6 16:05:28 2021] ata2.00: failed command: FLUSH CACHE EXT [Sat Feb 6 16:05:28 2021] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 20 res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) [Sat Feb 6 16:05:28 2021] ata2.00: status: { DRDY } [Sat Feb 6 16:05:28 2021] ata2: hard resetting link [Sat Feb 6 16:05:29 2021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sat Feb 6 16:05:29 2021] ata2.00: configured for UDMA/133 [Sat Feb 6 16:05:29 2021] ata2.00: retrying FLUSH 0xea Emask 0x10 [Sat Feb 6 16:05:29 2021] ata2.00: device reported invalid CHS sector 0 [Sat Feb 6 16:05:29 2021] ata2: EH complete </pre>

	==Status==		==Status==