• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by flyride

  1. Synology doesn't provide a DAS connectivity option to date. I had a similar desire to use DSM as the back end storage to a device that only was able to connect via USB. I was able to make this work by purchasing a $25 "NanoPi NEO2" which is a tiny Linux computer that 1) had a gigabit Ethernet interface, and 2) supported USB OTG mode. Then I built a sparsely populated image file on a Synology share and NFS mounted on the NanoPi, and used the Linux g_mass_storage gadget to emulate a USB drive from the image file. A Raspberry Pi only has a 100MB Ethernet and that's not fast enough
  2. flyride

    DSM 6.2 Loader

    The board will work fine. I am running on DS918+ image right now with J4105. As long as your RAM is compatible with the motherboard it doesn't matter very much. The board has an onboard Realtek NIC. This works fine with the DS918+ image. You want a second NIC? Just make sure the Realtek or Intel driver is supported. I have not seen anyone with this board running a second NIC however.
  3. You have a fairly typical setup. I am running on this same motherboard with no problem. The SSD won't be very helpful to you aside from SSD cache, and many frankly do not recommend it due to general DSM stability and corruption problems that are encountered with regularity with SSD cache.
  4. Why is it time to update your system to the latest possible version? The latest possible version is alpha status for XPenology. Upgrading to the current version is not yet a highly robust process and there a lot of ways for it to go wrong. Because of this, you have the risk to make your data inaccessible. If this happens and you are unable to follow recovery steps you may inadvertently lose your data. Even when upgrading works consistently on all hardware, you are unwise to attempt it without a backup. If you simply must proceed, perhaps you could attempt to
  5. flyride

    DSM 6.2 Loader

    I've found that using the Synology Assistant app can be more reliable than as it's fully contained within your network and doesn't rely on any Synology cloud services.
  6. No, this is derivative of how your controllers are set up in your VM. Make sure drive numbering starts with 0:0 and not 0:1, and also make sure you don't have an extra controller definition with no drives attached to it.
  7. My test VM is VMDK which I think is more than adequate for minor updates. For a major update (such as 6.1 to 6.2), I would idle my primary NAS instance, and use one or more of its storage bays (and spare drives) for a temporary RDM configuration.
  8. RDM can also be used to make non-compliant storage devices (NVMe in my case) available as emulated SCSI disks with all the attendant support benefits.
  9. What is your objective in using ESXi to provide a client to host DSM? Get access to DSM features for utility? Improve hardware compatibility? Performance? Reduce the number of physical boxes? Where is your storage - is it drives physically connected to the ESXi platform, or SAN? You should be able to answer these questions to decide how to approach your DSM storage strategy. For me, I am using ESXi because it is the most effective way to get directly-connected NVMe SSD's to be functionally supported on DSM. If it were not for that, I would run DSM baremetal for the best perfor
  10. Make sure you are selecting the ESXi boot option from the console. Then make sure the boot image is drive 0:0
  11. I'm sorry but you are in a bad way now, and your actions thus far have probably made things more difficult to recover. There is not a step-by-step method of fixing your problem at this point. However, depending on how much time and energy you want to devote to learning md and lvm, you might be able to retrieve some data from the system. I have a few thoughts that may help you, and also explain the situation for others: A RAID corruption like this is where SHR makes the problem much harder to resolve. If this were a RAID1, RAID5, RAID6 or RAID10, the solution would be easi
  12. How did the array look before the crash? Right now DSM seems confused as to the construction of the original array and your drives are in an odd order. Did you rearrange the drives or remove drives from the array in an attempt to fix it? SSH into your box and perform a $ cat /proc/mdstat Post the results here.
  13. Ah, you are editing the Syno JavaScript file where the information is hardcoded. Thanks for posting it!
  14. Thank you, however: Can you publish your source script? I assumed you were loading node.js to run the javascript code, but I am not sure how that could be compiled into an executable file with shc. I do not understand why you prefer to distribute as an executable file, seems a risk for others to accept this.
  15. flyride

    DSM 6.2 Loader

    Thanks for relaying your experience. But your comment #3 - let's all not forget that 1.03b development and 6.2 support is still seriously in beta. If you want stability and lack of problems, stay on 6.1 for now.
  16. As Dfds says, yes it's ok. Answers to your future questions in this regard are found here.
  17. flyride

    DSM 6.2 Loader

    I disagree with this generalization - Xeon does not offer any capabilities that desktop processors do not have. ECC RAM and improved security are Xeon's two main benefits, both which are irrelevant to DSM. So I would not worry about using DS3617xs with a non-Xeon processor as long as it supported the needed instruction set, which is a function of processor generation, not server vs. desktop. The final answer for your CPU should be discernible by reviewing the hardware capabilities as described in the Intel Ark pages. How to summarize all this? Basically, the DS916/3615/3617 DSM
  18. flyride

    DSM 6.2 Loader

    Info Center reports what it expects on the intended hardware for the image and is not correlated to the actual CPU in the system. That said I don't think you can use more than 8 cores in DSM, if you have HT and more than 4 cores, disable hyperthreading.
  19. Yes, that is the way Synology is supporting the older CPU's; they are not upgrading the kernel, at least in 6.2. So if you want a newer kernel, 918 will be the way to go.
  20. flyride

    DSM 6.2 Loader

    Load a vmdk file in a text editor and you will have your answer.
  21. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284U1 - Loader version and model: Jun's loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5.0 U1-7388607 - Additional comments: REBOOT REQUIRED / No issues with physical RDM and controller pass-through.
  22. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 1 - Loader version and model: Jun's Loader v1.02b - DS916 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J4105-ITX - Additional comments: NO REBOOT REQUIRED
  23. Unless you manually modify them yourself, you will not be using anything other than original PAT files from Synology. You should read the FAQ and best practices regarding updates. In short, nobody knows for sure whether an update is going to break XPEnology. Most folks either wait for someone to report success on a software/hardware platform similar to theirs before applying an update, or have a test system that they don't mind crashing to try it out on prior to committing the production system.