• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About cstout

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. @fjf I have a full backup on my DS412+ so I pulled 5 of my 8 drives and the 1517 booted right up with my login. Logged in with my DSM config in-tact and my array degraded (as it should be). I removed the volume and restored from backup. I am planning on replacing the old drives anyway so if I can't find what's causing this strangeness then I'll be doing a clean install with the new drives anyway. Just thought it was interesting enough to share is all.
  2. Strange as it may be it worked wonderfully with the exception of this one small thing (which is no deal breaker). It's mostly just piqued my curiosity to see if anyone was aware of a modification within DSM outside of or carried over from the XPE usb booter. In the meantime I'll post any updates I get as I work with support. If this was a deal breaker I would of course start fresh but I preferred to see if a migration would work (it almost entirely did) and I wanted to retain my app data and customizations from the last four years. Thanks all!
  3. Yes, it's the same account, but even if I wanted to change it I can't. I can't get the login/register window to open whatsoever. Also, I use this same account for my DS412+ and it still works with that same account so I'm leaning more toward some file/setting that migrated over from XPE into the real hardware.
  4. @Polanskiman, please note I am not asking for tips or tricks to abuse QuickConnect on XPE. I've been working with Synology support and they don't know what the problem could be and I'm curious if it's something that carried over from XPE. Ok, so I've used XPEnology for about 4 years now and have loved it. So much so that I recently bought and migrated to a DS1517+. This thing is great. I got excited to use QuickConnect legitimately but quickly found that I am unable to even log in. I get hit with the same screen that many XPE users see, which is, "The system failed to perform the requeste
  5. Thank you for your understanding. I appreciate all your contributions to this forum. I will work toward moving away from QC on my off site XPE box to avoid anymore topics like this.
  6. @Polanskiman, I am most certainly not complaining about the service not working. I asked a question whether others were experiencing the same issue. Also, I OWN a legitimate Synology box and don't use QuickConnect on it. I do, however, use QuickConnect on one remote XPE box that doesn't work reliably with DDNS services. It's interesting to see this policing and strong opinion when the forum allows and outlines how to set up QuickConnect on XPE yet when you ask a question about it you get smacked in the face. I'm not trying to perpetuate a dead topic. For anyone having the same issue i
  7. Wow. Useless. This is a *forum* and there are plenty of guides for setting up QuickConnect. All I did was ask if others are being blocked from this service. I'm not throwing out entitlement or any BS that would provoke such an arrogant response.
  8. I've been using QuickConnect successfully for over a year now on an off-site box and just a few days ago, while I was connected to DSM (XPE 5.1) I lost the connection and now all the iOS apps and the QuickConnect link for web access no longer work. I restarted the box multiple times and everything works locally, but I'm curious if anybody else has been blocked from QuickConnect when using a generated serial and MAC address. I'm going to try logging out and back into the QuickConnect service in Control Panel but I don't know why, other than a block, out of nowhere it would stop working. Has any
  9. Hardware: Dell OptiPlex 7010 SFF Install Type: Baremetal NIC Model: Broadcom, supported Storage: SATA, 1x500GB HDD Issue: Installation/Hard Drives Loader Version: 2.2 I am eager to test this new loader but I keep running into an error on the initial setup screen (see photo below). I only have one hard drive installed (HGST 500GB SATA) and the BIOS is configured for AHCI SATA operation mode and only the SATA-0 port is enabled in the BIOS. This is my XPE test box and has been fully compatible with ever other loader that's come across this website. I'm curious what the hangup is he
  10. cstout

    DSM 6.1.x Loader

    I successfully installed DSM 6.0.2-8451 Update 4 on my bare metal box without any issues.
  11. cstout

    Working DSM 6

    I migrated from the latest version of XPE 5.2 to 6 on SHR without any data loss. It's called a "migration" and DSM handles it perfectly. @foster182, your doubt is pretty close to exactly what I did. The only difference is that when you burn the dsm6 loader to USB just make sure to enter your config for SN and MAC address.
  12. cstout

    DSM 6.1.x Loader

    I had this same issue initially and read that you had to swap out a file on the flash drive with an updated one. Sorry that's vague and not very helpful, but if you haven't already, I'd recommend starting over with jun's v1.0 that just released. The file swap and many other issues are all fixed in this release. I also use Optiplex 760's and I am very happy with them. Edit: Sorry, just saw your most recent post so this is irrelevant. Congrats on the successful build!
  13. Hello out there, I'm asking this question on behalf of anyone else out there that may have some obsessive compulsive tendencies... Since switching my RAID mode to AHCI (required for DSM 6 bare metal boot) my motherboard SATA and Marvell SATA connections are separated by four blank drive spaces (images below). I've seen the question asked before, but I have not found any threads with an answer or solution. Does anybody know how the drives are numbered in DSM? Is it possible to change the order? In XPE 5.2 I had this exact same issue and disabling eSATA in the BIOS removed the gap and pl
  14. cstout

    DSM 6.1.x Loader

    Simple enough! Used vi to edit /usr/share/init/syno_poweroff_task.conf, found the line with console output and changed to console none. No more improper shutdown message.
  15. cstout

    DSM 6.1.x Loader

    I feel like I'm missing something very simple...would you tell just how you made this change?