flyride

Members
  • Content Count

    1,035
  • Joined

  • Last visited

  • Days Won

    59

Everything posted by flyride

  1. 6.2.1 and 6.2.2 had problems with driver compatibility and were difficult to make work. Stay on 6.1.7 or go to 6.2.3, you'll probably have a different result than with 6.2.2.
  2. You never said which DSM version you tried, only "newer." Should you want 6.2.3, try this combination: loader 1.03b, DSM DS3615xs version 6.2.3-25426. You MUST set Legacy Boot/CSM in your BIOS for your USB stick. The install (VID/PID, etc) is otherwise the same as what you have done for 6.1.7. That said, there is nothing wrong with 6.1.7. On the DS3615xs platform you have chosen, there really is no difference between 6.1.7 and 6.2.3. As someone decided to hijack your post, I will, without criticism or judgment, state for his sake that this exact advice has been posted on average once per day for at least the last month.
  3. Given all your constraints, you should probably ask what you want to use 16 threads for. There is no filesharing workload that requires more than 8 cores for maximum throughput (my system can max 10Gbe with 4C/8T at well under 100%). Is it to run other VM workloads on the same server? I don't know if anyone has actually done this, but it is technically possible to pass iGPU through under ESXi 6.7. It is also possible (although can be hardware limited) to passthrough NVMe devices. You might consider testing a switch to ESXi, run DS918+ DSM as a VM and passthrough iGPU/NVMe. If NVMe passthrough doesn't work on your hardware, you can RDM or RAW and present the disk to the VM as SATA and use it as cache. The performance will be the same. That would give you 4C/8T for DSM and whatever you have left for VM's.
  4. Amazing functionality for the cost - 8C/16T CPU and 32GB RAM for $US190? Wow. Wonder if they are reclaiming old chipsets or purchased enough new old stock to make a run of boards...
  5. Sometimes posts get lost in the noise. The raft of "doesn't work, help meee" posts come in a cyclical manner. This is a series of hacks, not a product. If one is not willing to learn some general tech and Linux in particular, this really isn't for him/her. No one person here has all the answers. Sometimes it's best to let people figure things out on their own; sometimes the community has something relevant to share that helps them. There is enough information and resources here to support both. That said, Well which is it? Awfully convenient as you are criticizing others. How about you buckle up and help?
  6. For those who haven't encountered this before, the period at the beginning of the name is what hides the folder or file.
  7. I'm using Mellanox Connect X-3 and VMxnet with no issues on 1.03b 3617xs 25426 and there are many posted examples of others using similar.
  8. Intel CT is the stalwart option for a PCIe card US$20 or less. Ironically the newer the motherboard, the less likely the drivers will be able to address the onboard NIC. extra.lzma can help but Intel enjoys changing PCI device ID's which breaks old drivers. Other more functional option for NVMe SSD is to use a hypervisor and then bring in the SSD as an emulated SATA device (RDM or RAW in ESXi, for example).
  9. Synology does not use btrfs native RAID5 (the code that is untrusted). DSM uses btrfs as a simple filesystem on top of a MDADM RAID (or a LVM comprised of multiple MDADM RAIDs in the case of SHR). Snapshots and scrubbing are standard btrfs features. But I believe Syno has forked the code to add/enhance the self healing services they advertise. They may have to keep enhancing it themselves as I think open-source btrfs development is coasting and falling out of favor on the major Linux distros. But there isn't any other low cost storage platform available that can offer the combination of features you speak of and run on modest hardware...
  10. Can't get really any more explicit than that. It will only exist if you had 5.x installed.
  11. I agree that is a strange comment since it's Syno's recommended default filesystem for some time now.
  12. Post a question like that in a question forum, not here. However DS3615xs supports 4C/8T, and the same loader supports DS3617 at 8C/16T. I'm not sure where you are getting your information, but review here: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/
  13. From the General FAQ: https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-82390
  14. Quoted is the last sentence in post #1. The script won't do anything if synoboot is properly configured, but it won't hurt anything either.
  15. Serial port is the only option. They are cheap and USB-connectable and generally work even when other things aren't. That said, you are facing some standard problems and there may be more expedient/simpler ways to solve them. When asking for help, stating your CPU type, loader used and the DSM version and platform are required. Not knowing the details of what you were trying, here are some specific combinations for your hardware that are very likely to work: 1. Loader 1.02b, DSM 6.1.7 DS3615xs, any boot mode 2. Loader 1.03b, DSM 6.2.3 DS3615xs, CSM/Legacy boot mode If neither of these work, you probably have a VID/PID problem despite your efforts and should try another USB key.
  16. Given the thread history, @StanG needs to now restore the original extra.lzma's to the boot loader or load the new ones for 6.2.3. The workarounds needed for 6.2.1/6.2.2 don't work on 6.2.3.
  17. Unfortunately I still can't duplicate this behavior. The issue is probably a resource timing issue in the first place, so I suspect it's a difference between the boot up time of the systems. Your system is somewhat slower than the system I am using to test. You might want to try the modifications suggested in this post here. If you do and it works for you please report back. https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/?do=findComment&comment=150336 Again, even if you receive the pop-up messages, your synoboot should be working correctly and your system ought to be fully functional.
  18. I wonder if this might be an option for you... never needed to try it myself, but it's an interesting idea. https://xpenology.com/forum/topic/12867-user-reported-compatibility-thread-for-dsm-62/?do=findComment&comment=157911
  19. The UI pop-up message is a cosmetic problem not a functional one. But the current version of the script is intended to suppress the pop-up error message. Reading back through the thread, there was an individual that for some reason received UI notification, and to my knowledge never resolved it. I was unable to duplicate this reliably in test. Can you be very specific as to what you are doing when you do and don't receive the message? Are you using ESXi or baremetal? Do you mean restarting ESXi?
  20. To run DS3615xs or DS3617xs you need to to turn on legacy boot in the BIOS. That board has very little for BIOS configuration. I seem to recall someone stumbled on a not-obvious boot option which caused it to disable UEFI. My best advice is to try everything. FMI: http://forum.asrock.com/forum_posts.asp?TID=8472&title=asrock-j5005itx-fails-missing-legacy-boot-mode
  21. Is there something not working? There are a lot of "normal" errors in /var/log/messages, particularly on bootup.
  22. Review this thread: https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/
  23. Oh, you are using DS918+ with original MaxDisk=16. So DiskIdxMap should be 1000, that will make the 50MB disappear. You have SataPortMap=4 which probably should be "1"
  24. It's a provided img file, you aren't creating it.
  25. /dev/md0 is your root filesystem (DSM). Check for core files, orphaned log files, etc. Or reinstall DSM.