tlsnine

But the tinycore build script keeps trying to grab it remotely and add multiple instances. How do I keep it from doing that?

This is nuts! Why does the ixgbe extension keep trying to download and install itself multiple times, only to fail and kill the build? EDIT: broadwellnk-7.0.1-42218 DS3622xs+ I'm using the 4.5 version of the img file and ran ./rploader update now to grab all the newest scripts. The extension file is in the default build now, right? Can I enter something in the user_config.json file or elsewhere to manually exclude this from trying to load? Thanks

This is nuts! Why does the ixgbe extension keep trying to download and install itself multiple times, only to fail and kill the build? EDIT: broadwellnk-7.0.1-42218 DS3622xs+ I'm using the 4.5 version of the img file and ran ./rploader update now to grab all the newest scripts. The extension file is in the default build now, right? Can I enter something in the user_config.json file or elsewhere to manually exclude this from trying to load? Thanks EDIT 2: I think I might've posted this in the wrong place. sorry

Success: Bare-Metal with Working ixgbe Extension (with caveats) TL;DR: If the onboard Intel x553 NICs are enabled, the script keeps failing on the ixgbe extension. Supermicro 1U Denverton-based server with onboard Intel x533 NICs. All 4 ports are being recognized. Four Seagate "unverified" drives are working fine. No errors reported. UEFI boot from USB The caveat: The Tinycore-RedPill build script fails with the onboard x553 NIC's enabled. I had to disable them using a jumper on the motherboard, slot in a generic e1000e Intel card to perform the build/install. Once I got the build done using the e1000e card, I turned my server off, reenabled the onboard NIC's using the jumper, removed the PCIe network card, and it fired right up! (because the correct ixgbe extension is already part of the image and it doesn't fail trying to reload them from the net) So, some slight-of-hand work had to be done, but it's working well now. Thanks for everyone's help and hard work!! I hope my little blurb can help someone else. EDIT: I should point out that http://find.synology.com doesn't always pick up my instance. However, the Synology Assistant app, does. Try both! EDIT 2: Shutdown and reboot don't seem to work right now.

I've successfully installed as DS3622xs on bare-metal, Denverton Supermicro server. (offline install is the only way right now) Caveat: This build is going to look for "certified" Synology drives. If you're using something other than what's on the official list, you're likely to receive the dreaded "Unverified" critical drive warning after logging in. I was able to get around the error by using the tutorial here: https://linustechtips.com/topic/1371655-synology-dsm-7-drive-lock-bypass/ TL;DR: ssh into your instance and using sudo, edit the correct file(s) for your build and drive details under /var/lib/disk-compatibility. In my case, I prepended {"model":"ST4000LM024-2AN17V","firmware”:”0001”,”rec_intvl”:[1]}, to the "ds3622xs+_host_v7.db" file, saved, rebooted, and the warning went away. (I didn't have a *.new file listed) I'm also able to see all the SMART details now as well.

I'd like to see builds for the Denverton-based models. I think they're mostly rack-systems so lots of room for hard drive expansion. The DVA3221 as being based off of Denverton and that one is geared towards AI surveillance (and pocopico's script generates correct serials for it already) The biggest drawback is native 4 core/thread. My Supermicro Denverton server is 8 cores, no hyper-threading.

Github changed their naming conventions. They removed "master" as a term so any url containing the word master isn't found. Replace "master" with "main" in all the scripts. Otherwise you need to wait for the maintainers to do it.

I've noticed the git repos are now named "main" as opposed to "master". I think GitHub has done that due to political sensitivities. However, the scripts don't reflect that change yet. The maintainers have some work to do.

Yeah, Nvidia! I run a Hackintosh at home so I know that pain lmao. Quite a few RackStations are powered by Denverton SOCs and obviously those are more for storage-whores and non-video related computing. And I fall into that category. I'm just interested in the process. For a some reason, my server uses a stupid onboard Intel X553 network stack and the current ixgbe drivers don't work because support wasn't offered until kernel 5.5-ish, I believe. Maybe I'm overcomplicating things? Wouldn't be the first time! I'm just trying to match my hardware to the real-deal. That said, I had Jun's loader (ds918+) working fine with my entire rig and I've done it via ESXi as well, but again, I'm annoying and I'm looking for as close to a bare-metal experience as possible. As a trade-off, right now I'd be happy with some direction on how to compile the ixgbe extension for my specific, weirdo network. At least I'd be up and running again and can toy around with things as this project matures. So if you know someone that can get those drivers done for me... Thanks for letting me vent!

Other than time and maybe Human Resources, what is keeping Redpill from supporting other models? I have a Denverton-based SuperMicro server that seemingly matches up well with several Synology offerings, yet I'm still required to install essentially one of these 3 models: ds918+, ds3615xs, or ds3617xs. Redpill allows me to generate a serial for the DVA3221 but then proceeds to install for ds3617xs anyway. I realize it's just grabbing what the json files are telling it to. I see the sources for Denverton are available, so what's truly involved in altering the script to support the 9 (NINE!) models Synology offers. For comparison, ApolloLake only has 6 models available. Time is something I have a lot of right now, and while I'm not a coder, if there was a basic script of flow-chart I could follow, I'm not opposed to giving it a shot to build for Denverton. Am I wasting my time? Can someone point me in the right direction or tell me, with a reason, why it's not possible? I'm also not opposed to donating some beer money if someone else want to tackle this. Thanks for everyones hard work!!

I'm looking for some help with a quad-port, x553 Intel on-board driver, please. It should work with the ixgbe driver, however it doesn't seem to be. DS918+ Apollolake-7.0.1-42218 It builds fine, but it's not grabbing an IP address from any of the ports. I even tried manually assigning my MAC address in the json file with no luck. Also tried manually adding the other ixg* extensions with no success either. Works perfectly in TinyCore, just not RedPill. I had it working with Jun's loader along with an upgraded extras file. I'm going to try other builds after some sleep, but any assistance would be appreciated. FWIW I can get it going with an old Intel e1000e PCIe and ASUS, Atlantic 10GB card but I'd rather use the onboard nics.

I ended up going with a virtual install on ESXi 6.7, using passthough mode for my LSI SAS controller. It's pretty quick and the install was more-or-less painless. What's kinda ironic is I had to insert network drivers into my esxi image anyway, however VMware had them available and it was an easy process. Thanks for the info!!

Thanks for the explanation! I kinda sorta figured it was something to that effect, but actually knowing the process behind it will help going forward. Thanks again and play safe

Ok, so I might have figured it out... I've gone into the ESXi settings and removed ALL virtual hard drives, cd/dvd, other virtual sata controllers, etc leaving JUST my passthough PCI device (which is my LSI controller) Rebooted my VM and now all 4 physical hard drives are showing and I can assign them to a storage pool. Guess it's got something to do with how the ds918+ only sees 4 drives natively. Not questioning it too much right now. I'll post if I find any other weirdness. Hope this helps someone!

As the title says, only 3 of 4 hard drives are found in my ds918+ "bare metal" virtual instance in ESXi 6.7 when connected to an LSI sas9220-8i controller card when using passthrough mode. Before toggling passthrough mode, all 4 drives are seen in ESXi individually. All 4 drives are also seen if I connect them to the motherboard's onboard SATA ports, however passthrough isn't an option with the onboard controller. (drives are setup as RDM) Not sure if anyone else has seen this before. I know the drives are good and I know the LSI controller is good along with the SAS cables. Because I'm passing the drives via the SAS card do I have to adjust my grub.cfg file??? For S&G I tried setting up a virtual ds3615 but I can't get the network working properly so I can't find the machine on my network. (tried vmnet and e1000 emulation) I'm a little perplexed and any assistance is appreciated!