Jump to content
XPEnology Community

IG-88

Developer
  • Posts

    4,628
  • Joined

  • Last visited

  • Days Won

    210

Everything posted by IG-88

  1. thats the best information about it afaik https://community.synology.com/enu/forum/17/post/54396 alsokeep in mind with the 6.x loaders from jun we are bound to use the original kernel, so even if you find out how to mod the kernel source, you can't use it only if its a loadable *.ko kernel module then it would be possible if its that important i'd suggest using omv if you can baer it, there are two 8port ahci controller with 2 pcie 2.0 lanes, beside lsi sas controller (only 8 port hba's are usually cheap) there is not much look for "IO Crest SI-PEX40137" and "SSU SA3008" for the two 8 port ahci controllers lsi 9211-8i and it mode for lsi sas (there are lots of oem controllers too) also keep in mind that xpenology is limited to 24 drives so far, quicknicks loader for 6.1 might do more but no one took the time to find out if its really working and how its done
  2. there are some exceptions on boards like apollolake, geminilake, usually 2 real onboard (soc) and when 2 more are added with a asm1061 then its one pcie lane with pcie 2.0, limiting the 2 ports to ~500MB/s together - not usable for SSD
  3. there is a working r8125 driver already in my extra.lzma, there might be very few newer cards that need a newer driver (possible for 918+) but the chip on that odroid is older for sure
  4. yes with a patched i915.ko (i do provide that in my 6.2.3 driver thread) but your systemboard is only ok for 8th and 9th gen cpu's, i use a i3-9100 on a B365M board from Gigabyte 8086:3E92 => iGPU UHD 630, Low End Desktop 9 Series (original driver) -> 8086:9BC8 => iGPU UHD 630, Low End Desktop i5-10500, i5-10600T and lower there are higher tier 10th gen that might not work, only had one feedback -> one user negative feedback for a i9-10900 (8086:9BC5) system does not boot anymore - seems to be a solid hands off?
  5. also dsm supports 2nd factor, that might be useful too https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Management/How_to_add_extra_security_to_your_Synology_NAS#t6 hiding it behind a firewall and using vpn to access it might be even better
  6. https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ !!! still network limit in 1.04b loader for 918+ !!! atm 918+ has a limit of 2 nic's (as the original hardware) If there are more than 2 nic's present and you can't find your system in network then you will have to try after boot witch nic is "active" (not necessarily the onboard) or remove additional nic's and look for this after installation You can change the synoinfo.conf after install to support more then 2 nic's (with 3615/17 it was 8 and keep in mind when doing a major update it will be reset to 2 and you will have manually change this again, same as when you change for more disk as there are in jun's default setting) - more info's are already in the old thread about 918+ DSM 6.2.(0) and here https://xpenology.com/forum/topic/12679-progress-of-62-loader/?do=findComment&comment=92682 I might change that later so it will be set the same way as more disks are set by jun's patch - syno's max disk default for this hardware was 4 disks but jun's pach changes it on boot to 16!!! (so if you have 6+8 sata ports then you should not have problems when updating like you used to have with 3615/17)
  7. not sure if that will help, if thats limiting i'd expect to see a high cpu load when using the raid system to copy data from my own systems i had the impression the lsi sas controller did not perform as good as the ahci pcie 3.0 controllers i used later what you can try for free is to use all 6 onboard sata and see if the performance is any better when the disks are connected to a ahci controller (and write cache for the disk is on)
  8. you should try the forum search, it can be helpful https://xpenology.com/forum/topic/39706-installation-on-iomega-px4-300r/
  9. then you should continue here https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/
  10. no NCQ (sata native command queuing) https://en.wikipedia.org/wiki/Native_Command_Queuing also try to disable VT-d in bios, might have effects too
  11. 1st check if something in /dev/dri is present after booting if not check /var/log/dmesg if that woks out and the driver is working properly you can continue
  12. QLC drives, if the cache is filled up you will see a terrible write performance, imho QLC is the equivalent of the shingled recording but for SSD's (and why only read cache if you have two)
  13. the files are named like that /var/log/dmesg /var/log/messages there are tons of corrected and uncorrected btrfs errors also two docker crashes you should have a backup and you should backup whatever you still need and is not recent on your backup check the hardware, there might be ram problems or something else, the file system should not break down like this i use a very similar hardware, gigabyte b365m-hd3, i3-9100, JMB585 added, no problems like that a few days i found out that you can have NCQ problems with WD disks and jmb585 but there where so problems visible beside some log entries
  14. as the cpu seem ivy bridge or earlier forget about loader 1.04b and 918+ this will be your read for starting https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ loader 1.02b 3617 dsm 6.1 would be a good start, if you get this installed you can try loader 1.03b 3617, that one needs CSM mode and the usb boot device also needs to be legacy (non-uefi) that one need to be in IT mode (aka HBA mode) you can google that and will find lots of tutorials on how to flash it, like this one https://www.taste-of-it.de/flash-dell-perc-h310-mit-lsi-9211-8i-it-mode/
  15. that hardware might need the MBR version of the loader (default loader is GPT) https://xpenology.com/forum/topic/7968-dsm-6xx-loader-with-mbr-partition-table/ also read this https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ loader 1.02b with dsm 6.1 is less of a problem as it works uefi and csm/legacy if you go for 1.03b and 6.2 (loader in the same section s above, member tweaked loaders) you need to find the right bios settings to have csm mode can be tricky with hp desktops, disable secure boot and completely disable uefi devices in boot devices menu in bios would be my advice as general howto use this (usb vid/pid is most important when installing 6.x) https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ "practice" with 1.02b (MBR) and if you get this right look into the csm/boot thing with 1.03b (also MBR if that works with 1.02b) if you are confident about the loader preparing you can concentrate an that
  16. way to overpowered as just a nas aka data tank one cpu and even half the ram would be more then enough as the cpu's are sandy bridge 918+ is not possible and with 8 core + HT its 3617 if you insist of 2xcpu you would need to disable HT to make use of all 16 cores as 16 is the max we can use with xpenology https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ as its persuably uefi bios you will have to use csm mode and non uefi usb boot device when using loader 1.03b and dsm 6.2.3 if you have trouble just try (practive with) loader 1.02b and dsm 6.1 as it can be run with uefi and csm/legacy for 20 sata ports there has to be additional controllers, not everything is working, lsi sas 92xx/93xx in IT mode might be a good choice as 12 ports are the default max. with 3615/3617 you will need to manually tweak synoinfo.conf after installing and would need to redo that after bigger installs (might nver come for 6.2 ever as 7.0 is about to launch) - you should read about that before jumping into it, starting with a broken raid can make people nervous even if it will be allright (usually) after fixing the synoinfo.conf depending on side quests you have (like vm's) it might be better to use the hardware with esxi and dsm as vm and have other vm's too an esxi
  17. https://www.hardkernel.com/shop/odroid-h2plus/ https://www.hardkernel.com/shop/odroid-h2-case-1/
  18. die jetzigen loader für 6.2 nutzen andere kernel versionen, würde wohl nur mit einem neuen koader (und hack) gehen https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/?do=findComment&comment=166009
  19. i dont think so, imho for booting from that the driver has to be in the kernel (zImage) and as we are bound to use the original synology kernel and its protected against tempering (checksums) in dont see how it should be doen, it mivht be possible to compile driver as module but that would not help booting, that way you would just be able to use the module when dsm is already running
  20. the z800 seem so have a intergated sas controller and from what i found and your symptoms its LSI SAS 1068E that has a hardware limit of 2.4TB for a disk, nothing you can do about it then using another controller like lsi sas 9211-8i and its clones (in IT mode) or a ahci sata controller (a two lane 88se9230 or a jmb585 would be working too, as its presumably only pcie 2.0 a one labe controller like 89se9215 would not be that good as it would only have max. 500MB/s on the one pcie lane) 9211-8i can have 8 sata ports and 8 pcie lanes and might be a good choice it its planned to be extended beyond sata 4 ports (edit: if there are normal sata onboard from the chipset you could use them instead the sas ports and you might not need anything additional for you two disks)
  21. before trying to boot from it you should check if its even working with dsm, my guess its not i did not find needed kernel config in synologys default kernel config "CONFIG_MMC_SDHCI_PCI" or a driver "sdhci-pci", so it seems like the hardware is not recognised after installing dsm with usb try "lspci" to check if a driver is used for this hardware
  22. FAQ: https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=82391 if that is important for you then try this https://xpenology.com/forum/topic/13030-dsm-5x6x-cpu-name-cores-infomation-change-tool/
  23. you can use the KB of synology for things like this as you use dsm as any other synology user https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/StorageManager/storage_pool_expand_add_disk ... Drive requirements: Please make sure the drives that you intend to add to your Synology NAS meet the following requirements: RAID or SHR configuration must be created by drives of the same type. Using drives of different types will affect system reliability and performance. Mixed drive types as shown below are not supported for RAID or SHR configuration: SATA drives and SAS drives 4K native drives and non-4K native drives For SHR: The capacity of the drive you intend to add must be equal to or larger than the largest drive in the storage pool, or equal to any of the drives in the storage pool. Example: If an SHR storage pool is composed of three drives (2 TB, 1.5 TB, and 1 TB), we recommend that the newly-added drive should be at least 2 TB for a better capacity usage. You can consider adding 1.5 TB and 1 TB drives, but please note that some capacity of the 2 TB drive will remain unused. For RAID 5, RAID 6, or RAID F1: The capacity of the drive you intend to add must be equal to or larger than the smallest drive in the storage pool. Example: If a RAID 5, RAID 6, or RAID F1 storage pool is composed of three drives (2 TB, 1.5 TB, and 1 TB), then the capacity of the new drive must be at least 1 TB. ...
  24. das it normal, nur der lsi sas treiber macht das anders, bei ahci ist das immer gleich, zumindest auf einem controller, wenn man controller umsteckt kann sich das "blockweise" ändern wenn sich die reihenfolge der controller ändert
×
×
  • Create New...