Search the Community

Hallo liebe Gemeinde, ich habe folgende Problem. Ich habe mir Erfolgreich das DMS 5.0-4493U2 auf meinem ESXI/Hypervisor 5.1 Installiert. Zusätzlich habe einen PCIe SATA Kontroller "Digitus DS-30104-1" (mit MARVELL 88SE9230 Chipsatz) per Passthrough an die VM-XPenology durchgereicht. Funktioniert auch alles erstmal soweit sehr gut und alle Festplatten werden erkannt. Mein Problem ist das ich gern die Festplatten Spindown Funktion nutzen wollen würde. Ich habe auch schon gelesen das bei einer nativen Installation der USB Stick einfach nur raus muss und dann Funktioniert die Einstellung die man im "Hardware und Energie" eingestellt hat . Wie mache ich es aber bei meinem Scenario? Den der "USB Stick" ist ja in meinem Fall eine VM-HDD. Ich hoffe ihr könnt mir helfen. Falls noch weitere relevante Daten notwendig sind sagt einfach bescheid...

Hi! I'm battling to get my server to sleep the hdds. (uses half the power with sleeping 6 disks, lots more when I fill it with 24 disks!) It will hibernate the disks fine without plex - try as hard as I can, plex will still access some files once an hour waking the disks.. My next idea is to move plex outside the array (onto a cheap ssd), thereby any log writes etc will not wake the whole array and although the ssd will remain active it uses far less power... However this is failing at the first step - as soon as I have a disk inserted which is not assigned to a volume, the disks again keep waking as synology accesses /var/log/smart_quick_log every 10-15 minutes (according to messages.log) even though nothing is written.. Is there any way to have an internal disk mounted not in the array without triggering this? How about moving all synology logs somewhere outside the array to stop wake ups? Would using an ssd in synology as cache drive help at all? I suspect not from reading synology site... Cheers!

Hi all, Let me first introduce my xpenology build: Intel E2140 Intel D945GCNL 1G DDR2 ram *2 4*1T hitatchi HDD 4493 u2 with nanaoboot (upgrade from trantor 4.3) After a bunch of test, I found that if I try to wake up the nas from hibernation through apps (video station etc), or samba file system (access a network drive from a windows client), the disk wake up from hibernation, and the access takes time to load. Sometimes it will just fail, and then I no longer access unless reboot. Even the web GUI login still failed. It will just stuck at the screen "Processing, please wait..." If I perform a reboot at commandline using root with command "reboot", the console will show the error "segmentation fault" and failed reboot. A hard reset is required. To work around this issue, I disabled the hibernation, and so far the system is great. Can someone please share with me your system with hibernation on and any unusual behavior occur? Thanks a lot for your help!

Disk hibernation not functional.

Just installed DSM5.0 on my N54L via Nano boot x64 iso. I have the problem with the hibernation. What I did include: 1> BIOS mod with O41100113 2> Enable eSATA for port 2-6, only port 1 set to SATA 3> WOL works well after adding the shutdown script. However, the hibernation does not work at all. After enable the debugging tools, I saw a number of log entry after disconnect LAN. Jul 2 20:38:09 DiskStation kernel: [ 9009.793257] [/etc/resolv.conf] opened by pid 17840 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:38:23 DiskStation kernel: [ 9024.164182] [pg_clog/0000] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:30 DiskStation kernel: [ 9030.661088] [base/16585/16725] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:33 DiskStation kernel: [ 9033.792095] [base/16585/16868] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:37 DiskStation kernel: [ 9038.135088] [base/16585/16875] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:42 DiskStation kernel: [ 9042.377092] [base/16585/16760] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:44 DiskStation kernel: [ 9044.700103] [base/16585/16751] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:46 DiskStation kernel: [ 9046.316093] [base/16585/16877] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:48 DiskStation kernel: [ 9048.336089] [base/16585/11778] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:49 DiskStation kernel: [ 9050.255095] [base/16585/16696] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:51 DiskStation kernel: [ 9051.530245] [/etc/resolv.conf] opened by pid 17841 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:38:54 DiskStation kernel: [ 9054.901103] [base/16585/11638] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:56 DiskStation kernel: [ 9056.820091] [base/16585/16682] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:57 DiskStation kernel: [ 9057.931082] [base/16585/16758] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:06 DiskStation kernel: [ 9066.314094] [base/16585/16788] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:08 DiskStation kernel: [ 9069.243082] [base/16585/16718] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:11 DiskStation kernel: [ 9071.970082] [base/16585/16694] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:12 DiskStation kernel: [ 9073.081091] [base/16585/16739] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:16 DiskStation kernel: [ 9076.717090] [base/16585/16659] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:21 DiskStation kernel: [ 9081.969089] [base/16585/16768] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:24 DiskStation kernel: [ 9084.393083] [base/16585/16709] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:31 DiskStation kernel: [ 9091.766082] [base/16585/16879] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:32 DiskStation kernel: [ 9093.079087] [base/16585/16621] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:42 DiskStation kernel: [ 9103.280084] [base/16585/11776_fsm] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:45 DiskStation kernel: [ 9105.502088] [base/16585/16726] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:54 DiskStation kernel: [ 9115.098168] [/etc/hosts] opened by pid 18194 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:40:14 DiskStation kernel: [ 9135.198247] [/etc/resolv.conf] opened by pid 17957 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:40:23 DiskStation kernel: [ 9143.592093] [base/16585/16730] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:40:36 DiskStation kernel: [ 9156.835177] [/etc/hosts] opened by pid 18194 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:40:49 DiskStation kernel: [ 9169.565092] [base/16585/16737] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:40:56 DiskStation kernel: [ 9176.935272] [/etc/resolv.conf] opened by pid 17958 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:41:18 DiskStation kernel: [ 9198.572331] [/usr/syno/etc/synoshare.db] opened by pid 18194 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:41:38 DiskStation kernel: [ 9218.726500] [/etc/resolv.conf] opened by pid 18010 [u:(/usr/bin/php), comm:(php)] Jul 2 20:42:01 DiskStation kernel: [ 9241.827178] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:42:21 DiskStation kernel: [ 9261.927264] [/etc/resolv.conf] opened by pid 18011 [u:(/usr/bin/php), comm:(php)] Jul 2 20:42:42 DiskStation kernel: [ 9283.028180] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:43:02 DiskStation kernel: [ 9303.128242] [/etc/resolv.conf] opened by pid 18012 [u:(/usr/bin/php), comm:(php)] Jul 2 20:43:23 DiskStation kernel: [ 9323.619077] [pg_clog/0000] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:43:45 DiskStation kernel: [ 9345.329306] [/etc/resolv.conf] opened by pid 18013 [u:(/usr/bin/php), comm:(php)] Jul 2 20:44:06 DiskStation kernel: [ 9366.430172] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:44:26 DiskStation kernel: [ 9386.530243] [/etc/resolv.conf] opened by pid 18014 [u:(/usr/bin/php), comm:(php)] Jul 2 20:44:48 DiskStation kernel: [ 9408.631155] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:45:08 DiskStation kernel: [ 9428.731249] [/etc/resolv.conf] opened by pid 18015 [u:(/usr/bin/php), comm:(php)] Jul 2 20:45:31 DiskStation kernel: [ 9451.832274] [/volume1/@appstore/VideoStation/plugins/plugin_data/com.synology.Synovideodb/cloud/info.json] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:45:51 DiskStation kernel: [ 9471.932289] [/etc/resolv.conf] opened by pid 18016 [u:(/usr/bin/php), comm:(php)] Jul 2 20:46:13 DiskStation kernel: [ 9494.033158] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:46:33 DiskStation kernel: [ 9514.133240] [/etc/resolv.conf] opened by pid 18017 [u:(/usr/bin/php), comm:(php)] Jul 2 20:46:54 DiskStation kernel: [ 9535.234168] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:47:15 DiskStation kernel: [ 9555.334249] [/etc/resolv.conf] opened by pid 18018 [u:(/usr/bin/php), comm:(php)] Jul 2 20:47:36 DiskStation kernel: [ 9576.435285] [/volume1/@appstore/VideoStation/plugins/plugin_data/com.synology.Synovideodb/cloud/info.json] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:47:56 DiskStation kernel: [ 9596.535300] [/etc/resolv.conf] opened by pid 18019 [u:(/usr/bin/php), comm:(php)] Jul 2 20:48:17 DiskStation kernel: [ 9617.636169] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:48:37 DiskStation kernel: [ 9637.736249] [/etc/resolv.conf] opened by pid 18020 [u:(/usr/bin/php), comm:(php)] Jul 2 20:48:58 DiskStation kernel: [ 9658.837168] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:49:18 DiskStation kernel: [ 9678.937251] [/etc/resolv.conf] opened by pid 18021 [u:(/usr/bin/php), comm:(php)] Jul 2 20:49:41 DiskStation kernel: [ 9702.038287] [/volume1/@appstore/VideoStation/plugins/plugin_data/com.synology.Synovideodb/cloud/info.json] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:50:01 DiskStation kernel: [ 9722.138307] [/etc/resolv.conf] opened by pid 18022 [u:(/usr/bin/php), comm:(php)] Jul 2 20:50:23 DiskStation kernel: [ 9744.239177] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:50:44 DiskStation kernel: [ 9764.339268] [/etc/resolv.conf] opened by pid 18023 [u:(/usr/bin/php), comm:(php)] Jul 2 20:51:06 DiskStation kernel: [ 9786.440171] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] it seems something keep still running and it is related to Video Station. Any thoughts/advice? thanks a lot.

Sorry for the stupid question. how do I/We know if the drive hibernation works or not If so can someone kindly help me and explain how to enable it.. ?

it does, if it boots and you find it in network its working, if the cpu is not up to it you would not find it in network if 918+ throws error 13 you can try with a wrong vid/pid, cant get worth then error 13 but as you cpu does not have gpu there is nothing to gain with 918+, more likely you will have driver problems with the lsi sas controller (-> 1st post, warning about disk hibernation and broken raids) 3617 seem to be the best choice but 3615 woul work too, as the h330 has a older lsi sas chip it should work with 3615 too in theory you could shutdown the r420, take its working usb and boot with it on the r430 before installing with it you should at least save the zImage and rd.gz because when installing the might be overwritten (when installing a newer version of dsm) that way you know its not the usb (as its working on r420) and just so see if disks are found it should be enough to just boot it and look with the browser on the systems ip address if its not booting at all or not found in network then check csm settings in bios and usb boot device (non-uefi to get csm mode booting, if you use the uefi usb boot device it will ignore csm mode as its just an option that gets chosen by selecting the right boot device)

Hi @ all, I am on gnoboot 10.5 alpha / DSM 5-4458 update 1. If I can trust the protocoll of DSM my HDDs go into hibernation because if I log in after the hibernation time there is an entry "Internal disks woke up from hibernation" BUT I cant declare lower power consumption. Is that normal? I am unsing two WD Red 2TB in RAID1. Thanks for all effort!

beside this with just 4 disks you will use onboard sata for sure (ahci as driver), no problems with this when using disk hibernation

Ehhhh right here, thanks IG-88 😀😀, however I don't use server hibernation / suspend, my server is always on because it acts as my mail server so everything should work fine 🙏🙏

maybe this one? https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ but thats specific for scsi/sas controller when using disk hibernation on 918+ the newly compiled driver (no smart, no sn) does not have this problem but makes disk handling more or less impossible as you cant identify disks properly in the gui and cant user smart data to determine the disks condition

04:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 3008 [Fury] (rev 02) Subsystem: Dell PERC H330 Adapter Kernel driver in use: megaraid_sas Kernel modules: megaraid_sas 1000:005F MegaRAID SAS-3 3008 [Fury] that driver is for raid mode so it still has the IR firmware and you use a hardware raid raid mode is only supported by additional drivers and not that good with that not to old cpu you would be able to use 1.04b 918+ and the megaraid driver from the newer 4.4 kernel would support the 1000:005F but there are some problems with lsi sas on that one related to disk hibernation https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ i'd suggest flashing IT firmware to it and use 3617, the lsi sas driver in there are from synology and are native to that 3617 unit, they should work best https://forums.servethehome.com/index.php?threads/flash-crossflash-dell-h330-raid-card-to-hba330-12gbps-hba-it-firmware.25498/ you would need to offload all data and install new that way you took the wrong start by using a raid mode controller, dsm in its core is completely about single disks and software raid with 6.x and its way of using synologys kernel we are much more restricted and with just me making drivers and being unable to change code of kernel drivers its hard to have newer lsi drivers (synology isn't offering source code for the drivers they use in 3617, with code they tempered with we might be able to do a megaraid_sas driver that works properly but for as it is we don't have that) when using a hacked appliance as we do here its much easier to bend in the way the system is implying or choose another OS so its more like IT firmware or using (maybe) Open Media Vault

the driver in 0.13.3 supports the following 1000:0064 1000:0065 1000:006E 1000:0070 1000:0072 1000:0074 1000:0076 1000:0077 1000:007E 1000:0080 1000:0081 1000:0082 1000:0083 1000:0084 1000:0085 1000:0086 1000:0087 1000:0090 1000:0091 1000:0094 1000:0095 1000:0096 1000:0097 and here is the list https://pci-ids.ucw.cz/read/PC/1000 your is this one https://pci-ids.ucw.cz/read/PC/1000/00c4 ? the lsi sas drivers in 918+ are problematic as you can see in the 1st post, i would recommend using 3617 as it comes with newer drivers from synology this would be whats supported in 3617 right now (and with smart and serial and without problems about that it might kill your raid if disk hibernation in on) so you 1000:00c3 would be supported in 3617 1000:0064 1000:0065 1000:006E 1000:0070 1000:0072 1000:0074 1000:0076 1000:0077 1000:007E 1000:0080 1000:0081 1000:0082 1000:0083 1000:0084 1000:0085 1000:0086 1000:0087 1000:0090 1000:0091 1000:0094 1000:0095 1000:0096 1000:0097 1000:00AA 1000:00AB 1000:00AC 1000:00AD 1000:00AE 1000:00AF 1000:00C0 1000:00C1 1000:00C2 1000:00C3 1000:00C4 1000:00C5 1000:00C6 1000:00C7 1000:00C8 1000:00C9 1000:00D0 1000:00D1 1000:00D2 1000:02B0 please use the forum search to find the attempts in that direction, its not that easy, its more then just a driver (*.ko file) that would be needed i have this one on my list but there might bo one or two more threads https://xpenology.com/forum/topic/22272-nvidia-runtime-library/ it looked like it was possible to just use the drivers from a "compatible" dsm version but as already stated it gets way more complicated as ffmpeg and other are involved,way more then i'm willing to do as i don't need that, i provided drivers and ways on how to build them, so other people with enough time to spare can push this forward if there is enough will to do it every case where it does not match the installed version (on disk, raid1 over all disks) it a issue usually dsm will not boot and offer a repair that usually copy's the kernel files from disk back to the loader i do mention this i the 1st post (afaik), as i'm only offering the extra/extra2 its up to the user to copy the (6.2.3) files to the loader, before using it how would you want to do that automatically? in theory its possible to offer pre-made (modded) loader with newer kernel files and matching extra/extra2 i'm not doing this for legal reasons, any one is free to offer this, either jun nor me have copyrights on that stuff and as long as there is a decent description with that loader making clear in what way its different from jun's original and giving the version of the extra/extra2 thats used i dont think there is anything to complain about i dont mind if anyone uses the extra/extra2, i would prefer to see a version number, not my name, to be used with it to give people a way to see if its the recent version and being able to read about problems and quirks i've seen my extra/extra2 been used in some stuff from china (like 1019+ loader) and i dont mind that, its free to use for everyone and if anyone tells people its his work then i dont mind too at some point i started to add checksums to the download to make sure people can check if its the version from me or anything modded and i may add some version text file to the extra/extra2 to make it easier to check what version is in use (extra/extra2 can easily be unpacked with 7zip to check a text file) so if you feel the need to offer loaders for pre configured for 6.2.3 feel free to do so and open a thread in the loader section (might need to be approved by a mod so it can be a few days before everyone can see it) btw before doing so PM me, i have a way to overcome the read/write problems in win10 so the offered loader would also be easier to handle as both partitions could be used freely in win10, auto mount drive letters and working without "as administrator" (as in older win10 version)

I have updated 4.2 to 4.3, and found hard disk hibernation can not work. It was OK under 4.2. I found there are some log write into /var/log/messages every 10min, I think this is why the disk can not hibernate. the error log as: DiskStation synorelayd[6939]:synorelayd.cpp:563 regist command auth error I think if the error can be sloved or I can write this error into RAM but not hard disk. The hibernation problem can be sloved. Is there anybody can help me to solve this issue? Or tell me are there same errors in your /var/log/messages ? ____________________________ Update, I have solved this problem. The "synorelayd.cpp:563 regist command auth error" because the quickconnection do not work normal. I did not use quick connection, but used the cloudstation. It default use quickconnection, but quickconnection working unnormally. and cause the problem. I cancel the selection of quickconnection, the error message did not appear again.

Bonjour à tous, je suis ravi de rejoindre la communauté des utilisateurs de XPEnology, qui plus est sur Proliant N54L Merci par avance de votre accueil et surtout désolé pour ces questions de débutant / setup ... qui agaceront peut être certains d'entre vous très aguérris (sincèrement désolé, je m'en excuse auprès d'eux) La connaissance ne vaut que si elle est partagée, c'est mon humble avis Quelle version d'ESXi faut-il utiliser : 5.5 ou 5.1 ? Lien lecture viewtopic.php?f=13&t=848 => le doc Idiot guide est-il toujours la meilleure voie à suivre ? => Auriez-vous sinon un lien / tuto / guide install ? En supposant que XPEnology soit en VM sur Esxi => est-ce que je dois toujours laisser une clé usb avec l'img d'xpenology pour permettre les reboots de la VM ? => y-aurait-il sinon une ame charitable qui récapitulerait comment faire sinon ? Quelle version d'XPenology est adaptée actuellement au N54L / Esxi => est-ce la XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2) ? => est-ce une DSM 4.2 ou 4.1 ? la 4.3 est-elle déjà d'actualité (il m'a semblé lire que des modifs bloquait la sortie de cette version...) => auriez-vous svp un lien de dl de la version adaptée ? Sécuriser l'alimentation électrique / couper automatiquement le n54L seulement Lien lecture viewtopic.php?f=13&t=777 => est-ce qu'un onduleur peut être reconnu sans devoir installer une carte usb supplémentaire ? => quel onduleur avec usb utilisez-vous / conseillez-vous svp pour ce seul n54l ? Est-ce que quelqu'un a réussi à activer sérieusement l'hibernation des disques sur le trio n54L/esxi/xpenology ? => merci par avance à ceux qui se donneront la Un peu HS : peut-on imaginer (en ajoutant une cg dédié) exécuter xbmc sous esxi (ex: VM OpenElec) et sortir le flux vidéo sur l'hdmi de cette carte graphique ajoutée ? => idem demande Akhlan viewtopic.php?f=13&t=848&start=10 Derniere question : J'avais lu le post de quelqu'un qui avait refait un tuto complet d'install (après avoir vécu lui-même toutes sortes de galères) y compris synchro mac adresses logique / physique qui résolvait également les problèmatiques de WOL ... => je n'arrive plus à remettre la main dessus, si quelqu'un l'a bookmarké je suis preneur Merci => ce post était différent de celui-ci spécifique au WOL viewtopic.php?f=13&t=716&start=60#p6936 Le newbie que je suis (même si j'ai déjà eu un syno donc pas de souci de ce côté) est complètement noyé ... : Il y a énormément de doc (trop ?) et de posts (ici et sur hardware.fr) sur ces sujets et peut être qu'un retour centralisé sur ces points va aider plusieurs membres de la communauté... Help ... Merci à ceux qui me liront et encore plus me répondront ldha

For Windows, there is ACPI. System BIOS can be set to S0-S5. Normally, I select S3. When S3, system power can be 6-7W with a ATX power supplier. For XPEnology, the system is DSM4.2, 4.3, some documents said DS3612xs DSM support hard disk hibernation only, rather than system hibernation. I tried, it is true. But most application here is for home although DS3612xs supports at least total 12 hard disks. So power saving is very important. Equiping system with a DC adapter is a very good idea. I tried motherboard with C1037U or G1610T plus 4X(or)5X hard disks, equiping with a DC adapter, the system power is about 24-25WATT while hard disk hibernation. So any guy can find a way to have Ds3612xs hibernate to S3 status? Thanks in advance for any suggestion.

still valid what i wrote about that sas3008 its the most basic sas3 and 918+comes with a mpt3sas.ko in the extra/extra2 but with 918+ there are special risk with lsi sas controllers, you should read the 1.03b/1.04b driver thread, 1st post, its either risking data, or not having disk hibernation or not having smart and sn (also risky) as your board has pcie 3.0 and 4 slots (16x, 8x, two 1x) you can use ahci controllers instead jmb585 or asm1166 for the non 1x slots and jmb582 for the 1x slots you would still have enough performance without extra risks and id 16 disks is you goal then you would still have a 16x/8x slot for a 10G nic (my board is very similar and i use it that way, and with a m.2 nvme to pcie adapter its still possible to squeeze out a additional 4x slot but with two of them you could also use nvme r/w cache) https://xpenology.com/forum/topic/35882-new-sataahci-cards-with-more-then-4-ports-and-no-sata-multiplexer/ or consider 3617 with its native lsi sas support, but you loose i915 driver for hardware transcoding that way

as the cpu only has a tdp of 25w it sound a little high, not sure what the ram consumes but you can tra with just half of it, dsm would work with 4 or 8GB good enough if you pass through a whole controller then dsm should be able to use disk hibernation for the disks also i'm not convinced a baremetal would that good as afaik its not throttling down the cpu at all, there are some scripts that can help https://xpenology.com/forum/topic/19846-cpu-frequency-scaling-for-ds918/ i'd expect a properly working hypervisor to being able throttle the cpu for lower consumption when there is no load you would also loose you r/w cache in a baremetal enviroment

Bonjour, Pouvez vous nous dire votre config en precisant si l hibernation des disques et le Wake ON LAN foncitonne ou pas. Je commence : Asus A8nSLI - Opteron : WOL et Hibernation ne fonctionne PAS. Merci pour votre partage.

Hi there, Please put your build below (in order to create a list) if you have Wake On LAN and/or Hibernation of hard drive working : I start : Asus A8N-SLI / Opteron : WOL and Hibernation not working. Thanks

спасибо за развернутый ответ уже не помню старых замеров своей малютки 414j. буду включать диск после проверки - измерю. по обзоу в сети с 4мя WD red Power Consumption: 36.7W (Access); 8.5W (HDD Hibernation) 4 диска 7200 и 4 диска 5400 обычно дают неплохую разницу (это не только сами диски, но и режимы кулеров по отводу тепла)

Hello everyone! Currently running 1.03b/3615xs/6.2.3 on an old HP workstation. Recently purchased a supermicro 2u server and intend on using that for Xpenology going forward. It has an e3-1220v3, so new enough for the 918+ loader. The backplane is currently connected to an LSI 9211-8i in IT mode. I'm also planning on adding a Mellanox Connectx-3 NIC for 10gb. However, I'm having trouble finding what the best build to run is, and what kind of migration path that leaves me, as I'll be reusing my existing disks. From what I can tell, 6.2.3 is broken when using an LSI controller, with either hibernation not working, or waking up from hibernation causing corruption. Is this still accurate? If so that leaves with with running an older build of DSM. That wouldn't bother me, except I plan on doing an "HDD Migration" using my existing disks, which I believe requires the source and destination machine to be on the same build, or newer on the destination. Any thoughts?

for one thats only true for 918+ and the other thing is even when present since loader 1.04b existed it only came to attention years later, there seem to be lot of users not having trouble with it, there might be other factors involved like what bios version the controller hast a what chip version you could test it with 3 disk in a raid5 and hibernation on, i di provide a extra version with the old driver (that can do sn and smart) you are safe when using 3617, just do a migration with 1.03b 3617 loader and thats it, you cant use hardware transcoding with that but most/all devices can replay higher grade streams so in most cases (in LAN) there is no real need for on the fly transcoding yes, you cant downgrade in a migration step

I originally had the way you suggested. 2x SSD were on the ASMedia SATA on-board connecter and 14x (12x active and 2x HS) HDD's on 2x LSI controller. But that would make a total of 18 ports, that's why I disabled all SATA connectors. But I think you are right, the MB has a total of 8x SATA ports (6x intel and 2x ASmedia) and even though I "disable" it in the BIOS it still counts a port. BTW two ports on one of LSI controller were not even being use, but I can see it counting towards the port count. Yep I do read your posts very carefully :). You have been a great help as I try to navigate to a best solution. Unfortunately with 14x drives and my NAS box mainly used of 4k media library/picture streaming I do need hibernation. It is not being utilized most of the time. Sorry I am not to familiar with kernels. Where can I get the 20141121, is that 3716xs based? Are there any limitation to that kernel? BTW the Intel® Xeon® CPU E3-1285L v4 @ 3.40GHz is a Broadwell with an integrated GPU "Iris Pro Graphics P6300"

i deliberately suggested the other way as it can be happen that even if you disable some sata stuff in bios the kernel will still find the device and still block the ports, its much safer to just have the two cache drives on the 1st two ports its also possible that the bios offers more then the two ports you have usable, i often have seen systems with 4 ports on the board and the kernel blocking 6 ports to be sure about that you could provide the dmesg log, in that one we would see what the kernel finds and how its counted you did read the red marked stuff in my extra driver thread for 6.2.3 about the lsi drivers and 918+ if you want smart you can use the older extra/extra2 that has juns driver but when using disk hibernation it would be risky