Jump to content
XPEnology Community

Friese

Transition Member
  • Posts

    10
  • Joined

  • Last visited

Posts posted by Friese

  1. 18 minutes ago, bearcat said:

    That's the thing ... the "O41100113.ROM" is the name of an original BIOS, and there are many different versions of the modificated version.

    I personally use "TheBay" on all the G7's MicroServers I have been setting up, and it have never "failed me".

     

     

    Thank you so much for your fast response.

     

    I'm using this one from "kamzata":

    https://www.bios-mods.com/forum/Thread-HP-Proliant-Microserver-AMI-BIOS-MOD?page=5

    (think a found it also under the name "Tobi Oo's version")

     

    Will have a look into you bios mod version.

     

    No didn't try another cable. Will do as soon as possible.

     

    And yes, _s_ata5, sry.

     

    Looking forward for your settings.

  2. 11 hours ago, bearcat said:

     

    What BIOS are you using, and how is your HDD/Sata ctrl. related settings?

     

    I'm using "O41100113.ROM" mod.

     

    Bios Setting are:

    C1E Support: disabled
    Atheros NIC: disabled (using Intel 360T)

    InChipNIC: disabled

     

    AHCI Bios Support: enabled

    SATA Controller mode: AHCI

    Embedded SATA Link Rate: 3.0gbps max

    Drive Write Cache: disabled

    OnChip SATA Channel: enabled

    OnChip IDE Type: IDE

    SATA IDE Combined Mode: disabled

    SATA ESP on all PORT: disabled (don't want HotPlug)

    SATA Power on all Port: enabled

     

    Anything missing?

     

    This config works fine with 6.1.7. All 6 discs were found and useable.

    In 6.2.3 Update 3 alle 6 discs are also found. But as soon as there is a write access to ata5, the system starts to fail.

     

    Additinal info: I tested with Linux Boot: as read only mount ata5 works withous any problems. Seems like only writing makes troubles...

     

  3. On 3/4/2019 at 10:16 AM, agustaf said:

    I made some experience in case of chnge from DSM 6.1.7 to DSM6.2 and I hope sombody can help:

    HP N54L, USB3.0 card installed, ethernet card installed, 4GB RAM, 4 HDs connected to the hot swap interface and one HD connected to the fifth sata cable - all works fine if I start the N54L with a inux live system.

    DSM 6.2-23739, Jun's bootloader 1.03b, VID and PID update, 3 MAC adresses in the script.

    Now I restart the N54L with the installed DSM 6.2-23739 and the system works fine but with limitations:

    ...

    - fifth HD will not work

    ...

    Is everybode able to explain me why some parts/services will not work?

     

    Hi,

    nearly same for me. Was on 6.1.7. Fresh new install 6.2.3 Update 3 with June 1.03.

    6 HDs (BIOS Mod+C1), all AHCI configured.

    But if it comes to write access to ata5, I get a strange error and the drives ata5 and ata6 stalles:

    "ata5.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0"

    little time later also ata6

     

    If I only use MiniSAS with 4 HDs and internal SATA, everything works great.

    As soon as I use eSATA, the system becomes instable.

    It was running several years with all 6 HDs on 6.1.7 - but something changed with 6.2.3 Update 6.

     

    Are all discs running in you system in the meanime?

     

  4. Update DSM to 4.3-3827 build, please update your system to fix security issues in previous version.

     

    Hi Trantor,

     

    what is your prefered update procedure from beta5 while keeping all data on the drives?

     

    My point of view is:

    1.) boot up with the new beta7 USB stick

    2.) modify /boot/grub/grub.conf with correct mac/serial

    3.) install new beta 7 *.pat file manually under dsm update

     

    This should keep all drives, right?

  5. Das DSM OS ist immer auf allen Platten als eigene Partition als Raid 1 installiert. D.h. man kann gar nicht auswählen, _wo_ das DSM OS installiert werden soll. Das macht ja auch Sinn: denn egal ob eine oder mehrere Platten abstürzen - solange eine einzige übrig bleibt, bootet das System.

     

    Nachdem ich die Pakete unwichtig finde, würde ich keinen Platz auf dem Raid 1 dafür verwenden. Man kann sie ja jederzeit ganz leicht wieder installieren.

  6. Ich verwende die 4.3 Beta 5 und Standby/WOL geht einwandfrei, wenn man den USB Stick unmounted (oder die PID/VID ändert) und die MAC Adresse auf dem Stick richtig einstellt. Allerdings dürfen dazu nicht irgendwelche Pakete auf die Platten zugreifen. Und nicht vergessen: das DSM OS ist per Raid 1 auf allen Platten verteilt - d.h. wenn im System ein Schreibvorgang stattfindet, dann geht keine der Platten in den Standby.

×
×
  • Create New...