blessendor

Members
  • Content Count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About blessendor

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Happy to help. A like from you to my post will be enough of thanks)
  2. You can try my steps
  3. Add to your vmid.conf serial0: socket Then qm start vmid qm terminal vmid You will see more information during start If you see 'DiskStation' greeting login - your DSM in the setup stage...
  4. That server running in the datacenter, so any hw router in-front. I use firewall on DSM and 2-factor auth.
  5. I'm not sure how bond can be configured in my case, because I must separate public (Internet) from private (Local) networks.
  6. It was the first reboot after starting Upgrade DSM - so my version was 6.2.2-24922 - but with not yet finished upgrade. There were two problems: 1) boot from USB img failed - fixed by replacing ich9-usb-ehci1 to nec-usb-xhci (found examples on the proxmox wiki page), 2) next I was must remove 'scsihw: megasas' string (I have 6 SATA and 2 SCSI disks attached to this VM, so I played with different SCSI controller model in the past on first-time setup). Solved.
  7. BTW, I got kernel panic after linux upgrade (and/or after DSM upgrade) on this server https://pastebin.com/CLetnkD0 CPU is Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
  8. UPD: After Linux/proxmox upgrade some patched script will also be upgraded (as was expected) and you can't just restore your patched version by replacing a new. You need to edit a new version of this script because old will not be compatible with pveproxy service. In my case after today Linux/proxmox upgrade, I patched again only QemuServer.pm. So always make a backup of the original proxmox scripts before patching. UPD2: Looks like you must restart pvedaemon with pveproxy service also (step 4 in my previous post).
  9. After successful testing of the @hellbondz's method, I found that my second network interface in the DSM is inaccessible from my LAN (I use multi-homed network). This was happened because: Without this script PVE will add both netdev into default bridge - vmbr0 (a public bridge in my case). I patched two PVE scripts to be able add network interface with Proxmox GUI and staying out from edit config manually (what somebody can't do it correctly). So my method of using Network Driver Intel e1000e with Proxmox, which required to be able upgrade to the the latest DSM version (current up to DSM 6.2.2-24922 Update 2) and keep network worked: 1) Make DSM VM backup as usual! 2) Make PVE scripts backup: cp /usr/share/perl5/PVE/QemuServer.pm /usr/share/perl5/PVE/QemuServer.pm.default cp /usr/share/pve-manager/js/pvemanagerlib.js /usr/share/pve-manager/js/pvemanagerlib.js.default 3.1) Open /usr/share/perl5/PVE/QemuServer.pm find needed block with keyword 'e1000 (or 'vmxnet3' - less results than for '1000') replace: my $nic_model_list = ['rtl8139', 'ne2k_pci', 'e1000', 'pcnet', 'virtio', 'ne2k_isa', 'i82551', 'i82557b', 'i82559er', 'vmxnet3', 'e1000-82540em', 'e1000-82544gc', 'e1000-82545em']; to (add 'e1000e'): my $nic_model_list = ['rtl8139', 'ne2k_pci', 'e1000', 'e1000e', 'pcnet', 'virtio', 'ne2k_isa', 'i82551', 'i82557b', 'i82559er', 'vmxnet3', 'e1000-82540em', 'e1000-82544gc', 'e1000-82545em']; 3.2) Open/find/replace /usr/share/pve-manager/js/pvemanagerlib.js if ((match_res = p.match(/^(ne2k_pci|e1000|e1000-82540em|e1000-82544gc|e1000-82545em|vmxnet3|rtl8139|pcnet|virtio|ne2k_isa|i82551|i82557b|i82559er)(=([0-9a-f]{2}(:[0-9a-f]{2}){5}))?$/i)) !== null) { res.model = match_res[1].toLowerCase(); to: if ((match_res = p.match(/^(ne2k_pci|e1000|e1000e|e1000-82540em|e1000-82544gc|e1000-82545em|vmxnet3|rtl8139|pcnet|virtio|ne2k_isa|i82551|i82557b|i82559er)(=([0-9a-f]{2}(:[0-9a-f]{2}){5}))?$/i)) !== null) { res.model = match_res[1].toLowerCase(); next replace block: Ext.define('PVE.form.NetworkCardSelector', { extend: 'Proxmox.form.KVComboBox', alias: 'widget.pveNetworkCardSelector', comboItems: [ ['e1000', 'Intel E1000'], ['virtio', 'VirtIO (' + gettext('paravirtualized') + ')'], ['rtl8139', 'Realtek RTL8139'], ['vmxnet3', 'VMware vmxnet3'] ] }); to: Ext.define('PVE.form.NetworkCardSelector', { extend: 'Proxmox.form.KVComboBox', alias: 'widget.pveNetworkCardSelector', comboItems: [ ['e1000', 'Intel E1000'], ['e1000e', 'Intel e1000e'], ['virtio', 'VirtIO (' + gettext('paravirtualized') + ')'], ['rtl8139', 'Realtek RTL8139'], ['vmxnet3', 'VMware vmxnet3'] ] }); 4) Run 'service pveproxy restart' and reload PVE admin interface - you will be able to change the Network driver of your DSM VM from e1000 to e1000e. 5) Save copies of edited scripts to somewhere else to be able restore/compare scripts versions after Proxmox upgrades. Again - make backups before run any test from my tutorial. Good luck
  10. It works, thank you Proxmox 5.3-5 DS3617xs DSM 6.2.2-24922 Update 2 Loader V1.03b for DSM 6.2 (current)
  11. DS918+ loader does not boot anything in my Proxmox
  12. @wenlez I can only upgrade to the posted above version - DSM_DS3617xs_23739.pat + update 2 pack
  13. Как можно все импортированные в Synology Office документы с внесенными правками, версиями, перенести на другую хрень? Я пробовал способом синхронизации папки, подключенной к Drive/Office - внес изменения в документ, получил файл формата Syno-Office, и он успешно прилетел на другой DSM. Путь общей папки такой же, имя то же. Но открыть такой файл на втором DSM невозможно - где-то хранится реальный объект, которому офис сгенерировал свой UUID и записал его в БД - но эта БД не копируется во время синхронизации папки. Где-то лежит БД с этими связями имя_файла->uuid и ее нужно дампить и испортировать напрямую черз mysql? Как вообще можно мигрировать на новый DSM со всем массивом наработок в офисе?
  14. Maybe I something forgets, but try with the next scenario (I'm sure I did these steps): 1) Boot from DS3617xs 6.1 Jun's Mod V1.02b.img -> https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg?PZ4UEJDQ 2) Install DSM DSM_DS3617xs_15284.pat 3) Then after successful install and several times reboot - power off your VM (from DSM login menu in the right corner - it must work). 4) Change bootloader in the VM config to the synoboot_3617.zip -> https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg?7NpGVKIA 5) Install upgrade from DSM update menu: DSM_DS3617xs_23739.pat 6) After reboot - install update 2 pack from DSM update menu: synology_broadwell_3617xs.pat 7) Backup your VM
  15. It seems you still use the wrong bootloader or you installed latest DSM in automatic mode - this log about kernel panic error, and you can't fix it without changing bootloader and/or DSM version for install.