amikot

Did you try to use controller onboard for at least one of WD drives? I think problem may be related to your card controller features - maybe there is conflict between software RAID1 of MD0 and hardware RAID1 capabilities of your controller card that are only causing problems with WD disks? Maybe there is option to switch hardware raid completely off?

Have you tried to not use other drives but WD only? Have you checked if there is newer BIOS for your motherboard/SATA controller? Have you tried to disable cache on these drives in Drives Manager of DSM? BTW. I have somehow similar configuration of Raid5, but also more mixed: 1x ST2000VM003 1x WD20EFRX 2x HCS5C2020ALA632 No problems at all, so in your case it may be even a kind of controller issue. Maybe SATA mode unsupported by WD drives? In my N54L server I was setting SATA to 3GB/s or something ( I was going with guide, so don't know exactly why some settings is set this or that way). But if it's controller fault, why it's just md0 affected? Maybe it's question that md0 isn't actually raid5? md0 as system partition is mirror type - so it's rather raid1. Maybe Raid5 can work with your controller/drives combination, but Raid1 can't? I would say it disabling cache may help but will probably decrease performance on data partition.

There is no need to wipe the drives completely. Only partition table must be cleared. It can be done easily from on linux with GParted or on windows10 with diskpart console tool. If after installation you landing constantly in recovery mode it may be caused by faulty drive. I had identical problem. I was struggling to install Xpenology and was thnking there is something wrong with bootloader, whilst the real cause was faulty HDD. I had bad sectors and after NAS could not boot from hard drive. So my suggestion is to try another drive.

I think you have 2 options: Recover and than wipe harddrives in DSM menu remove hard drives and wipe them using PC. Redooing USB bootloader stick is not necessary.

To be honest I don't believe there is such of thing apart of dLNA. I assume this is to be played on TV so for for Plex you need to use web browser or Plex app which is kind of external player anyway. Web browser can be built in, however it may not be as good as normal, and you may have issues. In that case I would suggest dLNA, but how to set it in DSM don't know. Never used it on DSM ... just on standalone Linux.

I'm not Plex expert, but as far as I know Plex needs some computing power on DSM side indeed. Solution is simple: Samba + good player on TV or any other device. No any transcoding happen on DSM side, so even with rather old device you can stream many 1080 videos at the same time - everything depends on your network bandwidth and maximum read speed of the NAS. I'm using VLC on FireTV 4K Sticks (with my both TVs), VLC on Android phones for whole family, and on PC I'm using MPV Player but actually this is easy part and anything can be used. Most important thing is that VLC is doing well for both videos and music. For Photos I'm using DS Photo. Of course Samba in recent version not let guests - so there must be some login/password set. But I don't think it's problem. VLC on FireTV and Android can connect samba without any additional software.

I have feeling it's all just network driver issue. Did anyone try serial debugging to see what's happening in the console?

To be honest I can't understand popularity of PLEX. People must simply don't know there is no need to install such of things to stream videos to TV. SAMBA on NAS and VLC makes it possible and is better than any videostation or Plex because it skips transcoding. OK - not all devices can play all formats in decent quality, but investing in good TVs/TV-boxes may be beneficial anyway. Lot's of people has them anyway.

I forgot to attach what was logged. synopoweroff.log : 2021-02-28T13:49:38+00:00 NewDiskStation synopoweroff: system_poweroff_pre_hook.c:17 synopoweroff: Begin SYNOPowerOffPreHook action. 2021-02-28T13:49:39+00:00 NewDiskStation synopoweroff: system_poweroff_pre_hook.c:22 synopoweroff: Finish SYNOPowerOffPreHook action. 2021-02-28T13:49:39+00:00 NewDiskStation synopoweroff: system_sys_init.c:95 synopoweroff: System is going to reboot syslog.log : 2021-02-28T13:49:39+00:00 NewDiskStation syslog-ng[4798]: Syslog connection broken; fd='0', server='AF_UNIX(/var/run/synologan.sock)', time_reopen='10' 2021-02-28T13:49:49+00:00 NewDiskStation syslog-ng[4798]: Connection failed; fd='45', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)', error='No such file or directory (2)' 2021-02-28T13:49:49+00:00 NewDiskStation syslog-ng[4798]: Initiating connection failed, reconnecting; time_reopen='10' 2021-02-28T13:49:59+00:00 NewDiskStation syslog-ng[4798]: Connection failed; fd='48', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)', error='No such file or directory (2)' 2021-02-28T13:49:59+00:00 NewDiskStation syslog-ng[4798]: Initiating connection failed, reconnecting; time_reopen='10' 2021-02-28T13:50:09+00:00 NewDiskStation syslog-ng[4798]: Connection failed; fd='42', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)', error='No such file or directory (2)' 2021-02-28T13:50:09+00:00 NewDiskStation syslog-ng[4798]: Initiating connection failed, reconnecting; time_reopen='10' 2021-02-28T13:50:14+00:00 NewDiskStation syslog-ng[4798]: syslog-ng shutting down; version='3.7.3' 2 messages: 2021-02-28T13:49:51+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release sysnotify for SynologyDrive when 0x0000 (done) 2021-02-28T13:49:51+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release csp-rule for SynologyDrive when 0x0000 (done) 2021-02-28T13:49:51+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release web-config for SynologyDrive when 0x0000 (done) 2021-02-28T13:49:51+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release webapi-desc for SynologyDrive when 0x0000 (done) 2021-02-28T13:49:51+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release webapi-desc for SynologyDrive when 0x0000 (done) 2021-02-28T13:49:51+00:00 NewDiskStation synopkgctl: SYSTEM: Last message 'resource_api.cpp:289' repeated 1 times, suppressed by syslog-ng on NewDiskStation 2021-02-28T13:49:51+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release pam-config for SynologyDrive when 0x0000 (done) 2021-02-28T13:49:53+00:00 NewDiskStation synoddsmd: synoddsm-hostd.cpp:130 Receive SIGTERM. Terminate Daemon. 2021-02-28T13:49:56+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release sysnotify for Docker when 0x0000 (done) 2021-02-28T13:49:56+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release webapi-desc for Docker when 0x0000 (done) 2021-02-28T13:49:56+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release webapi-desc for Docker when 0x0000 (done) 2021-02-28T13:49:58+00:00 NewDiskStation synopkgctl: SYSTEM: Last message 'resource_api.cpp:289' repeated 1 times, suppressed by syslog-ng on NewDiskStation 2021-02-28T13:49:58+00:00 NewDiskStation share-hook: ( 8509:43040) [ERROR] share-hook.cpp(285): failed to connect to cloud monitor 2021-02-28T13:49:58+00:00 NewDiskStation share-hook: ( 8509:43040) [ERROR] share-hook.cpp(286): notification is not sent ({"notify": "share_hook", "result": 0, "share_name": "homes", "type": "set_privilege_change"}) 2021-02-28T13:50:00+00:00 NewDiskStation share-hook: ( 8678:69664) [ERROR] share-hook.cpp(285): failed to connect to cloud monitor 2021-02-28T13:50:00+00:00 NewDiskStation share-hook: ( 8678:69664) [ERROR] share-hook.cpp(286): notification is not sent ({"notify": "share_hook", "result": 0, "share_name": "Seriale", "type": "set_privilege_change"}) 2021-02-28T13:50:02+00:00 NewDiskStation [737207.055793] init: pkg-SynologyApplicationService-notification_send main process (23092) killed by TERM signal 2021-02-28T13:50:03+00:00 NewDiskStation [737208.143904] init: pkg-SynologyApplicationService-pgbouncer main process (23358) terminated with status 1 2021-02-28T13:50:04+00:00 NewDiskStation [737209.222650] init: pkg-SynologyApplicationService-VapidSendServer main process (23520) killed by TERM signal 2021-02-28T13:50:05+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release webapi-desc for SynoFinder when 0x0000 (done) 2021-02-28T13:50:05+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release webapi-desc for SynoFinder when 0x0000 (done) 2021-02-28T13:50:07+00:00 NewDiskStation synopkgctl: SYSTEM: Last message 'resource_api.cpp:289' repeated 1 times, suppressed by syslog-ng on NewDiskStation 2021-02-28T13:50:07+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release usr-local-linker for SynologyApplicationService when 0x0000 (done) 2021-02-28T13:50:07+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release webapi-desc for SynologyApplicationService when 0x0000 (done) 2021-02-28T13:50:07+00:00 NewDiskStation synopkgctl: resource_api.cpp:289 Release webapi-desc for SynologyApplicationService when 0x0000 (done) 2021-02-28T13:50:10+00:00 NewDiskStation synopkgctl: SYSTEM: Last message 'resource_api.cpp:289' repeated 1 times, suppressed by syslog-ng on NewDiskStation 2021-02-28T13:50:10+00:00 NewDiskStation [737214.617078] init: scsi_plugin_server main process (5884) killed by TERM signal 2021-02-28T13:50:10+00:00 NewDiskStation [737214.652432] init: Disconnected from D-Bus system bus 2021-02-28T13:50:10+00:00 NewDiskStation [737214.718213] init: synoscheduler-vmtouch main process (24179) killed by TERM signal 2021-02-28T13:50:10+00:00 NewDiskStation synoiscsiep: iscsi_stop_all.cpp:97 Successfully stopped iSCSI service. 2021-02-28T13:50:11+00:00 NewDiskStation [737215.631863] init: pgsql pre-stop process (9020) terminated with status 2 2021-02-28T13:50:13+00:00 NewDiskStation root: Check device busy: error, refer: /var/log/DeviceBusyList 2021-02-28T13:50:13+00:00 NewDiskStation synoiscsihook: iscsi_stop_all.cpp:97 Successfully stopped iSCSI service. 2021-02-28T13:50:14+00:00 NewDiskStation umount: Kill the process "zerotier-one" with /volume1/@appstore/zerotier/bin/zerotier-one. 2021-02-28T13:50:14+00:00 NewDiskStation umount: Kill the process "syslog-ng" with /volume1/@SynoFinder-log/appindex.log. 2021-02-28T13:50:14+00:00 NewDiskStation umount: Kill the process "syslog-ng" with /volume1/@SynoFinder-log/fileindexd.log. 2021-02-28T13:50:14+00:00 NewDiskStation umount: Kill the process "syslog-ng" with /volume1/@SynoFinder-log/synoelasticd.log. 2021-02-28T13:50:14+00:00 NewDiskStation umount: kill the process "zerotier-one" [pid = 13936] using /volume1/@appstore/zerotier/bin/zerotier-one synoservice.log: 2021-02-28T13:50:00+00:00 NewDiskStation synopkgctl: SYSTEM: Last message 'synoservice: Waiting' repeated 3 times, suppressed by syslog-ng on NewDiskStation 2021-02-28T13:50:00+00:00 NewDiskStation synopkgctl: synoservice: Waiting for following services: pkgctl-SynologyApplicationService pkgctl-SynologyDrive pkgctl-SynoFinder pkgctl-Node.js_v12 2021-02-28T13:50:03+00:00 NewDiskStation synopkgctl: synoservice: Waiting for following services: pkgctl-SynologyApplicationService pkgctl-SynoFinder pkgctl-Node.js_v12 2021-02-28T13:50:06+00:00 NewDiskStation synopkgctl: synoservice: Waiting for following services: pkgctl-SynologyApplicationService pkgctl-Node.js_v12 2021-02-28T13:50:09+00:00 NewDiskStation synopkgctl: synoservice: synoservice: begin to stop /usr/local/etc/rc.d/*.sh 2021-02-28T13:50:09+00:00 NewDiskStation synopkgctl: synoservice: synoservice: all /usr/local/etc/rc.d/*.sh stopped 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:220 synoservice: WaitAllServiceStop, [180]sec left. 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [syno_ssd_bundle_bootup] with status start/running 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop syno_ssd_bundle_bootup &] ... 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [iscsi_pluginserverd] with status start/running, process 5882 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop iscsi_pluginserverd &] ... 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [synorelay-boot-state] with status start/running 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop synorelay-boot-state &] ... 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [dbus-system] with status stop/stopping, process 5463 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [pgsql] with status start/running, process 12307 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop pgsql &] ... 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [avahi] with status stop/post-stop, process 8959 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [iscsitrg-adapter] with status stop/post-stop, process 8956 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [dc-output] with status start/running 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop dc-output &] ... 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [ip-conflict-detect] with status start/running 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop ip-conflict-detect &] ... 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [iscsi_pluginengined] with status start/running, process 5881 2021-02-28T13:50:09+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop iscsi_pluginengined &] ... 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [scsi_plugin_server] with status start/running, process 5884 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop scsi_plugin_server &] ... 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [apparmor] with status start/running 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop apparmor &] ... 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [pgsql-adapter] with status stop/post-stop, process 8990 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [synopkicompatsync] with status start/running 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop synopkicompatsync &] ... 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [syno-packages-ready] with status start/running 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop syno-packages-ready &] ... 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [iptablesTc] with status start/running 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop iptablesTc &] ... 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:189 synoservice: [synoscheduler-vmtouch] with status start/running, process 24179 2021-02-28T13:50:10+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:194 synoservice: exec [/sbin/initctl stop synoscheduler-vmtouch &] ... 2021-02-28T13:50:11+00:00 NewDiskStation synoservice: service_pause_by_reason.c:11 synoservice: pause [synosnmpcd] by reason [stop-pgsql] ... 2021-02-28T13:50:11+00:00 NewDiskStation synoservice: service_pause.c:23 synoservice: [synosnmpcd] pausing ... 2021-02-28T13:50:11+00:00 NewDiskStation synoservice: service_pause.c:79 synoservice: [synosnmpcd] paused. 2021-02-28T13:50:13+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:220 synoservice: WaitAllServiceStop, [177]sec left. 2021-02-28T13:50:13+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:228 synoservice: finish WaitAllServiceStop, [177] sec left. 2021-02-28T13:50:13+00:00 NewDiskStation syno_poweroff_task: syno_poweroff_task.c:426 synoservice: umount volume ... 2021-02-28T13:50:13+00:00 NewDiskStation synoservice: service_reload.c:20 synoservice: reload [nginx]. 2021-02-28T13:50:14+00:00 NewDiskStation synoservice: service_reload.c:46 synoservice: finish reload [nginx].

Today I made small power cut for my family, and it was good opportunity to test UPS. It worked fine, but... When server entered Safe Mode it didn't power off and when switched the mains on again it didn't woke up from Safe Mode. Hard disks were in sleep, so I just held power button to switch server off and than switched it back on again. I wonder is that normal? Is there any way to fix this? I found only this link - but nobody provided any solution.

I don't see any real benefits in 6.2.4 update, so never mind In terms of DSM7.0 it would be great to have it, but if update will be not possible or risky I will consider OMV instead.

Thanks for answer. So this basically don't change anything. UPS works and can switch NAS off - that's most important. Only down side is that instead of values calculated by UPS or NUT, user must calculate Max Time on Battery by his own.

Thanks very much for that link to Github - it cleared out whole case. I've spent some time reading it and I started to think that there is no sense to play with installing new NUT. Riello IPlug UPS has no autonomy monitoring support and that's the reason why all it's users are getting stupid values in DSM. Even Riellos dedicated software has no that features for IPLug UPSes - just battery voltage can be viewed. Riellu IPlug users claimed this as Bug in NUT, and there is BUG because it should not show values out of any ranges. To fix this bug developers made dedicated function that for Riello UPSes is estimating autonomy basing on data that can be obtained (battery voltage and type) and assumed (age, power consumption by devices). In result we can get not very reliable values that are there just to fill the fields with something better than maximal values for type of record. As this fix isn't making it more useful I'm starting to thing whole work over the issue is just pointless. Installing whole new container just to get fake values made up just for better look? Nonsense. However if someone knows how to install new NUT in docker container - that could be helpful for these that want to try. Thanks

Is that possible that NUT in Docker could shut down the NAS? Any ideas how to configure something like that?

Hi, I just bought Riello IPlug 600AV UPS. It was just very good deal: In used but working order, with UK standard sockets and with USB cable included. Unluckily this UPS is not on official support list of Synology and I knew that someone else had strange issue with incorrect values for battery charge and estimated time on battery. But I bought it anyway - I like challenges and also I saw somewhere that UPS support can be reconfigured in Synology from the terminal. I guess that battery percentage is taken from wrong address - that's why it is showing 255% all the time, so my first idea is to find if there is any settings that could be adjusted using terminal that would let me to set different address where that value is stored by Riello. I have also work around idea to set Time Out for Safe Mode to value equal or greater than that incorrect one from settings - thanks to that NAS should power down just when UPS switch to battery - without any delay. For now as you can see UPS is recognised and can read current status - Connected or On Battery. Thing is that UPS won't shut down without signal that battery is low on power or without timer settings - here both battery indicator and timer are broken.

My CPU is N54L so its TDP is 25W, but still total consumption should be lower than 100W. Your suggestion of UPS unfortunately not match UK market - I think there is no exactly that model. Also prices of APC are higher here - probably because APC is American brand, or maybe taxes are higher in the UK ;( That's why I'm looking at PowerWalker which is also on compatibility list and it's much cheaper here.

Unluckily all these pages have no Turion II Neo processor for selection, so I'm not sure how accurate calculation can be. However whole server has 150W PSU, so I don't think that real power consumption is higher than 100W.

Problem already solved. It was my fault - only torrent/resume files should be imported to new NAS. Uninstalled, reinstalled, copied only that what was needed and voila. Works

Hi, I've installed Transmission from synocommunity and I'm experiencing that problem. Transmission has no problem to connect trackers - it is showing numbers of peers on the trackers. Transmission installed on another box in the same network works with the same torrents (I've tested linux mint and debian ISOs). I'm not using port forwarding on router, but it should not be a problem - never was. Maybe important (but maybe no) may be that /var directory has been copied from another box prior the installation. This was to migrate also incomplete torrents. Any ideas? Thanks

Sorry, I have sometimes a bit annoying style Of course I believe you have lots of experience - I'm the noob here. In case of getting G7 up and running - second disk arrived faulty/damaged. Seller wrapped it just into bubble envelope and nothing else, so it would be miracle if it would survive. I bought another disk from local seller, so have it tested. Unfortunately, the third one WDGreen (that I had problems earlier) - I tested it looking for bad sectors and found plenty - so that was the reason. I have 4 NAS dedicated disks in total, but I have not enough to fill two NAS drives at the same time. So I have to improvise. Anyway ... tonight it will happen , so soon will report.

Good example how the price of the same product differs depending of the country. In UK (with just different output plugs) this one costs £109.99 But even that £110 is not much regarding that what price range we have here. UPSes are expensive - probably one of most expensive devices, and they're not getting cheaper much over time. 10 years old units still costs 50% of the price - even if its completely ridiculous. Unfortunately paying even £110 too much. My whole NAS isn't worth this money. Precious data I have stored on disks in the drawer . UPS is only optional addition to save hardware if it's possible and not expensive. Paying £110 to save PSU that costs maybe £30 and actually may never get broke? Or maybe to save disks that I bought second hand anyway for £25 each ? Disks are dying anyway, so it's better to save money for spares. For me UPS must be below £50 - then I can think about - but must be sure that's not rubbish. I don't expect hours, I want just 3-5 minutes to power down the NAS. I'm interested in things like: Salicru 500 VA SPS ONE UPS or V7 UPS1P600E or V7 UPS1DT750-1K or second hand device, but not too old as old UPSes are not very efficient.

Hi, I'm not sure if it's perfect category for that question, but I thought it's safe place that nobody will complain. As new user of Xpenology installed on HP Microserver N54L I'm very interested how to protect that server against power outages? Since a week I'm trying to find cheap, possibly green, not essentially brand new UPS that would cooperate with Synology and will gently turn it off in case of power loss. Already found that there is compatibility list on Synology portal, but as I noticed - it's definitely not complete. There is many brands missing (like Riello or Salicru, or Amazon Basics) as the models of existing brands as well. Apart of that, Xpenology isn't real Synology - there might be hardware issues. So, how it is with UPSes for Xpenology ? What UPSes are you using? What about cheapest UPSes that gives just enough power to switch NAS off ?

You're right and wrong at the same time. For BIOS only USB stick is bootable, but from USB stick we load bootloader which is booting Synology OS (called DSM) from HDD. My problem was with that second booting - after bootloader from USB was already loaded. Situation is actually similar to modded consoles - some consoles could be soft-modded when custom bootloader was loaded from CD prior booting actual game from CD/DVD or hard-modded when custom bootloader was flashed into the console, or fitted as additional chip. "Have" it's to early to say I'm waiting for another disks that are about to arrive today - then I will be able to install DSM and set everything UP.

Hi everyone, I'm an technician and systems support in electronic manufacturing company in UK. Also I'm web developer with specialisation in managing databases (MS - SQL, Postgres, MariaDB). In my history I had great opportunity to work as beta tester of AmigaOS 4.0, as also as writer to Amiga paper magazine. Since Amiga period, I earned lot of experience on many platforms - mostly Linux based environments. Since few years I'm interested with network drives. Beginnings were not easy. My first file server was installed in Linux based satellite receiver (Dreambox), than I moved to home server, than I installed DD-WRT and FreshTomato routers with HDDs. First real NAS project was with Raspberry Pi 4.0 and OMV/NextCloud. After short time I bought a bit rusty NAS from Synology DS509. Finally I landed here - with Xpenology on my old/new Microserver N54L. I'm believer Christian, husband, father since ... long time . I'm sceptic about unproved theories (like evolution or about origins of Universe), I like trumpet music, electronic music. Hopefully this is enough.

I have DS509+ which is good but old. It s 5 bay NAS, but I'm using only 3 bays (RAID5) + forth is Hot Spare. I want to move to just installed Xpenology, but I have no new disks to install. So I want to keep old disks for now. There is several options that I see: 1. I could take 2 disks from old NAS (one hot spare and one working) and create RAID0 on new NAS - copy all data over the network and than move 2 outlasting disks, converting RAID0 to RAID5 as final move. However I'm a bit afraid of that, as my data will be exposed to risk for time of copying (I have backup, but...). 2. I could just move all my disks from 509+ to Xpenology and install new DSM - hoping that all data will stay on. I don't know if it's possible specially that I can't see SHR mode in my new Xpenology - is it obsolate or what? DS509+ is SHR raid matrix. 3. I could buy one more drive and use it to extend security while moving as in option 1. 4. Maybe there is kind of temporary service with capacity of few TB to use for few days where I could back my data UP? BTW. I wonder, what if after time I will buy bigger disk - how to will it be beneficial at all? Or I always have to buy in couples at least? Thanks