Leaderboard

Popular Content

Showing content with the highest reputation on 11/13/2020 in all areas

  1. sata might be more often used for the connector, the mode it operates can be old ide one and the newer ahci now days you usually only see ahci, the old ide mode was just on older systems and for compatibility to older os the ahci driver is natively used by synology an all models and is part of the kernel, so whatever happens to driver support, this should always work i point out at the 6.2.2 compatibility problems (longer time no compatible drivers) or the still existing scsi/sas problems with 918+ i did not wanted to say you should have read this before updat
    1 point
  2. yes but there is room left and not everything working is listed a quick glance in the drivers of the pat file from 6..2.3 shows more 10G nic's then just intel these are the drivers that belong to the list of nic's they support but you can use all alder hardware supported by this driver, the drivers usually have a list of supported pci id's qed/qede version=8.33.9.0 description=QLogic FastLinQ 4xxxx atlantic version=2.0.5.0+sh description=aQuantia Corporation(R) Network Driver -> imho this should enable pretty much all the cheap aqantia b
    1 point
  3. imho your old dsm did run on ide mode (sata_....ko driver) and with 6.2 you loose this and need to use ahci or the ports are not recognized i guess you did not read the part about pata/sata driver not working anymore with 6.1./6.2 https://xpenology.com/forum/topic/9508-driver-extension-jun-102bdsm61x-for-3615xs-3617xs-916/ !!!all sata_* and pata_* drivers are still not working because of the kernel source changes Synology did (same as in kernel 3.10.102 used and modded by Synology), as long as no one writes a patch for this I can use to fix this, it will stay this way !!!
    1 point
  4. also, note that HDD hibernation is broken in 6.2.3/1.03b in case you try to use it....
    1 point
  5. i did read that here in the thread and it worked on my 3617 test system mod the following file /etc.defaults/syslog-ng/patterndb.d/scemd.conf destination d_scemd { file("/var/log/scemd.log"); }; -> #destination d_scemd { file("/var/log/scemd.log"); }; destination d_scemd { file("/dev/null"); }; so you comment out the original line with a "#" and add a new one that will move the log data of scemd to /dev/null instead of writing them to disk
    1 point
  6. looks like they got tired of waiting for new intel soc's 4x1GbE?, just syno's crap, that soc has a 2x10Gb interface support it's syno family is"v1000" (same as amd's name for the soc class), nothing in 6.2.2 kernel source or tool chain we have from synology would be nice to see 6.2.3 or 7.0 kernel source, tool chain and toolkit (edit: there is 6.2.2 since 10/2020) (btw. in september synology added geminilake 6.2.2 source to its gpl source repository, not that we could make much out of this, only useful might be the new i915 driver they added for geminilake but we alr
    1 point
  7. You should upload it to folder with backup. By default, Proxmox creates "local" Storage which is located in /var/lib/vz. By the way, For information for All I have successfully update XPenology to DSM 6.2.3-25426 without modifying anything. Just Press button in WEB Interface to Download new version and after it to Update. After reboot by XPenology was available by internet. You can try to restore Clean XPenology from my backup and try it by yourself to experiment. Hardware: AMD Ryzen 7 2700 / Asrock B450M Pro 4 and Proxmox 6.2.1 (proxmox-ve: 6.2-1
    1 point