maxime Posted November 24, 2020 Share #76 Posted November 24, 2020 On 11/21/2020 at 6:23 PM, codedmind said: Hello, after restore i start the vm went to find.synology setup the account then try update but always get corrupted file... is that normal? I don't pretend keep the vm online, should i change mac and serial number, vid/pid? @arkilee how can i know the vid/pid after the backup restore? Thanks Before update you have at least to create a volume. Did you do it? Quote Link to comment Share on other sites More sharing options...
codedmind Posted November 24, 2020 Share #77 Posted November 24, 2020 10 minutes ago, maxime said: Before update you have at least to create a volume. Did you do it? @maximewell i'm cannot remeber... but try again ... create a volume try the update and it works. It was that step!!! Thanks 1 Quote Link to comment Share on other sites More sharing options...
maxime Posted November 24, 2020 Share #78 Posted November 24, 2020 3 minutes ago, codedmind said: @maximewell i'm cannot remeber... but try again ... create a volume try the update and it works. It was that step!!! Thanks you're welcome Quote Link to comment Share on other sites More sharing options...
codedmind Posted November 24, 2020 Share #79 Posted November 24, 2020 41 minutes ago, maxime said: you're welcome Well after all i'm not able to but it again... so it install but then fails to boot... more testing.. Quote Link to comment Share on other sites More sharing options...
arkilee Posted November 24, 2020 Share #80 Posted November 24, 2020 1 hour ago, codedmind said: Well after all i'm not able to but it again... so it install but then fails to boot... more testing.. I did few quick tests and it doesn't work for me either. Quote Link to comment Share on other sites More sharing options...
codedmind Posted November 25, 2020 Share #81 Posted November 25, 2020 12 hours ago, arkilee said: I did few quick tests and it doesn't work for me either. I only can update if change from sata to usb, change vid/pid then update works Quote Link to comment Share on other sites More sharing options...
bousbouss Posted December 7, 2020 Share #82 Posted December 7, 2020 Hi, Is it possible to add more drives? I ran into this solution: Quote args: -device nec-usb-xhci,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/var/lib/vz/images/108/vm-108-disk-0.raw,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 -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -realtime mlock=off -machine pc-i440fx-2.9,accel=kvm,usb=off,vmport=off,dump-guest-core=off -device 'ahci,id=ahci1,multifunction=on,bus=pci.0,addr=0x8' -drive 'file=/var/lib/vz/images/108/vm-108-disk-1.raw,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/vg0/vg0_backup,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' But when I adapt that to my own drive id's it doesnt work. Any tips? I want to migrate my baremetal xpenology with 6 harddrives, but the proxmox VM sata limit makes that difficult.. Quote Link to comment Share on other sites More sharing options...
ontljoshi Posted December 22, 2020 Share #83 Posted December 22, 2020 Hi your work is gra8" really appreciate it. although i have a question, i have two 1 TB hdds and would like to directly assign them to synology as a storage and do not want to attach them to proxmox. if i am successful enough then i would like to add one 4TB HDD later on so that i can take backup of my phones, other data and sync them to AWS later on. is there any ways if you could help me with attaching this 2 x 1 tb hdds directly to synology as a storage. awaiting your reply. Quote Link to comment Share on other sites More sharing options...
ontljoshi Posted December 22, 2020 Share #84 Posted December 22, 2020 On 3/1/2019 at 11:40 AM, timonych said: Yes, you can. Just use this command in console: qm set <vmid> -sata<id> /dev/<device> and your disk will used by QM. <vmid> = ID of Your VM <id> = Free Sata index <device> = Your Disk But this is QEMU / Proxmox question. not Xpenology. Of course. You need use --storage . I have made backup and restore via Web Interface. Being newbie... could you please add proper example and where to use --storage switch. what is the significance of it. Quote Link to comment Share on other sites More sharing options...
ontljoshi Posted December 22, 2020 Share #85 Posted December 22, 2020 Hi Timonych or any one... i have restored the xpnology from the backup but unable to figure out what is the ip. as its not seem to be picking up an ip from the proxmox. any help will be appreciated. thanks. Quote Link to comment Share on other sites More sharing options...
ontljoshi Posted December 23, 2020 Share #86 Posted December 23, 2020 13 hours ago, ontljoshi said: Hi Timonych or any one... i have restored the xpnology from the backup but unable to figure out what is the ip. as its not seem to be picking up an ip from the proxmox. any help will be appreciated. thanks. this is what i am receiving , is there any way i can get a real IP or assign real ip to this restored image. thanks. Quote Link to comment Share on other sites More sharing options...
timonych Posted December 23, 2020 Author Share #87 Posted December 23, 2020 4 часа назад, ontljoshi сказал: this is what i am receiving , is there any way i can get a real IP or assign real ip to this restored image. thanks. Hi! First, You should ue e1000 driver change delete MAC address on net1 and Proxmox will configure a new MAC Addreess. Second, which Image on which are you using? It's recommend to use DS3615/DS3617 on old hardware. Quote Link to comment Share on other sites More sharing options...
ontljoshi Posted December 26, 2020 Share #88 Posted December 26, 2020 On 12/23/2020 at 1:35 PM, timonych said: Hi! First, You should ue e1000 driver change delete MAC address on net1 and Proxmox will configure a new MAC Addreess. Second, which Image on which are you using? It's recommend to use DS3615/DS3617 on old hardware. Hi @timonych thank you for your reply. Merry christmas! i have used the image as per the post vzdump-qemu-xpenology-918-6.2.3_25426.vma.lzo and tried to delete the MAC address on net1 and tried that way also but no luck.. seems like not picking up an address. Quote Link to comment Share on other sites More sharing options...
timonych Posted December 26, 2020 Author Share #89 Posted December 26, 2020 27 минут назад, ontljoshi сказал: Hi @timonych thank you for your reply. Merry christmas! i have used the image as per the post vzdump-qemu-xpenology-918-6.2.3_25426.vma.lzo and tried to delete the MAC address on net1 and tried that way also but no luck.. seems like not picking up an address. And You Merry Christmas ! Try to use other backup instead of 918. I think that it's hardware incompatible with yours. For me, I can use 918, but I'm using DS3617XS. Quote Link to comment Share on other sites More sharing options...
ontljoshi Posted January 8, 2021 Share #90 Posted January 8, 2021 @timonych thanks for earlier help. hope you are keeping well. i have been able to get things working with DS3617xs. Now facing a strange issue when i am trying to connect with quick connect it is throwing an error message The System failed to perform the requested operation, the unknown error. have you faced this issue and how did you manage to fix the issue... i am trying to work with Moments and then want to work with S3/Glacier for backups later. but for Moments, i need quick connect working. could you please shed some light, thanks in advance. Quote Link to comment Share on other sites More sharing options...
timonych Posted January 8, 2021 Author Share #91 Posted January 8, 2021 9 минут назад, ontljoshi сказал: @timonych thanks for earlier help. hope you are keeping well. i have been able to get things working with DS3617xs. Now facing a strange issue when i am trying to connect with quick connect it is throwing an error message The System failed to perform the requested operation, the unknown error. have you faced this issue and how did you manage to fix the issue... i am trying to work with Moments and then want to work with S3/Glacier for backups later. but for Moments, i need quick connect working. could you please shed some light, thanks in advance. Hello, For quick connect You need a Real Synology. Or You can use DDNS with XPenology. Quote Link to comment Share on other sites More sharing options...
ontljoshi Posted January 8, 2021 Share #92 Posted January 8, 2021 7 hours ago, timonych said: Hello, For quick connect You need a Real Synology. Or You can use DDNS with XPenology. hi... i have configured DDNS - dnsomatic and still the same error. not sure what am i missing thanks! Quote Link to comment Share on other sites More sharing options...
timonych Posted January 8, 2021 Author Share #93 Posted January 8, 2021 (edited) 20 минут назад, ontljoshi сказал: hi... i have configured DDNS - dnsomatic and still the same error. not sure what am i missing thanks! You need External Access to Your Home Network. Maybe asked You Network Operator about Public IP address. (In my country there is an option which is called "Static IP address") I have successfully installed Synology Moment and connect via ddns. (But I never used it) Edited January 8, 2021 by timonych Quote Link to comment Share on other sites More sharing options...
bisch Posted January 13, 2021 Share #94 Posted January 13, 2021 On 10/24/2020 at 10:30 AM, arkilee said: To make it easier, and you can now find this repository all jun's bootloaders with virtio/9p loaded for all dsm version: - synoboot_103b_ds3615xs_virtio_9p.img - synoboot_103b_ds3617xs_virtio_9p.img - synoboot_104b_ds918plus_virtio_9p.img HTH Thanks everyone for templates and support. I started to try out out Xpenology in Proxmox after stumbling on the Geeked youtube. I followed 6.2_23739 clean image which I think was in the YT video. It worked well, but was a lot older release and had some bugs. I moved onto the 6.2.3-25426 and all the bugs were gone. I had issues getting this running with synoboot_103B_ds361Xxs_virtio_9p.img or boot loaders using a 3615 and 3617 image. it doesn't start my drives until slot 7 or up and will then not see my pass through hard drives, except for External hard drives. It looks like this may be an known issue with boot loaders and editing where the ata, usb and other drives start, and max drives. I increased the max drives, but my passthrough hard drives still showed as external drives. So I went back to the vzdump-qemu-xpenology-3617xs-6.2.3_25426.vma (withouth virtio_9P) and the drives were in the right order and all works well and stable. Will this be a problem going forward for updates I wonder? I really like Xpenology in Proxmox, but being new to it all, I don't have the experience to know how simple upgrades may be in the future. I think keeping the drives as passthrough may help challenging upgrades in the future, in case one must blow away or do a clean install, and it would allow them to repair the volume/SHR arrays, but I don't know for sure. I may build/test an unraid setup instead of proxmox/xpenology, but it wasn't my first choice Let me know if you also noticed this behavior with the virtio bootloader, and what risks upgrades have for xpenology in proxmox may have going forward. Thanks again, Xpenology is a pretty impressive. Quote Link to comment Share on other sites More sharing options...
r27 Posted January 13, 2021 Share #95 Posted January 13, 2021 3 hours ago, bisch said: Thanks everyone for templates and support. I started to try out out Xpenology in Proxmox after stumbling on the Geeked youtube. I followed 6.2_23739 clean image which I think was in the YT video. It worked well, but was a lot older release and had some bugs. I moved onto the 6.2.3-25426 and all the bugs were gone. I had issues getting this running with synoboot_103B_ds361Xxs_virtio_9p.img or boot loaders using a 3615 and 3617 image. it doesn't start my drives until slot 7 or up and will then not see my pass through hard drives, except for External hard drives. It looks like this may be an known issue with boot loaders and editing where the ata, usb and other drives start, and max drives. I increased the max drives, but my passthrough hard drives still showed as external drives. So I went back to the vzdump-qemu-xpenology-3617xs-6.2.3_25426.vma (withouth virtio_9P) and the drives were in the right order and all works well and stable. Will this be a problem going forward for updates I wonder? I really like Xpenology in Proxmox, but being new to it all, I don't have the experience to know how simple upgrades may be in the future. I think keeping the drives as passthrough may help challenging upgrades in the future, in case one must blow away or do a clean install, and it would allow them to repair the volume/SHR arrays, but I don't know for sure. I may build/test an unraid setup instead of proxmox/xpenology, but it wasn't my first choice Let me know if you also noticed this behavior with the virtio bootloader, and what risks upgrades have for xpenology in proxmox may have going forward. Thanks again, Xpenology is a pretty impressive Could you please share the link to boot loader you used. I can't get LSI controller recognized, so can't pass drives to xpenology. Every other VM works fine with this controller and pass. Quote Link to comment Share on other sites More sharing options...
strategischen Posted January 14, 2021 Share #96 Posted January 14, 2021 Anyone found a solution to use a guest-agent on the VM? Quote Link to comment Share on other sites More sharing options...
arkilee Posted January 27, 2021 Share #97 Posted January 27, 2021 For those, who wants to passtrough several harddrives, please just buy a sata controller 4/6 ports (20$ - 30$ , check in this forum for compatible an positive feedback) and then just passthrough this "sata controller" card to the VM with proxmox. This way, all your disks : - will be compatible to real synology hardware, in case of you may plan to migrate to it in the future - will be able to perform SMART test and get SMART info/error (and temp) from Xpenology - I think sleep/hibernate HDD works better and save you electric ... Well, just go for it if you plan to use it as our main NAS. Quote Link to comment Share on other sites More sharing options...
onkel bouncy Posted January 28, 2021 Share #98 Posted January 28, 2021 Hi, any recommendations for an Asrock J5040-ITX? DS918+? Quote Link to comment Share on other sites More sharing options...
Bart82 Posted February 8, 2021 Share #99 Posted February 8, 2021 Hello all i Passthrough a SATA Pci Controller. It just chows me 4 of my 8 HDDs. The first of them showing me on the 7 Position in the Drive Manager. Can Someone Help my ? Quote Link to comment Share on other sites More sharing options...
flyride Posted February 9, 2021 Share #100 Posted February 9, 2021 4 hours ago, Bart82 said: Hello all i Passthrough a SATA Pci Controller. It just chows me 4 of my 8 HDDs. The first of them showing me on the 7 Position in the Drive Manager. Can Someone Help my ? What other controllers are in the system? At least one virtual SATA controller for the loader, but do you have a second one? You will need to tweak your controllers, adjust SataPortMap and DiskIdxMap, or all of the above to correct it. https://xpenology.com/forum/topic/12470-how-to-play-around-with-hdd-mapping-with-sataportmap-and-diskidxmap/ If you see 1/2 of your HDD's and you are not out of slots, it's likely you have a port multiplier on your controller which is not supported. Post the controller type and someone here will know for sure. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.