Jump to content
XPEnology Community

ariel

Rookie
  • Posts

    2
  • Joined

  • Last visited

ariel's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Thanks very much for the quick reply flyride! I guess I can stop my clumsy attempts to modify XPEnoboot images then... I am listing here a partial list of customizations. Not included are various standard packages which can easily be re-installed. Linux GNU toolchain ipkg (optware) with bash binutils bzip2 coreutils cpio libc-dev libcurl libdb libidn libnsl libstdc++ ncurses ncursesw openssl py26-curl py26-setuptools python26 readline screen sqlite termcap wget-ssl zlib Modified Craftbukkit server with source and toolchain CrashPlan with modified configuration Replacement for FFmpeg with support for DTS Various customizations to MailServer including support for virtual users on multiple domains each with their own DKIM and DMARC configuration, modifications to SpamAssassin Git and SVN Java 8 Debian chroot It is of course possible to re-apply all of these customizations after an upgrade. But what worries me most is the possibility that something will prevent the upgrade from completing successfully on the production unit. Thanks again, Ariel
  2. Hello everybody, I have been reading up and trying out Xpenology. This is a truly awesome project! Thank you everybody! The main reason for my interest in Xpenology is to test the DSM upgrade from DSM 5.0 to (one of) the latest versions of DSM, before upgrading a production Synology NAS. The production NAS has been heavily customized which is why I feel it is prudent to test the upgrade on a virtual system before upgrading the production system. I have created a VirtualBox-based Xpenology running DSM 5.0 and implemented all of the customizations that are on the production NAS. I then successfully upgraded this system to DSM 5.1 and was able to check that the customizations remained in place and were operational. But before I continue to test the upgrade to DSM 5.2 and to DSM 6.x, I wanted to try and set the Xpenology model to the model of the production NAS. For this purpose I modified the "syno_hw_version" in the syslinux.cfg file of the Xpenology boot image. While the virtual system comes up in DSM 5.0 and is operational, when I try to upgrade this system to DSM 5.1 (after making this change also to the syslinux.cfg file of the DSM 5.1 boot image, and with the PAT for that hardware), the upgrade fails to complete. The error is Error 21. My questions are: 1) Is there any way to customize the boot images so I can use Xpenology to simulate Synology systems other than the specific models for which the boot images were made? Specifically, are serial numbers and MAC addresses tied to Synology hardware models? Is there anything else that needs modification? Or is this hopeless? 2) Is anyone able to give me some indication as to how different the versions of DSM are/behave on different multi-bay, Intel-based Synology models? In other words: if the upgrade works and keeps the customization intact on a DS3615xs, how likely is that result to be a valid indication of the result of an upgrade on a different multi-bay, Intel-based Synology model? Thank you! Ariel
×
×
  • Create New...