• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About anthonyuk

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. I tried this at first and it only worked out for me when all disks from the array were in place. Thanks for this post OP. It saved my ass as I forgot to delete the .xpenoboot folder when updating and SSH wasn't enabled.
  2. I updated after putting it off for so long from 5.0 -->5.2 --> 6.02. No major issues except the data volume was not available in 5.2. I could see that it was fine data wise in the OS so I just continued with the update and once in 6.0.2 all was good. All applications, users and settings was 100% functional. I'd already bought a PCI-e USB card for the UPS and this worked fine too. I'm now on 6.0.2 update7 on both my N54Ls and the 4Tb USB HDD I used to backup my primary data is now in the secondary after removing it from the case. I also have a remote
  3. On windows you can use OSF Mount to open the .img file to make your changes before writing it to USB. Just ensure you uncheck 'read only' and mount the first partition of the .img. Notepad++ is good for editing this type of text file
  4. anthonyuk

    DSM 6.1.x Loader

    On Windows you can use the free OSFMount app to open the .img file and edit the .cfg. I used an ovf file to create the machine which used Debian GNU/Linux 8 (64-bit) and works fine.
  5. anthonyuk

    DSM 6.1.x Loader

    If you've changed it yes. I change it to avoid problems with duplicate ser/MACs.
  6. anthonyuk

    DSM 6.1.x Loader

    upload the new loader with the same filename to the datastore overwriting the existing loader. If you want to use a different filename you can download the boot vmdk and edit it e.g. in Notepad++/vim/nano
  7. anthonyuk

    DSM 6.1.x Loader

    I just did this on my ESXi 6.0 install which previously failed and now works. Well done again Jun. I simply uploaded the new loader to the datastore overwriting the existing loader, started the VM, recovered then updated.
  8. anthonyuk

    DSM 6.1.x Loader

    Cheers. works well for me too. I just had to edit grub.conf by mounting the .img file. I tried 15132 in ESXi and it wasn't contactable so reverted to snapshot.
  9. Wow. Many thanks to all the guys involved whose efforts are very much appreciated by those in the community.
  10. anthonyuk

    DSM 6.1.x Loader

    Update 5 has been running on my backup N54L and an ESXi install for almost a week. I updated from control panel without issue.
  11. Four hotswap bays + optical + esata.
  12. The template doesn't work but you can just add the .vmdk in the file bundle as the boot device. You might want to edit the grub.cfg first so the esxi option is the default.
  13. I upgraded one of my N54Ls from 5.2 to 6.0.2 and also have an esxi 6.0.2 build in another location I was able to use for testing Hyper Backup/Vault. It looks really cool and works fine.
  14. You can use any serial# and MAC e.g. your actual MAC from your device and you'll only need to change it if you want to use Synology services such as quickconnect etc. This will not stop the install so I would try a different USB stick or try redownloading the .pat file. Please see above but if you do want a valid pair try - ... alid-pair/ This site will generate codes for you -
  15. anthonyuk

    DSM 6.1.x Loader

    Yeah 6.0u2 and loader v1.0. Using the OVF but make sure it is an SATA disk. I could only set this up in the webui (https://your esxi ip/ui).