Search the Community

Had a quick google around and can't find a straight answer. I'm running a Windows 10 machine with Hyper-V on the top. The disks are set to offline in Win10 then as direct attached LUN's to my Xpenology VM. One or more disks keeps disappearing entirely. I've looked around and found it's likely to be as a result of Windows power options, it was set to hibernate a disk after 20 minutes. I've switched this to 0 so it should hopefully keep it in the system, but noticed there's a 20 minute setting in DSM. Can this be left on? Or should it be switched off? I'm running WD Reds so I know they have their own idle settings built in. Any advice would be appreciated.

Build a new hardware setup, using 3 disks in total. 2 in SHR and one single. Two volumes in total. The single drive I use for downloads, Cloud Sync, Plex video etc. I now use disk hibernation set to default 20 min. DSM logs show disk become active every 30 minutes. So sleep is only 10 minutes. Questions; What is likely cause for waking every 30 minutes, without file tranfers or manual actions? Will all drives wake every time, or can this also be just one of the disks? Does it make sense to keep using disk hibernation or will it just wear the disk? Obviously hibernation is used to save energy and prolong disk life....but does it?

HI all ! @WiteWulf @pocopico After many months of following this thread I was able to play with some VM's (actually Fusion) and successfully install DSM 7.0.1 (918+) on them. Now I would jump on my BareMetal rig, firstly with some test HDDs then with the working ones. My HW is pretty simple (the one in signature): Gigabyte C246-m with Intel i7-9700T CPU, two onboard NICs (i-219 and a 1000e) plus an added NIC (Realtek 8125 2,5Gbe working thanks to extra_lma in Jun's loader 🙏 DSM 6.2.3u3), and two NVMe disks working as RAID1 cache. Now, considering that my mobo belongs to Intel 300's series and so it's SATA controller is 8th/9th gen and therefore I will go for DS918+ setup, some questions for you: To your experience do you expect any problems with the correct recognition of its 8 SATA ports? I need them all! IS there any chance of having both the 2 NVMe working as caching drives as expected? Please if someone could provide a procedure to successfully patch the necessary library, post it in replying to this msg. Thanks! I truly need my Realtek 8125 to work correctly because I've implemented a 2,5Gbe ring that's working very well. But I might consider upgrading to a 10Gb NIC if needed (which one is most compatible at the moment?) If I buy a Synology 10Gb NIC, I would have the chance to use QC? (which now is not enabled because I was not able the change the MAC address in a hardware manner). from a software's point of view I don't need that much: I do not use Docker at the moment. TM MUST work because I absolutely need a backup. It's very important to me. I do use extensively PLEX and I need it, with HW acceleration. The lack of it would be a no-go for me. I do use NextCloud, installed with this procedure . It needs Apache web server, mariaDB and Php. The lack of it would be a no-go for me. It would be nice if Synology Photos works correctly, including the facial recognition. WakeOnLan must work, on all the NICs. The lack of it would be a no-go for me. Sleep should work and HDD hibernation too, as I don't want useless spins of my HDDs. CPU should work at the correct frequencies, I really hate waste of energy and noise. QuickConnect would be nice if it's possible... Last but not least please suggest me the best branch of git which is now more robust and stable, including the necessary compiled drivers. Sorry for the length of my post and thanks and gratitude 🙏 to all who will have the patience of reading it all and answer all the questions.☺️

https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ there is a "older" version 12.1 for that, but keep in mind you might crash your raid especially when using disk spin down for special purpose and tests, extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.12.1 - this version shows s.m.a.r.t. info and serial of disks for lsi scsi/sas but might corrupt the raid when disk hibernation is active (see warning above)

Hi Guys, i have installed XPEnology Version 5 update 5 on my ESXi box. I am using RDM for my data hard drives. i am aware that smart is not functional in this version of XPEnology, however it is causing hibernation issues and my disks do not sleep/standby. they wake up soon after entering hibernation. there is nothing in the /var/log/messages escept that the smart is not able to read disk values on sda,sdb and sdc my 3 disks respectively. is anyone else facing this problem ? is there any workaround for it ? scemd.log May 2 22:27:24 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sda fail May 2 22:27:24 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sdb fail May 2 22:27:24 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sdc fail May 2 22:27:34 DS3615xs scemd: event_disk_hibernation_handler.c:24 Fail to set disk to standby May 2 22:27:34 DS3615xs scemd: event_disk_hibernation_handler.c:32 The internal disks wake up from hibernation. May 2 23:29:45 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sda fail May 2 23:29:45 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sdb fail May 2 23:29:45 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sdc fail May 2 23:29:55 DS3615xs scemd: event_disk_hibernation_handler.c:24 Fail to set disk to standby May 2 23:29:55 DS3615xs scemd: event_disk_hibernation_handler.c:32 The internal disks wake up from hibernation. May 2 23:48:42 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sda fail May 2 23:48:42 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sdb fail May 2 23:48:42 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sdc fail May 2 23:48:52 DS3615xs scemd: event_disk_hibernation_handler.c:24 Fail to set disk to standby May 2 23:48:52 DS3615xs scemd: event_disk_hibernation_handler.c:32 The internal disks wake up from hibernation. May 2 23:59:33 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sda fail May 2 23:59:33 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sdb fail May 2 23:59:33 DS3615xs scemd: AtaSmartRawValueGet(65) read value /dev/sdc fail May 2 23:59:43 DS3615xs scemd: event_disk_hibernation_handler.c:24 Fail to set disk to standby May 2 23:59:43 DS3615xs scemd: event_disk_hibernation_handler.c:32 The internal disks wake up from hibernation. /var/log/messages May 2 23:33:57 DS3615xs upnpd: (upnpd.c:269) no rule to add. May 2 23:34:01 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 2 23:34:01 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 2 23:34:01 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 2 23:34:01 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 2 23:34:01 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 2 23:34:01 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sda fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:34:02 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdb fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:34:02 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sda fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:34:02 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdb fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:34:02 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdc fail May 2 23:34:02 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:34:02 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 2 23:35:03 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sda fail May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:35:03 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdb fail May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:35:03 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdc fail May 2 23:35:03 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:35:03 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 2 23:36:04 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sda fail May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:36:04 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdb fail May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 2 23:36:04 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdc fail May 2 23:36:04 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 2 23:36:04 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:11 DS3615xs upnpd: (upnpd.c:269) no rule to add. May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:56 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:56 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sda fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:56 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdb fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:56 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdc fail May 3 00:06:56 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:56 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 3 00:06:57 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sda fail May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:57 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdb fail May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:06:57 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdc fail May 3 00:06:57 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:06:57 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sda fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sda fail May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdb fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdb fail May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartDataRead(107) read value /dev/sdc fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_temperature_get.c:71 read value /dev/sdc fail May 3 00:07:57 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sda fail May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:07:57 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdb fail May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed May 3 00:07:57 DS3615xs SystemInfo.cgi: AtaSmartRawValueGet(65) read value /dev/sdc fail May 3 00:07:57 DS3615xs SystemInfo.cgi: SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail May 3 00:07:57 DS3615xs SystemInfo.cgi: disk_lib.cpp:417 SmartFirmAndSerialRead failed

Bonjour à tous, Je me retrouve dans une sacrée panade depuis quelques jours : mon NAS m'a annoncé la mort simultanée de deux des quatre disques durs formant le volume 1. ("Le disque dur 2 dans le groupe de disques dans CoNAS est tombé en panne. Veuillez le remplacer"...) J'ai ensuite reçu une jolie notification par mail : "Le volume système (Root) dans CoNAS est entré en mode dégradé. (Nombre total de disques durs : 12 ; nombre de disques durs actifs : 2) Veuillez redémarrer le système, et il se réparera automatiquement au démarrage." Sauf qu'au redémarrage : "Le volume 1 dans CoNAS est planté. Le système peut ne pas démarrer." Et depuis, plus aucun accès... Je ne suis actuellement pas à proximité du NAS, mais j'aimerais votre avis pour la marche à suivre : Je précise que le volume 1 est composé de quatre disques durs en JBOD (1+2+3+8 To) et que ce sont les deux plus petits disques durs qui m'ont lâché. Le tout est installé sur une vieille carte mère avec un Core 2 Duo et 1 Gb de DDR2... Etant donné que l'ordinateur ne se mettait jamais en veille, et ne mettait pas non plus les disques durs en veille (matériel trop vieux ?), j'imagine qu'ils sont morts prématurément. J'ai donc plusieurs questions : comment faire pour réparer la grappe ? (Je suis prêt à racheter un disque, et même à changer de matériel ; j'ai d'ailleurs pensé à un combo Haswell en mini ATX). Les données sont-elles récupérables d'une manière ou d'une autre ?

I am currently running DSM 5.2-5967 update 1 & Xpenoboot 5.2-5644.5. As the subject line says, up until recently (2 updates back?) I was able to hibernate my barebones install of Xpenology. The disks would hibernate & then the NAS would shut down after 30 minutes. Because I don’t run the NAS all the time, I don’t know when the hibernation stopped working. Now when I go into “Hardware & Power” and set the disks to hibernate and click “Apply”, I get a pop-up telling me that “A reboot is required for Memory Compression…”. I don’t have “Memory Compression selected. If I click on “Yes” to the reboot, it takes me to the “UPS” tab instead. Anybody know what is going on? Anybody else having this issue with the same iDSM install as me? Is this on the list of 5967 broken features Thanks PS. Is it normal for the USB key to show up in the “Control Panlel –> General –> External Devices” ? The edited “syslinux.cfg” file always worked for me in the past, just not sure if it shows up here normally.

Hi I am currently setting up an xpen rig with the following specs: - z77-based MB - i7 3770k - DDR3 1066 RAM - 2x 120GB SSDs (RAID1 array -> volume1) - 4x 3TB HDDs (RAID5 array -> volume2) - HDDs are connected to a jmb585-based 5ports sATA controller (PCIe3.0 x4), while SSDs are connected to the onboard sATA3 (6Gbps) ports. - quad port GbE NIC AIC (PCIe2.0 x4) -> Bond connection, 4x GbE using LACP. Network infrastructure is compatible with LACP) - 550W PSU I used DS3617xs (loader 1.03b), DSM 6.2.3-25426 Update 3 Unfortunately, this setup is unstable. On occasions, the connection is lost. The rig is no longer detected by Synology Assistant either. All I can do is a hard reset and then it comes back online. I wonder if it could be a problem with the network connection or if it could be resulting from an issue with sleep management. I already tried to disable memory compression and HDD hibernation. What should I do next to troubleshoot this problem? Thank you very much in advance for your help. Best, -a- PS: after the last hard reset, DSM started data scrubbing on Volume2 upon reboot. Is this useful to locate the origin of the issue?

Disk hibernation does not work correctly even in real Synology devices. As for transcoding you’ll be fine if you have an intel cpu

Thanks so much help It's working!! I install version: DSM_DS918+_25426. NAS works very well. I still have to check transcoding and HDD hibernation Thanks again for your help

I have XPEnology experience since version 5.x on HP Microserver Gen7. I managed to compile 7.0.1-42214 somehow following a step-by-step-guide i found somewhere on the internet with maybe the third Linux distrubution or so. Linux is freaking crazy. It is working somehow, but compared to 6.2.3 it comes with limitations. These are my results on HP N54L: Hardware: HP Microserver Gen7, previously running fine with 6.2.3 DSM Version: DS3615xs 7.0.1-42214 Bootstick created using the toolchain with VID, PID, MAC, Ser. No. updated Booting fine, VGA output stops at 'Booting the kernel', which seems to be OK No connection using internal LAN -> added Intel PRO/1000 PT Machine now appeared in Synology Assistant as migratable I chose not to keep my settings for having a clean install of DSM DSM installed without any hick-ups Status: - Tab General in Info Center is blank - Volume and shares from 6.2.3 are still there - Volume manager asked for data scrubbing, which was successful. - WOL works using the usual shutdown script - Powersaving script fails with invalid parameter or so - New script (note there are 2 lines for the 2 cpu cores): #!/bin/sh echo "powersave" | sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "powersave" | sudo tee /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor - Note: scaling governor 'conservative' is not supported! Only performance and powersave This means 1500 MHZ (N40L) or 2200 MHz (N54L) constantly by default This is a kernel limitation as far as I understand, so no easy workaround! - but adjusting the frequency works! Instead of a scaling governor you might want to chose a fixed frequency between min. and max. frequency See supported frequencies under /sys/devices/system/cpu/cpu0/cpufreq/ Example for 800 MHz (same as governor 'powersave'): echo 800000 | sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq Do the same for cpu1 - HDD sleep does not work, even with modified scemd.conf :-(( - No idea if face recognition or docker are working as I only use it as a file or rsync server - packages.synocommunity.com could be added, this failed on my 6.2.3 install Again: I am not an expert. Opening the Linux terminal is like opening the gates to hell for me. My Linux is even much worse that my French. And I speak 4 words in French fluently without knowing their meaning. Conclusion: Start adding Intel PRO/1000 PT on bare metal before trying anything else. For now I would recommend to stay with 6.2.3 on HP Microserver, because: - Tab General in Info Center stays blank - No HDD hibernation - No dynamic CPU frequency

Hello. I would like to ask for a little help here. I have two HDDs in my box. One is connected to SATA port and another to "eSATA" (edited synoinfo.conf). What I would like to achieve is, that SATA drive would be on 24-7 and eSATA drive would go to sleep when not used (since it will only be used for backup a few times per day). Unfortunately DSM has only one setting for hibernation that works for SATA and eSATA. I tried putting eSATA to sleep with hdparm -y, but it wakes up after a few seconds for some reason (nothing is using it). If I set HDD hibernation in DSM, they go to sleep properly, but I don't want the first one to go to sleep all the time. Has anyone solved similar problem? The other option is see is, that I set timer in DSM and then make a script that would access first HDD all the tiem, so it won't go to sleep. But I am looking for somewhat better solution. Thanks

It may seem a stupid topic but I don't know if my system/hdd hibernates. I know there are logsbut I don't know where to find or whether I have to enable. Could anybody tell me where to find it. Please, make it noob proof. Thank you.

J'ai exactement le même probleme Quelques compléments D'information Ce ne sont pas les cables , changés partout Ce n'est pas le switch , changé J'ai 3 nas sous Xpenology DSM 6.1 Un seul a le probleme meme si les configurations réseau sont identiques a tous point de vue sur les 3 . Le probleme est qu'en download sous Samba le Nas n'envoie qu'a 2mo/sec il le fait aussi vers tous les PC , et même ma shield et ma TV ( ca lag.... ) Quand Le Nas n'envoie qu'a 2mo/s sous Samba , il n'y a aucun probleme en Upload vers le Nas , Il n'y a aucun probleme en Download depuis le Nas , sous File Station , Ni en FTP , Ni Si on accede via Samba a l'adresse Ip et non via le nom réseau . Souvent Un redemarrage regle le probleme ( mais pas un arret/demarrage ) provisoirement. Avec une autre Carte reseau ca le fait aussi , meme si cette carte ne rencontre aucun probleme sur les 2 autres Nas Le Nas peut envoyer apres en redemarage a 110mo/s puis recommencer a n'envoyer qu' a 2mo/sec apres une heure d'utilisation . J'ai pensé a l'hibernation de la carte mere via le bios, tout desactivé et aucun changement .

this is one frustrating feature i could never fix. There's no hibernation on my Ds918 image, drives spin up as soon as i spin them down manually (hdparm). Meanwhile electricity costs explode, my electricity provider bankrupted, and the drives which are needed for 1hour a day, make noise reminding me of this every day, just like the main fan makes horrid noise (unfixable issue on HP Gen10 thanks to weird fan setup, i've burnt one server playing with cables/adapters/regulators). surprising to see someone can spin down disks, i'd believe a complete hibernation is possible (not in my case), but how you can spin down disks on live system with / mapped to the RAID1 (md0)? the good ole' trick with installing on one drive, then add raid drives doesn't work as DSM will expand on all drives as soon as it detects them. i have 2 standalone drives and 4 RAID drives, so i could still have a "system RAID" active if i shrinked the system RAID(+swap) from 6 to 2 hdds. but i worry DSM would complain. i'd have to also create a dummy allocation there to make sure no RAID fits. the fix above didn't work. i remember very well drives couldn't spin down on an empty installation either. all i am reduced to now is read the bad advices how running drives 24/7 is 'healthy' (a hoax that spreads on internet like "BTRFS is not good for RAID").

On DSM 5.0 HDD hibernation used to work fine, though on every version after the disks won't spin down. Worth noting I switched from an ASUS H81M motherboard to an MSI H81i. I have tried ejecting the USB drive but to no avail. Does anyone else have trouble with HDD hibernation? Anyone know a fix?

Finally we've got some time to respond to the questions. We will try to respond to as many as possible so stay tight ======= Why there's a problem with compiling drivers when syno didn't publish kernel sources? This is going to be a separate post addressing "why you cannot randomly grab drivers and compile them" so we can link to it. Let us explain where's the problem, this applies to many questions really. There are few major issue with compiling drivers against a different sources. The three major ones are: 1) Versioning of syno kernel's is broken due to backporting 2) Drivers modification 3) Kernel <=> driver modification 4) Data structures missing in toolchains for in-tree drivers Now let us explain each one of them separately and why this is an issue. There's a lot to unpack here. First lets address few terms which are used in kernel development: "in-tree" = code which exists within the source of the kernel; in terms of drivers it means you will find it under "drivers/" (e.g. in drivers/scsi/mpt2sas) "vanilla kernel" = source of the kernel which is the official version from kernel.org "kernel headers" = .h files present in the toolchain. These are NOT all kernel's .h files but only a subset of public API kernel provides. You will find these under "include" or in the syno toolchain. What's important they DO NOT contain private interaction between modules. That's why if e.g. mpt3sas driver wants something from mpt2sas you cannot use toolchain to compile mpt3sas and you NEED full sources. "upstream it" = make your custom patch for the kernel and get it accepted into the normal kernel sources 1) Versioning & backporting Syno, like many other companies, take the kernel and modify it in house. This is something which kernel devs don't really like but since it's an open-source project everyone can. However, after some time these companies realize they want new features from new kernel but cannot get them as their modifications no longer apply to a new version. What they do is "backporting". They grab their e.g. 3.10.108 which was modified to oblivion, then download the e.g. 3.19.0 and check commits which add features they want. They get that commit and apply to their 3.10.108 making it 3.10.109. This is incorrect and broken. But that't not the biggest problem. In case you don't see it: this poses a HUGE problem for using drivers from the vanilla kernel. Often times if you take a driver from vanilla 3.10 you will realize that suddenly doesn't work at all... as in fact they previously lifted a newer one from 3.20 and stuffed it in 3.10. Good luck loading such driver and using it. For that reason alone you CANNOT use vanilla kernel code as you don't know which version of the code has to be used. Sure, there are ways to figure this out, but the only sane approach is to use the source provided by syno. In case of small-ish bumps in kernel it's usually safe to get e.g. driver from kernel from 3.10.105 and fake the version compiling for 3.10.108 hoping not much changed. 2) Drivers modification Syno modifies in-tree drivers directly. To be honest they have no way around it as they apply vendor-specific hacks for e.g. timing bugs in certain chips. They should upstream it but... that's a different story and it's not as easy as it seems. Depending on WHAT was changed in the driver sometimes you can use kernel from a different kernel version. How do you know it's safe? Well... it's hard. If you don't have the sources for the new kernel (since if you did you wouldn't bother lifting the driver from an older version) you cannot know if the data structures changed. If they did you're pretty much toasted. Languages like C or ASM (or hardware in general) doesn't have magical way of discovering sizes of things. Everything is based on static assignment (ok, not everything, but lets make a simplification here). This means if syno decided to add a field to a struct [it's like an object] in mpt3sas driver and that field was added to a struct used ONLY in mpt3sas driver you can probably load the old driver and be fine. However, if they added a new argument to a "public" function (function used outside of the mpt3sas driver) or a new field to a struct used externally from the mpt3sas driver things may APPEAR to work. Every time such function is called or struct is used more and more memory and/or stack gets corrupted. Eventually you will crash something very badly and you will be lucky if that was at least the driver and not something unrelated which was just in the same area. In kernel there's virtually no protections of one piece of code breaking memory of the other. There are small protection for the kernel CODE itself and some sensitive areas but it's not like in the user space where one process trying to write into memory of another process will simply be killed - in the kernel you just corrupt the memory silently. 3) Kernel <=> driver interactions Scrolling through the questions we saw that some of you load drivers and see missing symbols. Well, this is the effect of 2). When they modify the drivers they often add their own hooks by just placing a f... gSynoFoo() call somewhere in the driver. Honestly we think it's very sloppy but it is how it is. The issue here is two-fold: if you compile a driver from vanilla kernel you will not have these calls so things may look correctly... but these calls were placed there for a reason and other things exepect them to happen. Sometimes the issue may be really small like performance drop or hibernation not working correctly. Sometimes you may step into a data loss with a certain controller which syno fixed in their kernel after getting a possible fix from the manufacturer... you don't know. if you try to add e.g. SAS to a non-SAS model things break badly. This is because it's not as simple as flipping the flag in synoinfo. By doing so you're telling the DSM "this model supports SAS". But the issue here is that models which REALLY support SAS have A LOT of code which is compiled only and only when the kernel config option for SAS was enabled. This config option being disabled literally REMOVED a bunch of code from many places when they compiled the kernel without SAS support. That's also the reason why getting SATA boon on 918+ was so challenging as the SATA-DOM code is literally removed on 918+. Bottom line is don't try to activate functions which depend on the kernel features being present. You can tweak number of disks, supported number of cameras and other user-land features but not re-enable features which are partially kernel and partially userland. It's like trying to pump diesel fuel into gasoline car after drilling a larger hole to fit the bigger diesel nozzle into the tank. There's no straightforward way to KNOW if the feature you want to activate has a kernel component. However, going through ALL options in synoconfigs/KConfig.* files will give anybody an idea what sort of things can or cannot be activated. In general anything involving in-kernel drivers is a no-no (e.g. iGPU acceleration will not work on 3615xs most likely but NVidia GPU probably will). 4) Data structures missing in toolchains for in-tree drivers You cannot get the code of a in-tree driver and compile it against the toolchain. This is because in-kernel drivers have access to many more things and link internal kernel files. Should they? Most likely no. However, the kernel is 30 YEARS OLD codebase and only recently they started to encapsulate drivers from using internal things. In most cases it's better to stick to the hardware which is officially supported. We have v7 sources for geminilake which we took some hints from (e.g. about synobios structures). If there's a particular driver we can look and compare with v6. However, if there's anyone who has experience with drivers (@IG-88?) we can share the archive in a PM as syno pulled it from SF. Why they did pull it? It's possible it contains code from e.g. broadcomm which is under an NDA and should never be published as it's not GPL.

Maybe I'm an idiot but I followed the guide here and can't get root to work in WinSCP. Logging in as admin using Putty I get as far as 5) find text #PermitRootLogin prohibit-password but in sshd_config I see no lines like the above text to edit. Im running 6.2.3.-25426 on DS3617xs and need root to enable SHR plus fix no hibernation and no WOl problems. Any help appreciated I am a linux novice.

Hi, on my system the HDD Spindown / Hibernation is not working. I have testet it with no Packages and more (clean Install) but in the logs there is no entry with hibernation. In the DSM Settings i have activated the function (10min). Over SSH ist don´t work too, have anybody an idea where the problem is? Driver or BiosSetting Problems? My Mainboard is a P8H67-I with a i5 CPU. DSM 5.2-5565 Update 2 XPEnoboot 5.2-5565.2 hdparm -y /dev/sdc && hdparm -y /dev/sdd && hdparm -y /dev/sde && hdparm -y /dev/sdf /dev/sdc: issuing standby command /dev/sdd: issuing standby command /dev/sde: issuing standby command /dev/sdf: issuing standby command Thank you.

Since I updated to the new dsm5.2u1 (with XPEnoboot 5.2-5565.1) my disks won't hibernate (or spin down) for lower energy consumption. I have a HP N54L with USB stick. Does anyone have the same issue? Is it solvable? Thank you!

The thing goes into hibernation at 6% battery, can I reduce this to 1% safely?

Hi all. I have Nas made on gigabyte GA-C1007UN. Yesterday I added another drive (second) to my NAS. 1st disc was in SHR mode and the second drive, I did not specifically included in the raid, and created as a separate in BASIC mode. The implication is that it will often idle and I like that he was basically in hibernation mode. However, I found that the disc does not fall asleep. In the settings set 10 minutes. I also found that something is constantly read/write to the drive, but I can not find what. I turned off all the packages, but the activity continues. Of course the disc will not go into sleep mode. Leaving NAS with almost all services off for a long time and including the journal Sleep mode discs, I saw that the drive goes to sleep sometimes, but often wakes up ... I need help, please. Sorry for my bad English.

Hi gang. Im quite new to this.... I got XPEnoboot_DS3615xs_5.1-5022 update 3 running on ESXi 5.5u2 My config is a core i5 with a DELL PERC H310 Sas controller installed as passthough. I see a couple of issues that i can not figure out... every once in a while my HDD exists hibernation, its not related to the hibernation timer, which is default 20 min... Last time it was 30 min and 6 sec., before that it was 26 min and 1 sec and before that it was 34 min and 12 sec... that really wird.... why dont they stay hibernated? When i look at the Storage manager it say ZERO hot spares, but looking at Control Panel/Storage is shows 1 disk as not initialized but as hot spare. Still looking in control panel/Storage it shows HD model numbers (mount in the sas controller) but no temperature (-1 C), status Normal.. Going back to Storage Manager/HDD Serial numbers is "Loading..." Same with firmware... and SMART not supported. but why? im pretty sure my WD RED 4TB disks should support SMART. Any body have any ideas for my missig smart? and for the hibernation issue? /Stig

What bootloader did you use in the end? I was doing tests and only 1.03b (+extra) worked but there are certain things that did not work correctly with DSM. - disk hibernation does not work. - When using that bootloader, the transcoding doesn't work. - Fan speed does not change automatically - Network speed using different protocols is low (I have tried FTP, WebDAV, and SMB). According to my tests, with TOS I reach the maximum that the ethernet cable can give (approximately 115Mb / s). With DSM, it reaches about 30-40 Mb / s, or even less depending on the protocol you use.

Hello community, I have the following problem. I have successfully installed DMS 5.0-4493U2 on my ESXI / Hypervisor 5.1. I configured it with a PCIe SATA controller "Digitus DS-30104-1" (with MARVELL 88SE9230 chipset) wich is passed through to the VM XPenology via vT-d passthrough. Everything works first very good and all hard drives are recognized. My problem is that I would like the disks to use spin-down function. I've also read that just needs to get out at a native installation the USB stick. But what do i have to do in my Case? The "USB Stick" is in my case a VM HDD. I hope you can help me.