Search the Community

Salut à tous J'ai monté mon NAS avec XPEnology DS3612xs DSM 4.2 build 3202++ (repack v1.0) et tout fonctionne à merveille. J'ai juste deux questions à vous poser. 1- Est-ce que l'hibernation des HDD fonctionnent sur votre NAS? Il est activé dans syno au minimum (15 minutes je crois). J'ai l'impression que tous mes HDD fonctionnent tout le temps, même si je n'y accède pas (pas vérifier tous les périphériques chez moi mais c'est ce que je pense). Alors, comme je l'utilise principalement pour faire des backups et comme serveur DLNA, ça me dérange pas d'avoir un peu de temps mort lors de l'accès aux fichiers. Cela me permettrait de moins faire chauffer ma gang de 4 HDD empilés! 2- Avez-vous un logiciel ou un extension que je pourrais intégré directement dans le syno pour qu'il fasse automatiquement des backups de mes autres machines (et non un backup du synology)? Faut-il vraiment que j'installe un logiciel sur chacune de mes machines pour qu'il fasse un backup à xx:xx? Quels logiciels utilisez-vous? Merci à tous! yaaa4

there are some disk specific log files and the general "messages" log imho the safe way to exclude any dsm/driver related problems would be to change to loader 1.03b and migrate to 3617, no nvme and hardware transcoding with that but it has synologys lsi sas drivers they use for the business units, thats supposed to work stable, with 918+ is still added and not as safe as the "original" (as we can see with the smart and hibernation problems) by using 3617 (at least temporary) you could rule out some factors to drill down to the source of the problem did the same thing with my system, just swapped the loader and installed dsm 3617 over the 918+, can be reverted the same way, just insert the "old" 918+ loader and install 918+

LSI controller in IT mode yes, but not using Hibernation no In theory it could be both a PSU issue, or a cable - But both has been checked (Tried new cable and new PSU was used during the new build). It did happen again on a reboot yesterday.. So happens sometimes on either power off/on or reboot. (Had it happen 3 times now, 2 times on shutdown/startup and once on reboot) Havent checked /var/log - Do i need to look for anything specific there? Did a quick look or two in dmesg but could only see a message when the raid was degraded from what i could tell. Appreciate your help

lsi sas controller? 918+ has issues when disk hibernation is active, 3617 is the best alternative in that case (beside not using disk hibernation) can also be psu and maybe a cable problem did you check the logs in /var/log/ ?

Bonjour à tous, J'ai reçu et installé mon N54l avec Xpenology depuis quelques semaines, je viens de le mettre à jour aujourd'hui 4.2.3202 -> 4.2-3211 mais j'ai toujours un soucis pour la mise en hibernation des disques dur qui ne fonctionne pas comme le reveil du serveur via la carte réseau (mais qui n'a que peu d'importance pour moi), J'ai lu qu'on pouvait modifier le Bios, mais je ne comprends pas trop si cela va résoudre mon problème ou pas, autrement à par cela tout fonctionne bien même avec la nouvelle version 4.2.3211 que j'ai récupérer ici : http://www.av100fun.com/viewtopic.php?f=7&t=285203&st=0&sk=t&sd=a L'erreur: Si quelqu'un à des informations je suis preneur Merci d'avance Ma config: N54l 2go 2 x 3to (WD RED) 1 x 2to (WD Green) Carte Graphique HD6450 Silent (qui ne me sert pas à grand chose finalement) Logiciel: Xpenology 4.2-3211 IPKG Tâche Cron (j'ai un peu galéré pour installer cela)

@IG-88 Can you confirm that the errors in seeing in messages are due to the smart info being disabled via the driver extension on drives attached to my LSI card? I can see in storage manager that the the all the drives attached via the LSI card is missing the following information. If so, guess its time to invest in a PCIe JMB585 controller instead? (Shame, i like the thin cables from the LSI compared to normal sata cables) If i change it to a new controller, i could just move them physically and DSM would work the new disk order of the raid out on its own, right? It should be mentioned that i do not use hibernation.

what controller? the normal onboard sata can't be a problem, if its a lsi sas then 918+ can have issues when disk hibernation is active imho 3617 is a better choice as it has some newer drivers then 3615 and supports more cpu cores, just a better 3615 2-3 years ago there might have been some packages that where available for 3615 bot not showed for 3617, that should not be much of a thing now and if you have the spk file at hand you can change the INFO file make it work i'd say make sure the hardware is working by using 3615 or 3617, if you don't need hardware transcoding and nvme you are fine with 3617 (its even better suited for ssd raid's as of F1 mode that 918+ does not have)

Hi, may I ask if v1.04b loader for 918+ with mpt2sas under 6.2.3 still haven't issue with HDD Hibernation? Is there any solution to re-gain the HDD hibernation under this combination? Thanks a lot!

Unfortunately, you will not be able to run the Virtual Machine Manager on the AMD processor on the N54L. This means that if you want to run multiple operating systems on the box, then it is probably best to carry on with ESXi. There is a thread on here about running virtualbox under DSM but I can't say whether that is a viable option. I started running my box under ESXi and went bare metal when DSM was the only thing left on the box. I didn't notice any significant speed difference. The latest version that the N54L will run is 6.2.3 with the 1.03b DS3617xs loader and that works for both bare metal and virtualised. You must turn off C1E in the BIOS. If you are going bare metal and disk hibernation is important then maybe start with 6.1.7 and 1.02b. Bear in mind that if you go this route and you install a package that touches the disk regularly (as I have) then the disks won't hibernate anyway. Ignore all discussion about the releases in between 6.1.7 and 6.2.3.

This is fair. I suppose the vagueness of my question was regarding the vagueness of my uses. When I got my 418, I figured I'd just be using it as a nas, full stop. But I found other things I could do with it... My current use (and intended use, limited by functionality of the 418 unit) is: - Plex server, on network, off network. 1080p, shared library among myself, family, friends. (current hardware sucks for off-network. Realtek CPU) - Offsite backup for friends, in-network versioning history + backup for me. When a friend gets his server set up after the move (non-synology), I'll be using his as my off-site backup. We have an agreement where I can back up to him, and he can back up to me to maintain different geographical locations - Right click -> get share link. Don't care about the quickconnect service - Download station+VPN in docker(unable to do this at current). Or possibly in VM w/ another instance of DSM. Undecided yet. - Want to use active backup for business, though this isn't a deal breaker. Currently run backups + versioning w/ easeus to the NAS - Access via DDNS when off-site. Currently using synology.me, but I can switch to anyone. Don't care who, only that it works - BRTFS + SHR + Scrubbing + compression. Do that now, want to stick with it. Keeps bit rot away, scans drives to see if there are any angry sectors, can mix and match sizes + expand pool easily. I like the ecosystem. - I don't care about drive hibernation, I keep mine spinning 24/7. But losing access to SMART metrics is a point of tension for me. Any alternatives here to monitor drive health?

The limits on using Synology cloud services are self-imposed (by the community) and enforced by Synology (through legitimate serial number verification). FWIW, HA services seem to be hit or miss. Fan and beep control do not work because they rely on Synology proprietary hardware. Drive hibernation is a bit finicky, and SMART is not functional with all possible hardware combinations. Does VMM not work, or does it just suck? XPEnology has the ability to run as a VM under ESXi or other hypervisor, so reliance on VMM is less of an issue for those who need accompanying VMs. Those are a few that come to mind, but I'm sure I'm missing some significant items. It might be more efficient if you indicated what things you were interested in. Nobody uses or tests all the functionality from the Synology ecosystem.

no, that card is a r8168, check its pci id and you will fing out anyway there are drivers for r8168 aka 8111 and r8169 present the list in the older threads for 6.2 are still valid https://xpenology.com/forum/topic/12859-driver-extension-jun-103a2dsm62x-for-ds918/ can't help much with that, still try to use 918+ 1.04b, it can handle uefi and your cpu might be supported afaik it does as long as its in IT mode (usually a different firmware to flash from the default) also read the 1st post about the problems realted to this hardwre and disk hibernation check your /var/log/dmesg for information about the driver (mpt3sas) loading

this thread is about dsm 6.2.3 and you should read about the problems with lsi sas controllers with 918+ in the 1st post of this thread you should be able to update to 6.2.3 and use 0.12.1 or 0.13.3 extra/extra2 if using 0.12.1 you should disable disk hibernation

the only way to reproduce what was seen on your system was to use the later versions of the extra/extra2 (like 0.13.3) where all files where renewed with fresh compiled ones from synologys recent kernel source that would not crash raid sets with disk hibernation

did you find if hibernation is working ? how can i find if hdd hibernation is working or now..

I have a Fujitsu e734 laptop in the following configuration: cpu i5-4300M ddr3 1x4GB Intel® QM87 chipset3 Lan Intel 1217LM Gigabit 2xsata (2x1TB) 1xesata (no disk) 4xusb 3.0 (only one boot flash drive) Loader v1.04b DS918 + Installation and configuration works fine. But neither disk sleep nor xpenology sleep work. When I click turn off xpenology, it turns off without any problem and I can wake it up via WOL in Synology Assistant. But it doesn't work, after clicking "control panel / hardware and power / power plan / hdd hibernation / auto power off" How to solve the problem?

No problem. I would recommend that before you start you should back everything up anyway. Unfortunately, there isn't a "How to upgrade a Microserver Gen 8 to latest" step by step tutorial, but there is certainly enough information to get you going. The method is: 1) Create a new USB with the loader that is appropriate for your hardware and the release you are going to, 2) A bit of housekeeping to delete a directory from your old xpenology system 3)Download the .pat file for your chosen release from the Synology download site to your PC 4) Boot the new USB. connect via find.synology.com or Synology assistant and choose manual install for the file you downloaded. So. First of all, which release and which loader? See here====> The answer is 6.2.3 and loader 1.03b (either DS3617xs or DS3615xs) and ensure that your G8 is booting in CSM (legacy) mode UNLESS disk hibernation is important in which case 6.1.7 and loader 1.02b. The general method for the upgrade is here ===> The method is good but you will need to apply it to your chosen release and loader. Now. Before you boot the new loader to start the installation, you MUST do this ==> Or your new system will come up and then all the network services will stop! There are a number of fairly recent threads about updating G8 machines so they can be useful. If you have questions or encounter problems, come back.

Best chance for that is to do a passthrough of the SATA controller on the motherboard to your VM so that DSM can directly manage the disk. There are issues with spurious/unimportant log messages being frequently written to the logs which inhibit hibernation. It's a bit of a chore to fix, but see these links: https://xpenology.com/forum/topic/29581-suppress-virtual-disk-smart-errors-from-varlogmessages/ https://xpenology.com/forum/topic/34121-hibernation-doesn’t-work

i'd suggest to update to 6.2.3 and check for crashed drivers in dmesg with 6.2.1 and the original extra.lzma i'd expect some drivers crash on boot (that's the reason your onboard broadcom failed) and that can results in restart and shutdown not working when using 6.2.3 the old original extra.lzma will work again properly (synology reverted the changes from 6.2.1/6.2.2) and you onboard nic should be working again if disk hibernation does not work with 6.2.3 then its because of log activity, fix it with this https://xpenology.com/forum/topic/32861-hdd-fail-to-hibernate-after-upgrade-from-622-to-623/?do=findComment&comment=179577

generell lohnt auch ein blick in die logs um zu sehen was dort an meldugen steht wenn es schon mehrfach vor kam dann lohnt auch eine statistische betrachtung die strom und sas versorgung ist in 2 x 4 geteilt, wenn das problem immer auf einer 4er seite ist dann sind es ziemlich sicher kabel probleme, wenn es sich verteilt dann kann man aber leider nicht viel sagen, es könnte dann auch noch an den kabeln liegen oder am netzteil (selbst unverträglichkeiten platte/controller sind nicht auszuschließen) ganz allgemein ziehen 2.5" platten nicht so viel strom aber es kann trotzdem am netzteil liegen das log könnte auch aufschluss geben ob die platten im laufenden betrieb ausfallen oder evtl. nur beim hochfahren probleme machen auf grund von alten threads würde ich 1.04b 918+ vermuten und da drängt sich auch das disk hibernation problem auf das erst bei 6.2.3 aufgefallen ist aber schon immer existiert, also nachsehen ob die aktiv ist und abschalten, evtl. auf neue extra.lzma mit 6.2.3 umstellen (keine temp und smart infos) oder auf 3617 wechseln https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ erste priotität (nach disk hibernation abstellen) sollte aber ein backup haben, wenn man hier weiter rumspielt können auch schnell mal mehr als 2 platten aus dem raid fallen

How can check, if the HDD hibernation is working ? I enabled the function and the log, but doesn´t find any entries on the protocol center about it

По принципу "лучше поздно чем никогда" отписываюсь о текущих успехах в борьбе с "бессонницей" у хренологии. По материалам темы в английской части форума сделал свой вариант исправленного файла /etc.defaults/syslog-ng/patterndb.d/scemd.conf # begin scemd.conf patch to suppress ioctl messages filter f_scemd_ioctl { program(scemd) and match("polling_.*ioctl\ device\ failed$" value("MESSAGE")); }; #log with no destination and final flag = discard log { source(src); filter(f_scemd_ioctl); flags(final); }; # end scemd.conf patch filter f_scemd { program(scemd); }; filter f_scemd_sev { level(err..emerg) }; destination d_scemd { file("/var/log/scemd.log"); }; log { source(src); filter(f_scemd); filter(f_scemd_sev); destination(d_scemd); }; После этого сообщения в логе "ioctl device failed" из /var/log/scemd.log пропали, а в Log Center появились сообщения вида "Internal disks woke up from hibernation". То есть какой-то из двух дисков всё-таки иногда засыпает, но какой и надолго ли - непонятно. Начал искать, где бы посмотреть подробности. Пока всё что нашёл - вот такого типа записи всё в том же /var/log/scemd.log 2020-11-15T00:32:20+05:00 synoserver scemd: led.c:270 Enable power & phy LED 2020-11-15T00:32:29+05:00 synoserver scemd: event_disk_hibernation_handler.c:44 The internal disks wake up, hibernate from [Nov 14 23:59:36] 2020-11-15T02:50:09+05:00 synoserver scemd: led.c:270 Enable power & phy LED 2020-11-15T02:50:17+05:00 synoserver scemd: event_disk_hibernation_handler.c:44 The internal disks wake up, hibernate from [Nov 15 02:04:16] 2020-11-15T04:32:09+05:00 synoserver scemd: led.c:270 Enable power & phy LED 2020-11-15T04:32:16+05:00 synoserver scemd: event_disk_hibernation_handler.c:44 The internal disks wake up, hibernate from [Nov 15 04:30:47] То есть какой диск засыпает - по-прежнему непонятно (попробовать отследить по индикаторам на корзине?), но есть данные когда заснул и когда проснулся. По просмотренным меткам времени в логе за последние несколько дней получается, что диск засыпает до десятка раз за сутки, но спит не более часа. Есть подозрение, что виновник - Transmission, даже в простое что-то регулярно пишущая на диск, так как стороннего постоянно запущенного больше ничего нет. Буду проверять эту версию.

also, note that HDD hibernation is broken in 6.2.3/1.03b in case you try to use it....

Just a quick feedback to tell I managed to restore hibernation with the workaround found on an another post : I accessed to my NAS with Putty ; edit scemd.conf in /etc.defaults/syslog-ng/patterndb.d/ using vi and replace : destination d_scemd { file("/var/log/scemd.log"); }; with : destination d_scemd { file("/dev/null"); }; Reboot and that's all !

I'd lost hibernation since my upgrade to DSM 6.2.3 (on Baremetal DS3615xs). The workaround did works also for me to. Thanks a lot.