IG-88

Members
  • Content Count

    2,164
  • Joined

  • Last visited

  • Days Won

    86

IG-88 last won the day on May 20

IG-88 had the most liked content!

Community Reputation

425 Excellent

About IG-88

  • Rank
    Guru Master

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. you might be knowing exactly what hardware, loader (extra.lzma) and DSM version you are using but we cant know that without you telling (at least most - my crystal ball is in London for re-callibration where i bought in Diagon Alley and tea leaves are much to unreliable for computers) also maybe any log files like dmesg?
  2. yes, if you only used jun's drivers set on 6.1.7 as the name implies its just for 6.2.2 as long as we dont have a custom kernel we are bound to the original kernel of dsm and when synology decides to change things a new version we need to follow that and with 6.2.3 synology decided its back to what we had in 6.2.0/6.2.1
  3. was gibts aucher "normal" bei boot menu type? was wird sichtbar wenn man revovable media einscahltet, nur enabled oder gibts auswahl versuch mal hardddrive auf disable und nur removable media aktiv
  4. at least you need a driver for the controller (you did not mention!!!) you are using and there are limits to this, also you loose important functionality when only defining every disk as a single raid set to emulate hba behavior on a raid controller and it will be extremely difficult to to find and replace a not properly working disk, removing/replacing the wrong will result in a broken raid set, a situation that most users can't handle to repair did you read the tutorial? the part about drivers aka extra.lzma? its suggested to use a lsi sas based card in IT mode, that way you might be able to find a proper cable from controller to your backplane LSI SAS 9211-8i and reflashed oem versions are cheap to get used often already with it firmware maybe check your B320i (?) controller for HBA/IT functions here is something called hba mode option rom" listed https://pastebin.com/QipUzQHZ and here it looks like that it would be possible to disable the raid option in the setup https://www.manualsdir.com/manuals/393253/hp-rom-based-setup-utility.html?page=44
  5. just as a reminder, dsm is a appliance and a user is not supposed to change files on the system partition and when doing so its to expect to loose these changes when updating in this case synology might add ddns providers even on a small update and might overwrite this file even on normal linux systems there are rules on how to change config in a way that will survive updates
  6. read above, to see that you are wrong with that there are device id's that are not in the driver even when its "only" UHD630 https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/?do=findComment&comment=146656 synology's i915 driver date in dsm 6.2.3: 20171222 you can look up the supported device id in the binary driver with "modinfo" or just use a editor and look for vermagic, that will land you near the place about firmware and devie id's i added a comment about that and the list of device id's in the 1st post edit: i looked up a new i5-10500 and its device id is "9BC8" and there are no "9xxx" numbers in the driver we use so don't expect any newer gen10 to work even when it "only" has UHD630 https://www.intel.com/content/www/us/en/products/processors/core/i5-processors/i5-10500.html
  7. it places itself on every disk as raid1 over all disks so there is not really a recommandation if you want to boot faster you can make the 1st disk a ssd and just dont use the rest of the ssd or build in a second and use both as faster volume (cache ssd have no system, they are special) if you dont care about waiting 1 minute longer on boot then you dont have to do anything, just pliugin you hdd's and install
  8. cpu? from the hpe specs it seems to be ivy bridge, to old for 918+ (loader 1.04b) loader version and type? i guess you will have to use 1.03b 3615 or 3617 (dsm 6.2) and keep in mind that it will not work as uefi, it needs csm/legacy mode you can test with loader 1.02b (dsm 6.1),that one will work uefi and csm https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ not when you do it the right way that is a intel based card hpe has the intern 4port adapter as "HP Ethernet 1Gb 4-port 366i Adapter" in the specs and from vendor id (8086) thats intel
  9. must be a old unit out of waranty so why not peel off the usb case and use the internal sata drive? (there are a few where the internal drive is not a independent sata anymore so work in a way you can put it back together) the video is pretty much all you need to know, 1st define all as internal to find out whats the position of the usb 3.0 you want to use as intenal and then define all other usb ports as usb, leaving only the ports meant to be internal in the line of internel ports mas disk set to 24 (default is 12) internal 1111 1111 1111 1111 1111 1111 = ffffff usb 0000 0000 0000 0000 0000 0000 esata 0000 0000 0000 0000 0000 0000 example for two usb drives as internel internal 0000 0001 1000 1111 1111 1111 = 18fff usb 1111 1110 0111 0000 0000 0000 = fe7000 esata 0000 0000 0000 0000 0000 0000
  10. anderen usb stick probieren (z.b. den vom backup system, das dann aber wegen mac dopplung nicht am netz sein sollte), mit usb stick ins beios gehen einstellungen speichern, reboot und wieder ins bios, usb als ersten boot festlegen, erneut versuchen ob er von usb bootet gibts mehere usb geräte in der liste? gibts usb typ wie hdd, floppy usw.? ich habe kein handbuch gesehen das diese punkte des bios genau zeigrt so das es schwer ist die einstellungen zu überprüfen oder vorschläge zu machen, do kanm es je nach bios erhebliche unterschiede geben
  11. why not using a sata controller, your board has 3 pcie slots using a JMB585 based card (pcie 3.0 support) would be even better than a usb 3.0 drive, even a 8 port lsi fusion based sas controller is possible or if you have to a pcie 1x based 88se9215 (there are even M.2 sata controller you could use) imho esata would not change anything compared to usb, it will be shown as external storage and you cant create a raid with it when it comes to ease of mint and performance you should buy a sata controller to add more ports and use them the way its intended i cant see why your sata disks (screenshot) are all over the place, you have 4 internal ports and ...?
  12. how about using docker? https://github.com/jlesage/docker-firefox
  13. whats the M.2 ssd for? they can only be used as cache and with just one it would be only read cache, and it also need you to patch dsm for this and you need to repatch after bigger updates ssd read cache for just one client is useless in most cases, its more interesting in multi user enviroment some people use a sata ssd as 1st disk to speed up booting, if that was your intension for the M.2 ssd
  14. that's normal and documented https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ the synology default looks like this esataportcfg="0xff000" internalportcfg="0xfff" usbportcfg="0x300000" for extending usb from 2 to 14 you would need this usbportcfg="0x3fff00000" without any esata and only usb its this esataportcfg="0x0" usbportcfg="0x3fff000" i din't get the point why you want to define two usb ports as esata ports, these are both external devices so in the way how dsm uses the two types would be no difference i did not try this but i guess having two usb ports recognised as esata would need to overlap esataportcfg="0x3000" usbportcfg="0x3fff000" that way 2 esata ports are overlapped by two usb ports thats a ivalid configuration and its not safe to use as dsm can react different to this in later versions in theory the point where the overlap happens can be shifted, it would be the two "bits" (4 bits a hex number) esata 00 0000 0000 0011 0000 0000 0000 usb 11 1111 1111 1111 0000 0000 0000 if its two other usb ports to be esata like this esata 00 0000 1100 0000 0000 0000 0000 usb 11 1111 1111 1111 0000 0000 0000 -> esataportcfg="0xc0000" usbportcfg="0x3fff000" don't blame anyone when your system does not work es expected and i did not test these numbers, there are chosen in the way i think it would work also keep inn mind there settings will be back to defaults when updating a bigger version like 6.2.2 -> 6.2.3 (~250MB pat file) in that case the system starts with default values and might not recognize the disks that are now unknown (only the two first usb ports would work) and you would need to change the values again
  15. you need to reboot with csm active to see the plugged in usb as legacy (device without uefi in name)