Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 09/13/2019 in all areas

  1. Hmm, calling people out as arrogant isn't the way to curry favor for help. Anyone you could possibly reach with that comment has spent countless hours trying to help many, many people such as yourself. Based on your questions, both you and OP present with little or no evidence of effort to understand DSM and how the XPenology loader works. And only slightly below the veneer of that request is a challenge to be assured you won't lose data, which you cannot possibly get from someone on an online forum. It's your responsibility, nobody else's, to make sure your data is safe. Let's spell it out: All the loader does it let us boot DSM on non-Synology hardware. Nothing more, nothing less. Any other behavior is attributable to DSM, Synology's operating system. Yes, it's based on Linux, but that's not a limiting factor. Many XPenology users never launch the shell, nor do they need to. If you want to be successful running DSM on XPenology, it will be in your interest to know something about DSM. There are many, many places to learn about how to do things with DSM, not the least of which are Synology's forums. So here are a couple of key points that ARE, literally, embedded in the tutorials. Hopefully they will help steer you in the right direction. Upgrading DSM from 6.1 to 6.2 is a function of DSM. Not the loader. If you want to upgrade from 6.1 to 6.2, you'll need to install a 6.2 compatible version of the loader (either 1.03b or 1.04b), otherwise DSM will crash once upgraded The 6.2 compatible loader must also work with your hardware, which isn't a guarantee even if you were successfully running DSM 6.1. Installing a new loader is analogous to moving your disks to a new Synology Diskstation - DSM will prompt for migration or upgrade. Migrating and/or upgrading DSM isn't inherently a data-destroying process, if done properly. Again, this is a DSM behavior Any upgrade or migration operation can fail for many reasons, including loader incompatibility (ref hardware issues above) or user mistake. Those who attempt an upgrade or migration operation without a data backup plan are, bluntly, foolish To you, OP and anyone else who wants to upgrade - it's very much in your interest to build up a test environment and validate your upgrade plan each and every time before subjecting your production system and data to risk. This is repeated again and again in the tutorials. It is one of the benefits of a virtualized (i.e. ESXi) environment - it makes it very easy to test without extra hardware. Good luck to you and OP. Your linarrogant friends online will be waiting to help if you run into trouble.
    1 point
×
×
  • Create New...