Jump to content
XPEnology Community

Xpenology 24 Drive Capability and Synology Hybrid Raid?


Recommended Posts

Hi All,


As the title suggests, I wish to build and Xpenology box with a maximum available 24 drives, but also want to utilize the Synology Hybrid Raid option, so that I don't have to use the same amount of same sized disks etc.


This will be being used for offsite backup and wont contain any live data.


Is the above possible ? If so, could someone point in the direction of the latest version which will give me 24 drive capability and SHR ?


Many thanks in advance.

Link to comment
Share on other sites

synology has disabled that option in the newer 6.1 version but everything is still there, you just have to set 2 options in the config file and reboot to reenable it

just search in the 6.0.2 thead




btw. the default is just 12 drives you also have to tweak the config to 24 drives too

there is a nice video if you dont like the "dry" stuff here as text

Link to comment
Share on other sites

  • 3 weeks later...

Sorry to bring back the thread ! I managed to edit the config and able to add up to 24 drives ...


But when I am starting to configure, the first drive being added is classed as disk 7 ? Then the next disk inserted is 8,9,10 etc ...


Why has it not started at Disk 1 ? Ideally I need them all in order, so in one disk fails I know which to replace.


Hope I have explained that correctly.



Link to comment
Share on other sites

the first drive being added is classed as disk 7 ? Then the next disk inserted is 8,9,10 etc ...


Why has it not started at Disk 1 ? Ideally I need them all in order, so in one disk fails I know which to replace.


This happens because a lot of SATA/SAS controllers has virtual ports which normally does not see in Windows.

Usually you cannot do anything with discs numbering.


To check your hardware you can use dmesg.

ssh to your box and run:

dmesg > /volume1/media/dmesg.txt

better to open in Notepad++

[    2.026536] mpt2sas0: 32 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (2006212 kB)
[    2.026574] mpt2sas 0000:02:00.0: irq 43 for MSI/MSI-X
[    2.026580] mpt2sas 0000:02:00.0: irq 44 for MSI/MSI-X
[    2.026622] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 43
[    2.026623] mpt2sas0-msix1: PCI-MSI-X enabled: IRQ 44
[    2.026625] mpt2sas0: iomem(0x00000000dfff0000), mapped(0xffffc90000020000), size(65536)
[    2.026627] mpt2sas0: ioport(0x000000000000e800), size(256)
[    2.099015] mpt2sas0: sending message unit reset !!
[    2.101012] mpt2sas0: message unit reset: SUCCESS
[    2.194919] mpt2sas0: Allocated physical memory: size(14932 kB)
[    2.194923] mpt2sas0: Current Controller Queue Depth(9979), Max Controller Queue Depth(10240)
[    2.194924] mpt2sas0: Scatter Gather Elements per IO(128)
[    2.255396] mpt2sas0: LSISAS2308: FWVersion(, ChipRevision(0x05), BiosVersion(
[    2.255399] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[    2.255461] mpt2sas0: sending port enable !!
[    2.265307] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b005a6c4f8), phys(8)
[    2.277016] mpt2sas0: port enable: SUCCESS
[    2.279804] scsi 0:0:0:0: Direct-Access     ATA      ST1000DM003-1ER162       HP51 PQ: 0 ANSI: 6
[    2.279817] scsi 0:0:0:0: SATA: handle(0x0010), sas_addr(0x4433221107000000), phy(7), device_name(0x5000c5007b60758c)
[    2.279819] scsi 0:0:0:0: SATA: enclosure_logical_id(0x500605b005a6c4f8), slot(4)
[    2.279904] scsi 0:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.279908] scsi 0:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.293838] scsi 0:0:1:0: Direct-Access     ATA      ST8000AS0002-1NA17Z      AR17 PQ: 0 ANSI: 6
[    2.293849] scsi 0:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x5000c5009289c3f3)
[    2.293851] scsi 0:0:1:0: SATA: enclosure_logical_id(0x500605b005a6c4f8), slot(3)
[    2.293958] scsi 0:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    4.678105] sata_nv 0000:00:08.0: setting latency timer to 64
[    4.683374] scsi1 : sata_nv
[    4.688814] scsi2 : sata_nv
[    4.691303] ata1: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xb880 irq 20
[    4.691309] ata2: SATA max UDMA/133 cmd 0xc000 ctl 0xbc00 bmdma 0xb888 irq 20


To check which drive you should replace in case of failure you can use serial number.

You can find it it StorageManager and then on drive.



Usefull links:

https://hedichaibi.com/fix-xpenology-pr ... rd-drives/


Link to comment
Share on other sites

with my setup, with onboard sata and marvell based sas/sata add on controllers, I found the onboard to be drives 1-4 then depending on the pci slots and sas ports, 5-20, but with some weird things like ports 0-3 on controller1 would be drives 9-12 in DSM. Not always 'logical' so I ended up labelling sata leads for the hdd number as defined by DSM rather than the 'logic' of the pci/controller enumeration, plus put large labels with the last 4 characters of the drive serial number stuck on the drive itself, as a cross check to the storage manager hdd screen :smile:

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...