Search the Community

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. Well done, I hope everyone will work together to make this loader more perfect while trying the loader From Yanjun howto add your disk into synology DB

I was able to install on Supermicro X10SDV-6C+-TLN4F with a Xeon D-1531 onboard 10gb nic working at full speed, My issue is that I'm only able to recognize the hard drives attached to the onboard SATA ports 8 hard drives connected to the a LSI 9211-8i are not been recognized I had this machine working with a 3615 RP build all drives recognized Any suggestions???

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.

Добрый день. В наличии сервер SuperMicro 813M-2, нашел на просторах Интернета описание и инструкцию как запустить. Скачав все на сторонних источниках (лоадер и PAT) получал похожую ситуацию: при первоначальном запуске агент обнаруживал устройство, заходил в интерфейс, начинал установку. По завершении установки перезагружался и все, система стартовала корректно. При просмотре через COM процесса загрузки при разных PAT файлах были разного рода ошибки, в основном kernel error. После долгих попыток и перечитывания статей дошел до официального форума XPEnology. Скачал лоадер и PAT файлы по ссылкам соответственно. После установки перегружается и требует обязательной миграции. При попытке установить любую версию, в том числе только что установленную выдает ошибку невозможно загрузить пакет, файл возможно поврежден (13). В чем может быть проблема?

Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Jun's 1.04b bootloader - Loader version and model: RedPill DS3615xs v7.0.1-42218 update 2 - Installation type: BAREMETAL - SuperMicro x10slm-f / 8* 4tb SAS drives - Using custom extra.lzma: NO - Additional comments: DSM update - 20 min, required prior to build: sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json

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.

Moin zusammen, habe nun endlich mal Zeit gefunden, meine gebrickte 3617-Version neu aufzusetzen und wollte dabei mal die DS918+ mit Loader 1.04 testen. Bei allen 8 Platten am PC die 2,37GB Partition mit Partition Wizzard geswiped und den Bootstick mit der 918+ vorbereitet, gebootet und das DSM_DS918+_23739.pat file zur Installation genutzt. Platten kamen sofort mit allen Daten wieder hoch. Soweit , so gut. Leider erkennt die 918+ meine Mellanox Karte nicht. In der Grub.cfg ist analog zur 3617 Grub.cfg nur die Onboard-NIC des Supermicro-Boards eingetragen. Unter der 3617 wurde die Mellanox-Karte damals sofort erkannt, auch ohne zusätzliche Treiber. Gibt es hier bei den mitgelieferten Treibern Unterschiede? Kann ich den Treiber dann nachträglich hinzufügen oder muss ich die Grub nochmal anpassen? Die Mac-Adresse der Mellanox-Karte habe ich (zumindest die aufgedruckte, finde leider keine alte Log-Datei von den Netzwerk-Settings der 3617 zur Überprüfung. Falls ich die Grub anpassen muss, brauche ich dann die Extra LMZ von IG-88 ? SO, gerade nochmal testweise auf die DSM_DS3617xs_23739 migriert, hier ist die 10Gbit NIC sofort da. Bleibe dann wohl erstmal dabei. Was ist die letzte stabile Version von 3617, auf die ich gefahrlos updaten kann? Gruss Clemens

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!!

wie ich schon schrieb, war mein HBA zuerst im IR Mode (Raid) geflasht....habe Ihn dann in den IT Mode (stink normaler HBA) geflasht ...somit sind die Platten ganz normal einzeln ansprechbar..die backplane sollte hier eigentlich egal sein...ich habe auch Systeme mit Backplane...und jetzt habe ich auch eine mini-Backplane drin Ich weiss, dass bei gebrauchten HBAs (HP, Dell,...wie sie alle heißen, aber im original LSI sind) gerne die IR Firmware drauf ist....bei Tante Google findet man viel dazu das habe ich hierzu genutzt.. https://forums.servethehome.com/index.php?threads/supermicro-onboard-lsi3008-from-ir-to-it-mode.19083/ habe das Gehäuse hier.. https://www.amazon.de/gp/product/B07TVTYCTV/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&th=1 das hat sogar Anschlüsse für nen 2. Controller je SAS Backplane..^^ ..habe extra mal für dich ne SSD schnell an den HBA angeklemmt... das steht dazu im DMESG " [ 2870.010878] ==== end ==== [ 3226.447484] mpt3sas_cm0: detecting: handle(0x0009), sas_address(0x44332211020 00000), phy(2) [ 3226.455927] mpt3sas_cm0: REPORT_LUNS: handle(0x0009), retries(0) [ 3226.697096] mpt3sas_cm0: TEST_UNIT_READY: handle(0x0009), lun(0) [ 3227.737680] mpt3sas_cm0: detecting: handle(0x0009), sas_address(0x44332211020 00000), phy(2) [ 3227.746126] mpt3sas_cm0: REPORT_LUNS: handle(0x0009), retries(0) [ 3227.752295] mpt3sas_cm0: TEST_UNIT_READY: handle(0x0009), lun(0) [ 3227.849042] Check proc_name[mpt3sas]. [ 3227.852791] scsi 8:0:0:0: Direct-Access ATA Crucial_CT750MX3 R011 PQ : 0 ANSI: 6 [ 3227.861251] scsi 8:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221102000000), phy(2), device_name(0x500a0751125fb747) [ 3227.871945] scsi 8:0:0:0: enclosure logical id(0x5d0509900005f2c8), slot(0) [ 3227.879061] scsi 8:0:0:0: enclosure level(0x0000), connector name( ) [ 3227.885886] scsi 8:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 3227.894667] scsi 8:0:0:0: serial_number( 1615125FB747) [ 3227.900484] scsi 8:0:0:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1) [ 3227.908992] scsi 8:0:0:0: Serial Number: 1615125FB747 [ 3227.914899] Check proc_name[mpt3sas]. [ 3227.914908] Check proc_name[mpt3sas]. [ 3227.918636] Check proc_name[mpt3sas]. [ 3227.922413] sd 8:0:0:0: Attached scsi generic sg2 type 0 [ 3227.926087] Check proc_name[mpt3sas]. [ 3227.931526] end_device-8:0: mpt3sas_transport_port_add: added: handle(0x0009 ), sas_addr(0x4433221102000000) [ 3227.937107] sd 8:0:0:0: [sdc] 1465149168 512-byte logical blocks: (750 GB/699 GiB) [ 3227.976661] sd 8:0:0:0: [sdc] Write Protect is off [ 3227.981520] sd 8:0:0:0: [sdc] Mode Sense: 9b 00 10 08 [ 3227.982035] sd 8:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supp orts DPO and FUA [ 3228.001012] sdc: sdc1 [ 3228.007980] sd 8:0:0:0: [sdc] Attached SCSI disk [ 3228.012668] Check proc_name[mpt3sas]. [ 3228.016397] Check proc_name[mpt3sas]. [ 3237.294305] ---- NAS_Disk_Hot_Add(enc_id=0, port_id=6) start. [ 3237.513059] ---- NAS_Disk_Hot_Add(enc_id=0, port_id=6) finished. [~] # "

Hello everyone, after various installation tests of DSM 7.0.1 and functionality tests (it seems to me to work correctly), migration test from DSM 6.2.3 up3 to DSM 7.0.1 all done in v.m. mode and all are successful with the image redpill-DS918 + _7.0.1-42218_b1635406499 I wanted to upgrade the DSM (migration from DSM6.2.3 up3 to DSN 7.0.1) of my machine running in baremetal mode (supermicro motherboard , hhd SATA and 100/1000 network), I needed to know something that I could not test with vm installations; my machine has 2 NVMe which I use as SSD cache, does anyone know if the redpill has problems with these disks ?? When migrating, it is better to disassemble them and then reassemble them once the upgrade has been carried out ??? (I seemed to have read something about it somewhere). There are additional drivers in the image redpill as it was for the 104b loader ??? (also on this I seemed to have read something in the forum about it) does anyone know something ??? thank you

It's quite impossible to give any assurances in current state. I'm actually trying it out using Tinycore Loader, however not so much luck getting the drives on the LSI 9211-8i to show up, even though mpt3sas was detected and me running rploader satamap, so I will probably have to either play around with satamap settings or connect to serialport using IPMI on the Supermicro mainboard to see what's not happening.

всем привет. получил рабочий вариант на серверной плате SUPERMICRO x9scm. Важно, не делайте никогда обновление в автоматическом режиме - убил 3 дня на решение этого вопроса, обновление только вручную подробности как делать правильная ссылка

- Outcome of the update: SUCCESSFUL - DSM version prior update: Fresh Install - Loader version and model: RedPill DS3615XS+ v7.0.1-42218 - Using custom extra.lzma: NO - Installation type: BAREMETAL - SuperMicro x9spv-ln4f-3qe (i7 3612QE BGA, 16GB RAM, INTEL QM77 EXPRESS) - Additional comments: All Working 4 NIC + IPMI (iLO). used SataPortMap=24

Hello TheEvilSide and everyone, I wanted to ask you if you can better describe (step-by-step) the procedure you performed to upgrade (at least if I didn't get it wrong) from DSM 6.2.3 to 7.0.1. I also watched the video, I'm not an IT guru but I don't think I'm the last one, but I miss some steps that I don't understand in particular how to manage the red pill; this discussion does not help (I remember that it had started to upgrade from 6.2.3 to 6.2.4, then it went into everything as usual and made it practically useless, at least from how I see things, precisely because there is everything inside). Currently I have a server that I built specifically to run the DSM on 918+ loader which now I have version 6.2.3 up3 in barematal mode (for this I ask you, I saw you did it), with a Supermicro motherboard, an intel Xeon processor E2276 4 HHD sata, 64 Gb ram and 2 nvme ssd, thank you if you want to help me; particularly if it is a migration or a new installation. Thanks to those who will be able to help me bye

@hitman22Das mit der fehlenden Lizenz hatten auch schon andere Kollegen hier. Keine Ahnung woher das kommt. Ich habe bisher nur mit QTS experimentiert. Die Config wird auf allen Platten und auch auf der NVMe gespeichert. QNAP reserviert sich hierfür auf jedem Device eine kleine Partition. Daher brauchst Du am Stick nichts machen. Eher an den Platten. Bei einigen Tests hatte ich auch den Fall das in der Console einfach nichts mehr kommt aber das Webinterface trotzdem erreichbar ist. Auf meinem S1200 (Intel-Server) ist das auch der Fall und trotzdem läuft er schon einige Zeit sehr stabil. Ich werde bei Gelegenheit mal mit einem voll ausgestatteten X10?? Supermicro Dual-Prozessorboard mit LSI 3108, SAS-Expander und 16 Platten testen. Da wird dann auch die TS-1886 oder ähnlich zum Einsatz kommen.

@VauRa Danke. Dir auch ein gutes und gesundes neues Jahr. Die NVME wird mit der Adresse B00:D28:F4 erkannt. Allerdings will QuTS Hero mit dem Modell TS-1886XTU-RP eine Lizenz. Mit dem Modell TVS-872XT wollte es keine auf meinem Tesgterät. Ich stelle es mal um und teste nochmal und formatiere den Stick mal nochmal komplett neu oder werden die Configs auf eine Festplatte gespeichert? Einen SAS Expander habe ich nicht im Einsatz. Ich habe einen SAS 9300-8i Host Bus Adapter im IT Mode verbaut. Das Modell TVS-872XT scheint auf dem Supermicro Board nicht zu starten. Irgendwann kommt dann im KVM Viewer nur noch No Signal. Beim TS-1886XTU-RP ist das nicht der Fall. Habe es mal stehen lassen und das System startet trotzdem. Bei dem Modell TVS-872XT meckert komischerweise QuTS Hero nach keiner Lizenz. Meine 10Gb Karte wurde auch erkannt von Intel. Habe jetzt das Modell TVS-872XT am Laufen.

@VauRa Ich habe mal von meinem Supermicro System ein lspci -vttn gemacht, auf dem das QuTS Hero dann eigentlich laufen soll. -[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] +-01.0-[01]----00.0 Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 [1000:0097] +-01.1-[02]--+-00.0 Intel Corporation Ethernet Controller 10G X550T [8086:1563] | \-00.1 Intel Corporation Ethernet Controller 10G X550T [8086:1563] +-02.0 Intel Corporation HD Graphics 610 [8086:5902] +-13.0 Intel Corporation 100 Series/C230 Series Chipset Family Integrated Sensor Hub [8086:a135] +-14.0 Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] +-14.2 Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] +-16.0 Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] +-16.1 Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #2 [8086:a13b] +-17.0 Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] +-1c.0-[03]----00.0 Intel Corporation I210 Gigabit Network Connection [8086:1533] +-1c.1-[04]----00.0 Intel Corporation I210 Gigabit Network Connection [8086:1533] +-1c.2-[05]----00.0 Intel Corporation I210 Gigabit Network Connection [8086:1533] +-1c.3-[06]----00.0 Intel Corporation I210 Gigabit Network Connection [8086:1533] +-1c.4-[07]----00.0 Intel Corporation NVMe Optane Memory Series [8086:2522] +-1c.6-[08-09]----00.0-[09]----00.0 ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] +-1f.0 Intel Corporation C236 Chipset LPC/eSPI Controller [8086:a149] +-1f.2 Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] \-1f.4 Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] Wenn ich richtig gerechnet habe, sollte dann die PCI Adresse wie folgt sein: B00:D28:F4 oder? Auf dem System habe ich auch noch einen SLI 3008 Adapter, allerdings wurden dort auf dem normal QUTS keine SMART Werte der Platten ausgelesen, über smartctl geht es aber. Gibt es da vielleicht auch noch einen Trick, damit das funktioniert? Vielen Dank.

Just been looking at this mobo for my new build here is a review http://www.servethehome.com/supermicro-x10sdv-tln4f-review-platform/ Not cheap by any means but looking to use as a plex / camera x 4 / VM server Any comments would be appreciated: is it suitable or overkill for my requirements might drop the VM side.Do i go for a i5 or i7 build suggestions for my requirements much appreciated

habe es heute testweise als TVS-472X mit Q0120_Q0180_10_10 auf einem alten XEON X3430 mit 8GB RAM installiert. Meinen LSI SAS HBA hatte er erkannt, meine Mellanox Connect X2 nicht...muss hier mal schauen, ob ich eine Intel oder andere 10G NIC zum laufen bekomme. Ich überlege nun mir einen intel atom soc (supermicro) zu holen und mein TS-251B in Rente zu senden....wichtig sind für mich die Docker container...die teste ich morgen....erst mal Daten vom richtigen NAS herschaufeln... interessant sind die 0 von 8 GB RAM...

Hello. Im about to build my first NAS. I have been looking for parts now over 5 weeks and it´s driving me crazy. Im standing between 2 motherboards that i would like to have some help with. 1. Supermicro X11SSL-CF http://www.supermicro.nl/products/mothe ... SSL-CF.cfm 2. Supermicro X10SL7-F http://www.supermicro.nl/products/mothe ... 0SL7-F.cfm Socket 1150 vs. Socket 1151.. That is the question. Is option 1 even compatible with XPEnology? If not, lock the thread. BR. Hostis.

Hello All - From reading the documentation, it looks like the SAT2-MV8 (Marvell 88SX6081-BCZ1 chipset) -- 8-port SATA PCI-x adapter -- should be supported, but multiple machines hang during the initial boot with the card installed. Swap it out for a 9211 or other LSI card, and it's good to go.... Problem is several of my machines only have PCI-X slots and no PCI-E, so i need these 88sx6081 cards to get things rolling Card Info: http://www.supermicro.com/products/acce ... T2-MV8.cfm Is there a bug? Maybe I'm doing something wrong with inits? Thanks!

Hello, I also got the QNAP running on my Supermicro X11SSH-LN4FMainboard with an Intel Pentium G4560. I have builtin a LSI 9211-8i which is also recognized and also the HDDs but the QNAP says that the SMART Status isn't supported by the HDD. Is there any Fix for this or is this really caused by the HDDS? The HDD Models are HSGT HUS726020ALS214. I have also built in a Mellanox ConnectX2, which doesn't seem to be supported from the newer Kernels because I have seen that the mlx4 Drivers are in there. Is there maybe a possiblity to compile the Driver that the Mellanox Connectx2 will be also supported? My QNAP Model is a TS-1886XTU-RP with Firmware 5.0.0.1870. Thank you.

Добрый день, тврщи. Хотелось бы услышать от бывалых, в какую сторону лучше смотреть. Что имеем: шкаф серверный на 18юнитов глубина общая 450мм(полезная около 370мм), микротик 2011, систему видеонаблюдения на собственном реге. Что хочу сделать: домашная файлопомойка, умный дом, возможность создавать виртуалки, анализировать потоки с камер видеонаблюдения и проч ересь. Одним словом: необходим задел на будущее. Вопрос: тврщи, в какую сторону глядеть? На данный момент смотрю престарелые сервера типа: супермикро на x9 мамках. На данный момент склоняюсь к supermicro x9scl-f, Процессор Intel® Xeon® E3-1220 v2. Хотелось бы услышать советы опытных товарищей, нормальный ли выбор или все же следует выбрать что либо другое?

Решил я собрать себе NAS. Пару дней занимаюсь вопросом подбора железа. Помогите определиться ) Изначально я нацелился приблизительно на J4125M, ибо энергосбережение и наличие PCIe. Значит смогу воткнуть LSI и вторую сетевку, а может и двухголовую, еще и про запас будет слот. И транскодинг будет работать, хотя пока он мне и не нужен. Далее я обратил внимание что во всех слотах подведена только одна линия PCIe. Контролер то работать будет, но вот 8 дисков... Интересно услышать мнение того кто использует, при подключении 4-8 SAS дисков. В теории должно хватать - ибо узким местом будет пропускная сетевого линка, а это 200MBs... Мысли о энергосбережении покоя не дают. Поэтому решил собирать вот такой конфиг MoBo Supermicro X10SLH-F Ram DDR3 8+8 ECC unbuf //просто немного завалялось CPU xeon 1220l v3 //тоже вроде в наличии, осталось только найти Это как говорится будет сердцем NAS. Хотелось бы услышать мнение по этой сборке. И нужен мне этот транскодинг при наличии норм процессора?

Меня терзают смутные сомнения по поводу дохленького, мы же сравниваем его с Серебряным пнем или вообще селиком, уж они то явно будут намного хуже ксеончика. Как бы надежность у них повыше, на время отладки конечно будут сата диски, но когда разберусь, однозначно SAS. Изначально сделаю 4 дисковую полку, и в корпусе предусмотрю установку еще. Но это так сказать на более поздний этап Оно то конечно хорошо, НО! J4125-ITX мне не нравится по нескольким причинам, первое ограниченность возможности расширения - 4САТА и все, второе отсутсвие поддержки ЕСС у материнки. Если уж смотреть серебряной серии то в сторону J4125M уж она явно универсальная. Потом надо покупать память ДДР4(без ЕСС), на supermicro я вставлю с ЕСС, тем более покупать не надо. гхм... supermicro -30$ или 120-140$+Ram