Search the Community

Another Small Test https://github.com/fbelavenuto/arpl/releases/tag/v0.3-alpha5 I tried Mellanox cx353a 10gb There a constant issue with it turns after the kernel loads. Next, I'm also having a issue with ssh I can't get it working Putty with Windows 10 or Ubuntu I have a great dislike for the credentials, they suck.... So now I have tested three revisions and they all fail because the of the Mellanox cx353a 10gb issue I changed the test because it's frustrating to hit wall over and over with testing. So new test Supermicro 10gb single port SPF Go thru the install and it works like butter DSM_DS3617xs_42661 It finds the 10gb nic and my LSi 9207 automatically I can see all the drives, It was the easiest install I have ever done Great job fbelavenuto, I appreciate you efforts...it a good idea.......

Need some help, trying to get this to work with a Supermicro X10SDV-6C+-TLN4F and using a LSI 9211-8 HBA mode, I'm currently running 3622xs 42218 built a few months ago using rploader, would like to update to 7.1 using arpl I can build the loader and find the box but can't find any disks I've tried adding DiskIdxMap and SataPortMap to the commandline but still can't find the disks any suggestions, btw using onboard controller I can find the disks ok but my onboard controller i believe is failing as i encountered several disk crashes while using it, none when using the HBA card TIA

So here is my question, I build a loader months ago using rploader for my bare metal Supermicro X10SDV-6C+-TLN4F mobo which has integrated 10gb ports everything work , also using a LSI HBA card , no issues running DSM 7.0.1-42218 Everything I have tried since with the new loaders either doesn't recognize the HBA card or the network card How did we digress to this state? I am by no means complaining, but if it worked back then why is so hard to get it to work now? I'm also running a vm on unraid using the same img , something I'm yet to accomplish with the new stuff

- Outcome of the update: SUCCESSFUL - DSM version prior update: brandnew install DSM7.0.1-42218 - Loader version and model: tossp/redpill-tool-chain 7.0.1-42218 - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL Supermicro X11 SSH-LN4F E3-1260L v5 Samsung udimm ECC 16G - Step : 1st install 7.0.1-42218 2nd updated to 7.1.0-42661-up1/up2/up3 via GUI - Additional comments: 16G MLC usb = synoboot SSD Intel S3710 100G = software and docker 2TBx4 Raid5 = PT download 5TBx1 = files 2TBx2 Raid1 = most important files backup

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1-42661 Update 3 - Loader version and model: Automated Redpill Loader - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro X10SDV-TLN4F, LSI SAS2008 - Additional comments: Upgraded via GUI

DS3622xs+ Motherboard: Supermicro X11SRM-VF CPU: 8core/8thread RAM: 128GB ECC HBA: LSI SAS3224 Network: connectx-3 I also tried ESXI with this guide VM boots and can install DSM with one virtual disk, but as soon as I add either one of the PCIE passthrough device (SAS3224 or connectx-3), it automatically shutdown. I see that during builds the ./rploader found driver for both devices. Here is my config: { "extra_cmdline": { "pid": "removed", "vid": "removed", "sn": "removed", "netif_num": "2", "mac1": "removed", "mac2": "removed", "SataPortMap": "11", "DiskIdxMap": "1000" }, "synoinfo": { "internalportcfg": "0xffff", "maxdisks": "16", "support_bde_internal_10g": "no", "support_disk_compatibility": "no", "support_memory_compatibility": "no" }, "ramdisk_copy": {} }

Thanks a lot for this tool. As said previously, I had issues getting TCRP working but I was able to upgrade from DS3615xs (jun mod) to DS3622xs+. Had some issues but overall using arpl was a breeze. Thanks again! Hardware info: Baremetal: SUPERMICRO MBD-X10SDV-TLN4F-O D-1541 (2 x 10 GbE LAN & 2 x Intel i350-AM2 GbE LAN) LSI HBA with 8 HDDs (onboard STA controllers disabled) (haven't tested 10GbE nics yet)

Since we are hacking access to specific Synology platforms, for baremetal it always makes sense to me to try and match the platform configuration. So I am running DS918+ on an Asrock J4105 - virtually identical to the real DS918+ configuration. I am also running DS3622xs+ (originally DS3615xs) on a SuperMicro X11SSH-F board - also very close to the DS36xx hardware. But I test every platform on VM, and they all work one way or another, so if you are willing to put in the effort to learn how to use ESXi or Proxmox, it is very much achievable. Regarding the integrity of your data, a failed DSM install or upgrade doesn't put data at risk. A reckless upgrader may blow up the data partitions while they try unsavory things to get the system back up, but the worst that should happen is that data is inaccessible while you figure out how to get DSM back up and running. But as always, it is best to have a backup so that if YOU mess up, you can burn it down and build it back up without losing anything. I have a second copy (and for some data, a third) of everything. The tutorial gives you information on how to test a migration successfully. There are many success stories in the upgrade threads. That said there are a lot of little things that can go wrong migrating to or upgrading DSM 7. Even with extensive testing I still had a problem with the SuperMicro migration, and I had to rebuild DSM from scratch (but not my data).

I have a motherboard Supermicro x9SRi-3F with a Xeon e31220, when i tried to install Tinycore redpill .. when inserting serial command there was no compatible serialloader, so i had to try another serialloader with another intel (I3) Also tried bootloaders for 6.1 and 6.2 none of them are loading, only happy hacking then nothing. Which bootloader (DSM six or seven) do work with the xeon e31220?

Same issue for me with a Supermicro X10SDV-TLN4F except mine is currently on DSM 6.2.3. What loader did you use for 7.0.1?

I just tried on my supermicro X10SDV-6C+-TLN4F which has been running 3622 7.0.1 for a while built back about 3 months ago, not using TCRP, wanted to upgrade to 7.1 and used TCRP but can't find 10gb network card using 3622 so I used 3617 with that I can find network but can't find any drives , so I just plug back my old usb and still running 7.0.1 any suggestions

Проблема с данной железкой :(. Завести смог только 5.2, причем установлено 8 дисков, видется только первые 6.%) На любом загрузчике для 6 система вообще не видит HDD для установки. Как быть, что делать ?

To be fair, the PN is this: MBD-X10SDV-TLN4F, the CPU is a D-1541. https://www.supermicro.com/products/Product_Naming_Convention/Naming_MBD_Intel_UP.cfm

MBD-X10SDV-TLN4F-O D-1541 I'm don't mean to be rude, in fact i may even sound "simple" saying this... But do you think Supermicro will ever stop adding #'s to their motherboard models? Like in 50 years how long will the model numbers be.... 1000 digits?

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 ((Jun 1.03b loader) - Loader version and model: TinyCore 0.8.0 - DS3622xs+ - Using custom extra.lzma: No - Installation type: Proxmox 7.2-3 VM (i440fx and SeaBIOS) - Supermicro X10SL7-F - E3-1246 v3 - Storage Disks using LSI 2308 PCI Device Pass-through - Additional comments: Use dodo-dk rpext for ACPI to work properly inside VM. Restart and Shutdown VM from Proxmox GUI works fine. ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/dodo-dk/rp-ext/main/acpid/rpext-index.json

I'm running loader 1.03b under ESXI 6.5. Server is a Supermicro with LSI 9207 SAS HBA. HBA is passed through. I have setup using the various instructions that I have found on these forums. I can add virtual hard disks without any problem. However, none of the passed through drives are recognized by the GUI. There are 12 physical disks. The OS sees the drives, but none of the drives show up in the GUI. The card seems to be getting passed through correctly. If I boot a rescue disk on the VM, I can see the drives fine too. I have tried various versions of 6.2.X and none seem to work. I have tried setting it as a 3615 and 3617 I have searched these forums, but none of the suggestions have helped. Any ideas?

Serial console is always helpful to see what is going on. EDIT: your Supermicro probably supports serial redirection so you might be able to view the serial output from a Java console launched via the IPMI. Are you certain the loader is compiling without errors? If you have an Intel CT (e1000e) card you could drop that in temporarily see if you can find what is going wrong with the i350.

Any chance of some insight into why my NICs don't show up after TCRP boot up? Motherboard which used with Jun's mod and had no issues.: SUPERMICRO MBD-X10SDV-TLN4F-O D-1541 (2 x 10 GbE LAN & 2 x Intel i350-AM2 GbE LAN) After booting up, everything looks fine except I can't get a network connection. The process I used is below: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh identifyusb now ./rploader.sh serialgen DS3622xs+ realmac now At this point I edited user_config.json to add additional 3 NICs before continuing. ./rploader.sh satamap ./rploader.sh build broadwellnk-7.1.0-42661

have just installed supermicro saslp-mv8 into my server that I had lying around. on connecting some drives xpenology says no disks are installed. Does anyone have a way I can make xpenology support this card?? thanks.

Baremetal installation Motherboard: Supermicro X11SCH-LN4F socket 1151 Processor: Intel Xeon E 2276G Coffee Lake RAM: 64Gb 4 Hhd Western Digital 4Tb EFRX 2 NVMe Samsung NVMe V-NAND SSD 670 Pro 512Gb Loader: found on the net already made for 918+ Hello everyone, yesterday I dreamed of updating DSM 7.01 up.2 working from January to up.4 manually, I downloaded the update from Synology 7.0.1-42218-4 (apollolake) site and started the update, after the update, however, the machine was never found; I thought I had everything busted but I tried to search for it with Synology web assistant (find.synology.com) and I realized that the machine is there (indeed it sees two), only that it has changed the IP addresses (I had assigned it an address static ip) with a very different range from mine, I use 192.168.1.1/254 while now he gives it to me with DHCP server and assigned ip addresses 169.254.63.90 to one machine and 169.254.58.122 to the other. Obviously my network can't see it can see hosts with that ip address renga, I tried with the Synology assistance program to change the addresses but it doesn't (it tells me that the machine is recoverable), how can I do ??? I had thought of changing the range of in to my lan (router and pc to possibly control the host) in 169.254.63.1/254 and see if I can enter the DSM and try to change the ip from the, can you do ?? ?? Or suggestions ???? Thanks

@flyrideI have three servers to choose from. My newest is a self built Norco 24 case, supermicro x12spa-tf motherboard,Xeon 3rd gen silver processor, is has 240 gb ram, 4 nvme in vroc config on motherboard, with 12ssds, and 12 spinning disk, and 1 optane 905p, using with primo cache, as cache drive. I also have a HP Dl380 gen 9, dual processor e5-2670v3, 64 gig ram, 12-6tb sas 3 spinning drives, with 9305 16i LSI hba card.(This currently runs DSM 6.2.3) in a raid 10 configuration). Has been rock solid. And I also have a 24 bay supermicro server with dual processor x9 motherboard, with 192gb ram, 24-3tb Sas drives, currently running proxmox 7.2 with 2 tinycore redpill 3622xs vms instances, and a couple of server 2022 vms also. The first server mentioned uses some of the same hardware as the FS6400. I believe that with the hardware I have, I can achieve better performance with the software for the higher end synology boxes. Things like RDMA(SMB3+), which synology provides in their higher end hardware, that they dont provide in the lower end stuff like the 3622xs,etc. I have both 40Gbe and 10Gbe connectivity to these boxes. And yes all this is part of my home lab.

- Outcome of the update: SUCCESSFUL - DSM version prior update: NONE - fresh install - Loader version and model: redpill.v0.4.6.img DS3622xs+ DSM 7.1.0-42661u1 - Using custom extra.lzma: NO (added ext drivers manually) - Installation type: VM Proxmox v7.2: cpu: E3-1270v2 mobo: SuperMicro X9-SCM-F - Additional comments: Successful as Q35 and i440fx system. PCIe/PCI Pass Thru LSI HBA controller (Dell H710 flashed IT MODE ver P20) using ext MPT3SAS. Paravirtual nic using ext V9FS. ACPI working using ext https://raw.githubusercontent.com/dodo-dk/rp-ext/main/acpid/rpext-index.json

This motherboard is a Supermicro X9-SCM-F and has 6 sata ports, 2 sata 6 and 4 sata 3. (LINK TO MOBO) I never added anything to the vm except the hba card as a pass thru pci device, I am not sure if proxmox adds these controllers by default or what? Rebuilding loader will post results in a minute

Hello Xpenology gurus.... I'm relatively new to Xpenology and only just starting to learn more about it. There's a lot of information around here and that's so much appreciated. I was able to successfully experiment with Xpenology as a KVM virtual machine using Jun's loader 1.02b. So, I decided to try it on real hardware; specifically a Supermicro 825, with X8DTU-F + 2x L5640, 128GB RAM, and a AOC-USAS2 controller, which is a LSI SAS2008 based controller, and 8x HGST SAS 3TB drives. Booting this hardware with CentOS-7, I see all the hardware no problem. However, when I boot Jun's loader 1.02b for DS3617xs with a USB drive, I get the web setup page, but when I try to proceed to do the setup, it only sees 6 of the 8 hard drives. Specifically, it says: "All data on the hard disk(s) 7 8 9 10 11 12 will be removed during installation. Are you sure you want to proceed?" If I proceed with the setup, it proceeds as normal and downloads DSM and sets up the 3 partitions on each of the 6 drives. These 6 drives correspond to port 0,1,2,3 and 4,5. The ones that are not seen are in the last 2 ports 6 and 7. So, for one, I think the mptsas2 driver for the LSI SAS 2008 chipset must be working, since all 8 drives are connected to the same controller. I was reading: And learned about the SataPortMap parameter and thought maybe that has something to do with it? Not sure, but thought it would be worth a try. Since it is a single controller with 8 ports, I set SataPortMap=8 in the grub.cfg file (there was a line where it was set as SataPortMap=1, and I changed that). Not sure if I'm doing the right thing, nor do I know if this is even related to the issue. Can anyone please advise? Or, if there's something I missed from reading these forums and elsewhere online, sending me a RTFM with a link would also be appreciated. Thanks in advanced for any help...

Hey Folks - We have made some great progress with our install and stuck on the very last step. 😩 Our Disktation installs successfully, reboots and comes back up again - after a few minutes the interface refreshes and says "Starting Services" in the assistant, if you browse to the web interface it states "System is getting ready" and simply sits there.... After a good 30 minutes nothing happens and it doesn't seem to move past this stage. We have Juns 1.02b boot loader and the DSM_DS3615xs_15152.pat file for the installation as per the guide. Hardware Setup: SuperMicro X9DBL-IF Motherboard 2 x Intel XEON E5-2418L 48Gb Ram ECC 3 x LSi 9211-8i (Flashed to IT Mode - Dell H200) HP NC365T Ethernet controller Various Hard Drives on the LSi's Has anyone else experienced anything similar to the above or can offer any insight / guidance as to what might be up? Many Thanks! MrTPN