Jump to content
XPEnology Community

bisch

Rookie
  • Posts

    1
  • Joined

  • Last visited

bisch's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. 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.
×
×
  • Create New...