tracky
-
Posts
9 -
Joined
-
Last visited
Posts posted by tracky
-
-
use the script on proxmox 6.2, update from 6.2.3-25423 to DSM 6.2.3-25426, works like a charm
thank you!!!
-
- Outcome of the update: UNSUCCESSFUL
- DSM version prior update: DSM 6.2.3-25423
- Loader version and model: Jun's Loader v1.03B 3615XS
- Using custom extra.lzma: No
- Installation type: VM - Proxmox 6.2 - HP Microserver Gen8 E3-1230 V2 - Custom NIC e1000e
- Additional comment : ERROR 21 while loading update
-------------------------------------------------------------------------------------------------------------------------------------
after use FixSynoboot.sh, everything is ok
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 6.2.3-25423
- Loader version and model: Jun's Loader v1.03B 3615XS
- Using custom extra.lzma: No
- Installation type: VM - Proxmox 6.2 - HP Microserver Gen8 E3-1230 V2
- Additional comment : Custom NIC e1000e + FixSynoboot.sh
-
1
-
-
- Outcome of the update: UNSUCCESSFUL
- DSM version prior update: DSM 6.2.3-25423
- Loader version and model: Jun's Loader v1.03B 3615XS
- Using custom extra.lzma: No
- Installation type: VM - Proxmox 6.2 - HP Microserver Gen8 E3-1230 V2 - Custom NIC e1000e
- Additional comment : ERROR 21 while loading update
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 6.2.2-24922 Update 4
- Loader version and model: Jun's Loader v1.03B 3615XS
- Using custom extra.lzma: No
- Installation type: VM - Proxmox 6.1 - HP Microserver Gen8 E3-1230 V2
- Additional comment : Custom NIC e1000e
-
- Outcome of the
installation/update: SUCCESSFUL- DSM version prior update: DSM v6.2-23739-2
- Loader version and model: Jun Loader v1.03b - DS3615
- Using custom extra.lzma: NO
- Installation type: VM - Proxmox 5.4-3 (HP GEN8 G1610T)
- Additional comments: Changed LAN from e1000 to e1000e
-
On 3/18/2019 at 7:40 PM, hellbondz said:
Hi everyone. After a grate help from 'dodo-dk' (You're the best man) and a lot of try and errors i managed to run DSM 6.2.1u6 on Proxmox 5.3-11. I'll share my insights and maybe it'll be useful for someone. Proxmox does have 4 LAN cards model to chose from the list, but as we all know Synology dropped drivers for some devices (e1000, vmware3...) so new version of DSM stopped working on Proxmox. But Proxmox allows you to chose different models (not shown in choosing list) , we just have to add it to 'args:' parameters, just like we did with usb boot key. For this to work you need to know few things:
1) This won't work on OVS bridge/bond - it has to be Linux bridge/bond
2) The Linux bridge/bond has to have gateway set
When we are adding LAN card from 'args:' it looks like the LAN card chooses bridge/bond on which the gateway is set, so that's why it's needed to be set.
First thing you may check it's if e1000e LAN card is available in your kvm. So in Proxmox shell write command:
kvm -device help
Under 'Network devices' you should see line:
name "e1000e", bus PCI, desc "Intel 82574L GbE Controller"The next step is to find your 'args:' parameters. To do this we need to use another command:
qm showcmd YOUR-VM-ID
YOUR-VM-ID - is ID of your Xpenology machine with added e1000 LAN card. From the output you need to copy two arguments: netdev and device. In my case it looks like this:
-netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown'
-device 'e1000,mac=00:11:32:2c:a7:85,netdev=net0,bus=pci.0,addr=0x12,id=net0'
For this to work you have to remove the 'script' parts from 'netdev'' and change model from 'e1000' to 'e1000e' in device argument. you can also remove the " ' " signs. After changes it should look like this:
-netdev type=tap,id=net0,ifname=tap100i0
-device e1000e,mac=00:11:32:2c:a7:85,netdev=net0,bus=pci.0,addr=0x12,id=net0
Next you need to add changed arguments in to the VM config file (/etc/pve/qemu-server/YOUR-VM-ID.conf). In my case 'args:' line looks like this:
args: -device ich9-usb-ehci1,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/var/lib/vz/images/103/vm-103-USB103b.raw,format=raw,if=none,id=drive-usb-disk2,cache=writeback -device usb-storage,bus=usb.0,port=2,drive=drive-usb-disk2,id=usb-disk2,bootindex=1,removable=off -netdev type=tap,id=net0,ifname=tap103i0 -device e1000e,mac=BA:E2:8A:3B:AC:3E,netdev=net0,bus=pci.0,addr=0x12,id=net0
The last thing is to remove the 'net' device from config file, so just comment or remove the line with 'net' device. In Proxmox web interface the LAN device wont be visible, but it will work.
So, summing things up, I'm not Proxmox specialist so i didn't knew all of that. One more time thank you 'dodo-dk' for your knowledge and time. God bless all Xpenology enthusiasts, Xpenology devs and Proxmox for being best free virtualization tool i know.
thanks very much
GEN8 G1610T, Proxmox 5.4.3, Loader 1.03b, update to DS3615xs 6.2.2, work like a charm
-
On 11/25/2018 at 5:41 PM, Redbeard said:
Currently my HP Gen8 Microserver is thinking its a DS3615xs running version DSM 6.1.5-15254 Update 1.
I am using Jun's loader 1.0.2b. I read about a new loader but thats not mentioning DS3615xs, but ds918. Can i use this loader and let my Gen8 think its a newer DS918 model? Anyone tried?
GEN8 (CPU 1610T), 1.04b ds918, can't find IP.
I return to 1.03b ds3615xs, DSM 6.2-23739 Update 2, work like a charm
-
2
-
-
thanks rhplus
HP GEN8 + Proxmox 4.4 + 5.2.5967 Update 1
work like a charm
DSM 7.1.1-42962 Update 2
in DSM Updates Reporting
Posted
- Outcome of the update: UNSUCCESSFUL
- DSM version prior update: TCRP v0.9.2.6 DS3622xs+ DSM 7.1.1-42962 Update 1
- Loader version and model: TCRP v0.9.2.9 DS3622xs+ DSM 7.1.1-42962 Update 2
- Using custom extra.lzma: no
- Installation type: Proxmox 7.2 - HP Gen8
- Additional comments:
updating from the DSM GUI, but the system got stuck in a recovery loop.
postupdate command didn't fix it.
tcrp friend didn't fix it too.