New Members
  • Content Count

  • Joined

  • Last visited

Everything posted by vinceg77

  1. @hellbondz blessendor method is perfect but another way would be to passthrough 2 PCIe sata controller cards with a bunch of 4 disks each ! (more expensive though)
  2. Hi @stasheck I finally managed to install Xpenology after having spent hours ! Even if everything is working now, I would not be able to tell you exactly what I really did well to make it work !!! (given that I discovered I had a faulty motherboard/bios not really able to deal with DSMAR table and so I had to use the unsafe_interrupt method within proxmox, and I am not able to tell how it might have affected my xpenology installation...) I hope you will get some more precise help form experts, but I can provide some partial outputs : 1/ I never managed to install 918+ nor loader 1.04, I was getting a fatal error during installation (I do not remember precisely error details) 2/ ds3617 xs was working with 6.2.1 but I was unable to update to 24922.pat or higher, it was also crashing 3/ I so use ds3615xs with 1.03b. I firstly installed 6.2.1 then update to 6.2.2 (I kept 1.03b) 4/ Yes I use e1000e nic drivers, implemented following the @blessendor method 5/ I did not managed neither to use virtual USB key for loading, I had to use sata disk. And the boot disk does appear in HDD manager but normally I depends of your choice in the loader boot menu (baremetal or VMware options) 6/ I firstly managed to get xpenology working and updated before any device passthrough I was finally able to passthrough 1 PCIe sata controleur card with 5 sata disks and USB + 3 other sata disks directly I hope this partial feedback will give you some clues. And do not give up, it should finally work fine also ! ... even if I am quite anxious about the moment the next update will show up !!! Good luck
  3. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.23739 - DSM version after update: DSM 6.2.2-24922-update 3 - Loader version and model: JUN'S LOADER v1.03b - Using custom extra.lzma: NO - Installation type: VM Proxmox 6.0.7 running on Asus P6T Deluxe / 24 Go Ram / CPU Intel core I7 990X - Additional comment: Achieving to GUI select e1000e network card led to success after many kernel panic ! I have spent almost 2 weeks to try to get Synology last update to work with proxmox 6.0.7. Hours and hours trying thousands of different options ! Until I found this post (to be honest, I tried it a week ago, without success, maybe I did it wrong!!??) Then it finally happened ... Xpenology using 6.2.2-24922 (last update as of 09/11 !!!). I would never thank enough @blessendor for the hack he published in order to use Intel e1000e network card within Proxmox. I first tried everything with the '-arg:' command line in vmid.conf to define e1000e as default network card, including great @hellbondz 's trick, but it never really worked out for me. Hacking the files allowed me to select e1000e in the Proxmox GUI and then my virtual DS3617xs finally accepted last update without crashing ! I could not believe it ! ... Now I have to succeed in passing through my 2 sata controller cards and my 8 hdd disks - which is another story! Thanks again @blessendor for your sharing, you saved my last few weeks, and also for all the people using or developing Xpenology, and specially for @jun the master !
  4. Pas de souci pour moi non plus avec l'update 3 si ce n'est le firewall qui m'empêchait d'accéder aux lecteurs mappés depuis Windows 10 (serveur de fichier Windows). Mais cet n'était finalement peut-y été pas directement lié à l'update ??? Rien de méchant en tous cas, très vite résolu. Le reste est ok. Envoyé de mon SM-N910F en utilisant Tapatalk