toshas

В данной теме это оффтоп, но всеже: для 6го обновления к 3827, эти обновленные скрипты являются опасными? Для сборок 4.3 не происходит никакой перезаписи, там же не использовался загрузчик gnoboot/nanoboot Спасибо! storagehandler.rar volumehandler.rar

/usr/syno/synoman/webman/modules/StorageManager/storagehandler.cgi /usr/syno/synoman/webman/modules/StorageManager/volumehandler.cgi Was changed... Is it possible to manual download and apply patches ?

After update xpenology was auto-rebooted and now works fine. There is no any "strange" message. All is as usual. p.s. N54L with Trantor's beta7 (4.3 3827)

According to viewtopic.php?f=2&t=3799 viewtopic.php?f=2&t=3802 there is some strange behaviour of DSM 5.0U4 update. Does anyone tried apply U6 (the same as 5.0U4) to 4.3 3827 build ? Thanks!

Trantor, but your beta7(8) based on 4.3 3827 seems to be secure. It can be updated to Update2 or higher.

Do you know anything about recent OpenSSL bug ? Vulnerability is described here - http://heartbleed.com/ . You can test your nas hare - https://filippo.io/Heartbleed/ . It was fixed in updates for 4.3 and 5.0.

Which version of xpenology do you have (4.2/4.3/5.0, any updates) ?

Thanks, vtrchan! Very cool design.

Hi! You can use sheduled task (custom script/smart check). It is safe. These action only modify /etc/crontab file, you can check it via "vi" command. Do not use sheduled poweroff or wakeup. These requires changing bios parameters and synology bios is not the same as n40/n54 bios, thus you will get reset issue.

Hi! 4.3 patch is already out - http://www.synology.com/en-global/suppo ... 7_update_2 Your beta7 can be upgraded to it without any issues. Where do you been ? We started worry about you.

Hi! Do you use router or firewall ? What kind of ports is open to internet (web/ftp/smb)?

How to schedule a data scrubbing ? Synology has software raid. There is one weak point of soft-raid - data will be checked only during read/write access to this data. So on raid1,raid5 (and even on raid6 in worst case) is possible such situation: 1. one hdd fails 2. hdd replaced by new one 3. synology start data recovery 4. old data on another hdd has bad sector (which wasn't tested in near past) 5. synology marks volume as read-only 6. all data (several TB ?) should be moved to new place with partial data lost. To prevent this situation periodical data scrubbing is strongly recommended. Even in 5.0 beta there is no way to create schedule for this job. http://forum.synology.com/enu/viewtopic.php?t=65340 http://forum.synology.com/enu/viewtopic.php?t=78392 http://forum.synology.com/enu/viewtopic.php?t=23454 http://forum.synology.com/enu/viewtopic.php?t=8926 So the question is: Could someone to share script for periodically checking and repairing raid volume (maybe even with email notifications) ? thanks a lot!

How to schedule a data scrubbing ? Synology has software raid. There is one weak point of soft-raid - data will be checked only during read/write access to this data. So on raid1,raid5 (and even on raid6 in worst case) is possible such situation: 1. one hdd fails 2. hdd replaced by new one 3. synology start data recovery 4. old data on another hdd has bad sector (which wasn't tested in near past) 5. synology marks volume as read-only 6. all data (several TB ?) should be moved to new place with partial data lost. To prevent this situation periodical data scrubbing is strongly recommended. Even in 5.0 beta there is no way to create schedule for this job. http://forum.synology.com/enu/viewtopic.php?t=65340 http://forum.synology.com/enu/viewtopic.php?t=78392 http://forum.synology.com/enu/viewtopic.php?t=23454 http://forum.synology.com/enu/viewtopic.php?t=8926 So the question is: Could someone to share script for periodically checking and repairing raid volume (maybe even with email notifications) ? thanks a lot!

Please remember about power consumption too. N40L has 15w TDP and N54L has 25w TDP. (N40L + 2x2tb WD Green = 31w in hdd hibernation mode) For 24/7 home use it can be important. Just for NAS (w/o torrent, media transcoding and etc.) even N36L is enough (transfer speed is equal).

I user before bays(?) BIOS 41 and it worked, recently I have updated to the latest one from German site and it still works. Do you perform any bios setting modifications? (virtual ram size to 32, sata mode to 3.0gb/s or etc.) Even with default bios settings xpenology works fine! Bios reset is annoying thing by itself.

By default DSM 4.2 has no "on battery" and "on line" UPS notifications. This ability was added later only in DSM 4.3. I want to share solution How to add these notifications in DSM 4.2: (original post was found on synology forum http://forum.synology.com/enu/viewtopic ... 60#p255546 ) Here is attachment of patched files (Trantor build 1.2 DSM 4.2 3211). Place files from UPS_notif_mod to 1. /usr/syno/synoman/webman/texts/enu/notification_category 2. /usr/syno/etc/notification/notification_filter.setting 3. /usr/syno/synoman/webman/texts/enu/mails 4. /usr/syno/bin/ups.sh 5. /usr/syno/bin/synoups Place files from UPS_notif_mod_rus to 1. /usr/syno/synoman/webman/texts/rus/notification_category 2. /usr/syno/synoman/webman/texts/rus/mails For other languages change files in corresponding folders. UPS_mod_4.2_3211.rar

emilk,shteve Be aware APM (and DSM sheduler) resets your bios to default state during every sheduled poweron/poweroff. I recently wrote about it on that thread viewtopic.php?f=2&t=1789

HDD hibernation (and System hibernation (for native-syno users)) issue is one of the biggest problem on syno devices. proof-link http://forum.synology.com/enu/viewforum.php?f=83 I played around it several weeks (N40L, Win enviroument, Trantor's 3211 1.2). And now I can share some tweaks. First of all you should stop all packages. Then check hdd spinup. If it exists at random times probably you have "bad" network traffic: 1. You should disable all NetBios services on Win PC. Or just create blocking firewall rules for 137,138,139 ports in DSM. Now your NAS will be lost at network places. To prevent it you can edit /etc/hosts file with appropriate NAS ip. 2. Block 1900 UPnP port in firewall rules. 3. (Not sure about this point) Disable WinMediaPlayer Sharing features and stop WMPNetwork service too. Then check hdd spinup again. If problem is exist in certain time: 1. Disable NTP service in DSM and check crontab file for any tasks. Start appropriate package and check again. There is some packages which prevent hdd hibernation/generate random spinup. http://www.synology.com/en-global/support/faq/568 For example Plex package. It wakes up NAS every hour. With some tweaks of settings Plex wakes up NAS every 24h (actually this is still bad). (Long story is here https://forums.plexapp.com/index.php/to ... s-running/ ) P.S. It's is really sad that power schedule is not working now (bios resets)... This can help prevent spinup at night. P.P.S. My NAS still has random wakeup. How to debug it ? 1. You can use Wireshark for network activity monitoring. 2. syno_hibernate_debug_tool can help too. Keep in mind that syno_hibernate_debug_tool can perform hdd wakeup by itself. So use it carefully.

You have lucky hw configuration! I got the same bios reset problem (on N40L) that I had before with default Synology scheduler. All work fine with default settings eg loading from usb, wol and etc. But flash memory has limitation on write cycles count (around 1000). And thus every day rewrite is not good.

Could you share more details ? Do you mean "Advanced Power Manager for Synology DS" ? http://sourceforge.net/projects/advpowermgr4ds/ Does APM bios reset ? (I know that sheduled poweroff-poweron resets bios on XPEnology)

Are you sure that WD assess it via NFS and not via CIFS/SMB? Try to run from shell (SSH) command /usr/syno/etc/rc.d/S83nfsd.sh restart Any errors while loading modules? I'm using PCH A200 with NFS access. And all works fine too!

Dadudeondacouch, Where did you add this script and where did you find it? I would like to hide the boot USB / SD card (in my case) too. I've done a quick search in the forums for boot unmount USB but did not see anything. Perhaps this is documented in one of the PC setup guides? Thanks Quick Hi! I posted a solution here http://xpenology.com/forum/viewtopic.php?f=2&t=6&start=340#p6356

Volume crash during reboot or sheduled power-off is known bug in 4.3 http://forum.synology.com/enu/viewtopic ... 67#p281159 http://forum.synology.com/enu/viewtopic ... 29&t=74180 http://forum.synology.com/enu/viewtopic ... 29&t=74361

Solution that allows you login via SSH with a RSA keypair was found here: http://www.mauchle.name/blog/?p=239 All steps can be done via ssh or telnet. At step 16 Connection->SSH->Remote command: allows you to send different commands after login for shutdown it should be nohup poweroff > /dev/null 2>&1 & For more complex command set "C:\Program Files (x86)\PuTTY\putty.exe" -load "sessionname" -m C:\commands.txt If you don't want to close session immediately, change Connection->Close windows on exit: Always/Never/On clean exit SSH with a RSA keypair login is more secure than Telnet. p.s. with this thread Turn on your XPEnology with *double-click* http://xpenology.com/forum/viewtopic.php?f=2&t=1330 Win users have complete 'double-click' solution for turn-on/turn-off their synology

To prevent terminal hang you could use SEND "nohup poweroff > /dev/null 2>&1 &\m" instead of SEND "poweroff\m" More secure way is authorization via SSH. I'll post step-by-step guide in next post.