Jump to content
XPEnology Community

robermix

Member
  • Posts

    12
  • Joined

  • Last visited

Posts posted by robermix

  1. On 8/2/2017 at 7:47 PM, tuonoazzurro said:

    Hi, i'm running Jun's Loader 1.01 on a HP Microserver Gen8. I've noticed that hdd are always spinning, they don't go into hibernation. Could someone tell me if is this ok or i'm missing a step? On the power setting i set hibernation for sata to 10 minutes. I've resilio sync package installed but i tried stopping it with the same problem.

     

    Does HDD hibernation works for you?

     

    Thanks

     

    On 8/2/2017 at 8:27 PM, Fizz Khalifa said:

     

    I have the same problem, hibernation not working with 6.0.2-8451 update 8. I even reinstalled and set up a SSD as volume 1, so if a package or something needs to be loaded it doesn't need to spin up my hard drive. But it isn't going into hibernation ever.

    Could we somehow monitor what is accessing the drive? Or is this a driver problem? I use WD Red 3tb.

     

    On 8/2/2017 at 11:30 PM, tuonoazzurro said:

     

    Are also you on HP Microserver gen8? I'm not using wd red, i'm using seagate barracuda, but with Dsm 5.2 the hybernation worked with the same hardware setup so i think the problem is not related to HDD

     

     

    Same problem !

     

    I set up an SSD as internal volume and other 3 drives configured as eSata data-only drive by editing the synoinfo.conf file. I have also connected an external USB drive.

    I've stopped all services but no one disks go into hibernation. With the same hardware setup and DSM 5.1 hibernation worked.

  2.  

    A possible (?) dirty solution is to manually corrup the system partition of the old drives (https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/), add them to the new build and when DSM 6 will boot it will copy itself to the old drives fixing the volumes. But i think that is a very dirty and dangerous solution and i'm not sure it will work.

     

    I'm switching to esata drive mode to avoid this problem. DSM (and packages) installed in only one drive and all other are only data drives. (I don't need RAID or SHR solutions.)

  3. Great news. In this days i'm planning to upgrade my build from DSM 5.1 to DMS 6.1 with a fresh install.

     

    Now i've installed 4 sata drives each with their own volume, so nothing RAID o SHR.  To avoid the problem to have to backup data before each DSM update i will change the build.

    I'm switching the sata drives from sata internal mode to esata mode, in this way the drives will become only data EXT4 drives, and i'll add a new drive which will runs DSM. 

     

    So when i want to update DSM i have only to unplug the esata data drives, update DSM, check synoinfo.conf and reconnect the drive in esata mode.

    I'm thinking to use a SSD as DSM system drive to create a zero-noise build when the esata data drives gone to sleep/hybernation. 

     

    About the new transcoding option for Plex i've found this topic: https://xpenology.com/forum/topic/7151-difference-ds916-ds3615xs-and-ds3617xs/

     

     

    DS3617xs use the Xeon D-1527 which doesn't have any GPU integrated, so i infer that the hardware transcoding will not work with a DS3617xs system image.

     

    At this point, i wonder which system image is better between DS916+ and DS3615xs to test the new hardware transcoding feature.

  4. I have an issue.

     

    Bios 1.40. Serial and Parallel ports disabled. Intel USB 3.0 and Legacy Support Enable.

    XPEnoboot on bare metal, DSM 5.1-5022 Update 4.

     

    Pen Drive connected to an USB 2.0 port: it works.

    Hard Disk USB 2TB 3.5" with external power supply, connected to an USB 2.0 port: it works.

     

     

    Pen Drive connected to an USB 3.0 port: it works.

    Hard Disk USB 2TB 3.5" with external power supply, connected to an USB 3.0 port: it dosn't work.

×
×
  • Create New...