coalfield

Members
  • Content count

    27
  • Joined

  • Last visited

Everything posted by coalfield

  1. I have looked at numeroud thread on this issue ans searched separately. I am still none the wiser on if and how I go about allowing the HP Gen 8 microserver to spin down the HDDs and to spin down the disks. I am using the latest DSM 6. Should this be working by default or anything needs amending. Any help from those with it appreciated!
  2. coalfield

    Power button package

    thank you!
  3. coalfield

    DSM 6.1.x Loader

    Maybe a silly question but where are the links to Jun's v1.03a2 loader?
  4. coalfield

    Sleep / HDD Hibernate / AutoShutdown HP Microserver Gen 8

    This is still an ongoing issue. No hibernation on the HDD's whatsoever despite closing down every running app. Running the discs on AHCI. Any help welcome!
  5. coalfield

    DSM 6.1.7-15284

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 Update 1 - Loader version and model: Jun's Mod V1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HPE Proliant MicroServer Gen8 - Additional comments: REBOOT REQUIRED
  6. coalfield

    Proliant HDD driver

    Keen to understand this since its not they are spinning up all the time they simply never sleep!
  7. without wanting to stray too far off topic, how did you get it to turn the HDDs off and the server, and when you mean the server off do you mean power down or standby? I can only turn off with the power button and HDD will not standby
  8. coalfield

    DSM not starting SOMETIMES in proliant gen8 G1610T

    Same here with Jun 1.02b ds3615xs, i dont have a screen plugged in so cannot see the status. However I have switched to DHCP (not static or allocated on router) and so far seems to be OK. Any thoughts on why would changing to DS3617XS fix this, and where you got the idea?
  9. coalfield

    HP Microserver Gen8 drives hibernation

    I have always had this issue, since pre DSM 6. No idea how to fix this either, I would love the unit to go into sleep when not in use...
  10. coalfield

    DSM 6.1.6-15266 Update 1

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Proliant MicroServer Gen8 - Additional comments: NO REBOOT REQUIRED
  11. coalfield

    DSM 6.1.6-15266

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: Baremetal (HP Proliant MicroServer Gen8) - Additional comments: REBOOT REQUIRED
  12. coalfield

    View error logs for xpenology

    I am having an issue on my HP Gen 8 Microserver on DSM 6 where on some boots it does not get an IP and I cannot access it. Power button is not shutting it down (I have confirgured it to), so hard reset is the only fix. Next boot all fine. Is there any way for me to find through error logs what is causing the issue. Presumably it is hanging during the xpenology boot sequence, but cannot easily connect a display to find out?
  13. coalfield

    DSM 6.1.5-15254 Update 1

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP Proliant MicroServer Gen8) - Additional comments: No reboot required
  14. coalfield

    DSM 6.1.5-15254

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4-15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP Proliant MicroServer Gen8) - Additional comments: Requires reboot
  15. coalfield

    DSM 6.1.4-15217 Update 5

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4-15217 Update 2 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP Proliant MicroServer Gen8) - Additional comments: Requires reboot
  16. Remember my old SS4200 revolutionary design for its age. Lovely bit of kit! Nice MOD
  17. coalfield

    DSM 6.1.4-15217 Update 2

    HP Microserver Gen 8 baremetal DS3615xs from - DSM 6.1.4-15152 Update 1 Updated through DSM All went OK and reboot fine
  18. coalfield

    Gen8 and fan noise - how to lower

    Anyone up to the challenge of a dummys guide for AMS for Gen 8 baremetal on 6.1? the referenced thread dates back to 2015 and I am not familiar with modprobe Currently fans are reasonable on my Gen8 as I don't have in the open so not sure how much of a benefit AMS would be however now the box is up and running on the latest I would prefer to have more visibility of temps. Any help appreciated
  19. coalfield

    DSM 6.1.4-15217 Update 1

    HP Microserver Gen 8 DS3615xs DSM 6.1.4-15152 (fresh from install from 5.2) Updated through DSM All went OK
  20. just did this on my hp microserver gen8, worked flawlessly to boot in so ready to give it a whiz. Thanks!
  21. I am struggling to get my Intel G1610T to throttle on a HP Gen8 Intel Microserver. nasbox> grep "MHz" /proc/cpuinfo cpu MHz : 2294.596 cpu MHz : 2294.596 I have tried to install the script 'S99PowersavingINTEL.sh' contents: #!/bin/sh for c in $(ls -d /sys/devices/system/cpu/cpu[0-9]*); do if ! grep -q 'conservative' $c/cpufreq/scaling_governor ; then echo conservative >$c/cpufreq/scaling_governor ; fi done in the correct folder and rebooted, but still showing the same CPU info. Any advise welcome as I am sure I am missing something, most likely quite obvious
  22. coalfield

    Power off from the buttom

    Worked for me using those instructions: Steps to unpack: 1. download file acpi-button-dsm5.2.tgz https://www.dropbox.com/s/6rcuignyxsxre ... 2.tgz?dl=0 2. enter to DSM console (directly or by ssh) and type following CODE: SELECT ALL cd / tar zxvf /volume1/path_to_downloaded_files/acpi-button-dsm5.2.tgz on DSM 5.2-5644 Update 5
  23. I have been struggling to find this info out so tested it myself. On a HP Microserver with 4x WD RED 3TB using SHR Dual Redundancy writing large files produces 70 MB/s utilising the Gigabit connection approx 70%. For smaller files (i.e. photos), the throughput was around 50MB/s and 50% utilisation (writing). Reading was ~75MB/s not affected significantly by the file type. Increasing the number of copy streams shares this total bandwidth, so total throughput does not increase. With the same setup on RAID 5 (note: single disk redundancy only) on large files I get approx 100 MB/S which is essentially a 100% utilisation of gigabit. For smaller files I get 50MB/s, similar to SHR. However increasing the streams, i.e. a copy of large files with small files separately but simultaneously produces a transfer speed of 90MB/s, almost a complete utilisation of Gigabit. Reading was ~100MB/s not affected significantly by the file type. If an aggregated dual LAN was setup , I am sure the speed would be faster on RAID5 as it appears to be network limited. I hope this helps some. For me the clear choice unless you have mixed drives is to go for RAID over SHR, at least if you dont intend to expand in the future. Some forums state there is only a slight overhead for SHR (as quotes by synology), however in my experience this is not the case, the overhead is significant. Will update once I have aggregated the LAN
  24. coalfield

    Synology SHR Vs RAID5 which is faster (Gen 8 Microserver)

    Fair point I didn't try SHR with single redundancy but still cant see any advantage over RAID if the drives are all the same an no future expansion requirement
  25. coalfield

    Is XPEnoboot required permanently?

    Sorry in advance for this question, but I hope its a striaghtforward question for you to answer I have a HP Gen8 microserver and am installing XPEnology direct to the box, no vitrual environment, I dont think I need it. I have managed to get XPEnology installed to the single drive I currently have in the system, via the MicroSD card with XPEnoboot installed. The system is up and running, however I was under the impression once installed the system was installed to the main drive, and hence I would no longer need the SD card. However after removing the microSD it fails to boot. So am I right in saying the system will always need a microSD (or USB key) in the system in order to launch the software? Thanks