• Announcements

    • Polanskiman

      DSM 6.2-23739 - WARNING   05/23/2018

      This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked.  You have been warned.   https://www.synology.com/en-global/releaseNote/DS3615xs

spyrule

Members
  • Content count

    49
  • Joined

  • Last visited

Community Reputation

0 Neutral

About spyrule

  • Rank
    Junior Member
  1. Thanks guys, a great community as usual!
  2. Thanks for the info. Sound stupid, but its been so long since I've done the vid/pid step, can you link me the instructions where it describes that process?
  3. Hello, Its been awhile since I hit these forums, and I realized today that it has been awhile since I last upgraded my current Xpenology box. I'm currently running DSM 6.0.2-8451 Update 11 on a DS3615 image with (if I remember correctly) Jun v1.01 boot. I'm now reading that the Jun 1.02b is a fairly stable upgrade for AMD based systems (AMD FX based system). However, I'm noticing images for DS3617 based systems now. Can I upgrade my bootloader AND DS platform at the same time if I've been running DS3615 this whole time? Is there any benefit of going from 3615 to 3617? Thanks in advance guys, Spy
  4. DSM 6.x.x Loader

    Sorry guys, Its been awhile since I've popped in here, I'm just curious, is AMD hardware being dropped, or is it just a delay on the new bootloader to get it to work?
  5. DSM 6.x.x Loader

    So I can confirm Jun 1.02a with 6.1.1-15101-1 Baremetal on a Dell DCS C6005 (C6100 series cloud server) running the Dual AMD Opteron 2419EE, 48GB of Ram and using the onboard 6 port sata connections, I am not using the onboard pci-e slot just yet, but I'll be testing a Mellanox ConnectX-2 in the next week or two (hopefully). Just for sake of notes: Install using DSM_DS3617xs_15047.pat with the Jun 1.02a (NOT 1.02a2) I then used the DSM update option to upgrade first to 15101, then again to update to the 15101-1 version. So far, everthing seems fine.
  6. DSM 6.x.x Loader

    Can someone link a 6.1 Pat file that worked for 1.02a2 loader? I've tried a few and none seem to work on my baremetal setup (Dell DCS C6005)
  7. Does anybody know of the drivers for the Mellanox ConnectX2 cards are included in this build ?
  8. I used this http://www.xpenology.com/forum/viewtopic.php?f=2&t=22100 to upgrade from 5.2 worked perfectly Update instructions are intentionally left blank until rerelease. I jumped the gun thinking it was ready, but missed a couple of things. Don't worry it will be back. Sent from my SM-N920T using Tapatalk Nono, thank you! I literally just read about this release today, so I'm just happy to have an upgrade path! Would this next release likely be ready for "home" production ?
  9. When is the hopeful date to have Upgrade instructions for people coming from 5.2 ?
  10. DSM 5.2-5967 out now - safe to install?

    So, It turns out it was a bad NIC on my Domain Controller (which is also my primary DNS/DHCP server). Once I fixed its connection, everything started to respond and work correctly again. Still not sure why the GUI wouldn't load (even with an IP instead of Domain name), but as long as it working, thats my main concern.
  11. DSM 5.2-5967 out now - safe to install?

    I upgraded a few weeks back, and only just rebooted my NAS for other reasons (UPS swap), and now I cannot get into my NAS via network. First thing to note, I have not changed any configurations within my network at all (literally shut everything down, swapped an NMC card on my UPS, and powered everything back up). I'm getting an IP on each interface on my NAS (one 10Gig fiber, 1 x 1Gig NIC), and I can ping out from the NAS, but I cannot ping back to the nas from the rest of the local network. If I try to use Synology Assistant, it finds the two ports, but it says connection failed, and gives me the option to "setup" my NIC (which fails). I'm at kind of a loss as to what is going on here...
  12. Any easy way to identify HDDs on custom hardware?

    Don't know why shutting down didn't occur to me. Luckily, most of my NAS is backed up daily via Crashplan. Luckily, I was able to find my original setup notes where I identified each drive by serial # against the physical drive cage # (and slot its in). I just had to go digging for those notes. I was hoping to be able to identify the drives via Lights, but I guess manual control is my best long term option.
  13. Hey guys, I'm running 5.2-5644 u 8 on a Dell PE2950 hardware. Its been running great, except one of my hdd's received a bad sectors error, but the NAS recovered from it. The drive is currently operating "normally" but these are older WD Green Desktop harddrives (that I fully planned to replace as I had money for replacement drives). I have some replacement hard drives in my hands now to replace the bad drive, except they are numbered Disk 3 through 8 (6 disks total). I don't know how to identify the initial problematic drive without physically pulling them. Is there a command line util to make the hdd controller set the drive as degraded/shutdown ?
  14. Has anybody tried simply installing this patch via manual patch?
  15. DSM's GUI, how is it coded?

    Perfect!, Exactly what I wanted to know. Thank you!