ML30 Gen10 post code 0034

[BunnyPon]

I decide to reboot the Hexagon, as people are wont to do after updating the linux kernel and what not. only it grinds to a halt with just the "HPE Proliant" and the green bar maybe 1 block worth.

The next time, it stalls at POST CODE 0033 for the longest time.

Stuck at 0033

That missing check box on "Smart Array" does not look good, does it? This device doesn't really matter to me too much as it's not really being used for anything except to provide 8 SATA ports for those drives. (Good old 04-HD Max but let's not go there today.)

Then if I am lucky, it gets a little bit Now after a few attempts it seems to be at POST CODE 0034

Of course, the AHS logs are useless because AHSV is dead and the replacement has never heard of the ML30. 

[BunnyPon]

(update 1)

For reasons unknown, I suspect some USB device is causing it to lose its marble, but WHICH ONE and how do we find out.

So, if anyone can tell me how to identify which device is causing post to hang at 0033 or 0034, please let me know. Ideally without doing a pile of reboots.

Removing everything to get past post, then plugging them in gets me:

[   37.440516] usb 2-4.4: new high-speed USB device number 8 using xhci_hcd
[   37.590082] usb 2-4.4: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=32.98
[   37.590094] usb 2-4.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   37.590100] usb 2-4.4: Product: USB2.0 Hub
[   37.591521] hub 2-4.4:1.0: USB hub found
[   37.591984] hub 2-4.4:1.0: 4 ports detected
[   37.880534] usb 2-4.4.1: new high-speed USB device number 9 using xhci_hcd
[   43.148568] usb 2-4.4.1: device descriptor read/64, error -110
[   58.760660] usb 2-4.4.1: device descriptor read/64, error -110
[   58.948639] usb 2-4.4.1: new high-speed USB device number 10 using xhci_hcd
[   64.136656] usb 2-4.4.1: device descriptor read/64, error -110
[   79.756723] usb 2-4.4.1: device descriptor read/64, error -110
[   79.869063] usb 2-4.4-port1: attempt power cycle

    |__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:2817 VIA Labs, Inc.
        |__ Port 4: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
            ID 05e3:0610 Genesys Logic, Inc. Hub
            |__ Port 4: Dev 17, If 0, Class=Vendor Specific Class, Driver=, 480M
                ID 3275:0080 VidzMedia Pte Ltd
            |__ Port 2: Dev 15, If 0, Class=Vendor Specific Class, Driver=smsusb, 480M
                ID 3275:0080 VidzMedia Pte Ltd
            |__ Port 3: Dev 16, If 0, Class=Vendor Specific Class, Driver=, 480M
                ID 3275:0080 VidzMedia Pte Ltd

That appears to be a PLEX PX4UD.

Although I find it worrying that a perfectly normal device can totally stall your server.

[TVVJ]

Hello,

Please refer to this community post and see if it helps.

Regards,

[BunnyPon]

I have got as far as determining it is a USB device. but which one and why. It seems that the bios can output debug messages to a serial port, so I can experiment with that later. Current suspect is the PX4UD being badly behaved, but...

What is worrying though is that means that if Tom leaves a USB device plugged in your server, **bleep** reboots it for a BIOS update or something remotely, someone has to send Harry all the way to the datacentre, or possibly use the HP 24hr onsite support for a stupid device error.

Is there a way to make POST just complain and keep going, because this stall could happen to anyone. and as you can see from the images. NO CLUES and the immediate suspect would be the smart array has died since the check-mark never shows up.

[shiva_jr]

Hi @BunnyPon ,
    Please follow these steps and let us know.
a. Power off the system
b. Check all the USB ports are not connected to any device (External - 4 ports and Internal - 1 port)
     Please refer motherboard diagram in quickspecs for internal USB.
c. Perform the power flush from the system.
   Hold the power button for 10-20 seconds continously so that power can be dischanrged from motherboard
d. Remove extra components connected (RAM, HDD, HBAs etc) and run with minimal hardware configuration.
e. start the system and verify it works or not.
f. Please check in iLO events if iLO port is configured.
Regards,
Shiva_JR

[BunnyPon]

Under (B) I have a sneaking suspicion that a POWERED USB device is the culprit.

(I also stand corrected, it's not the PX4, its  PX-Q1UD)

https://www.plex-net.co.jp/product/px-q1ud/

This device.

It still shouldn't bring your server to a grinding halt.

More testing is called for, during my copious free time waiting for HPE to update the mcp version of ams for the version that doesn't crash on device removal.

[shiva_jr]

Hi @BunnyPon ,
   If the USB device PX-Q1UD is connected, please remove and boot. Still the issue, better to contact the HPE support.

Regards,
Shiva_JR