Jump to content
XPEnology Community


  • Posts

  • Joined

  • Last visited

Everything posted by CtrlAltDel

  1. Is your Xpenology machine using DHCP or did you give it a static/fixed IP? If you gave it a static IP you will either need to set the new router to the same IP range as your old router, or change the network settings in DSM to use DHCP, and then setup a static IP for the server on the new router. Option two would be my preference.
  2. The serial number and mac you use in the grub config need to be specific to a real Synology device. The one in the default grub of the loader version you're using will be a matched pair for the device the loader is emulating. I.e. you can't invent a serial number or mac and the two you use need to be a matched pair, that meets the values expected for a real Synology DS3615xs, if that's the hardware supported by loader you have chosen. You can't use the serial and mac for a DS3615xs in the grub for the DS916+ it wont work. Try again and this time only change the vid and pid values to match your usb stick in the grub, and use the default serial and mac.
  3. Hi, I just realised I didn't post a link for you in my first reply, I mixed this post up with another topic sorry. Anyway here is the link I was referring to https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/
  4. Yep. it's pretty straight forward if you're a bit rusty you should probably read the post I linked to just to refresh. There is a link to another post early on to directions for upgrading HP's iirc. You only really need the vid and pid to successfully install the system you don't need to change the serial and mac. No afaik Synology have put an end to abuse of quick connect and to be honest it's not something that the community would encourage or endorse. One it is a clear abuse of Synologys services and two it harms the future prospects of this project. In fact you should probably create a firewall rule to block Synology domains to prevent leaking your systems details and IP. address=/checkip.synology.com/ address=/update.synology.com/ address=/autoupdate.synology.com/ Doing that will also prevent the system update utility from accessing the version check, so you will need to keep an eye out and manually apply updates yourself. You can use this tool to find your vid and pid https://www.nirsoft.net/utils/usb_devices_view.html If you need external access it's easy enough to sign-up for a free ddns service and point the domain at your box. There is a tutorial on here somewhere which explains it if you haven't used that method before. If you setup a VPN server along with your ddns you should be secure provided you don't expose ports outside of the VPN. OpenVPN is the most secure option but it takes a bit of messing about to create the certs and keys etc. but it's worth the effort imho. Having said that using Synology's OpenVPN is a simple process, you can just export the client files iirc.
  5. Your N54 will run it just fine. You could always get a used Gen8 and build a new machine and keep your N54 as a backup device (updated to the new version of course). That's what I did with my N40 which I use as a backup for critical data now. You can't simply jump from 5.0 to 6.1 you need to update to 5.2 before making the leap. https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/
  6. I just updated a Gen7 and the process is the same as it was before, assuming you have performed a major update and it's a bearmetal system. You just need to create a new usb key using Jun's 1.0.2b loader, mount the loader img using osfmount, edit the grub with vid, pid, serial and mac to match your usb stick and machine. Then burn the image to your usb stick, shutdown swap the usb sticks over and reboot, find your machine in your browser and follow the migration dialogue. Then you can apply the latest update patch to bring your machine up to 6.1.4-15217-2. After that you should be good to go.
  7. Another N40L bearmetal that seems to be good so far using Jun 1.0.2b DS3615xs DSM 6.1.4-15217 Update 2. It's only a backup box so no packages tested. WOL is still working but the Power Button looks like it requires some attention. EDIT: Installed POWERBUTTON_6.1-0005.SPK which fixed the Power Button. By the way this unit was updated from DSM 6.x to 6.1.4 ud 2.
  8. I'm out of suggestions I'm afraid. All I can say is WOL local and via VPN WAN works flawlessly for me on my HP units running DSM 6.0.2.x using the methods mentioned above.
  9. If your unit isn't going to sleep properly then WOL will never work! Have you doubled checked your config and S99ZZZ_Shutdown.sh script including making sure the script has write access? You need that working to get your unit to sleep. I use that method with HP N40L and Gen8 devices without any issues. WOL works fine for me using LAN or VPN WAN. P.S. I also have the power button fix applied to my HP servers, which I need if I power off using the power switch, rather than the DSM control panel shutdown. Maybe your hardware needs a similar fix? Try searching the forum for 'acpi power off' or 'acpi power switch' etc. there should be some scripts and instructions on here. There's also an alternative power button script called 'POWERBUTTON_6.1-0005.spk' - I'm not running 6.1 so I don't know if the old method works on 6.1, maybe try this newer script first?
  10. UDP 7 and 9 iirc not all routers will pass/broadcast the magic packet correctly so this may or may not work for you? If you use a router with Tomato installed there is a WOL utility under tools which is handy if you have VPN access to your router. Obviously you need access to the routers control panel so only people with admin rights could use that method. Other flavours of router firmware offer similar tools in some cases. Stock consumer routers firmware tend not to support WOL via WAN very well in my experience. If you can join your network using a VPN you should be able to use WOL to start machines that are accessible on the same network using a WOL script/utility. Obviously that's not much help if the machine in question is the VPN server and it's down. This maybe useful? https://www.depicus.com/wake-on-lan/woli
  11. Edit root/etc/synoinfo.conf: Search for eth0 or the lan connection required for WOL. eth0_wol_options="d" change the "d" to "g" = eth0_wol_options="g" this will set a tick in the WOL for eth0 in the control panel power settings. Make sure > wol_enabled_options="g" < is set to "g" not "d" Make sure > support_wol="yes" < Copy file or create a file called: S99ZZZ_Shutdown.sh to: dsm5.x root/usr/syno/etc/rc.d dsm6.x root/usr/local/etc/rc.d Set execute permission. Script command (file content): #!/bin/sh case $1 in start) if [ -f /var/packages/shutdown_script/DSShutdown.sh ]; then /var/packages/shutdown_script/DSShutdown.sh & fi ;; stop) if [ -f /var/tmp/shut.down ]; then rm /var/tmp/shut.down fi ifconfig eth0 down ;; *) echo "Usage: $0 [start|stop]" ;; esac Now set the WOL option in the synology assistant and then shutdown the machine. Use the WOL option in synology assistant to test WOL is functional. If you need WOL over a WAN connection your router will need to be able to pass the magic packet on to the LAN devices.
  12. Judging by their latest developments I would be amazed if they don't start implementing signed code at least for core scripts etc. They are also trying to move towards a subscription/licensing based model for packages like MailPlus etc. and I expect the office apps will go the same way, once they mature a little more - which kills it for personal use for the majority of people imho. I guess Synology may offer a limited number of free user accounts like they have with MailPlus. In reality how many people will want to pay £250 for 5 extra licenses or £1000 for 25? You can setup a server running Round Cube or Squirrel mail for free without too much difficulty. They may not offer some of the features but they sure as hell could handle plenty of mail for a good number of users. ISPConfig is a free and feature rich web hosting control panel which can manage user accounts and webmail etc. https://www.ispconfig.org/ it's obviously not as easy to set-up and manage as Synology DSM. Regular NAS storage is absent, but you can install any of the apps that can run on a lamp stack and it will run on any old hardware pretty much or in a VM. Asustor's ADM looks like it comes closest to the Synology DSM experience and could offer an alternative solution in the event that Xpenology stalls based on the nest DSM release? My gut feeling is that there will be no sure way of implementing future versions of the DSM on rough hardware. I will be happy to be proven wrong though! It would be cool if this community could change with the times, even if it requires a change in the code base to keep us all entertained.
  13. Asustor Overview https://www.asustor.com/admv2?type=1&subject=1&sub=101 Version 3 Live Demo https://www.asustor.com/live_demo Packages/Apps https://www.asustor.com/app_central/ It looks like Synology will be signing the core elements of their DSM which is probably going to make it difficult to continue with Xpenology solutions moving forward. Maybe Asustor warrants some investigation as a viable alternative? If some of the smart folk in the community are interested perhaps someone or a team could do some exploration and hopefully create a package for testing? I'm too stupid to attempt it myself so I'm throwing it out there for the guys with the skills.
  14. No way in hell I would EVER expose my NAS onto the Internet in that way.. I would check whether your router supports use of a VPN and use it to access your network..... #H I agree using a vpn is the way to go, but I get the feeling the member asking the question isn't familiar with this type of access or the security risk associated with exposing ports/services. Maybe some links to synology vpn/security resources would help them out, or a post with a basic guide might help prevent a bad situation occurring for people that are new to this type of usage? I'm not sure if there's anything like that on this forum already? This may do as a starting point for a vpn setup http://bpmsg.com/how-to-make-your-synology-disk-station-nas-more-secure/comment-page-1/ but it doesn't really go beyond the vpn aspect. This article gives some useful info https://www.wijngaard.org/hardening-access-to-your-synology-diskstation-and-prepare/ Ideally you need to find information that's more generic, that doesn't explain everything directed towards a real synology and their quick connect service etc.
  15. Which micro server do you have? I have Gen7 40L and Gen8 microservers and they run DSM 6.0 (Jun's v1.x loader) including power governor, wol and the power button.
  16. @Trantor Please could you add a link to the post quoted in the OP so people can be find it easily? I actually did something a bit more complete in reference to that post where Jun kindly provided that information due to some technical difficulties I was having. Here we go: Tutorial: How to access DSM's Data & System partitions Nice work!
  17. @Trantor Please could you add a link to the post quoted in the OP so people can be find it easily?
  18. But did you install the packages in 6.1 or were they installed in 6.02 and worked after migrating to 6.1? I ask because some packages work OK if they are part of a migration but fail when you try to install them on newer builds. I haven't tried 6.1 I'm just curious to know what to expect under both conditions? I suspect some packages work when migrated but fail to install on the latest build based on past experience. Yes they were all previously installed on my 6.0.2 install (and my 5.2 install for that matter!) It gave a warning that Plex was incompatible, but it was up and running just fine after the update. Thanks for clarifying that. Some of those packages may not install on a clean build of 6.x.
  19. But did you install the packages in 6.1 or were they installed in 6.02 and worked after migrating to 6.1? I ask because some packages work OK if they are part of a migration but fail when you try to install them on newer builds. I haven't tried 6.1 I'm just curious to know what to expect under both conditions? I suspect some packages work when migrated but fail to install on the latest build based on past experience.
  20. You can migrate up to DSM 6 (not 6.1!) using Jun's loader and the tutorial in the sticky threads. Afaik you need to update to 5.2.x before attempting to move to DSM 6. As Dfds said it's best to do some reading first so you're up to speed and understand what you're doing. Make sure you backup all critical data because you never know for sure nothing will go wrong. If you have enough storage to back everything you need to keep you could avoid some steps by doing a fresh install of DSM 6. DSM 6 gives you btrfs as an option which is a pain to migrate to because you can't make volume 1 btrfs in an straight forward process, because the packages can't me moved to another volume. Also keep in mind that shr volumes aren't accessible by default with DSM 6! You need to make some minor edits to the default conf file to access shr again. You can migrate shr volumes if you go the migration route, but you still need to edit the conf file to get shr fully usable if you need to change or add volumes etc. later on. There are lots of nice features in DSM 6 so it's worth taking some time researching before you make a decision imho. General Security is improved and letsencrypt ssl is nice to have. Oh and the root user works differently under DSM 6...your main admin account is no longer the root user, so you need to use -sudo in ssh sessions or apply a password to the root user (less secure) to login directly as root. The cpu governor, power button and wol scripts all work on the 40L with DSM 6 and 5.2, although you may need to tweak some config files and manually add some scripts. Some script locations differ between 5.x and 6.x. Lastly there is no console output on the 40L so make sure you take note of the work round in the installation notes. Start here and read the OP expand the [+] panel to see the notes viewtopic.php?f=2&t=20216 and then see this thread viewtopic.php?f=2&t=22100 for the how to. I used the migration method and the fresh install approach and imho the fresh install was preferable in my case, but it means you have to reconfigure everything. The advantage was the new admin user account process is applied cleanly...you're forced to create a new account that's not named admin, it also creates the home folder appropriately. Applying btrfs is much easier with a fresh install and you end up with a nice clean DSM 6 build. The downside is the time it takes to backup and shuffle all your data about, especially if you have large volumes full of data. If you need to juggle drives around and you want to use shr make sure you use the drive with the lowest capacity as part of your initial array, because you can't add drives with a lower geometry to an existing array. Been their, done that and that brain fade cost me a lot of time rebuilding. In your case taking the leap to DSM 6 will save you going through the DSM 5.1 to 5.2 process. Not that that is a big deal, but if you're not familiar with migration it may pay you to go for a fresh DSM 6? I guess it deepens on your pain threshold and how much effort you're willing to put into the research? Other peoples opinions may vary so don't accept what I have said without doing some further research.
  21. It's possible to run Virtual Box on DSM 5.x but no chance on DSM 6 afaik. A quick search of the web should throw up some how to's and links to the package. The developer has stated that he can't develop a DSM 6 version without the source. DSM 6 has some nice new features so there's a choice to be made before committing unless VMs are vital. Most of the more popular packages seem to be working on DSM 6 but you should check the ones you need to be sure. Using Quick Connect isn't recommended as it's an abuse of Synology's resources and reflects badly on Xpenology users. It's easy enough to use a third-party Ddns service to gain remote access. It's worth installing DDNS Updater 2 from the community packages because it's better than the built in DSM option. The main advantage is you can add multiple domains from the same provider. It has good provider support and some additional options.
  22. Wouldn't it be better to open a new thread for Juns New DSM6.1 Development build? I have a feeling that a few people are going to get confused when both are being discussed in the same thread. Someone is going to end up in a world of hurt as a result imho. Plus this is already a long mature thread which is probably already difficult for newer users to wade through. Mixing 6.1 information is going to make it a much more difficult task and potentially generate loads of unnecessary support requests for the community to deal with. That's my two cents. P.S. Thanks to Jun for his continued efforts and his 6.1 test release, which I look forward testing when time permits and early adopters (crazy folk) submit their reports.
  23. Boot with a linux live cd and edit the mtu value in the config file.
  24. Lots of people have reported that ud6 is working OK and it has been fine on my machine also, so you should be good to go.
  • Create New...