• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About denmalley

  • Rank
  1. Ok now I've disconnected the SSD drive and reconnected the original raid drives. Rebooted the system, and it shows up in it gives the option to migrate data...but Still asking for an update, but it allows you to provide a pat file rather than download the latest. Tried using the one provided in the tutorial, but the system will not allow it - "must be 23739 or later" so I got Jun's 1.03b loader so it can handle the 23739 update. went to the synology archive and navigated to the 23739 folder, got the ds3617 pat file rebooted the machine wi
  2. Ok, so here's where I'm at: - created a new loader usb stick. - booted successfully - took me to a screen asking me to install the DSM software (everything had been running on my four raid drives so I had them unplugged and instead have a blank ssd plugged in. - software installed, then the reboot cycle started. When it finished, it said it couldn't find the device. - gave the option to "detect manually" which redirected to find/ - now it is sitting at this screen: Only the "newer DSM" it wants to instal
  3. The server is present in the router's device list. Set to static. Pings fine. (based on those facts I don't see it necessary to check the cable) I don't think it has iDRAC, no mention in the online info for this server model. I guess I'll try to build a new boot usb. Is there a better option for a more stable boot solution than a usb stick? Sure don't wanna do this again in 6 months.
  4. Hi, I am running jun loader 1.02b, installed per tutorial. Running on bare metal Dell T30 server as DS3617xs. It had been running fine for about 6 months or so. I think I maybe updated the DSM once in that time, so I think I'm running 6.1.7-15284 if I recall correctly. Didn't take the jump to 6.2xx and beyond. A few weeks ago, I got the "Sorry, the page you are looking for is not found." synology splash page when trying to access via web browser. Doing a little googling presented a handful of solutions that involve putty, but I am getting "connection refused" when t
  5. Do you speculate that they'll continue to "root out" past generated S/Ns or would it just be a problem for those generating new S/Ns in the future?
  6. Fellow noob here. I just got a Dell t30 that came with 8GB ECC and added another 8GB stick. Put 4 - 3GB WD Reds in there and followed this guide: It took me a few read-throughs to really "get" it, but I am also totally linux illiterate and had this up and running within 1/2 hour. BTW I used a sandisk cruzer mini flash drive (32GB for $12 on amazon) - better to use a known brand name for your flash drive than some scrappy junk drive you have laying around. And this minis sit flush in the port. Currently running using jun's 1.02b loader as a synology DS3617XS, DSM ve
  7. Docker is sooo easy though. I'm brand new to this project and I have sonarr and nzbget working flawlessly on a bare metal Dell T30 with 6.1.3 I was in the same boat, not thrilled that synocommunitywas broken for 6x and not crazy about using docker. Check out the guides at
  8. HI there! Looking forward to exploring this awesome software. I successfully loaded a Dell Poweredge T30 bare metal with the DS3617xs version of DSM, and now that I'm in, I'm basically wondering if I need to be wary of anything as far as using the "official" synology services. Like can I go to their package center to get stuff? I guess I should turn off automatic updates? I unchecked anything during setup regarding sending them any info, but I guess basically wondering if there's anything I need to watch out for in settings or access that will violate TOS or whatnot. In the m