fonix232

Tutorial: DSM 6.x on Proxmox

Recommended Posts

You must read once more my next post:

 

And second one:

 

 

And use correct boot loader.

Latest 1.04 bootloader don't work for me also (with Proxmox).
 

 

Share this post


Link to post
Share on other sites

after the install the vm isn't getting an ip address...i dont really see any errors...

[   49.325024] RIP  [<ffffffff81007aa2>] dma_set_mask+0x22/0x50
[   49.325024]  RSP <ffff88010a997c00>
[   49.325024] CR2: 00000000ffffffff
[   49.506556] ---[ end trace e169fc0603087d05 ]---
[   49.518569] pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de
[   49.526119] VMware vmxnet3 virtual NIC driver - version 1.1.30.0-k-NAPI
[   49.545742] cnic: Broadcom NetXtreme II CNIC Driver cnic v2.5.16 (Dec 05, 2012)
[   49.564534] r8168: Unknown symbol pci_disable_link_state (err 0)
[   49.572138] r8169: Unknown symbol pci_disable_link_state (err 0)
[   49.590418] usbcore: registered new interface driver ax88179_178a
[   49.596941] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[   49.598847] ACPI: Power Button [PWRF]
[   49.654393] 2018-12-14 21:59:35 UTC
[   49.655258] synobios: load, major number 201
[   49.656277] Brand: Synology
[   49.657006] Model: DS-3617xs
[   49.657693] set group disks wakeup number to 4, spinup time deno 7
[   49.659116] synobios cpu_arch proc entry initialized
[   49.660262] synobios crypto_hw proc entry initialized
[   49.661418] synobios syno_platform proc entry initialized
[   49.662686] synobios open /dev/ttyS1 success
[   53.425281] usbcore: registered new interface driver usblp
[   53.542982] usbcore: registered new interface driver usbhid
[   53.544890] usbhid: USB HID core driver
[   53.571331] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/input/input1
[   53.574513] hid-generic 0003:0627:0001.0001: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
Fri Dec 14 13:59:40 2018
DiskStation login: [   55.782980] ata2.00: configured for UDMA/100
[   55.784390] ata2: EH complete
DiskStation login: 

 

Edited by Polanskiman
Added code tag

Share this post


Link to post
Share on other sites
3 minutes ago, Bar1 said:

[   49.526119] VMware vmxnet3 virtual NIC driver - version 1.1.30.0-k-NAPI

 

Seems you don't know how to read somebodies lessons)

 

vmxnet3 instead intel e1000? Really?

 

Share this post


Link to post
Share on other sites
Just now, Bar1 said:

 

i did notice that....but my network is definitely set to e1000....

Sorry, U'r right, it's just a synology's modules loading and vmxnet3 also there.

You will not see IP ion the terminal boot log after install - log in (type your admin username and password here - which you choose during install.

Then execute 'ip a' command, and you will see your interface addresses.

Or you can check your DHCP server for latest leases address (belong to your mac).

 

  

Share this post


Link to post
Share on other sites

i didnt get to the part where you set your username and password....by the way, thank you so much for your help!

and my dhcp isn't showing DSM is connected.

 

Share this post


Link to post
Share on other sites

no ipaddress....

 

admin@DiskStation:/$ dmesg  | grep 'e1000'
[   15.872062] e1000e: Intel(R) PRO/1000 Network Driver - 3.3.4-NAPI
[   15.872066] e1000e: Copyright(c) 1999 - 2016 Intel Corporation.
[   18.404408] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[   18.404412] e1000: Copyright (c) 1999-2006 Intel Corporation.
[   18.434466] e1000 0000:00:12.0: setting latency timer to 64
[   18.435017] Modules linked in: e1000(F+) sfc(F) netxen_nic(F) qlge(F) qlcnic(F) qla3xxx(F) pch_gbe(F) ptp_pch(F) sky2(F) skge(F) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(O) libcrc32c mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) atlantic(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) igb(O) i2c_algo_bit e1000e(O) dca vxlan fuse vfat fat glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4
[   18.435017]  [<ffffffffa0ad09a3>] ? e1000_probe+0x373/0xf60 [e1000]
[   18.435017]  [<ffffffffa03be04c>] ? e1000_init_module+0x4c/0x82 [e1000]

 

Edited by Polanskiman
Added code tags

Share this post


Link to post
Share on other sites

I installed the PAT file, it did a reboot.

it did not ask me to chose a password yet.

Share this post


Link to post
Share on other sites
On 12/15/2018 at 5:20 AM, Bar1 said:

no ipaddress....

 


admin@DiskStation:/$ dmesg  | grep 'e1000'
[   15.872062] e1000e: Intel(R) PRO/1000 Network Driver - 3.3.4-NAPI
[   15.872066] e1000e: Copyright(c) 1999 - 2016 Intel Corporation.
[   18.404408] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[   18.404412] e1000: Copyright (c) 1999-2006 Intel Corporation.
[   18.434466] e1000 0000:00:12.0: setting latency timer to 64
[   18.435017] Modules linked in: e1000(F+) sfc(F) netxen_nic(F) qlge(F) qlcnic(F) qla3xxx(F) pch_gbe(F) ptp_pch(F) sky2(F) skge(F) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(O) libcrc32c mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) atlantic(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) igb(O) i2c_algo_bit e1000e(O) dca vxlan fuse vfat fat glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4
[   18.435017]  [<ffffffffa0ad09a3>] ? e1000_probe+0x373/0xf60 [e1000]
[   18.435017]  [<ffffffffa03be04c>] ? e1000_init_module+0x4c/0x82 [e1000]

 

 

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.

 

Share this post


Link to post
Share on other sites

ok please confirm:

 

 posted version above: Last tested and worked for me is 6.2 update 2 with bootloader 1.03 (DS3617).

 

is this 1.03a or b?

 

i am sure i am using the right one.....103b 3617

Edited by Bar1

Share this post


Link to post
Share on other sites

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

 

Edited by blessendor

Share this post


Link to post
Share on other sites
3 hours ago, wenlez said:

Oh, I see.  My mistake, I thought you are using the DS918+ loader.  

 

DS918+ loader does not boot anything in my Proxmox

 

Share this post


Link to post
Share on other sites

I have a Xpenology DSM 6 running on Proxmox successfully for several months now, and I am testing emergency scenario's such as how to recover the data in case something goes very bad. 

The system has 2 X 8TB disks that I have mirrored with mdadm in a plain debian prior to installing Proxmox. I don't have any spare disks that I can "passthrough" to Xpenology.
At this moment I am testing different storage types, and trying to mount them on other linux VM's in case something goes wrong. 
What works well is a SATA disk on the local storage with a QCOW2 image, I can mount that on another VM and read the data. 
But when using a SATA disk as an image, I can see that there is an LVM created for that storage, but I cannot get to that data unfortunally.

 

Any idea ? 

Charles. 

Share this post


Link to post
Share on other sites
On 1/1/2019 at 5:18 PM, Charles said:

I have a Xpenology DSM 6 running on Proxmox successfully for several months now, and I am testing emergency scenario's such as how to recover the data in case something goes very bad. 

The system has 2 X 8TB disks that I have mirrored with mdadm in a plain debian prior to installing Proxmox. I don't have any spare disks that I can "passthrough" to Xpenology.
At this moment I am testing different storage types, and trying to mount them on other linux VM's in case something goes wrong. 
What works well is a SATA disk on the local storage with a QCOW2 image, I can mount that on another VM and read the data. 
But when using a SATA disk as an image, I can see that there is an LVM created for that storage, but I cannot get to that data unfortunally.

 

Any idea ? 

Charles. 

Are you able to run proxmox with sata controller? How do you add it? I add a sata disk but but in the options still appear scsi controller..

Share this post


Link to post
Share on other sites
On 12/14/2018 at 10:42 PM, blessendor said:

Release (to install with bootloader)

https://archive.synology.com/download/DSM/release/6.2/23739/

 

Update for release (from installed DSM)

https://archive.synology.com/download/DSM/criticalupdate/update_pack/

 

 

 

 

I managed to unstall the 6.2 23739, but what should I do with the critical updates ? Which ones do you need to install ? 

 

Thanks a lot!

Share this post


Link to post
Share on other sites

Is this possible to setup in VMware ?

I followed the steps and start VM(100), but it said No accelerator found!

 

args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/{VM_ID}/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot'

Is it  may because I didn't use usb to install proxmax, but only ios ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now