Orphée

Ho do you manage rd.gz file ? do you just untar it with 7z and build a new gzip file ? as the original is cpio ... Thanks Edit : nevermind

I may be wrong but not available yet for DSM7. https://github.com/NeverEatYellowSwissSnow/synology-dsm-open-vm-tools/issues/3 https://github.com/SynoCommunity/spksrc/issues/4170

vmxnet3 driver for DSM7 would be cool

I tried to update my test vm from 7.0 to 7.0.1 and update failed... not at home currently to put logs. I kept same user config as usual... i'll check later what could be wrong.

Here I gave some details : It seems loader consider "not a SATA disk" and then ignore it

This is more or less my current setup : Gen8 ESXi running jun's 6.2.3 / ds3615xs with LSI HBA passthrough. 4 disks plugged to PCIe LSI card. one SSD as vm storage pool on inboard SAS/sata AHCI HBA. works perfectly fine. but as already mentionned here, even with mpt2sas loaded on redpill loader, disk passed through is detected as /dev/sas* and not handled by DSM gui.

From my understanding, can't be updated from DSM GUI. Loader block it, and crash the install.

https://github.com/RedPill-TTG/redpill-load/issues/18

Try to change to : "DiskIdxMap": "1000", "SataPortMap": "4",

Actually Serial to Telnet is a ESXi / Proxmox feature. I'm not sure telnet can access to real baremetal serial port. I mean on VM, you add a serial port, and you link it to telnet with a VM parameter. BTW, do you actually have a serial port on your laptop ?

You are trying to install RP Xpenology on a laptop... Good luck ! It may work but usually laptops are quite tricky with their componants... if you can access it from network, you should be able to telnet to it on port 21, 22 and 23 I guess.

Be prepared to flash/update the BIOS with modded FW can't remember which one exactly.

If you follow the tutorials for N54L floating around there. It works as baremetal just plug and play. Latest DS3615xs 1.03b jun's loader do the job perfectly well. You must have the right modded bios to configure it (C1E disabled) And you must set PID and VID inside the grub.cfg to match your USB key. No need to re-eplain it again... everything needed is already explained. Mine is rock stable : I have a PCI-e network card but it is not really needed with 6.2.3. Not needed anymore. It may be needed for next loaders, I did not check it yet. You won't acheive anything without screen and keyboard...

I checked and it works. But after looking inside, the result is the same as V2V converter. It build a vmdk index file pointing to "flat" file, and actually, there is no need to do anything with flat file. You can keep original IMG built loader, you just have to set the index file with the right name of img file... So once you have the correct VMDK index file, you just need to overwrite the IMG file on the storage pool ESXi. The only main difference between V2V and qemu-img once fixed with vmkfstool is : (left is qemu-img, right is V2V where I replaced flat file with original loader's IMG) So now I don't need to convert the IMG each time a build it. I only overwrite the old one and keep VMDK index as this.

I edited my original mpt2sas post for ThorGroup. But it seems redpill loader detect the drive as SCSI and not SATA and then ignore it. @pocopico Not really the same. your workaround work when disk is shown as not meeting requirements. At least it is how I understand it. Here, with mpt2sas, disk is not detected at all in GUI, no disk shown in HDD section.

I tried under ubuntu VM but it failed for me... the converted vmdk was not working. Whereas V2V converter did the job.

Using DSM 7 bromolow, I did not have to do anything special expect creating a .conf file to autoload the module at boot. Inside : /usr/lib/modules-load.d/ create a .conf file named as you like (mine is : 70-disk-0000-mpt2sas.conf) Only put one line in that file : mpt2sas Save file and reboot.

@haydibe Thanks for your answer, still I must admit it is not very easy to understand for me so still unclear... In the meantime I tried to play with with mpt2sas module... I took a SSD drive as a temp test drive. At DSM first installation. No disk detected. Logged in to serial as root and loaded mpt2sas module : After module, disk is detected in console, but still not shown after a refresh in GUI. "No disk detected" Then I tried to add it to an already running DSM 7 with a virtual disk : Same happens, disk not detected in GUI managment disks. Edit : Comparing with Jun's loader 6.2.3 : dmesg_70_ssd_sas.txt

@ThorGroup Actually I'm really not skilled with ESXi... But I'm trying to progress with it. Some things about Jun's loader vmdk compared to V2V redpill IMG converstion : Actually, the only important thing actually is the VMDK index file... the redpill IMG file isn't modified by V2V converter. I think it only builds the right VMDK index file : I guess the RW number took from Jun's loader was too short and because of this I had an error message "data after end of disk" Since I use the VMDK index file built by V2V converter this step now works good. Regarding DiskIdxMap and SataPortMap values... I played a bit with them. As a reminder, on ESXi VM, I dedicate first SATA controller to redpill IMG disk, and add a second data controller for data disk SATA 0:1 = redpill IMG boot SATA 1:0 = virtual 16Gb data disk test with recommended values given by everyone : DiskIdxMap=1000 SataPortMap=4 I can install DSM and it boots OK. I tried to change the values to understand why with my old values it did not work 'DiskIdxMap=0C SataPortMap=1) And it seems : - DiskIdxMap : - you can change first two digit to 0C instead of 10 if you like. - 2nd two digits must be 00 (and must be written like 0C00 or 1000) - If you don't put the two 2nd digits (00) when you install DSM, depending on SataPortMap value, DSM will ask to format X drives (5 if you have SataPortMap=4) - SataPortMap : - I did not play that much with it but if you set a value like SataPortMap=1 DSM install fails, when you set it back to SataPortMap=4 DSM install works (I did not try values 2 or 3) If you dont set DiskIdxMap and SataPortMap values, then the disk detected is actually the redpill IMG loader, and it is destroyed when DSM tries to format the disk. about mpt2sas module : the /usr/lib/modules/mpt2sas.ko file exists natively in DSM 7.0 Bromolow Shouldn't it be loaded with other modules inside /usr/lib/modules-load.d/ ? I did not play enough with it yet but without loading it, my LSI passthrough SAS card is not detected at all and if I manually create a .conf file to load module at boot, card is detected in DMESG. I'm still missing a real SATA test drive to investiguate more if it could be detected for installation of addition... Thank you

Hi, could you please keep Pat fule outside container ? As we need it to install DSM, it avoid downloading it twice ans search it elsewere. thank you

Step 6 isn't necessary. It Just list table content.

https://archive.synology.com/download/Package/

I don't have these issues with Gen8.

Switch to ESXi instead of baremetal. You'll have VMs outside Xpenology.

I'll stay on esxi then, unless redpill loader needs proxmox in near future (esxi bugs or anything else)