Jump to content
XPEnology Community

Twisted

Member
  • Posts

    27
  • Joined

  • Last visited

Posts posted by Twisted

  1. Is your switch IEEE 802.3ad compliant?

    It does not say anything about it in the documentation, so I don't think so. This is a pretty popular switch, so I am surprised I cannot find any information on IEEE 802.3ad:

     

    TP-Link 8-Port Gigabit Ethernet Web Managed Easy Smart Switch (TL-SG108E)

     

    Are all 4 NICs the same model?

    Yes, I am using all 4 ports on a NIC card:

     

    HP NC364T PCIe 4Pt Gigabit Server Adptr

  2. So I manually set the MTU value from 2000 to 1500 during the bonding process and I was able to get it to bond. It says it is connected, but I get the following error message.

     

    1000 Mbps, Full duplex, MTU 1500, Failed to establish IEEE 802.3ad connection.

     

    I have it connected to a new switch that is powering the server and it does support link aggregation and is setup properly (I think). Any ideas on this error message?

  3. I tried 4 with the tutorial below and it will freeze at about 90% of completion. It recognizes the ports, so I don't think its a driver issue, but I could be wrong. I bought the HP NC364T PCIe 4Pt Gigabit Server Adptr. Is there a compatibility list anywhere?

     

     

    I am nervous to try again, as it destroys the installation, but I would like to fix this as the transfer rates are not that great and I have a lot of large files to move.

  4. i think polanskiman said the 1.02a2 is pretty much the same as 1.02a, just extended for 3617xs (such as time bomb fix), so why not using 1.02a for 3615xs? it a working solution

     

    1.02a for 3615 seems to have mixed results. I am still stuck on error code 13 with no end in sight. :???:

     

    Proper vid/vip? Tried a force install?

     

    @Polanskiman I figured it out. I accidentally removed 0x from the VID & PID :roll:

  5. Can anyone tell me if you need to reformat your HDD and remove all of the old Synology files in order to perform a bare metal install? When I choose clean install on the migrate screen, I keep getting error code 13.

     

    Hi, I have bare metal just install with latest DSM 6.1.1-15101 Update 4 from 6.0.2

     

    I create a bootable disk from 1.0.2a2

    Change VID & PID for my flashdrive

    Change MAC ADDRESS : you can use this guide how to change http://xpenology.me/how-to-generate-synology-mac-and-serial-valid-pair/

    Plug in flashdrive, boot it up

    type find.synology.com, click migrate from DS3615 to DS3617

    Click migrate again for clean install.

    and Wait, Done.

     

    My baremetal able to boot now I will copy some files and test it.

     

     

    @astrorion Thank you for the suggestion. I have a 4 core CPU, does this work for an Core i7? The DS3617 is meant for more cores.

  6. Can anyone tell me if you need to reformat your HDD and remove all of the old Synology files in order to perform a bare metal install? When I choose clean install on the migrate screen, I keep getting error code 13.

  7. i think polanskiman said the 1.02a2 is pretty much the same as 1.02a, just extended for 3617xs (such as time bomb fix), so why not using 1.02a for 3615xs? it a working solution

     

    1.02a for 3615 seems to have mixed results. I am still stuck on error code 13 with no end in sight. :???:

     

    Proper vid/vip? Tried a force install?

     

     

    Yes. I also tried force install with no luck. Do I need to reformat the drive to erase all past files for a clean install to work? I tried a clean drive last time and same error. I also tried DSM_DS3615xs_15047.pat and DSM_DS3615xs_15101.pat with the same error for both. Any suggestions would be appreciated.

  8. i think polanskiman said the 1.02a2 is pretty much the same as 1.02a, just extended for 3617xs (such as time bomb fix), so why not using 1.02a for 3615xs? it a working solution

     

    1.02a for 3615 seems to have mixed results. I am still stuck on error code 13 with no end in sight. :???:

  9. Do you have a data backup?

     

    I had this when I was building my server and ended up doing a forced re-install. I had no data on there then so did noit pay attention to what impact it will have on your data sorry. Still quite new to xpenology.

     

    What I can say is that a fresh install on blank drives works just fine bare metal and will update perfectly to 6.1.1 update 2. I have mine operating and have copied all of my data from my production NAS across to it and it seems stable and is past the 24hr timeframe.

     

    Pretty sure some comments in thread suggest that you cannot upgrade yet you have to do it as a fresh install.

     

    Can you please share the details of what you used? I just tried this with DS3615xs 6.1 running Jun's Mod V1.02-alpha and DSM_DS3615xs_15047.pat and still received error code 13.

  10. I was running DS3615xs 6.0.2 with Jun's Mod V1.01 and decided to do another bare medal install with DS3615xs 6.1 running Jun's Mod V1.02-alpha and DSM_DS3615xs_15047.pat and DSM_DS3615xs_15101.pat. I kept getting error 13 when I chose to migrate and choose a fresh install.

     

    So I put a brand new hard drive in to trouble shoot if that's what was needed to be a 100% clean install and I still got the same error 13. Before I revert back to 6.0.2, I wanted to see if anyone had any suggestions?

  11. can some one please tell me what pat file i should use with V1.02a2

    i have tried pat files DSM_DS3617xs_15101.pat, DSM_DS3617xs_15047.pat and DSM_DS3617xs_8754.pat

     

    they all get to around 56% install then they fail with a your pat file may be corrupt but i don't think they are

     

    I also used DSM_DS3617xs_15101.pat and had the same error. :sad:

×
×
  • Create New...