flyride

Members
  • Content Count

    1,618
  • Joined

  • Last visited

  • Days Won

    81

flyride last won the day on February 4

flyride had the most liked content!

Community Reputation

484 Excellent

About flyride

  • Rank
    Guru Master

Recent Profile Visitors

6,911 profile views
  1. Please post the IP addresses, gateways and network masks of your XPe NAS, your Mac and your TS5400R. Are you configuring static devices or DHCP assigned? If DHCP, what device is providing DHCP? What protocol are you using to access the NAS on your Mac? CIFS, NFS, AppleTalk? Are you trying to use Jumbo Frames on any of your devices? We need to establish confidence that we have no obscure issues with the network. Incorrect masks, inconsistent frame sizes or intermittent routing can cause issues like you are describing. Here are a few discovery items you can do.
  2. So far this opinion has not solved for you, so you are asking for assistance. Yes, I gave you suggestions and you wrote a lot of response to dismiss them. I'm not sure what you are trying to say here. This is your problem. It won't fix itself. So at risk of being entirely repetitious, please consider that in order to troubleshoot, you must rule out the obvious. I offered some specific items to review and it is apparent you have not done so. If you require feedback on them, please POST something that can be objectively evaluated. For exa
  3. Slow read speeds, and the 2MBps write and from your other NAS suggests network misconfiguration or physical problems. Check network link speeds, network masks, patch cables, terminations, and gateway/routing if applicable. 2MBps is poor performance on a 1Gbe network. I expect something around 40-50MBps read/write from a three drive SHR when testing with large files.
  4. There is no such thing as a "system" disk; DSM installs to all disks in your system. The guides for installation on virtual usually have a step for the creation of a 16GB virtual disk but there is nothing special or required about it if you intend to use other storage devices. SataPortMap and DiskIdxMap are grub.cfg arguments. If they are properly configured, you should not see the loader device at all. Between the two, they give you the ability to place the controller ports exactly where they need to be in the UI port enumeration map (which corresponds to /dev/sda.../dev/sdl).
  5. That sounds like backing up a client and being able to restore it to indepenent hypervisor a la VEEAM, not virtualizing DSM for profit. If Synology were to license DSM for virtualization on non-Synology hardware, there would not be much point to XPenology. I am personally all for it, but the model that has emerged so far is subscription-only and the pricing is a bit steep (QuTSCloud, $20/month for 4 cores - yikes). If Synology were to market a perpetual-use license (even with a limited upgrade mode) for a reasonable price, for virtualization, I would think it would strongly appeal
  6. Thank you for posting the solution, hopefully that will help someone else.
  7. DiskIdxMap and SataPortMap
  8. Not a helpful comment per se, but I can confirm replication does work fine over high latency connections and VPN. Make sure each side can PING the local VPN interface as well as the remote one.
  9. No I cannot assure you of that. It depends on whether the HP controller applies a metadata wrapper using part of the disk storage or not. But generally, running it in AHCI mode is a superior solution for working with DSM.
  10. I just use Snapshot replication to another DSM instance; that way not to worry about quiescing the Docker containers for data integrity.
  11. This guide doesn't help you recover any data; it only gets you access to a functioning array if you can't boot DSM. If you have a problem with your array, it very well will make things worse. Put it all back and start posting diagnostic information. @pdavey's approach is a good start.
  12. One last point, if you offload the files and find that critical items are corrupted, we still have the secondary option to use the /dev/sda7 copy of /dev/md3, repeat the process, and manually extract those specific corrupted files (in hopes that they are intact on the other copy). Obviously that's a little more heavy lifting, but do keep it in mind to evaluate before you do anything destructive with your Storage Pools, drives, etc.
  13. If you attached a large USB connected disk, it will be accessible from the command line as /USBVolume1 (or something similar to that). You may have to format it from the Control Panel UI. rsync is probably the best way to get everything over intact if you have direct-connected storage.
  14. I think we are crossing paths again, File Station is the only web interface tool that I would use at this point. If it were my data, I would use RAID5 with non-SMR drives and then a remote backup copy (RAID is not backup) but I don't intend to soapbox you until you actually get your data recovered