IG-88

Members
  • Content Count

    2,692
  • Joined

  • Last visited

  • Days Won

    112

Everything posted by IG-88

  1. yes, the recent extra.lzma's have the aqc111.ko driver for the Aquantia AQtion AQC111U after using the extra.lzma and plug in the hardware you could check with lsusb if its detected (bearcats link shows some of that)
  2. as far as i'm aware for usb 3.0/3.1 and 2.5G/5GBase-T its always Aquantia AQtion AQC111U and if its "only" up to 2.5GBase-T then its Realtek RTL8156 we have drivers for both adapters in the additional extra.lzma already edit: btw, you really expect anyone to just identify a product by the picture? you should write the name of the product to have at least a few people giving you an decent answer (my guess its qnap)
  3. i guess if you get charged 2-3 hours and parts (if thats even possible, because most of the hardware is custom) and compare it with a new 4 slot nas ... you can get a DS420j (latest modell, the 20 stands for 2020) for <300€ and the same model as your's as new iteration (DS419slim) is about 340€ and maybe now days you might not even need a 4 slot modell, a 2x3,5" model can hold a lot of data with up to 2x18TB hdd's and thses units are 180-250€ there seem to be some TerraMaster "converts" here with xpenology, so that might be a option too if you want to stick to DSM maybe
  4. dsm is a linux appliance and does not have a package managment like apt or yumm its more like a fixed environment for more stability the normal way for a native running app would be synologys package center in the webgui, these spk packeges need to be build specifically for synology (https://synocommunity.com/) the more modern way and not bound to synology would be docker in your case there seems to be a native package https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559 but as flyride already mentioned its better to use doc
  5. i thought that but had no good point where that could be, 918+ can do uefi and csm and the cpu is ok for 918+ (4th gen cpu minimum) when you see the grub menu and after this jun's message then its at least booting from usb (there can be problems with cpu gen in 918+ or cam mode not used with 3615/17 after this point resulting in a not found in network) its the 2nd partiton, on the 1st it the grub.cfg but when you replaced the two files it must have been the right partition just to find it in network you dont need any of that, the usb vid/pid is imp
  6. i only remember one or two comments about the filedropper links and when i checked the link worked anyway one of the problems was to find a new free file hoster where i dont have to register, where files stay up long enough and where you preferably not get scammed to much, i found this pretty frustrating, you get zillions of candidates but you need to invest some time on each only to find out they do not really provide the service i'm looking for - i will try the hosters you used next (i have 6 now, will hopefully enough - and tinyupload.com is back online and it seems they still have the
  7. the e1000e driver version in the extra 3.6.0 is ~1 year old, you device id is in that driver as supported device the latest driver is from 3/2020, 3.8.4 with the driver also comes a file pci.updates and both contain the same entry for this device and no sub devices from that it seems the 3.6.0 should be enough you can try again at any time, just make a usb flash drive and boot it up, there should be no harm to a disk in the system by just booting the loader and trying to find it in network would also be my next try if i ditched DSM
  8. just to mention the option, if you backup/offload your data you could delete the shr pool and create a new one with all disks including the small disks
  9. imho the "add drive" will only be available if there is a drive that can be added remove the 2nd volume and storage pool and check if the drives are shown in the HDD/SSD area
  10. yes, jun's default extra.lzma does not have aacraid.ko as i heard today no, if someone finds out more, let me know (and maybe provide a patch?) you might pm @SkyEyes he asked me today about driver support for Adaptec 71605e and the aacraid driver is already present in my extra.lzma, the card is working but atm, does not show smart or serial of the hdd the next version of the extra.lzma will have a newer driver, but the problem might also be the way synology tweaked the kernel source and the lsi driver and that might leave out other cards as long as they d
  11. https://xpenology.com/forum/forum/83-faq-start-here/ https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ the tutorial is still valid for dsm 6.2, just the loader is 1.03b https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ https://xpenology.com/forum/topic/12952-dsm-62-loader/ maybe to make things easier you can try this tool https://xpenology.com/forum/topic/12422-xpenology-tool-for-windows-x64/ i'd say go with 1.03b 3617 dsm 6.2.3 (needs csm/legacy mode in bios)
  12. looks all pretty normal and in working order - how you find out it does not work? i'd say look for other sources of trouble maybe just connect a already tested 1G network cable and look in the dsm gui if the link status of one nic changes (i guess 2.5G and 5G might not work, only 1G and 10G) i did some testing and wrote a little about 8 port ahci controller that are possible to buy (for a reasonable price) https://xpenology.com/forum/topic/19854-sata-controllers-not-recognized/?do=findComment&comment=122709 i also started
  13. plex needs the /dev/dri devices and thats only possible with 918+ DSM 6.2.3 has its own improved i915 driver and only needs some additional firmware to support more then the intended apollolake and geminilake cpu's a added extra.lzma that takes care of it would be here and also some advice about the cpu's https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ a good overview about the cpu decoding and encoding features is this https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_encoding
  14. the new extra will have the latest version of the r8168 driver and a driver for the adaptec too the downloadable pm80xx drivers are 2014/2015 so i guess all later development was done in the kernel driver,the kernels synology used for dsm 6.2 are fro ~2017 so the old source from microsemi/adaptec might not even match to compile properly, from my older driver listings in 6.1 extra and 918+ extra thread the 6405 i listed a external aacraid driver with newer date like from 2018, if anything than its aacraid as driver, if i can find a newer driver i might try this one the realtek
  15. DSM uses just the normal mdadm und lvm stuff from linux https://wiki.archlinux.org/index.php/RAID https://www.thomas-krenn.com/en/wiki/Mdadm_recovery_and_resync https://www.thomas-krenn.com/en/wiki/Mdadm_recover_degraded_Array_procedure https://www.thomas-krenn.com/en/wiki/Partition_Alignment_detailed_explanation if you have never done this before i'd suggest to wait for flyride or at least read one ore two of his threads where he helped people with recovery its most important to know the reason the the failure to prevent it h
  16. your driver (ixgbe) is version 4.1.1 and 5 years old, my extra contains a newer driver 5.6.3 whats in dmesg about the driver, whats the vid:pid you see with lspci? it supposed to be that way, some bios or ipmi might contain a option to make this available as nic but the normal default is exclusive management network without os HT "vitual" cores are counted as cores so its 4 with HT (or 8 without) for 3515 and 918+ 3617 comes with 16 (default kernel config from synology and as we only can add drivers its fixed) sata ss
  17. and the cpu cores all showing up now without any other changes in bios? 3615/17 use a older kernel (3.10.x vs 4.4.x) but there should not be such difference but if it works you won't loose anything as 918+ main thing is M.2 nvme support and i915 (intel qsv) driver based hardware transcoding, your hardware does not have this shr raid support can be activated after installing on 3615/17 (-> faq)
  18. it's in bold red letters in the tutorial link above
  19. you are aware it needs CSM mode? (and the non uefi usb boot device seleced for booting) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ maybe try 1.02b for testing it that one boots with uefi and csm
  20. what make you think its a driver problem? did you connect a serial 0-modem cable to see the local console? from my experience here its not, for >>90% of the cases when it comes to network its something else, the r8168 driver in the extra.lzma's available is recent enough for rtl8111g (same as 8168 or 8118), many people with that chip already using it as we are in 6.2.2 area here its to mention IF using 6.2.2 dsm *.pat file you will need to use exactly the extra.lzma made for 6.2.2 and also follow exactly the instructions about copying the kernel from 6.2.2 to the loaderm
  21. latest bios? os in bios set to "other os" (not windows)? did you change anything in grub.cfg in the area of kernel boot parameters? set extra_args_*= set common_args_*= set sata_args=
  22. the 2nd boot option in the loader forces a reinstall with factory settings, i guess that should overwrite the the sudoers file if not you can extract the file from the *.pat file with 7zip the hda1 von be opend too with 7zip and contains the whole file system of the root dsm system partition you could boot a recover linux, mount the raid1 of all 1st partitions over all disks and then replace the sudoers file with the default file
  23. yes but how does a system boot and is seen in network with blank disks its either PXE from the nic or the usb, at least there must be a way to force the usb boot when nothing its installed on disk
  24. older and newer xeon's whrere already used with xpenology, i cant emeber a case where only one core was working the xeon does not seem to special, haswell gen cpu with 6 cores, not HT maybe anything useful in dmesg? the cpu should be detected by the kernel and there should be something in the log you could also try older loaders and dsm versions
  25. check the bios, maybe there is a special limit set to only have one core you could also try to boot e rescue linux from usb to check if it shows the same