IG-88

usually synology suggests a update to the recent version and thats 6.2.3, if you started with 6.1 and loader 1.02b you would need a newer loader 1.03b that would need to be prepared in the same way as 6.1 loader 1.02b (grub.cfg, usb vid/pid)

linux is very different from windows when it comes to drivers, you would need to compile your own driver from the source, you cant just use a (binary) driver

try the version the loader was made for (6.0.2) https://global.download.synology.com/download/DSM/release/6.0.2/8451/DSM_DS3615xs_8451.pat maybe do a test install with your new usb loader and a single empty disk, if that works out, use the usb with your 5.2 disks (if you got 6.02 installed you could pretty much do the same steps with loader 1.02b or 1.03b and try to install dsm 6.1 or 6.2) there is a warning in the 6.0.2 tutorial and its kind of prominent

anyone knowing a case thats not higher then ~4HE (19cm) and max. 40 cm depth that can handle 12 disks i use a silverstone SST-GD09 that i customized to fit 12 vertical 3.5" hdd's with an micro atx board that has only slightly more depth then mini itx i did see some rackmount units with 38-40cm but non where you could fit 12 disks ootb (either fixed mounted internal or hot plug), units with 12 x hot plug are usually 55-66 cm in depth the thing that came near it was a silverstone RM41-506 (but it has 44.6 cm depth), with 2 x FS305 it could hold 14 disks and 10 would be hot plug https://www.silverstonetek.com/product.php?pid=887&bno=0&tb=43&area=en

its not a mismatch of usb vid/pid, that just throws a mount failed on the serial console and dsm does not start at all i guess taking a new usb and redoing the loader from scratch cant do anything wrong if dsm does not start it can be checked in network (ip address), as the loader comes with 6.2.0 and there is a newer kernel (dsm system) on the disk it should offer recovery/repair and doing so will copy the newer kernel back to the loader (only takes less then a minute) and it should do a reboot, after that dsm should start again (if a extended extra.lzma was used it should also be copied to the new usb - and no files should be used from the old loader)

if looking for a hardware its good to check dmesg log for drivers loading and for pci vid/pid there are drivers for lsi sas cards in ir mode (megaraid) the only thing you dont see in that case is the disk, the driver will detect the hardware

:-))), and again https://xpenology.com/forum/topic/8057-physical-drive-limits-of-an-emulated-synology-machine/?do=findComment&comment=122819

thats just your interpretation, any activity (console) goes to the serial port the you should describe what loader and dsm type and version you had and what you have done (with what goal in mind) in general a normal update does not delete data on volumes, that worst thing is usually that dsm does not start and that can be fixed (usually lost of dsm configuration is worst case, but its usually not impossible to reconfigure ip address, users, shares and plugins)

there mus be more to it as if you had a shr1 it would mean you have one disk redundancy and if one disks fails the volume should still be available to access the data - but its not in your case, so there seems to be more damage then just a failed disk and as long as its not analyzed you would not take any action @flyride is the expert here, only if he's not available i might help out, i'm not as good and experienced in this

no, i'm not using kvm/proxmox and dont test this and i have not seen a positive feedback of people loading the modules manually in integrated in the current releases of the extra.lzma (you can open the extra.lzma with 7zip and extract the virtio modules to test them)

found a different hardware of a asm1166 card, Silverstone ECS06 https://www.silverstonetek.com/product.php?pid=973&area=en (not as cheap as the others, ~55€)

no, dont cchange anything until you know about the reason dont do any repairs, 1st step is to collect information and get a picture of the problem and you should be tripple carefull if you dont have a backup and need that data yes, synology usese mdadm and lvm2 for its software raid, both standard linux software depends on the problem, 1st step is still gather some information about the state how did you confugure your disk array, any non redundant volumes like raid0, basic or jbod?

irgend ein anderer computer in dem du sie mal testen kansst?

yes and to help other people we usually document it by telling what the reason was maybe (rare case, i know) someone tries to use the forum search (or another search engine like google)

interesting behavior from the picture its not a intel nuc (afair "NUC" is a intel specific, https://en.wikipedia.org/wiki/Next_Unit_of_Computing)

i did this last week and a user tested it, just forgot to go on and publish it look in the 1st post, i changed the text and link (now u3 mod2 for 918+) its also possible that the slot is limited to a certain type of card, look in the manual (might be not that prominent to see) and maybe try to find some more info about people who tried to extend y this slot with other cards then network/wifi could you be more specific about the hardware? i did not found a intel nuc system with a N3150 cpu

maybe with some additional magic? haven't seen a user with a working solution and no one seemed to bother to try this with quicknicks loader https://xpenology.com/forum/topic/8057-physical-drive-limits-of-an-emulated-synology-machine/#comments

its supported by the ahci driver and thats part of the kernel, no extra's needed as its "native" to dsm 1st boot a normal live linux and check with "lspci -k" if the additional device is found and if the ahci driver ist used its device id should be 1B21:0611 you should see that device id in your dsm's dmesg log, if its not there then a diver cant work

not sure where these drivers are from (the ahci support is already part of the kernel synology delivers) and how you where intending them to use but you are supposed to use the extendet extra.lzma i linked above (what extra.lzma you hae to use depends on the loader, dsm type and dsm version) whats the difference in hardware to the 5100 you had used above? (seems to be the same cpu generation and same storage controller so i gess no difference when it comes to choosung the loader an drivers pack) you would not just need csm mode you also need to boot from the non uefi (legacy) usb boot device (often you will see the usb drive 3 times, 2x uefi (for every partition in the usb) and one without a "uefi" in the name anr thats the one you need to choose when booting if you cant use csm you can still get 1.02b, that does both sn and mac are not important for installing and can be changed later if needed, you extract the extra.lzma from the zip and replace the file on the second partition of the loader with the new one

the 500B/s will also limit the rebuild speed when a disk failed (will be interesting for 6TB disks and bigger) i would not go with a pcie 2.0 card anymore when i can get a pcie 3.0 capable card

da schleichen sich gern fehler ein, weshalb ich empfehle den stick zu nehmen der schon läuft das oben war weg eins, man weiß was man macht und ist sich sicher man kann auch etwas komplizierter vorgehen und die dateien der 2. partiton sichern (sicherheitshalber nicht auf dem DSM system) dann die neue extra/extra2 UND den neuen kernel aufspielen (rd.gz und zImage aus dem 6.2.3 *.pat file - kann man mit 7zip rausholen) und das ding booten, dsm wird nicht hochfahren da das system auf den platten älter ist als das was auf dem usb ist, man sollte das system dann im netzwerk finden (nic driver = checked) und es sollte anzeigen das man migrieren/updaten kann entweder man mach das an der stelle oder man restauriert die 2. partition wieder fährt sein 6.2.2 wieder hoch und verfährt dann wie oben beschrieben (bei laufendem 6.2.2 die extra/extra2 aufspielen und update über die gui) das einzige was sich beim update am usb ändert ist der kernel und das man bei 6.2.2 -> 6.2.3 die extra/extra2 wechseln muss ist sehr speziell aber eben in dem fall notwendig normalerweise bleibt die extra/extra2 über die lebeszeit einer major realiease (6.1, 6.2) gleich und wenn man mit 6.2.0 (org. loader mit extra von jun) startet und dann auf 6.2.3 geht (ohne andere extra.lzma) laufen die treiber auch (ist nur 6.2.1 und 6.2.2 die aus der art schlagen weil sysnology an den kernel settings für das pcie power managment gespielt hat)

nein, bei laufenden 6.2.2 den usb rauszeihen, extra/extra2 aufkopieren (alternativ geht das auch unter dsm, man sollte nachher aber die usb partitons wieder unmounten) danach update auf 6.2.3 über die webgui durchführen, bei dem update wirde der kernel von 6.2.3 auch auf den usb kopiert ja, afir ist das atlantic.ko, du kannst die mit 7zip öffnen und nachsehen

du kannst ja mal als gegencheck ein live linux booten und schauen ob damit die karte gefunden wird

der usb ist wenn dsm gestartet ist nicht gemounted und wird nur beim booten benutzt

beside 4 disks sharing 500MB/s (pcie 2. 0, one lane, marvell 88se9215) doesn't esxi support ahci in general, the controllers i mentioned above are ahci