Rikk

Hello, I am trying to build the image for bromolow-7.0.1-42218 , following the advise below. Unfortunatly, it is not working as expected: the error message received is in red below : .... [#] Checking runtime for required tools... [OK] [#] Adding new extension from https://github.com/jumkey/redpill-load/raw/develop/redpill-boot-wait/rpext-index.json... [#] Downloading remote file https://github.com/jumkey/redpill-load/raw/develop/redpill-boot-wait/rpext-index.json to /opt/redpill-load/custom/extensions/_new_ext_index.tmp_json ######################################################################## 100.0% curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused [!] Failed to download https://github.com/jumkey/redpill-load/raw/develop/redpill-boot-wait/rpext-index.json to /opt/redpill-load/custom/extensions/_new_ext_index.tmp_json *** Process will exit *** [!] Failed to add "https://github.com/jumkey/redpill-load/raw/develop/redpill-boot-wait/rpext-index.json" as an extension: , *** Process will exit *** [!] Failed to install thethorgroup.boot-wait bundled extension - see errors above *** Process will exit *** Makefile:30: recipe for target 'build_redpill_load' failed I am using a Mac Book with big sur 11.6. Someone already encountered this error ? Thanks, Rikk

yes, you are right. I have added a PCI network card with 82574L chip.

Yes. My hardware is : Gen8 HP microserver with Xeon E3-1220L CPU update 6Gb of RAM I am using le last env (redpill-tool-chain_x86_64_v0.7.2) to build the image with MAC OS big sur platform., and docker installed. My bromolow_user_config.json: content is (xx and yy are replacing real values and pid/vid are the one from my USB key): { "extra_cmdline": { "pid": "0xFFF7", "vid": "0x203A", "sn": "yyyyyyyyyyyyy", "mac1": "xxxxxxxxxxxx" }, "synoinfo": {}, "ramdisk_copy": {} } Commands to build the image: cd ~/Desktop/redpill-tool-chain_x86_64_v0.7.2 sudo chmod 777 redpill_tool_chain.sh sh ./redpill_tool_chain.sh build bromolow-7.0.1-42214 sh ./redpill_tool_chain.sh auto bromolow-7.0.1-42214 The image is written on USB key with BalenaEtcher To have it working,(booting) I set the 1st (FAT32) partition as active (with MiniTool Partition Wizard).

Hello to all, I am trying to test the loader on my current hardware and I am stuck to a stupid step : my system didn't find the USB key to boot on it. With the previous setup (Jun's loader with 3615xs model, 6.2.3 DSM) it was working well. My hardware is : Gen8 HP microserver with Xeon E3-1220L CPU update 6Gb of RAM I am using le last env (redpill-tool-chain_x86_64_v0.7.2) to build the image with MAC OS big sur platform., and docker installed. My bromolow_user_config.json: content is (xx and yy are replacing real values and pid/vid are the one from my USB key): { "extra_cmdline": { "pid": "0xFFF7", "vid": "0x203A", "sn": "yyyyyyyyyyyyy", "mac1": "xxxxxxxxxxxx" }, "synoinfo": {}, "ramdisk_copy": {} } Commands to build the image: cd ~/Desktop/redpill-tool-chain_x86_64_v0.7.2 sudo chmod 777 redpill_tool_chain.sh sh ./redpill_tool_chain.sh build bromolow-7.0.1-42214 sh ./redpill_tool_chain.sh auto bromolow-7.0.1-42214 The image is written on USB key with BalenaEtcher Did I am missing something ? Help will be appreciate. Thanks ! Rikk

Thanks a lot for this useful and accurate how to! Rikk

Hello to All, I have currenlty a Gen8 (E3-1220LV2) with ESXI 6.7 and loader 1.03B /3617 installed and everything works fine. I would like to create an new VM with loader 1.04B/918+ but I didn't find any setup to have it working (even through duplication of my current VM and replacement of synoboot.img). I tried to follow the tutorial "Tutorial - Install DSM 6.2 on ESXi 6.7" (with 1.04b loader) without success. I an another side, I have seen some hardware compatibility issue with CPU. Somebody was able to set the VM with Gen8 /918 / ESXI 6.7 ? Thanks for help! Rikk

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254-1 - Loader version and model: Jun's Loader v1.02b - DS3615XS - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5 - HPE Proliant MicroServer Gen8 - Additional comments: NO REBOOT REQUIRED

This link should help : http://www.vm-help.com/esx40i/SATA_RDMs.php I have almost the same setup (DRM + datastore).

Perhaps because you have the flags "raid" in partion . I have the same issue when I have switched to VM from bare metal. I had switched to ACPI mode (not raid) and remove all partions /flags with parted tool (live CD). After I have declared as "new" disks in VM DSM. I am a newbie also, so .. Regards.

Thanks Dutchman for your comments. To clarify: Any reason you use the internal raid? -->lack of knowledge for my side: I was convinced that the DSM use the RAID controller to create/manage RAID Sure you have ilo so if raid fails you can still connect remote and troubleshoot. I didin't check the status though ilo, I have just lanched the VM with RDM created to the DD, and the disk was not seen by the DSM. But I would like to understand why you would use the low performing internal controller above dsm? stupid idea , finally.. I will restart my trials..

My configuration/setup is so stupid or unique (to not have any comments) ?

Hello, I have my Gen8 Proliant server (t1610, 6Go RAM), which works fine with the new loader, in bare metal config. I would like to switch to VM with ESXI, but taking in account several "contraints/specifications": - DSM disks (4 HDD, 2 in raid mode, 1 data, 1 SSD - connected internal in CDROM plug,not used until now -) --> reuse of disks without migration (RDM mode needed) + RAID controller activated in the bios (as of today with the bare metal DSM 6.0.2) - ESXI installation --> could be installed on USB ou internal SD card - SSD disk --> used for VM storage What I did: Tried several time to install ESXI (6.0 / 6.5) custom HP version (SD & USB key ): OK, no issue, ESXI properly installed Creation of Datastore : - OK: in ACPI mode activated in bios (disks visible in administration interface), but not compatible with current settings (RAID controlled activated --> issue: data not accessible by DSM (virtual) - NOK: in RAID controlled mode activated in bios (disks not visible in ESXI administration interface) compatible with current settings (RAID controlled activated)-->issue: no disks visible Did somebody have tried to set the same config (settings) , with RAID controller activated in the bios, and disks visible ? Some advise ? Thanks a lot. Rikk

Both works, on bare metal + DSM 6.0.2. Rikk

I succeed to launch Virtual DSM on Gen8 bare metal, with DSM 6.0.2. - no issues at all. Link to virtual DSM pat file: 6.0.2: http://global.download.synology.com/dow ... M_8451.pat 6.1 (beta): http://global.download.synology.com/dow ... _14871.pat If somebody retrieve the link to VirtualDSM install file, please, post the link ! Thanks. Rikk