urundai

Thank you @flyride. I had my DSM installed on the HBA disks and I was little confused by the tutorial as well. I wasn't sure if there were particular benefits to installing on VMDK vs directly using the devices. I have decided to go back to my original model and deleted SATA 1 controller and the vmdk. I am all good now. Thanks for the great tutorial, it was spot on and helped me immensely.

@flyride, does this mean that the 21GB disk is now attached SATA 0 controller - as Sata 0:1? I have this exact setup and trying to understand what deleting SATA 1 controller means

I am not sure what specific use case is driving this need for bare metal. As I noted in my previous response, You will be allocating the entire disk only for use of the 1GB redpill image. Even then, TTG created this SATA boot option specifically for VM installations which can't be booted from USB. I also read there is some slim size hard coding (maybe less than 1G disk size?). It can be a great POC to see if it works or not, but I am failing understand the real need. Can you elaborate on the specific situation for this kind of a boot model for bare metal?

For anyone looking for a tutorial, I point you to this post from @apriliars3. This is the closest your will get on a step by step and helps you setup the linux build machine (what libraries and packages are needed). There are multiple GH forks of the main repo from @ThorGroup. I am a fairly experienced developer (having done coding for better part of 20+ years including messing around heavily with docker and several other framework). In spite of that, I couldn't get any of the forks to work and spent better part of 2 weeks to recover everything without data loss (had a backup but still took it as a challenge to recover without reinstalling everything). I finally had success with @tossp's fork. It worked perfectly for me in the end. But, throwing the above in here as caution - this project is not ready yet for someone who is not willing to roll up the sleeves and also go through some kind of exploring the unknowns if things don't go well (including reinstalling if needed) In the post I quoted above, just change the repo fork that you are using in the (such as changing "https://github.com/jumkey/redpill-load.git" to "https://github.com/tossp/redpill-load.git if you decide to use tossp's fork instead of jumkey's ). Please also change the branch to match the fork (tossp doesn't have develop branch but instead of 42218-20211021 etc). I used @tossp's tool chain as well (https://github.com/tossp/redpill-tool-chain), though any tool chain for building should work. As everyone has remarked, you need to be fairly familiar with concepts of linux vms, command lines and git repo concepts in general). This is meant for a reasonable comfortable dev at the moment as we have seen so many nuances and unique problems so far.

Another option is to check your router o see if IP was issued. That was the case for me - assistant couldn’t find but I was able to get to it through the IP address (IP:5000).

are you building it natively in Mac or a VMware / virtual box linux image running on Mac? To my knowledge, there are some other linux packages needed to build with the tool chain and I don't think it can be built natively on Mac. Specifically on this error, you can look at Stack overflow. Seems more to do with GitHub is not reachable (on that stack overflow, recommendation is to use the google DNS server but it's likely that your ISP or DNS provider is blocking access to git?)

Same situation and works for me as well. @havast, can you translate your error to english? What does it actually complain about?

You are right, last time, I think the repo was taken down. Last commit on the GitHub repo by TTG was more than a month ago (shared by @WiteWulf). But, given that the repo is still there, it's unlikely due to legal action. Maybe due to some personal issues with TTG and I do hope they aren't severely impacted with anything. Wish them the best to resolve those issues quickly.

Given almost a week since this thread started and no response from @ThorGroup, I am worried if Synology again silenced them. That will be be tragic. hope they answer soon at least to update their status.

Sata option is typically meant for VM install (proxmox or ESXI etc). It will be a lot of wasted disk if you want to boot like that on bare metal. Nothing else can be on that SATA disk. Not sure if RAID of the boot disk is even worth it - you can just backup the image and start from a new USB drive or dis, if the current one fails. Actual data and synology system partition will already be part of your data disks (should be RAID, to sustain disk failures) and it will boot up with nothing lost with the new USB.

Can you try with DiskIdxMap of 1000 and SataPortMap of 1?

Cables can go bad but that's still a rare case. Just to rule out any other issues - if you connect the WD drive to the same broken cable, are you still having issues? Or the other way around, connecting Seagate to good cable and making sure it work?

If your PSU is newer, it shouldn’t be a problem. If it is older (5+ years), you would be surprised how their output drops and not enough depending on the number of things you have going on. you mention about the upgrade. How did you go about upgrading redpill? Did you build a new image or upgraded from synology control panel?

@chrram, there are reasons why nobody can share images. This is also very early development oriented project at the moment - meaning, meant for developers as you need to comfortable building and messing around with the config files etc and being able to debug any issues you will run into. If you are up for it, everything you need was shared just couple posted earlier by @r27 (I have quoted his post below for you). This is all that you should need and since it's meant for devs, there aren't many detailed tutorials - things are still trial and error, based on ones unique hardware setting etc. If you aren't passing pci-e card, add a second SATA controller in the VM settings and attach your hard disks to that controller (image on controller 1 and all disks in controller 2). Due to a bug, Disk 1 is not visible within synology. So, attach your disks from 2nd position onwards on the 2nd controller. That should be it hopefully.

Thank you @r27. I had been struggling all along (several weeks, multiple failures - learnt to repair Btrfs etc along the way - not all lost) and I was able to get going with your instructions. I was able to upgrade my 6 raid 6.2 ESXI install to 7.0.1. Everything is fine except my system is showing volume degraded because it's not detecting Drive 1 (same as your case). Regardless of what we do, looks like DiskIdxMap is not handled by the redpill loader ( @Orphée has a ticket open to that effect). For now, I will try to move my Sata cables around, so my drive 1 becomes drive 7 which I don't use :). Thank you for your help. This is awesome.

wasn't there a break between their previous post (when they answered a lot of questions) and the one before? I am hoping this is due to @ThorGroup being occupied with other things.

I am not familiar with SaS, hope someone that tried redpill with Sas disks before can help you further. I also noticed that you included both bromolow and apollo configs. Which one are you building? I notice both mac1 and serial are xxxxxx... wanted to make sure that because you masked it for uploading and you have updated the default files with the actual serial number and mac in your local copy that you are using for building.

Thank you. Global config is generic but can you also share the bromolow or Apollo user config as well? (please take out the serial number). Also, can you explain the Sas part of the comment? Are these SATA disks or Sas ?

Can you share some additional details? Is this for passthrough of HBA card or you have individual disks? What's your json config for the build? On PCI-E Passthrough, I had the same problem and gave up after trying multiple things. I was able to telnet and fdisk -l showed all the disks being there. I couldn't figure out why (even with help from experts on this forum). Hopefully, your situation is different but bit more details will help provide some options to explore.

My disks are 2TB each. I have 6 disks. Forgot to mention - I was running these in 6.2.3 Jun's loader before, in a raid config.

Thank you @Orphée and @pigr8. Here is the fdisk -l output. All disks showing up but not sure why the disks are showing sde, sdf etc: Disk /dev/synoboot: 128 MB, 134217728 bytes, 262144 sectors 16 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 16,81,1 253952 262143 8192 4096K 83 Linux Disk /dev/sde: 1863 GB, 2000398934016 bytes, 3907029168 sectors 243201 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sde1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sde2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sde3 587,111,37 1023,254,63 9437184 3907015007 3897577824 1858G f Win95 Ext'd (LBA) /dev/sde5 588,112,5 1023,254,63 9453280 3906822239 3897368960 1858G fd Linux raid autodetect Disk /dev/sdf: 1863 GB, 2000398934016 bytes, 3907029168 sectors 243201 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdf1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdf2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdf3 587,111,37 1023,254,63 9437184 3907015007 3897577824 1858G f Win95 Ext'd (LBA) /dev/sdf5 588,112,5 1023,254,63 9453280 3906822239 3897368960 1858G fd Linux raid autodetect Disk /dev/sdg: 1863 GB, 2000398934016 bytes, 3907029168 sectors 243201 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdg1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdg2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdg3 587,111,37 1023,254,63 9437184 3907015007 3897577824 1858G f Win95 Ext'd (LBA) /dev/sdg5 588,112,5 1023,254,63 9453280 3906822239 3897368960 1858G fd Linux raid autodetect Disk /dev/sdh: 1863 GB, 2000398934016 bytes, 3907029168 sectors 243201 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdh1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdh2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdh3 587,111,37 1023,254,63 9437184 3907015007 3897577824 1858G f Win95 Ext'd (LBA) /dev/sdh5 588,112,5 1023,254,63 9453280 3906822239 3897368960 1858G fd Linux raid autodetect Disk /dev/sdi: 224 GB, 240057409536 bytes, 468862128 sectors 29185 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdi1 0,32,33 1023,254,63 2048 468857024 468854977 223G fd Linux raid autodetect Disk /dev/sdj: 93 GB, 100030242816 bytes, 195371568 sectors 12161 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdj1 0,32,33 1023,254,63 2048 195366464 195364417 93.1G fd Linux raid autodetect Disk /dev/sdk: 1863 GB, 2000398934016 bytes, 3907029168 sectors 243201 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdk1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdk2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdk3 587,111,37 1023,254,63 9437184 3907015007 3897577824 1858G f Win95 Ext'd (LBA) /dev/sdk5 588,112,5 1023,254,63 9453280 3906822239 3897368960 1858G fd Linux raid autodetect Disk /dev/sdl: 1863 GB, 2000398934016 bytes, 3907029168 sectors 243201 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdl1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdl2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdl3 587,111,37 1023,254,63 9437184 3907015007 3897577824 1858G f Win95 Ext'd (LBA) /dev/sdl5 588,112,5 1023,254,63 9453280 3906822239 3897368960 1858G fd Linux raid autodetect dmesg | grep sas output: [ 1.318327] <redpill/intercept_execve.c:57> Filename /tmpData/upd@te/sas_fw_upgrade_tool will be blocked from execution [ 2.390160] mpt2sas version 20.00.00.00 loaded [ 2.392635] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8152752 kB) [ 2.465986] mpt2sas0: MSI-X vectors supported: 1, no of cores: 4, max_msix_vectors: -1 [ 2.466973] mpt2sas 0000:03:00.0: irq 73 for MSI/MSI-X [ 2.468960] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73 [ 2.469954] mpt2sas0: iomem(0x00000000fd4fc000), mapped(0xffffc90000018000), size(16384) [ 2.470951] mpt2sas0: ioport(0x0000000000004000), size(256) [ 2.596914] mpt2sas0: Allocated physical memory: size(7445 kB) [ 2.597912] mpt2sas0: Current Controller Queue Depth(3305), Max Controller Queue Depth(3432) [ 2.598910] mpt2sas0: Scatter Gather Elements per IO(128) [ 2.658630] mpt2sas0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.27.01.00) [ 2.658901] mpt2sas0: 0x1F4E: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F4E) [ 2.659902] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 2.663103] mpt2sas0: sending port enable !! [ 2.669634] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b006bea440), phys(8) [ 2.674918] mpt2sas0: port enable: SUCCESS [ 2.679023] scsi 4:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x50014ee0ae347ea7) [ 2.709273] scsi 4:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x500003993c40037e) [ 18.513653] scsi 4:0:2:0: SATA: handle(0x000a), sas_addr(0x4433221101000000), phy(1), device_name(0x50014ee2b1b4bb32) [ 33.610139] scsi 4:0:3:0: SATA: handle(0x000b), sas_addr(0x4433221102000000), phy(2), device_name(0x50000397dbd81f98) [ 48.893537] scsi 4:0:4:0: SATA: handle(0x000d), sas_addr(0x4433221104000000), phy(4), device_name(0x50015178f366abf7) [ 64.002050] scsi 4:0:5:0: SATA: handle(0x000e), sas_addr(0x4433221105000000), phy(5), device_name(0x55cd2e400033064c) [ 79.102315] scsi 4:0:6:0: SATA: handle(0x000f), sas_addr(0x4433221106000000), phy(6), device_name(0x50000398bd101889) [ 94.173073] scsi 4:0:7:0: SATA: handle(0x0010), sas_addr(0x4433221107000000), phy(7), device_name(0x50014ee60331902f) I changed SataPortMap to 4 as suggested. I notice that all my disks are being picked up but I still end up with no drives detected message.

Thank you @Orphée. I have removed those lines. The problem still remains the same. With both sas_activator and without that, I continue to get 'No Drives Detected'. With @pocopico extensions, I am able to get to the install but after completion, it continues to prompt 'Not Installed' with directions to install pat again. I have attached my vm config - don't think it's any different what I had for jun's loader before.

Thank you @pigr8. That results in 'No Drives Detected in DS3615xs' message. Here is my user config: { "extra_cmdline": { "pid": "0x6300", "vid": "0x13fe", "sn": "xxx", "mac1": "324D220C3CD1", "sata_uid" : "1", "sata_pcislot" : "5", "synoboot_satadom" : "1", "DiskIdxMap" : "0C00", "SataPortMap" : "18", "SasIdxMap" : "0" }, "synoinfo": { "supportsas": "yes" }, "ramdisk_copy": {} } Let me know if I messed any of the bromolow config

I was able to successfully compile on ESXI V7. I am using LSI SaS controller. If I use the sas_activator from thorgroup, I end up with no disks found. With @pocopico's extensions, it finds the disks and I was able to install the pat. It goes to 100% completion and ends with the 'Restarting Synology' with the count down timer for 10 minutes. But, after that, when I go to the IP address (ip:5000), it still presents 'Not installed' and prompts me to go through the pat installation again. I have attempted this few times and it ends up this way - it's almost like the install is not recognized. I tried with the latest LKM (with the SAS->SATA mapping) as well. Nothing obvious in the logs either. Any thoughts or guidance from the experts will greatly help.

quick question: Per the loader documentation, one can remove vid and pid if they are using SATA based boot. Unfortunately, when I do that, my build fails with 'unbound parameter extra_cmdline('vid')'. For now, I am still leaving vid/pid in there for my esxi but not sure why the build fails. Any thoughts?