flyride

Members
  • Content count

    111
  • Joined

  • Last visited

  • Days Won

    3

flyride last won the day on October 7

flyride had the most liked content!

Community Reputation

18 Good

1 Follower

About flyride

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. flyride

    Extend monolithic VMDK within DSM.

    For others who might be reading this: software management and recovery of RAID is gradually becoming a more capable strategy than hardware RAID. Even enterprise storage systems are moving to software models instead of custom circuitry. In the case of DSM, using btrfs and intelligent file recovery is a significant enhancement over the hardware implementation. But enough said, you've explained your preference. Regarding your loader and DSM versions - are you asking me if you should be nervous about being on the latest and greatest because I'm not? If that's your question, the answer is: it depends. 6.2 support is not as robust as earlier 6.x versions. Depending on your hardware, there may be problems with upgrading. I have one system on 6.2-23739U2 because if I upgrade, the Realtek NIC will cease to work, at least until a new loader and/or driver signing strategy comes forth. My main system is actually on DSM 6.1.7-15284U2 because of its complexity, and the amount of testing I will require to change major DSM versions.
  2. Just go get it out of the PAT file?
  3. flyride

    Extend monolithic VMDK within DSM.

    What is the logic of the hardware RAID to run DSM? It seems a bit backwards to run an OS designed for software RAID on top of a hardware RAID. In any case, if you want to preserve the system state, do it all with DSM, and end up with a larger VMDK, you can add a 4TB second VMDK and RAID1 in DSM, then delete the original VMDK and replace with a 4TB VMDK, remirror and your DSM storage will get expanded for you. Then remove one of vdisks, force the array back to one member (RAID1 to Basic) using mdadm.
  4. flyride

    nvme on baremetal xpe

    So far Synology only supports NVMe on SSD cache, and DSM only has that capability with DS918 image. Other images have no support. Several people (myself included) have attempted to modify DSM to make NVMe supported as a normal disk device. To my knowledge, the only way this can be done today is using a hypervisor. Here's some detail on how this was successfully implemented: https://xpenology.com/forum/topic/12391-nvme-optimization-baremetal-to-esxi-report/?tab=comments#comment-88243
  5. flyride

    Synology apps requiring a valid serial number

    Please check out General FAQ and in particular, Synology cloud services
  6. flyride

    To SHR or not SHR, that is the question

    Yes, you need 3 drives for RAID5. You can set up RAID1 and then convert to RAID5 when you have more than two drives, if needed. Your other statements are accurate for RAID5. SHR will allow you to mix drive sizes, but one of the largest drives will be totally reserved for parity. As mentioned, DSM is normally installed to all drives. You can isolate Plex to the SSD if you install it at a separate, Basic volume (obviously no redundancy). I do something like this with my system - 2x SSD's in RAID1 for Docker/Plex, 8xHDD in RAID10 for media files and other storage. You actually can remove the DSM replicas and from specific devices - i.e. HDD's leaving DSM on SSD's, but it's a little obscure (and unsupported) how to do that, and there is no way to reclaim the space that DSM would have used. It's a bit of an extreme tuning strategy and I would not consider it without having at least 2 devices for DSM. If you want to learn more read this: How to manage DSM to specific drives
  7. System partition is the multi-drive RAID1 across all member drives where DSM is stored. The array is getting initialized during boot without the USB drives being online and so it goes critical. Using USB as array members is non-standard so something isn't quite going right during boot. Repairing the system partition is just resyncing that RAID1. Edit: didn't see Balrog's post but he basically says the same.
  8. flyride

    To SHR or not SHR, that is the question

    All good advice. However, if you manually troubleshoot your volumes, a standard RAID1/RAID5 array is easier to work with than SHR (which is multiple RAID arrays joined via LVM). So if you don't need that extra 500GB of storage, I'd leave those two off and just add to your array when you get additional, larger drives. Also, consider skipping the cache. It is less effective than you might think. And much of the value is duplicated with the large amount of RAM you have which will write cache. There are many, many instances of corrupted volumes due to SSD cache. At a minimum, do some testing with and without cache for a workload you are likely to do. I think you'll find that it isn't meaningful enough to warrant its use.
  9. flyride

    RAID Card Recommendation

    You are on the XPenology forum. The point of DSM (the operating system enabled by the XPenology loaders) is to implement RAID in software, not at the hardware/ASIC level. So what you really want for the best functionality and performance is drive port density to match your desired number of drives. So you should look at the hardware compatibility threads for the SATA controller chips that are supported by DSM and see if any of those are implemented in mini-PCI. I don't know of RAID controllers on mini-PCI, but again, that should not be what you are looking for. FWIW, most modern RAID controllers can be reflashed to perform as multi-channel SATA controllers, which would maximize their usability for DSM/XPenology.
  10. flyride

    DSM 6.2 Loader

    Please check out General FAQ and in particular, Synology cloud services
  11. flyride

    Multiplication of UEFI

    You should be able to deselect any boot source in your BIOS boot priority menu. If a key is removed and the system powered-on, that will usually cause the BIOS to forget any preferred boot settings regarding that key (even if the key is reinstalled later). It also might be worth trying to disable legacy mode in case you are seeing the same key twice (once for UEFI, once for legacy).
  12. 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 to provide performance similar to traditional USB DAS.
  13. 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.
  14. flyride

    Shopping list

    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.