Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 06/13/2019 in all areas

  1. no tienes que domwgrea. lo que tienes que haser , porque a mi me paso. es desavilita la targeta de red integrada que tienes en tu motherboard. eso lo tiene que haser el los Bios de tu placa madre. despues crear una memoria flash nueba. y inisiar una instalacion nueba en el nas . el te dira que ya existe un instalacion y entoses le dises que recupere la instalacion anterior y ya .. incluso puedes instalar la ultima vercion de DSM la que te proboco el problema.. y veras que suve todo perfecto. y toda mi data y configuracion estaba ayi. Claro hago esta aclaracion ( cuando desabilites la targeta integrada. asumo que solo usaras la intel que pusiste en tu puerto PCI .!!!!!
    1 point
  2. Buenas, Pues si puedes esperar al miércoles es bastante probable que si la tarjeta INTEL es del tipo E1000 te funcione con solo instalarla. Así te evitas mas quebraderos de cabeza. Un saludo.
    1 point
  3. Hola, pues creo que la primera metedura de pata es no haberse pasado por los post de las nuevas versiones, en las que muchos usuarios advierten que la 6.2 no funciona con tarjetas de red que no sean Intel. (no sé si habrá otros módelos compatibles). Dicho esto, te tocará hacer otro bootloader con la versión anterior y volverla a instalar, en tu NAS.
    1 point
  4. Adding my two cens to this fantastical tuto. Finally I got working all the drives via passthrough. What I did was: ** Enable passthroug in the Cougar Point 6 port SATA AHCI Controller. ** Remember, we have now 3 SATA controllers so, we need to modify the SataPortMap in the grub. In may case, look like this: set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=1F SataPortMap=116 SasIdxMap=0' Basically I've modified: 1.- DiskIdxMap=1F to hide the synoboot drive 2.- SataPortMap=116 to tell the bootloader I have one drive in the first SATA controller, 1 in the second and 6 in the Cougar. And boom, worked flawless, recognice perfectly the volume, It was only needed repair the system partiton, and now I have my 4 SATA drives and 1 SSD for cache. Hope this help somebody. Cheers.
    1 point
  5. Depending on whether you have added a SATA1 controller, the problems and the settings to prevent them will be different. In my setup, the SATA1 controller is recognzied as first, this is why DiskIdxMap=0C mapped my SATA1:0 disk to the first eSata slot, which made the volume unusable for me. Setting DiskIdxMap=09 moved my SATA1:0 disk to the 10th slot, which made it usable again. Since I have SATA0, SATA1 and the Passthrough controller, I used SataPortMap to tell DSM that each of the controller has 4 harddisks, regardless of the real number of drives. I had 114 before, though the result was slot 1,3,4,5 have been the LSI-Harddisks, 2 was SATA0:0 and whatever DiskIdxMap inidicated was SATA1:1. With my setup, I use DiskIdxMap=09 and SataPortMap=444. This settings work without modifiying any of the two synoinfo.conf files Those are not the best feasable settings! DiskIdxMap determins the first disk on a controller and is a two digit hex value, while SataPortMap is a single digit value from 1-9 per controller. I am pretty sure that DiskIdxMap=000C01 SataPortMap=114 would result in SATA1:0 = Slot1, SATA0:0 = Slot13, LSI Slot2-5.
    1 point
×
×
  • Create New...