Jump to content
XPEnology Community

Tutorial: DSM 6.x on Proxmox


fonix232

Recommended Posts

Hi!

 

Thanks to all of you, one or two contribution of each, I was finally able to install Xpenology on a VM on Proxmox 6.1-4.

 

I guess that the turning point was the use of img2kvm, something that I never heard of. Until this utility, I tried to insert the boot image through "args: " in the VM conf file, and through the use of the native Proxmox "qm importdisk". But this img2kvm give me the first jump I needed.

 

The second jump was the use of this boot image, that I found on this tutorial, when I searched for img2kvm.

 

Thank you very much!!!

Best regards.

Link to comment
Share on other sites

I am trying to get my Proxmox zfs storage pool work with Xpenology VM but only thing that I managed was to get acces to it by File Station (mounted as NFS share) and Download Station ( so it can download to selected folder on my pool). Is there any way to mount it to indexing folder for Multimedia server/Video Station, Audio Station , etc? The only multimedia application that work is Plex- my tv sees it by DLNA but subtitles doesnt work (Video station dont have access to pool, same as Emby, but Jellyfin as Docker container have a option to add folder/mount point when it is created but I can not get DLNA to start...).  Did someone managed to start multimedia server indexing or some dlna aplication to work in xpenology vm?

Edited by ruffpl
Link to comment
Share on other sites

hi ruffpl,    I'm not able to answer your question yet,  however, may you tell me how did you add zfs storage pool / virtual drive ?     I added a virtual hard drive (local-zfs)  through Hardware tab of Proxmox GUI, and not sure how to make Synology detects it.

 

 

regards,

Edited by pumin
add more info
Link to comment
Share on other sites

I am testing small btrfs pool. I added 2 old sata drives (ext4) from my previous synology box and add the lines  " sata_: /dev/disk/by-id/ata-____,serial=____,backup=0 "    in    /etc/pve/qemu-server/     config file and they show up in DSM without any problem. Can all extra drives  be added  this way or I had to perform some extra commands in terminal? In DSM I dont see any S.M.A.R.T. informations about them/ is theres a way to fix it?

And also- how can I get on the pool from Windows by ftp/sftp ( FIlezilla, Winscp, etc)? Do I need to mount this pool in Proxmox or something? Where it is stored? I can access only by Xpenology ip to shared folders only as admin not by root.

Edited by ruffpl
Link to comment
Share on other sites

Is there a way to add more than 7 drives? When I write lines with sata3, sata4, etc in config file they show up  in DSM, but when I try with this SCSI solution it only passthrough one drive from raid. When I change it back to sata, it works again. Is there a way to fix it? I would like to attach 8 sata hdds to xpenology

 

 

nb n.PNG

jckhkg.k.PNG

nvmbv.PNG

Edited by ruffpl
Link to comment
Share on other sites

  • 2 weeks later...

You need to add secondary sata controller and disks by args, just like blessendor wrote few posts ago.

 

Example:

-device ahci,id=ahci1,multifunction=on,bus=pci.0,addr=0xb -drive 'file=/var/lib/vz/images/103/vm-103-disk-4.raw,if=none,id=drive-sata7,format=raw,aio=threads,detect-zeroes=unmap' -device ide-hd,bus=ahci1.1,drive=drive-sata7,id=sata7,rotation_rate=1

 

"Rotation_rate" option at the end is args parameter for emulating ssd.

Link to comment
Share on other sites

Hi,

 

Let me give an overview of my install with Proxmox 6.1 and DSM 6.2.2-24922 Update 6

 

Don't have to explain the preparation of bootloader you can find it on the forum, i used

 

DSM 6.2(.1/.2/.3/.4) - Read Jun's topic

Jun's Loader v1.03b DS3615xs

Synoboot_3615.zip | 17.3 MB | MD5 = e145097bbff03c767cc59b00e60c4ded

 

Created a new VM with settings:

 

args: -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,cache=writeback -device usb-storage,bus=usb.0,port=2,drive=drive-usb-disk2,id=usb-disk2,bootindex=1,removable=off
balloon: 0
bootdisk: sata0
cores: 4
machine: q35
memory: 4096
name: DSM
net0: e1000e=E6:9E:29:69:A6:01,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: local-lvm:vm-100-disk-0,size=65G
serial0: socket
smbios1: uuid=xxxxxxxxxxxx
sockets: 1
vmgenid: xxxxxxxxxxxxxx

 

I had edit the pve manager to be able to select the e1000e from the menu, you can find the info in the forum as well.

Only difference is the path was not the same, maybe to do with 6.1 proxmox version

 

/usr/share/pve-manager/js/pvemanagerlib.js

 

I am passing disks later by using qm set 100 -sata1 /dev/disk/by-id/.....

before i do that i will clone everything

 

What i am still looking for is someone who can help me getting virtio drivers to work

 

 

 

Link to comment
Share on other sites

Hi all and thanks a lot for all information,

 

Here is my working config :

HP ML330 G6 with P410 controller

Proxmox 6.1-7

 

Jun's Loader v1.03b DS3615xs with MAC/Serial mods

1408681909_Capturedecran2020-04-11a11_07_55.thumb.png.a5da75e07c1eb586ccdcba8bd3953c56.png

Quote

args:

-device 'nec-usb-xhci,id=usb-ctl-synoboot,addr=0x18'

-drive 'id=usb-drv-synoboot,file=/var/lib/vz/images/100/synoboot.img,if=none,format=raw'

-device 'usb-storage,id=usb-stor-synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot'

-device 'ahci,id=ahci1,multifunction=on,bus=pci.0,addr=0x8'

-drive 'file=/dev/disk/by-id/wwn-0x600508b1001cc2d7535be11d678e08da,if=none,id=drive-sata6,format=raw,cache=none,aio=native,detect-zeroes=on'

-device 'ide-hd,bus=ahci1.0,drive=drive-sata6,id=sata6'

-drive 'file=/dev/disk/by-id/wwn-0x600508b1001c4f776a62390a49c7dca6,if=none,id=drive-sata7,format=raw,cache=none,aio=native,detect-zeroes=on'

-device 'ide-hd,bus=ahci1.1,drive=drive-sata7,id=sata7'

-drive 'file=/dev/disk/by-id/wwn-0x600508b1001c83814e04bcb86677c43d,if=none,id=drive-sata8,format=raw,cache=none,aio=native,detect-zeroes=on'

-device 'ide-hd,bus=ahci1.2,drive=drive-sata8,id=sata8'

balloon: 0

boot: c

bootdisk: sata0

cores: 6

memory: 8192

name: xpeno

net0: e1000e=00:11:32:12:34:57,bridge=vmbr0,firewall=1

numa: 0

ostype: l26

sata0: Crucial240:vm-100-disk-0,size=2G,ssd=1

sata1: Crucial240:vm-100-disk-1,size=32G,ssd=1

sata2: Crucial240:vm-100-disk-2,size=32G,ssd=1

sata3: /dev/disk/by-id/wwn-0x600508b1001c20a8daafb3a1b346d898,size=2930233816K

sata4: /dev/disk/by-id/wwn-0x600508b1001ccbfd1f00be6db2130ec1,size=2930233816K

sata5: /dev/disk/by-id/wwn-0x600508b1001c0ff7abe01f288c2ff451,size=1953481816K

#sata6: /dev/disk/by-id/wwn-0x600508b1001c4f776a62390a49c7dca6,size=1953481816K

serial0: socket

smbios1: uuid=5896b373-6728-40c9-9572-0ec32db22fb4

sockets: 1

vmgenid: 8ad811ee-940e-4d05-bc36-bfefdcd281b2

obviously args on 1 line

 

As you could see :

  • e1000e mod
  • disk passthrough with additional emulated sata controller. I've tried to passthrough P410 controller but there is the RRDM error.
  • 2 disk file on 1 physical SSD to have cache

It's really ugly but it works !

Link to comment
Share on other sites

  • 2 weeks later...

Hi, that's great that it work's for you. I know you probably know all this, but i want to point one thing. I strongly recommend not to use "2 disk file on 1 physical SSD to have cache". I'm guessing that you use it for r/w cache. Much better solution is to add 2 ssd's and pass them trough directly to the vm or pass trough one SSD and set only read cache. They're not that expensive. With the solution that you have you must remember that you may and probably will lose data. There's very high risk of this to happen, let's say you just accidentally disconnect your SSD from motherboard and you loose your most recent data or it will get corrupt. It's ok for test environment but it's very bad idea for production use.

Link to comment
Share on other sites

Hi, all. I just checked that with proxmox 6.1-8, DSM 6.2.3, v1.03b DS3615xs loader, e1000e lan card is no longer needed, 1000e works out of the box. I don't know what changed, but it just works (without any custom extra.lzma). Cheers.

Edited by hellbondz
Link to comment
Share on other sites

I've been trying to get this work but I always get stuck on 56%: Failed to install the file. the file is probably corrupted (13). I setup my VM like stasheck (Post ID 210, page 9. I did the E1000e hack etc.
vm seems to boot up fine and I can find my synology using find.synology.com. I tried all 3 bootloaders (1.03b and 1.04b)

 

I forgot to add that the pat files i tried so far are:

DSM_DS3615xs_23739.pat

DSM_DS3615xs_24922.pat

DSM_DS3615xs_25423.pat

 

DSM_DS3617xs_23739.pat

DSM_DS3617xs_24922.pat

DSM_DS3617xs_25423.pat

 

DSM_DS918+_24922.pat

DSM_DS918+_25423.pat

 

Any thoughts?

 

 

Edited by REK1
Link to comment
Share on other sites

1 minute ago, hellbondz said:

You just need to write proper vid, pid to your groub file in loader disk.

Thanks for this. The only things I changed in the grub.cfg:

1. I added a serial generated from here -https://xpenogen.github.io/serial_generator/index.html

2. Added mac addresses for my network devices.
I had this in my config file:
args: -device 'nec-usb-xhci,id=usb-ctl-synoboot,addr=0x18' -drive 'id=usb-drv-synoboot,file=/path/images/<VM_ID>/synoboot.img,if=none,format=raw' -device 'usb-storage,id=usb-stor synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot'
 

but this didnt seem to work so I ended  up converting the synoboot.img into qcow2 format:
qemu-img convert -f raw -O qcow2 synoboot.img synoboot.qcow2

 

and then added it to my config:
sata0: local:<VM_ID>/synoboot.qcow2,size=29M

 

So in the above I ended up using Jun's Loader v1.04b and the latest pat file - DSM_DS918+_25423.pat

 

I have it now installed. I just need to add the drives.

 

 

 

Link to comment
Share on other sites

Thanks many for providing feedback and inputs in this thread.   One suggestion I would have is I think the title of this thread should be changed to 6.1.x/6.2 and maybe started separate thread on DSM 6.2.3-x as I think the initial post and earlier portion of this thread is no longer relevant with the latest release of DSM.  Maybe it's just limited my personal experience. 

 

I've spent past couple of days combing through this thread and various other threads on this forum for my 6.1.7-x upgrade to the latest version 6.2.3-25423.  Brief background, I've started xpenology out with DSM 6.1 running bare metal with Jun's Loader v1.02b, migrated it to another bare metal machine, and then to a VM hosted on ESXi 6.7U3 and eventually settled with VM hosting on Proxmox 6.1 now.  I've been running DSM DS3615sx 6.1.x stably for at least 1+ year so now I've decided it's time to venture into upgrading it to the latest 6.2.3-25423 version. 

 

After dozen of attempts with new test VM and config changes, it worked out better than expected in the end for me. 

 

What previously VM settings such as BIOS and Machine type worked for me no longer works with the latest version.  Similarly to what @REK1 mentioned above, my test VM kept getting stuck on 56% with error "Failed to install the file. the file is probably corrupted (13)", changing vid/pid did not help.  Instead, what's ultimately resolving it for me is having the correct args: -device ... information, most importantly, "piix3-usb-uhci" needed to be changed to "ich9-usb-ehci1".   Alternatively, you can also do an qm importdisk of the synoboot.img and assign it to SATA0.  That'd been more straightforward and worked for me as well, but personally, I'd prefer not seeing the loader visible as a mountable drive inside the DSM OS so I took the former route of mounting it as a usb device like what you'd normally do in a typical bare metal scenario. 

 

For those who's using EFI instead of Seabios, latest version 6.2.3-25423 will NOT WORK.  Also, if your VM is set to "Default (i440fx)", it needs to be changed to "q35" instead. 

 

I highly recommends doing a MIGRATION to the latest update instead of in-place upgrade.  This means creating a new VM, test your Jun's Loader v1.03b settings first and VM settings first to make sure it's working properly, then attach your existing data disks to the new VM and do the standard DSM migration as if you're moving your hard drives to another NAS device. 

 

I'm on latest Proxmox 6.1-8.  Note latest version works fine with Intel E1000 out-of-the-box.  I did not have to use custom E1000e adapter.  Here's my working VM config:

 

args: -device ich9-usb-ehci1,id=usb-ctl-synoboot,addr=0x18 -drive id=usb-drv-synoboot,file=/var/lib/vz/images/103/synoboot103b.img,if=none,format=raw -device usb-storage,id=usb-stor-synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot -device ahci,id=ahci1,multifunction=on,bus=pci.0,addr=0x8
boot: c
cores: 2
hostpci0: 02:00.0,rombar=0
ide2: none,media=cdrom
machine: q35
memory: 4096
name: nas-prod
net0: e1000=AE:75:AE:DD:9E:B2,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
serial0: socket
smbios1: uuid=92d896c6-9071-43ae-94d7-66df8e6e33b7
sockets: 1
vmgenid: 3d8f4923-4400-444e-b627-ca5e0e8e39b7

 

Post-migration, I did notice Jun's Loader keeps showing as mounted USB drive inside DSM admin, what fixed that for me was using the "FixSynoboot.sh" posted by @flyride in the other thread below.  Now, I no longer see the loader mounted each time I'm login to the DSM console, but only see my passthrough disks, just like before when I was on 6.1.7-x version. 

 

https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available

 

PVE_DSM_6.2.3-25423.png

Edited by Rooster
Link to comment
Share on other sites

3 hours ago, Rooster said:

Alternatively, you can also do an qm importdisk of the synoboot.img and assign it to SATA0.  That'd been more straightforward and worked for me as well, but personally, I'd prefer not seeing the loader visible as a mountable drive inside the DSM OS so I took the former route of mounting it as a usb device like what you'd normally do in a typical bare metal scenario. 

 

Fixsynoboot.sh would probably had fixed this as well.

Link to comment
Share on other sites

Thanks for confirming on the FixSynoboot.sh script.  Good to know.  It'll help someone else later who see this later.  Since I have already decided to go with usb mount option, I myself did not test the script with the SATA0 mount option. 

Link to comment
Share on other sites

Le 03/04/2020 à 20:16, hellbondz a dit :

You need to add secondary sata controller and disks by args, just like blessendor wrote few posts ago.

 

Example:

-device ahci,id=ahci1,multifunction=on,bus=pci.0,addr=0xb -drive 'file=/var/lib/vz/images/103/vm-103-disk-4.raw,if=none,id=drive-sata7,format=raw,aio=threads,detect-zeroes=unmap' -device ide-hd,bus=ahci1.1,drive=drive-sata7,id=sata7,rotation_rate=1

 

"Rotation_rate" option at the end is args parameter for emulating ssd.

Hello,

 

I want to use this method but I can't. I would like to mount the following physical disk: /dev/sde, size=488386584K (visible via the Proxmox node). Should I proceed like this?

args:
-device ahci,id=ahci1,multifunction=on,bus=pci.0,addr=0xb -drive 'file=/dev/sde,size=488386584K,if=none,id=drive-sata7,format=raw,aio=threads,detect-zeroes=unmap' -device ide-hd,bus=ahci1.1,drive=drive-sata7,id=sata7,rotation_rate=1

 

Thanks for your help

Edited by SebRider
Change code
Link to comment
Share on other sites

Hi, yes this should work, but I'd rather took 'file=/dev/disk/by-id/ata...' or 'file=/dev/disk/by-path...', because normal '/dev/sda...' letters could change, and 'size' parameter is not needed. 'rotation-rate=1' option will set your disk as SSD drive in your VM.

Link to comment
Share on other sites

Hello,

Thanks it works now!

args: -device ahci,id=ahci1,multifunction=on,bus=pci.0,addr=0xb -drive 'file=/dev/disk/by-id/ata-ST500DM009-2F110A_ZA480LWF,if=none,id=drive-sata6,format=raw,aio=threads,detect-zeroes=unmap' -device ide-hd,bus=ahci1.1,drive=drive-sata6,id=sata6
Edited by SebRider
Link to comment
Share on other sites

Hey, I'm new here until a day ago I didn't know there was such a thing.
I'm trying to install on Proxmox 6.1-8
DS3615sx
Loader v1.03b
I was finally able to move on to something only when converting the synoboot.img into qcow2. otherwise it didn't work
But now that I'm trying to install the pat file it says "Failed to format the disk (53)"
The VM config

 

bios: seabios
cores: 2
cpu: kvm64
machine: q35
memory: 2048
name: synologytest
net0: e1000e=9E:55:42:1F:CB:60,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: NFS1:201/synoboot.qcow2,size=50M
smbios1: uuid=9d6a9bd1-5af2-40e5-b988-XXXXXXXXX
sockets: 1
virtio0: G500:vm-201-disk-0,size=64G
virtio1: G500:vm-201-disk-1,size=64G
vmgenid: 79acaa43-5f89-4c2f-b06e-XXXXXXXXX

 

What to do?

UPDATE: I managed to install !!
I had to add another disk and it installed it!

Edited by Itay1778
Link to comment
Share on other sites

  • 2 weeks later...
On 4/28/2020 at 3:12 PM, hellbondz said:

You just need to write proper vid, pid to your grub file in the loader disk. Please try those values:

vid 46f4
pid 0001

Ther's a lot of articles about this on the forum.

Hi @hellbondz, can you explain me how to obtain a proper vid and pid? this is a lost passage for me...

i get error 13 when i try to install dsm...

thanks

Edited by dextm80
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...