mats42

Members
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mats42

  • Rank
    Junior Member
  1. mats42

    DSM 6.1.x Loader

    well. what I did was shutdown the box from the gui, replaced the usb memory with one with 1.02 booted the system, klick on the upgrade to 6.1.1. it installed and did an automtic reboot. after that it newer booted again, I tried all three bootalternatives - no boot and not detectable by find either. Even tried with reimaging the usb device just for saftey. Can it be something else at the same time - maybee. Is it a big deal that data was lost? nope - it took a few mins to recreate the backup job and the box fixed the rest during the night. The point is that you should have backup or be prepared to loose data when playing with alpha stuff. I was and I'm happy with my upgrade
  2. mats42

    DSM 6.1.x Loader

    Updating, upgrading reinstallling does not cause loss of data. System and data are in two very distinct partitions. having the partion table go corrupt does ......
  3. mats42

    DSM 6.1.x Loader

    tried to update 6.02 -> 6.1.1 on bare metall Did it work - No Did I loose all data - Yes Do I blame somebody for it - No Did I have to reinstall - Yes Am I happy - Yes It is an Alpha loader and my box is only used as a backup for the true server so after reinstall, I just configured the backup jobb again. It actually took longer time to clean the disks for the new install
  4. I don't do Xen myself but I found this for you https://www.netservers.co.uk/articles/o ... 00_gigabit
  5. mats42

    DSM 6.1.x Loader

    YES
  6. mats42

    DSM 6.1.x Loader

    I missed that you had an ML server. I will dig deeper and see if i can find where the sensor is on my microserver Dead Easy on the Microserver to. The Tempsensor connector is located on the inside of the powerconnector on the mainboard. It has a brown loop on it. And removing it gives a reported 6% fanspeed on the microserver. Of course I take no responsibilty what so ever for this
  7. mats42

    DSM 6.1.x Loader

    I missed that you had an ML server. I will dig deeper and see if i can find where the sensor is on my microserver
  8. mats42

    DSM 6.1.x Loader

    Look here for how to fake the fan signal, etc.. http://homeservershow.com/forums/index.php?/topic/7294-faking-the-fan-signal/page-1 Ciao ema Hi, Thanks for the link, but its a two year old link and lots has changed with the Bios and iLO fw updates. Its not the same issue as well. What we need is the drivers from HP ESXi u2 injected into xpenology like the AMS module i've managed to work. Just don't know how/where the iLO drivers. The only solution that I found that works is to disconnect the front temp sensor and makes the iLO think that its running at 0C and the fan stays at 6%. Of-course if the cpu load/temp goes up fan spins higher. There seems to be no ill-effect of disconnecting the front intake temp sensor. By the way, DSM6 runs fine as a VM in HP ESXi u2 with no fan issues. Fan stays at 6% at any ambient temp for me. The only thing is that the HDDs wont spindown/sleep as they are running in RDM mode from the HP B120i controller. Can you tell me how you did disconnect that sensor?
  9. mats42

    DSM 6.1.x Loader

    Look here for how to fake the fan signal, etc.. http://homeservershow.com/forums/index.php?/topic/7294-faking-the-fan-signal/page-1 Ciao ema No, that's more about fooling the termal protection (ie killing of the rotation detect protection) which might be a bad but unavoidable workaround if we can't fix the real problem If you install Windows, Vmware, Redhat Enterprise, Suse, Fedora or Centos with propper drivers the fan will run at 6%. If you instead install Xpenology the fan will be at 12-15% on exactly the same hardware under the exact same conditions. If you dig deep into it the problem is that the ILO reads temps from all drives as a base value for it's cooling settings. In AHCI mode or in raid mode without the propper driver loaded into the running OS, the ILO can't get the temp values and therefore has to use (higher) failsafe values for the fan speed. By loading the right driver - ILO now can read the temp Values and adjust the fan speed properly Therefore the fix is to make sure the ILO can get temps under XPenology and only if and when we know that it can't be done - then it's time for "dirty" HW hacks - prefferbly one that just adjusts the fan speed a little lower so that the protection system still works as intended.
  10. mats42

    Wd Red 8 TB in HP Gen8

    I don't know about that specific drive but the controller will do 8GB drives at least. See http://homeservershow.com/forums/index. ... n-8/page-2
  11. mats42

    DSM 6.1.x Loader

    1. You miss the point. There is no RPM signal in the connector so you can't send one. The ILO requires a different type of signal (rotation locked/tach). If you try to send a RPM signal on that wire the ILO will see the fan as faulty and shut down the system directly. 2. Not often but have I seen it happend on HP servers -yes and why take the risk when you don't have to 3. Not on a microserver. At 10% system load with 20C ambient temp (calm winter day) about 6-8% is enough. At 90% cpu load it will need at least 15-20% and the noice difference is huge so therefore a temp controlled solution is the best 4. Well, two small problems - there is no 3 or 4 pin fan connector in a microserver .......... Only a HP only six pin and there is no rpm pin in that since the ILO doesnt messure RPM. It messures temp and if the temp isn't right it orders the fan to higher speeds. The ILO will also order higher fan speeds if it can't read drive temps - Values it tries to read from the missing driver 5. Since the "problem" is that Xpenology doesn't contain the driver HP do provide - HP can't fix it but we may be able to if we include the ILO amd AMS drivers. Hence the request for including them. The ams driver was hacked into 5.X-somwthing (I read about it earlier)
  12. mats42

    DSM 6.1.x Loader

    co i would just create a new pwm controller with 2 NE555's 1 to control the actual fan itself the other for making the ilo happy. You can slowdown the fan to let say 4 or 5 % lowest possible pwm setting to let the fan rotating and the other setting pwn pulses which enters the ilo. its about 1 or 2 euro on components.something like this http://i.imgur.com/Hw1zBKO.png I sed a few problems with that approach. 1. the fan doesn't give an rpm signal back so you can't send a pulse based signal to the ilo. It needs a tach/rotation locked signal 2. If the fan fails, a faked signal would allow the server to overheat 3. If the temp in the server rises a fixed PWM signal would allow the server to overheat 4. Hw hacking would void warranry 5. Why do a hw workaround on what we know is a software problem instead of fixing the SW? we know that the fan will run at correct speed with the right sw Sorry
  13. mats42

    DSM 6.1.x Loader

    co i would just create a new pwm controller with 2 NE555's 1 to control the actual fan itself the other for making the ilo happy. You can slowdown the fan to let say 4 or 5 % lowest possible pwm setting to let the fan rotating and the other setting pwn pulses which enters the ilo. its about 1 or 2 euro on components.something like this http://i.imgur.com/Hw1zBKO.png I sed a few problems with that approach. 1. the fan doesn't give an rpm signal back so you can't send a pulse based signal to the ilo. It needs a tach/rotation locked signal 2. If the fan fails, a faked signal would allow the server to overheat 3. If the temp in the server rises a fixed PWM signal would allow the server to overheat 4. Hw hacking would void warranry 5. Why do a hw workaround on what we know is a software problem instead of fixing the SW? we know that the fan will run at correct speed with the right sw Sorry
  14. mats42

    DSM 6.1.x Loader

    mine is stock 1610. No extra cards and four disks. Runs on 12-15% in ahci with XPenology. In Redhat with raidmode it goes lower. I like silent things and I can't see a reason why we shouldn't be able to get that under Xpenology
  15. mats42

    DSM 6.1.x Loader

    Have you read this?: http://www.silentpcreview.com/article1377-page8.html Yes. To reduce noise you have to use raid mode. To use Raid mode you must have the driver in Xpenology - hence the requst to include it