Search the Community

Showing results for tags 'ssd'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • GERMAN
    • KOREAN

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 9 results

  1. For users who may run HP servers or custom builds with HP SAS SSD drives: a critical firmware bug leads to the dead of the drive if a specific on-time (32,768 hours) has been reached. The drive will become inaccessible and is completely dead. Link to the advisory and patches:
  2. Hello, I am new here. My Settings: Hardware: HP gen8 16GB, Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz, LSI-9211 HBA Exsi 6.7 installed on SSD connected from Motherboard , 4 bay connected through LSI-9211, 4 Bay with 2x8TB, 1x 10TB, 1x12TB, I use miniSAS to sata from motherboard for SSD I added two ned SSD (2x240GB) connected with miniSAS to sata from montherboard System runing 6.2.2 DS3615xs My Questions: When I mount 2 new added SSD to VM, it shows HDD instead of SSD please help, I did a lot of search, but I couldn't get any answer to that. Thanks!!
  3. Интересует совместимость по железу. А именно видит ли ХРЕНЬ m.2 накопители? Интересую и которые работают по SATA шине и PCI-E? Есть ли совместимость с NVMe? Также, как дружит хрень с 1151v2 мамками? Планирую собрать новую хранилку на Asus H310T...
  4. Hello, community! Thank you in advance for your interest I'm new in this environment, I knew a part of the basic knowledge of xpenology. What I have in mind : Build a NAS powerful, more than 2gb/s. 10Gbps and Raid 10 for safety. So, I have thought about 12 IronWolf 4TB. Also, some SSD for cache (I really don't want a slow NAS). My first's questions : Can be possible to use my future NAS xpenology like a DAS too? What MB will I need? (With how many SATA ports? Because I don't really know how PCI controllers are working) Will be awesome if you have some hardware in mind. Thank you for you're helping.
  5. Установил DSM 6.1.1-15101 Update 4. В системе имею один твердотельный диск SSD - 250Гб, и пока один HDD-1,5Тб. Подскажите как правильно создать разделы с учетом применения SSD? Планирую использовать медиасервер и download, ну и хранить файлы.Спасибо!
  6. I have a DSM 6.1.5 running on a LSI 9207-8i controller with 8 Samsung EVO 250gb SATA drives. The raid group is a RAID10. I have also tested with a single disk basic volume as well.I cannot see the tab that allows SSD trim to be enabled. I was running in RAID6 prior, but rebuilt in RAID10. I know the option was not allowed in RAID6, but I know it *used* to be configurable and could be enabled in DSM 5.2. I upgraded from 5.2 to 6.1, so I do not know when it might have broken. Does anyone else have a different experience? What might I be missing? *edit* Forgot to mention I am using the ds3615xs firmware if that matters.
  7. Hi Guys, I've been setting up my XPEnology for the past few weeks and noticed that my write speeds went down horribly after enabling SSD-cache. The transfer starts out at about 1GByte/s (not bit) but goes down all the way to 30MB/s or even lower write speeds, read speeds are fine though. After trying some diffrent settings and also making a RAID 0,1,5 and basic RAID setup the speed still seemed to stay really poor,.. I blamed the network settings at first but noticed my raid5 3 HDD setup manages to keep a steady 500-600MB/s (Bytes not Bits) while transfering from my pc to the XPEnology. Copying a large file from one SSD to another gave me the same poor performance. At the Benchmark in the storage manager the SSD read speed caps out at about 550MB/s but the Write caps out at about 30MB/s. I've tried a different ssd, port, cable and controller so far but nothing seems to help. Booting up Windows and benchmarking the SSD with Crystal Disk Mark gave me about 550/500 Read/Write on both SSDs. I'm using DSM6.1.4-5 on 1.02b with the extra.lmza v4.3 driver package on a SuperMicro a2sdi-h-tf motherboard. I have come across a couple of seemingly similar cases but these were unsolved or different causes (like SMB and networksettings). Does anyone have a tip for me to try out or could give me some advice? Kind regards, Mike
  8. I have Proxmox 5.1. Xpenology 1.02b loader; DSM6.1.4 Update 5. Intel onbard (AHCI) SATA controller passthrough. I have 3 SSD in RAID0 mode. What I notice is, the write performance on SSD is terrible. I've try to tweak Proxmox, and the Xpeno VM, but nothing seems to help. My VM config: args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/100/synoboot_jun2b_virtIO.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot' bios: ovmf boot: 4 cores: 4 hostpci0: 00:17.0,pcie=1 machine: q35 memory: 6144 name: DSM6.x net0: virtio=00:11:32:xxxxxxx,bridge=vmbr0 net1: virtio=00:11:32:xxxxxxx,bridge=vmbr1 numa: 1 ostype: l26 scsihw: virtio-scsi-pci serial0: socket smbios1: uuid=7fda6843-8411-473f-91a5-xxxxxxxxx sockets: 1 I've tried to passthrough the VM without q35 machine type, and without PCE=1. Write performance is the same. What's strange is, the write performance was really good back in October, when I was still on Proxmox 5.0. So I want to ask everyone, how's your SATA passthrough performance?
  9. Bonjour, Dans le passé j'avais suivi le tuto ( pour monter un proliant HP 54L. Je souhaite réaliser les améliorations suivantes à mon Proliant HP54L : 1) ajouter 2 HDD red 3To acheté depuis juillet ! 2) changer l'ordre des disques afin que le SSD de 120Go où il y a le DISKSTATION et les VM soit au niveau de l'emplacement du CD-ROM 3) ajouter une carte Ethernet TP-LINK TG-3468 pour augmenter le débit. Je suis sous Exsi 5.5 4) mettre à jour Xpenology pour une version 6.2 ou supérieure (si c'est possible) 5) migrer vers Exsi 6 6) mettre en place une copie entre mon 54L et mon DS213air qui a deux disques de 3To Red de manière à sauvegarder les données clefs. Je suis pour l'instant à l'étape 1. J'ai ajouté les 2 HDD de 3To dont un dans l'espace CD-ROM. Ce dernier est relié à la carte mère avec un cable SATA (il est en version 3 mais je ne sais pas si cela a une importance ?). Je suis passé par les étapes 5 et 6 du tuto mentionné ci-dessus et au moment de mettre en marche le DISKSATATION j'ai l'erreur suivante : "Cannot open the disk '/vmfs/volumes/540548fa-3fda98c2-c6a1-9cb654046298/DISKSTATION/WDC_WD30EFRX2D68EUZN0.vmdk' or one of the snapshot disks it depends on." L'erreur provient du disque placé dans l'emplacement CD-ROM. Questions : - comment résoudre ce problème ? - est-ce lié au fait qu'il soit relié à la carte mère avec un cable SATA ? - est-il possible de supprimer les .vmd dans cd /vmfs/volumes/120Go-DATABASE/DISKSTATION afin de recommencer l'étape 5 ? - est-il possible de changer les disques d'emplacement pour mettre le SSD qui ne chauffe pas dans l'emplacement du CD-ROM mais dans ce cas que dois-je faire ? Faut il refaire des configs en SSH ? - est-il possible de renommer les vmdk des disques pour avoir des noms plus parlant : SerialNumber_rack_n (n = emplacement du disque dans le serveur) ? Sans pour autant tout refaie et SURTOUT sans perdre les données ! les disques sont pour l'instant localisé ainsi : IDE (0:0) Hard disk 1 - [120Go-DATABASE] DISKSTATION/XPEnoboot_DS3615xs_5.1-5022.3.vmdk - dans le Rack 1 SCSI (O:1) Hard disk 2 - [120Go-DATABASE] DISKSTATION/WDC_WD2DWMC4N1163018_3T.vmdk - dans le Rack 2 SCSI (O:2) Hard disk 3 - [120Go-DATABASE] DISKSTATION/WDC_WD2DWMC4N2305136_3T.vmdk - dans le Rack 3 SCSI (O:3) Hard disk 4 - [120Go-DATABASE] DISKSTATION/WDC_WD30EFRX2D68EUZN0_3To.vmdk - dans le Rack 4 SCSI (O:4) Hard disk 5 - [120Go-DATABASE] DISKSTATION/WDC_WD30EFRX2D68EUZN0.vmdk --> ce dernier est dans l'espace CD-ROM --> c'est ce dernier qui génère l'erreur mentionné "Cannot open the disk '/vmfs/volumes/540548fa-3fda98c2-c6a1-9cb654046298/DISKSTATION/WDC_WD30EFRX2D68EUZN0.vmdk' or one of the snapshot disks it depends on." quand je souhaite démarrer DISKSTATION J'ai posté sur le forum fibaro des questions mais je ne suis pas certain qu'il y est beaucoup de monde comme par le passé. Donc je poste sur ce forum en espérant avoir de l'aide afin de redémarrer mon serveur.