hellbondz

Members
  • Content Count

    49
  • Joined

  • Last visited

  • Days Won

    2

hellbondz last won the day on April 10

hellbondz had the most liked content!

Community Reputation

6 Neutral

About hellbondz

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Please start small. Change bootloader to 1.3b version for ds3617xs from this link : https://mega.nz/#!zcogjaDT!qIEazI49daggE2odvSwazn3VqBc_wv0zAvab6m6kHbA, Next find.syno.... and install this file: https://global.download.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat?model=DS3617xs&bays=12&dsm_version=6.2.2&build_number=24922. There's a difference with ds3617xs and ds3617xs+ version.
  2. If your DSM works as an internet router with DHCP server and is accessible from internet, than bond configuring would be complicated (if not impossible). But if that's the case i strongly suggest against it, especially considering recent events - https://xpenology.com/forum/announcement/21-very-important-brute-force-attack-against-synology-nas/. My proxmox\synology stands behind DD-WRT router so it isn't accessible from internet.
  3. Everything works on my side. I just updated proxmox 5.4 to 6.0-5 working on DSM 6.2.2-24922 Update 2. What's your DSM version?
  4. Hi that's great solution also. In my case i just created a bond from few network cards. And pass every virtual LAN card trough this bond. Also work's good and it's more "update proof" ;).
  5. Ok three things. I'm not sure that usb drive still works on piix3-usb-uhci. Please change it to ich9-usb-ehci1. Example: -device ich9-usb-ehci1,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/var/lib/vz/images/100/synoboot.img,format=raw,if=none,id=drive-usb-disk2 -device usb-storage,bus=usb.0,port=2,drive=drive-usb-disk2,id=usb-disk2,bootindex=1,removable=off and verify if path: /var/lib/vz/images/100/synoboot.img is really available. Next thing is that you have comma sign on end of "-device..." declaration and before "-netdev..." declaration (-device usb-storage,id=synoboot,drive=synoboot,-netdev), so please remove it and insert "space": (...)drive=s ynoboot -netdev(...) Last thing is that you have ",bootindex=200" option at the end of the net device declaration. I don't know what this option does but i don't have it (it may be irrelevant). Please let me know i this will work for you.
  6. Please paste your VM config.
  7. Please read carefully my earlier post ID: 157, and next time please try to read first and ask questions later.
  8. What network card model did You chose when you created your VM?
  9. Is it at machine startup? Please write exactly what version of proxmox do you have, and please show your vm config.
  10. 6.2.2 works with proxmox, You just need to do some editing in vm config files. Check out this thread
  11. You really need so much power just for NAS?
  12. If you try it on proxmox and still get Hdd errors, than my guess would be some hardware malfunction.
  13. I'm just curious did you try to run it on Proxmox? I'm using it for few years with xpenology, and never had disk problems.
  14. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: Jun's v1.03b DS3615sx - Using custom extra.lzma: NO - Installation type: VM - Proxmox 5.3-11 - Additional comments: Changed LAN from e1000 to e1000e
  15. I have older hardware, based on socket 775. From what i know and tested 1.04b does not run on core2duo, it needs at least Haswell CPU. My hardware has much too much power for my DS3615xs setup so i don't see a point in forcing to 1.04b loader and change hardware. Basically for my needs i don't need DS918+ features 😉. Cheers.