Search the Community

Showing results for tags 'proxmox'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • GERMAN
    • KOREAN

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 24 results

  1. This is a simple guide and step by step tutorial on how I got tiny core red pill loader running and working on a proxmox server. This not the only way, just the way I do it and it seems to work. You will need a few things downloaded and ready to access on your local machine. The tiny core red pill image from @pocopico DOWNLOAD Putty for windows (or your mac equivalent) DOWNLOAD WinSCP for windows (or mac equivalent) DOWNLOAD and of course a working server with proxmox installed and running. DOWNLOAD The correct .pat dsm installation file downloaded direct
  2. Vous verez sur mon Github la procedure qui a marché pour moi si vous avez des question hésitez pas.
  3. I'm running DSM 6.2.3-25426 Update 3 / DS3615xs on Proxmox. I have my actual HBA card (JMB585-based one) connected to the VM using PCI passthrough and it works perfectly. However I added another disk using Proxmox: However no matter what I do DSM doesn't see that disk in the UI. I tried changing "SCSI Controller": VMWare PVSCSI - disk is visible in CLI only (fdisk) VirtIO - not detected LSI 53C895A - not detected Some people suggested that VirtIO but DSM doesn't seem to support it. LSI 53C895A was mentioned in multiple tutorials for DSM
  4. Voici ma méthode sur Proxmox [DS3622xs+] Pré-requis : 1 - Être sur Promox 2 - Mettre Sa carte Réseau en Intel e1000 (Ce qui voudrait dire que le pilote que vous aller installer est celui de intel et non virtio.) Sur Tiny Core en Ssh : sudo su (important pour ajouter le pilote Intel) ./ update now ./ fullupgrade now ./ serialgen DS3622xs+ ./ satamap now ./ ext broadwellnk-7.0.1-42218 add
  5. I need the steps because I did everything but it doesn't work either I have errors redpill/intercept_execve.c:82 or else nothing works help me!! I try to install it on Promox
  6. Hi there, After using Synology for 6 years I build a Proxmox server for some smart home stuff and also switched to Expenology for my DS214play I had. Yesterday I had a power outage but everything started right up afterwards. Only to notice now that I can login to Expenology but nothing is there... No volume, no storage pool. I used this tutorial to make it initially: I made some screenshots of everything to give additional info. Any info or pointers about what I can do to restore the volume? Of course I made the mistake to not have regular backups. The l
  7. After fiddling with it for a day, and getting it to work, I thought it would be nice to share the knowledge, especially since "officially" only ESXi is supported, and ESXi is picky about supporting stuff... The main reason for me to move to a hypervisor was because Synology has not yet introduced NVMe support AT ALL. And even with a kernel driver, the Storage Manager will not see it as an SSD, as an HDD, or anything. Synology is silent about this, even though some have requested it on their forums (although they do not have a model with M.2 NVMe connector yet, they have some models
  8. After 4-5 years happy usage of Debian9 + Proxmox5.2 + Xpenology dsm 5.2 I upgraded six months ago to DSM6.2.3 Proxmox6.3-3 Debian10. All went well, until a few weeks ago... One night at 3am my volume 2 crashed! Since then I can read my shares from volume 2, but not write. It is read-only. I suspect the activation of write back cache in proxmox is the reason. Status of SMART and all my harddrives and raid controller is just fine, so I suspect no hardware issue. After using google, this forum and youtube I still have no solution. The crashed volume has all my musi
  9. Hi All, So i have built myself a new setup and having issues with Synology VMM. So what i would like to know is there any point for me to Re-Do my setup on Proxmox or ESXI. I have the Hardware and I can move my data to build a new RAID 5 Setup etc.... If this is an good Idea how will i go about it and what is the Recommendations. Thanks in advanced.
  10. I try to install dsm under proxmox ve with 1.02b loader, sata0 is the loader and sata1 should be the system disk. When I boot it, sata0 works well and I can visit the install web page. But the web page says NO HARDISK FOUND ON DS3615xs using qm terminal I find " Exit on error [1] DISK NOT INSTALLED... " . I doubt it's the root cause. But I don't know what should I do ? the last msg is DiskStation login: but I don't know username and password root@pve:/etc# cat pve/nodes/pve/qemu-server/100.conf boot: cores: 4 ide2: none,media=cdrom me
  11. After wracking my brain for the New Years weekend and scouring both Xpe and Proxmox forums, I finally got IOMMU pass-through working for my LSI card. (Pay attention to the little details guys!!! The code goes on one line, one line!!!! It isn't delineated line by line. /rant) Prior to the PT fix, Proxmox was showing all of the 7 drives installed on the LSI PCI card. After pass-through obviously not as the Xpenology VM is accessing. However, upon logging into DSM I'm seeing some weird behavior and I don't even know where to begin so maybe someone has seen this before and can point
  12. Hi, I am new to Xpenology and Proxmox but I just managed to install Xpenology DSM 6.2.3 on Proxmox 6.2-4. DSM was assigned a single disk that is created by Proxmox from a RAID10 (mirrored striped) ZFS storage. Seeing that this disk used by DSM already has redundancy from the underlying ZFS storage and also has some features similar to BTRFS like snapshots, replication, quotas, integrity protection, Is it redundant to use BTRFS instead of ext4 for a new volume in DMS? Should we use 'Basic', 'JBOD' for the storage pool in DMS? DSM only sees a single disk here.
  13. Hallo zusammen, ich bin neu hier im Forum. Ich wusste bis gestern gar nicht, dass es so etwas wie Expenology gibt........ Ich habe auch gleich mal eine Frage: Ich nutze derzeit eine Synology DS918+ als Mailserver / Plex / ecoDMS / Datengrab. Darüber hinaus habe ich einen Proxmox Rechnern auf dem 4 VMs laufen (W10, 2x Ubuntu). Darüber hinaus habe ich noch diverse Container (ca. 10) am laufen (nginx, ioBroker, influxDB, Grafana usw.). Die Synology hat nicht genug Power und daher möchte ich gerne aufrüsten. Ich habe gedacht einen HP Proliant G8 oder
  14. Ciao a tutti, sto tentando di installare xpenology su proxmox. Ho tentato varie guide, anche quella ufficiale su questo forum, ma senza successo. Inizialmente son riuscito a farlo partire, rilevava il nas (il sito di ricerca), tentavo di installarlo ma al 56% mi dava errore. Allora ho mollato per un giorno, oggi ho ripreso ma ora non viene rilevato nessun nas nonostante il booloader parta normalmente. Ora un paio di domandeda niubbio: - che cosa cambia tra i vari bootloader? 1.02, 1.03 ecc ecc - con che criterio scegliere il modello? (918, 3615 ecc ecc) C'è qualcuno ch
  15. Hello! I searched, and didn't see this anywhere sorry if I missed it. Proxmox VE 5.4-13 DSM 6.2.2-24922 Update 6 DS918+ Jun's Loader v1.04b DS918+ Trying to build a second XP DSM node in proxmox with a LSI 9240-8i flashed to IT mode and a ConnectX-3 10gbe ethernet card. I can't get the node to start when I try to passthrough the ConnectX-3 card. When I press the Health Info button it says "Access Error An error occurred when accessing this drive. This may indicate that issues have occurred on the drive and/or with the connection between the d
  16. Hi, I booted from loader 1.03b-ds3617xs, entered Syno's web-GUI and chose to install latest DSM (6.2.2-24922-4). Then rebooted and now I always get a Kernel panic when booting. Proxmox's host is Ivy Bridge: CPU model name : Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz This is my Proxmox's config, which basically includes: e1000e hack Since Proxmox may only boot from USB if using UEFI and 1.03b doesn't support UEFI, I selected Seabios but did another hack: booting from CD and then chain-loads to USB. 1.03b loader is embeded in a phys
  17. Dear Community, I am new to PVE or KVM, but I did install xpenology on ESXi with success. However, after I install xpenology on PVE, the web assistant shows “No Hard Disk Found on DS3617xs” error. The mod I use is "with Jun's Mod v1.03b". I have changed the SATA port from 0 to 1. I also changed SATA to SCSI or IDE with no luck. I have attached the settings on PVE as the screenshot below. Is it not possible to install 6.2 on PVE? What's the lastest version that PVE supports? Please help!
  18. I installed DSM 5.2 in a VM in proxmox 4.4, generally runs properly, but when shutdown xpenology into web interface, xpenology shutdown properly, and if I start xpenology another time the boot process fails, appearing the next errors, first: Loading module ata_piix [Busy] And later: /usr/syno/bin/synocfgen return 0 Killed Killed lynuxrc.syno failed on 137 When this problems appears, I need restart one or two times proxmox, and later the vm with xpenology then start properly. I attached snapshots of the errors specified, and another snapshot
  19. I'm thinking about upgrading my hardware and moving from VMware to Proxmox. It'll be a good exercise which I'll probably am going to regret when I'm half way the upgrade I'm looking for some help in the migration steps; Current setup: Hardware: i3 6100 8Gb 250Gb SSD + 4x3TB + 3x5TB+2x8TB VMWare ESXi 6.7.0 XpenologyA: Jun's Loader v1.04b - DS918 RDM 4x3TB - Photos, backups and document storage (The important stuff) XpenologyB: Jun's Loader v1.04b - DS918 RDM 3x5TB + 2x8TB - Home media server (The not so important stuff) XpenologyC: Jun'
  20. Hi, Im looking for a nas setup as cheap as possible i dont need a case or drives (got those coverd). What i need is motherboard, cpu and ram which can run xpenology with plex (i need 2 transcoded streams) Bonus woud be to run proxmox. If possible i'd like to get this stuff from ebay (best case woud be ebay germany). thx 4 reading. -Sammy Edit: Putting a steam libary on it shoudent be a problem right? i have a ssd here i coud use as a cache but is that even posible?
  21. Hi, I've just got an XPEnology install up and running with Jun's loader under a Proxmox hypervisor. Everything seems to be working fine, persisting across reboots etc, but I'm just wondering where the DSM configuration data is stored? I have 4 SATA disks configured for direct passthrough and a RAID5 volume placed on them, and I boot the system using the synoboot.img from the loader. But where is all the DSM data stored? I can't see the synoboot.img changing and I don't know where else it would go.
  22. I have Proxmox 5.1. Xpenology 1.02b loader; DSM6.1.4 Update 5. Intel onbard (AHCI) SATA controller passthrough. I have 3 SSD in RAID0 mode. What I notice is, the write performance on SSD is terrible. I've try to tweak Proxmox, and the Xpeno VM, but nothing seems to help. My VM config: args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/100/synoboot_jun2b_virtIO.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot' bios: ovmf boot: 4 cores: 4 hostpci0: 00:17.0,pcie=1 machine: q35 memory: 6144 name: DSM6.x net0: virtio
  23. Plop all, J'ai pas mal écumé ce forum il y a quelques semaines (en plusieurs langues) et je n'ai pas à trouvé de post avec un ModOp assez simple pour moi. Alors voilà le mien : Préparation du bootloader Télécharger la version officielle de DSM voulue : Ce tuto a été réalisé avec DSM 6.1 sur DS3615xs => DSM_DS3615xs_15047.pat Télécharger l'archive contenant le bootloader de June :
  24. Hola, He adquirido el servidor HP Microserver G8 recientemente....llevo 2 semanas con el y de momento aún me faltan cosas por aprender Os comento.... El NAS lleva instalado el sistema Xpenology desde un pendrive usb.... y me gustaria saber si es posible cambiar el sistema operativo por PROXMOX sin perder la configuración ni los datos que tengo en los HDD, seria virtualizar lo que tengo montado ahora. Sabeis si se podria realizar? y como? :S Gracias