CtrlAltDel

Members
  • Content Count

    344
  • Joined

  • Last visited

Community Reputation

0 Neutral

About CtrlAltDel

  • Rank
    Super Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  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 t
  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 shou
  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 yo
  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
  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
  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 c
  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 ser
  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?
  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
  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.