HPE Proliant Servers

    Weird, I thought JanN had tried ACHI mode and it was not working. Maybe he has issue with his machine or there is something to disconnecting the power? It seems once set in bios it should just work period.

    Zitat von tekkb

    Weird, I thought JanN had tried ACHI mode and it was not working. Maybe he has issue with his machine or there is something to disconnecting the power? It seems once set in bios it should just work period.


    Yeah in the other forum thread I linked there is mention of an iLo issue when you upgrade- it won't boot sd card. I don't know anything about that issue but the people there seem to know the server inside out.

    Zitat von Spy Alelo

    So your SSD is not booting when the controller is on AHCI mode? I assume it is on bay one. I'll have to test that on Monday when I come back to the lab. I'm sorry guys, but I've been so busy that I hardly have time for anything anymore.


    Can you try installing a regular hard drive (any size will do) and replicate the issue? I want to see if this is an issue with SSDs only.


    Hi guys,


    i made some cross-testing with the following devices:


    Microserver Gen8 G1610T, latest BIOS, Bootblock 02/04/2012
    Microserver Gen7 N54L,
    two SSD Cruzial_CT100MXSSD1 (Firmware MU01), one with OMV 1.19 installed on Microserver G8, one with OMV 1.19 installed on MIcroserver G7,
    SSD KingFast F8 120 GB with OMV 1.19 installed on Microserver G7,
    2,5" HDD Seagate Momentus 60 GB with OMV 1.19 installed on Microserver G7.


    As i wrote, the G8 G1610T is not (cold-)booting from the Cruzial-SSD (in port 1) when the Controller is set to AHCI SATA Mode, but it boots from the same SSD, when the controller ist set to SATA Legacy Mode. It is the same with both Cruzial SSDs: The Cruzial SSDs weren't recognised by the G8-Microservers contoller (HP AHCI SATA Controller 0.90) during initialization.


    The G8 G1610T boots from the Seagate-HDD, and it also boots from the KingFast-SSD in port 1 with the controller set to SATA AHCI-Mode.


    The Microserver G7 N54L boots from all the above listed drives with its controller set to AHCI-Mode.


    Conclusion:
    The Microserver G8 SATA-Controller Firmware for AHCI-mode has a massive problem with the Cruzial MX100 SSDs.
    Also strange: The SmartStorage Diagnostic-App reports more than 6000 hours of operation and a worn out drive for the nearly brandnew Cruzial-SSD:


    ADU Version 2.0.22.0
    Diagnostic Module Version 8.0.22.0
    Time Generated Sunday June 14, 2015 7:50:30AM


    Device Summary:
    6 Series/C200 Series Chipset Family SATA AHCI Controller


    Consolidated Error Report:


    Report for 6 Series/C200 Series Chipset Family SATA AHCI Controller
    -------------------------------------------------------------------


    6 Series/C200 Series Chipset Family SATA AHCI Controller : Host Bus Adapter Info


    Marketing Name 6 Series/C200 Series Chipset Family SATA AHCI Controller
    Adapter Type Generic HBA
    PCI Bus 0
    PCI Device 31
    PCI Function 2
    PCI Subsystem ID 272380685


    6 Series/C200 Series Chipset Family SATA AHCI Controller : 256 GB SATA SSD (SN: 14510E1E9D42) : Physical Drive Info


    Interface SATA_SSD
    WWID 500A07510E1E9D42
    Drive Model Crucial_CT256MX100SSD1
    Serial Number 14510E1E9D42
    Firmware Revision MU01
    Total Blocks 500118192


    6 Series/C200 Series Chipset Family SATA AHCI Controller : 256 GB SATA SSD (SN: 14510E1E9D42) : SmartSSD Wear Gauge


    Supported TRUE
    Log Full TRUE
    Utilization 655.350000
    Remaining Days Until Wearout 0
    Power On Hours 6399
    Has 56 Day Warning TRUE
    Has Utilization Warning 2PERCENT


    6 Series/C200 Series Chipset Family SATA AHCI Controller : 256 GB SATA SSD (SN: 14510E1E9D42) : Workload Information


    Power-on Hours 6399
    Total LBA Read 18446744073709551615
    Total LBA Written 18446744073709551615
    Workload Rating (TB/Yr) 65535
    Month(s) of Operation 8.765753
    Total Bytes Read (TB) 18446744.073710
    Total Bytes Written (TB) 18446744.073710
    Total Combined Read/Write Bytes (TB) 18446744.073710
    Workload Rate (TB/Month) 2104410.560058
    Projected Rate (TB/Year) 25252926.720690
    SSD Usage Remaining (%) -555.35



    ADU Version 2.0.22.0
    Diagnostic Module Version 8.0.22.0
    Time Generated Sunday June 14, 2015 7:53:22AM


    Device Summary:
    6 Series/C200 Series Chipset Family SATA AHCI Controller


    Report for 6 Series/C200 Series Chipset Family SATA AHCI Controller
    -------------------------------------------------------------------


    6 Series/C200 Series Chipset Family SATA AHCI Controller : 256 GB SATA SSD (SN: 14510E1E9D42) : Physical Drive Info


    Interface SATA_SSD
    WWID 500A07510E1E9D42
    Drive Model Crucial_CT256MX100SSD1
    Serial Number 14510E1E9D42
    Firmware Revision MU01
    Total Blocks 500118192


    6 Series/C200 Series Chipset Family SATA AHCI Controller : 256 GB SATA SSD (SN: 14510E1E9D42) : SmartSSD Wear Gauge


    Supported TRUE
    Log Full TRUE
    Utilization 655.350000
    Remaining Days Until Wearout 0
    Power On Hours 6399
    Has 56 Day Warning TRUE
    Has Utilization Warning 2PERCENT

    Hope that are enough information to catch and kill the bug ;)


    BR
    Jan


    Edit: Just found and installed the latest firmware MU02 for the Cruzial MX100 - unfortunately that didn't solve the issue.... :(

    • Offizieller Beitrag

    I have seen some compatibility issues with Crucial SSDs on SATA 3 (6Gbps) mode, not just on some Proliant servers but also other makes such as Intel and Asus. What's weird is that this is more prevalent when using backplanes for quick removal, but if is wired directly to the board, they seem to behave better. And by better, I mean recognized at least 70% of the time.


    I have also seen that behavior where in Legacy mode, the SSD does get recognized and my theory is that the drive is forced to link on SATA mode 1, then the controller takes care of the IDE translation layer. I've tried switching cables, backplanes, just about everything and I still had issues on AHCI mode. Using an Intel or Samsung SSD (is what I had on-hand) didn't have any issues with these boards. I have not tested the Crucial SSDs on the Microserver, but it seems odd that you have the same problem I had with other boards. Try wiring it straight to the optical drive port and see if you get the same issue. Also, try another brand that works on SATA 3 mode to see if you can still replicate it. I don't know if you can force these drives to SATA 2 or 1 on AHCI mode, but if that's possible, that's also worth a try just for troubleshooting purposes. Keep in mind, I'm not suggesting to leave it on those modes, so don't flame me for that lol

    Hello together,


    I am running OMV on a HP N54L as a NAS.


    I have discovered during the last days some activities (mainly caused by owncloud i guess) where the nas has to perform a lot of sync activities and the temperature was incresing until approx. 55/58 °C - could you elaborate a bit on the temperature and what might be acceptable for this type of server? Currently I am not sure if this value is still okay, or if I should change something related to owncloud.


    Thanks!

    I'm thinking about the Gen8 G1610T with 2GB as my first OMV NAS configured with 4x3TB WD Red disks.
    From what I read here and with the assumption I will use a SSD as my OMV system disk I will need additionally
    -USB stick (to store grub) -> Which size is needed here? Any special requirements?
    -SSD (for OMV) -->Which size is recommended? Will be 120GB enough if I plan to try some Plugins later?
    The SSD will be connected to the SATA port for the optical drive? Is there any special wire for this needed or can I use a typical SATA wire?


    Anything else what I need to order?

    • Offizieller Beitrag

    -Grub is very small. Any size usb or microSD drive will do.
    -OMV itself will not take more than 2GB installed with some plugins. A 32GB drive is enough since is the smallest one you can get. Personally, I am using a 120GB SSD.
    -The SSD will connect to the optical drive port. Any SATA cable will do.

    i am having trouble with my Gen8
    it keeps powering off, nothing in the IML, nothing in the diagnostics etc.. the iLo event log only shows errors like below, i opened case with HP but all they do is ask me for the diagnostics which don't list anything ..
    i have also noticed today that i get tg3 0000:03:00.0: tg3_abort_hw timed out, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff in the syslog and nothing but a reboot will fix it.


    4013 InformationaliLO 407/16/2015 07:5507/16/2015 07:551Server power removed.
    4012 CautioniLO 407/16/2015 07:5507/16/2015 07:551Server reset.
    4011 InformationaliLO 407/16/2015 07:5507/16/2015 07:542Server power restored.
    4010 CautioniLO 407/16/2015 07:5407/16/2015 07:541Server reset.
    4009 InformationaliLO 407/16/2015 07:5307/16/2015 07:531On-board clock set; was previously [NOT SET].
    4008 InformationaliLO 4[NOT SET][NOT SET]1APO: System configured to always remain off after power is restored.
    4007 CautioniLO 4[NOT SET][NOT SET]1Power restored to iLO.
    4006 InformationaliLO 4[NOT SET][NOT SET]1APO: System configured to always remain off after power is restored.
    4005 CautioniLO 4[NOT SET][NOT SET]1Power restored to iLO.

    • Offizieller Beitrag

    According to iLO, you are losing power from the power supply directly. Remember that iLO is to remain always on even if the server itself has been powered off. In other words, for as long as iLO has power, it will be up and running no matter what. If you have the server on a UPS that has a battery more than 2 years old, try bypassing it for now. Check that the AC cable is secure to the power supply.


    Also, the logs we need are the AHS logs. Download them from iLO (they are quite large) and send them to tech support.

    HP have finally sent me a another motherboard, hopefully this is the issue.
    I am also getting

    Code
    tg3: eth0: transmit timed out, resetting
tg3: DEBUG: MAC_TX_STATUS[ffffffff] MAC_RX_STATUS[ffffffff]


    and the server drops off the network, hopefully the new MB will sort it all out.

    Well it's early days but the new MB seems to have sorted the hardware issues.
    I now have the nics bonded and no issues so far (I know that's probably tempting fate) so fingers crossed my omv 2.0 on the gen8 will continue to perform as well as v1 on my old N40L

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden