Discussion on LSI Array Cards of DSM7.0+


Recommended Posts

Hello everyone, there have been too many discussions about the LSI array card of DSM7.0, in various posts on github, xpenology forums, but so far, there is no clear solution. The problems that everyone focuses on appear in the following points:
1. After adding the mpt2sas/mpt3sas driver, the array card cannot be recognized
2. The array card can be correctly identified, but the smart information of the hard disk cannot be obtained

These two questions have troubled me for a long time, and I have made a lot of attempts, so I thought of publishing some results and experiences of my attempts for your reference.

  1. Regarding question 1:

There are many types and versions of LSI array cards, and the key to whether mpt2sas/mpt3sas can identify the driver is whether the driver has the Vendor ID and Device ID of the corresponding card.

So first we need to use

 lspci -nn | grep LSI

On my machine, I get results like the following:

01:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0087] (rev 05)

Next, we can check whether the driver contains this id, and we can execute modinfo mpt3sas.ko on any machine (the driver is from pocopico's github repository
rp-ext) results are as follows:

filename:       /root/test/mpt3sas.ko
alias:          mpt2sas
version:        22.00.00.00
license:        GPL
description:    LSI MPT Fusion SAS 3.0 & SAS 3.5 Device Driver
author:         Avago Technologies <MPT-FusionLinux.pdl@avagotech.com>
srcversion:     80624A1362CD953ED59AF65
alias:          pci:v00001000d000000D2sv*sd*bc*sc*i*
alias:          pci:v00001000d000000D1sv*sd*bc*sc*i*
alias:          pci:v00001000d000000D0sv*sd*bc*sc*i*
alias:          pci:v00001000d000000ACsv*sd*bc*sc*i*
alias:          pci:v00001000d000000ABsv*sd*bc*sc*i*
alias:          pci:v00001000d000000AAsv*sd*bc*sc*i*
alias:          pci:v00001000d000000AFsv*sd*bc*sc*i*
alias:          pci:v00001000d000000AEsv*sd*bc*sc*i*
alias:          pci:v00001000d000000ADsv*sd*bc*sc*i*
alias:          pci:v00001000d000000C3sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C2sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C1sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C0sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C8sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C7sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C6sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C5sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C4sv*sd*bc*sc*i*
alias:          pci:v00001000d000000C9sv*sd*bc*sc*i*
alias:          pci:v00001000d00000095sv*sd*bc*sc*i*
alias:          pci:v00001000d00000094sv*sd*bc*sc*i*
alias:          pci:v00001000d00000091sv*sd*bc*sc*i*
alias:          pci:v00001000d00000090sv*sd*bc*sc*i*
alias:          pci:v00001000d00000097sv*sd*bc*sc*i*
alias:          pci:v00001000d00000096sv*sd*bc*sc*i*
alias:          pci:v00001000d0000007Esv*sd*bc*sc*i*
alias:          pci:v00001000d000002B0sv*sd*bc*sc*i*
alias:          pci:v00001000d0000006Esv*sd*bc*sc*i*
alias:          pci:v00001000d00000087sv*sd*bc*sc*i*
alias:          pci:v00001000d00000086sv*sd*bc*sc*i*
alias:          pci:v00001000d00000085sv*sd*bc*sc*i*
alias:          pci:v00001000d00000084sv*sd*bc*sc*i*
alias:          pci:v00001000d00000083sv*sd*bc*sc*i*
alias:          pci:v00001000d00000082sv*sd*bc*sc*i*
alias:          pci:v00001000d00000081sv*sd*bc*sc*i*
alias:          pci:v00001000d00000080sv*sd*bc*sc*i*
alias:          pci:v00001000d00000065sv*sd*bc*sc*i*
alias:          pci:v00001000d00000064sv*sd*bc*sc*i*
alias:          pci:v00001000d00000077sv*sd*bc*sc*i*
alias:          pci:v00001000d00000076sv*sd*bc*sc*i*
alias:          pci:v00001000d00000074sv*sd*bc*sc*i*
alias:          pci:v00001000d00000072sv*sd*bc*sc*i*
alias:          pci:v00001000d00000070sv*sd*bc*sc*i*
depends:        
retpoline:      Y
vermagic:       4.4.180+ SMP mod_unload 
parm:           logging_level: bits for enabling additional logging info (default=0)
parm:           sdev_queue_depth: globally setting SAS device queue depth 
parm:           max_sectors:max sectors, range 64 to 32767  default=32767 (ushort)
parm:           command_retry_count: Device discovery TUR command retry count: (default=144) (int)
parm:           missing_delay: device missing delay , io missing delay (array of int)
parm:           host_lock_mode:Enable SCSI host lock if set to 1(default=0) (int)
parm:           max_lun: max lun, default=16895  (int)
parm:           hbas_to_enumerate: 0 - enumerates all SAS 2.0, SAS3.0 & above generation HBAs
                  1 - enumerates only SAS 2.0 generation HBAs
                  2 - enumerates SAS 3.0 & above generation HBAs (default=-1, Enumerates all SAS 2.0, SAS 3.0 & above generation HBAs else SAS 3.0 & above generation HBAs only) (int)
parm:           mpt3sas_multipath: enabling mulipath support for target resets (default=0) (int)
parm:           multipath_on_hba: Multipath support to add same target device
                as many times as it is visible to HBA from various paths
                (by default: 
                        SAS 2.0,SAS 3.0 HBA & SAS3.5 HBA-This will be disabled) (int)
parm:           disable_eedp: disable EEDP support: (default=0) (uint)
parm:           diag_buffer_enable: post diag buffers (TRACE=1/SNAPSHOT=2/EXTENDED=4/default=0) (int)
parm:           disable_discovery: disable discovery  (int)
parm:           allow_drive_spindown: allow host driver to issue START STOP UNIT(STOP) command to spindown the drive before shut down or driver unload, default=1, 
                Dont spindown any SATA drives =0 /      Spindown SSD but not HDD = 1/   Spindown HDD but not SSD =2/  Spindown all SATA drives =3 (uint)
parm:           prot_mask: host protection capabilities mask, def=0x7f (int)
parm:           protection_guard_mask: host protection algorithm mask, def=3  (int)
parm:           issue_scsi_cmd_to_bringup_drive: allow host driver to issue SCSI commands to bring the drive to READY state, default=1  (int)
parm:           sata_smart_polling: poll for smart errors on SATA drives: (default=0) (uint)
parm:           max_queue_depth: max controller queue depth  (int)
parm:           max_sgl_entries: max sg entries  (int)
parm:           msix_disable: disable msix routed interrupts (default=0) (int)
parm:           smp_affinity_enable:SMP affinity feature enable/disbale Default: enable(1) (int)
parm:           max_msix_vectors: max msix vectors (int)
parm:           mpt3sas_fwfault_debug: enable detection of firmware fault and halt firmware - (default=0)

I can find my corresponding id in this line,
alias: pci:v00001000d00000087sv*sd*bc*sc*i*
Where v00001000 corresponds to Vendor ID 1000
d00000087 corresponds to Device ID 0087.

So you can also use the same method to check whether the driver supports your LSI adapter.

 

  1.  
  2. Regarding question 2:

Because the situation is more complicated, I made a table to show the results of my test.

 

DSM model DSM version drivers souce drivers version LSI card1 model

smart infomation

result

LSI card2 model 

smart infomation

result

 

DS918+

7.0.1-42218 pocopico/rp-ext/mpt3sas 22.00.00.00 LSI SAS2308<LSI 9207-8i><1000:0087> no smart information  LSI SAS3416<LSI 9400-16i><1000:00ac> OK
 

DS918+

7.0.1-42218 broadcom latest drivers for LSI 9207-8i 20.00.04.00 LSI SAS2308<LSI 9207-8i><1000:0087> no smart information  LSI SAS3416<LSI 9400-16i><1000:00ac> NO  PCI ID
 

DS918+

7.0.1-42218 broadcom latest drivers forLSI SAS3416 40.00.00.00 LSI SAS2308<LSI 9207-8i><1000:0087> no smart information  LSI SAS3416<LSI 9400-16i><1000:00ac> OK

I also tried ig-88's suggestion, using the mpt3sas driver from broadwell's 7.0-41890 GPL source to try to compile the driver for the 918+, but got the following error.

 

make: Entering directory '/home/dog/dog/nas/toolkit/build_env/ds.apollolake-7.0/usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-7.0/build'
  CC [M]  /home/dog/dog/nas/sourcecode/broadwell/linux-4.4.x/drivers/scsi/mpt3sas/mpt3sas_scsih.o
/home/dog/dog/nas/sourcecode/broadwell/linux-4.4.x/drivers/scsi/mpt3sas/mpt3sas_scsih.c: In function ‘_scsih_probe’:
/home/dog/dog/nas/sourcecode/broadwell/linux-4.4.x/drivers/scsi/mpt3sas/mpt3sas_scsih.c:8790:14: error: ‘struct scsi_host_template’ has no member named ‘syno_set_sashost_disk_led’
  shost->hostt->syno_set_sashost_disk_led = syno_scsih_lsi3008_set_led;
              ^~
scripts/Makefile.build:277: recipe for target '/home/dog/dog/nas/sourcecode/broadwell/linux-4.4.x/drivers/scsi/mpt3sas/mpt3sas_scsih.o' failed
make[1]: *** [/home/dog/dog/nas/sourcecode/broadwell/linux-4.4.x/drivers/scsi/mpt3sas/mpt3sas_scsih.o] Error 1
Makefile:1445: recipe for target '_module_/home/dog/dog/nas/sourcecode/broadwell/linux-4.4.x/drivers/scsi/mpt3sas' failed
make: *** [_module_/home/dog/dog/nas/sourcecode/broadwell/linux-4.4.x/drivers/scsi/mpt3sas] Error 2
make: Leaving directory '/home/dog/dog/nas/toolkit/build_env/ds.apollolake-7.0/usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/sys-root/usr/lib/modules/DSM-7.0/build'

 

  • Like 1
Link to post
Share on other sites

Just a reminder that if you have a card (or any HBA) that does not work with DSM, but is supported by your hypervisor - disk-based passthrough may be possible.  On ESXi, this is via Raw Device Mapping (RDM).

Link to post
Share on other sites
14 hours ago, yanjun said:

I also tried ig-88's suggestion, using the mpt3sas driver from broadwell's 7.0-41890 GPL source to try to compile the driver for the 918+

my intention was using the binary drivers from 7.0.1 3617 for 918+ (including scsi_tramsport_sas.ko and raid_class.ko) as the are now from the same kernel version

the mpt3sas driver in 3617 is newer the then the one in the kernel synology uses for both (but the don't provide any source for that newer driver, my guess is that the driver is modded like the kernel)

 

 

Link to post
Share on other sites
  • 2 weeks later...

DELL H310 RAID CARD(passthrough it mode)

01:00.0 RAID bus controller [0104]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)

I can find my corresponding id in the pocopico/mpt2sas&mpt3sas,but the HBA card can not be drivered.

 

Snipaste2.thumb.jpg.3eb654e484eb824b3091a4865d19218a.jpg

 

Edited by Derrik
Link to post
Share on other sites
5 hours ago, Derrik said:

DELL H310 RAID CARD(passthrough it mode)

01:00.0 RAID bus controller [0104]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)

I can find my corresponding id in the pocopico/mpt2sas&mpt3sas,but the HBA card can not be drivered.

 

Snipaste2.thumb.jpg.3eb654e484eb824b3091a4865d19218a.jpg

 

 

According to :  https://linux-hardware.org/?id=pci:1000-0072-1000-30b0  for 918+ you should use MPT3SAS which has an alias for MPT2SAS.

 

On kernel version 4.4+ the drivers for MPT2 and MPT3 have been merged into a single module. For kernels < 4.3 the sources provide MPT2 and MPT3 as a separate module and thats the main reason that MPT2SAS extension exists. 

 

The modules for 918+ have been compiled and are available on my GH repo. You can try to test once you have a DSM system installed.

 

Link to post
Share on other sites

I had issues on this as well. When i checked my system on TC i could see the mtp3sas finding my card (LSI 2008 in admin mode)

 

Found SAS Controller : pciid 1000d00000072  Required Extension : mpt3sas
Searching for matching extension for mpt3sas
Found matching extension : 
"https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json"
[#] Checking runtime for required tools... [OK]

 

Once i rebooted the system i was presented with a screen "Unable to find any hard drives" or something to that effect.

 

I put a request on the TC git page and got a really great person help me out with the following comment.

 

For LSI SAS2008 cards, depending on the actual model, you might need mpt2sas (MPT Fusion SAS 2.0)
or a specific megaraid extension. I'm not 100% sure about this, but the mpt3sas extension should 
work with MPT Fusion SAS 3.0 cards (like a LSI SAS3008 card). I don't know why it defaults to it.

sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json

 

SO once i booted back into TC i ran the above addition and hey presto,rebooted and i had a working system again and data preserved too which is always nide to see.

 

Just thought i would put this out in case anyone else has the same issue of mpt3sas trying to be the big boss and not working.

 

 

  • Like 1
Link to post
Share on other sites
22 hours ago, eXcalibre said:

I had issues on this as well. When i checked my system on TC i could see the mtp3sas finding my card (LSI 2008 in admin mode)

 


Found SAS Controller : pciid 1000d00000072  Required Extension : mpt3sas
Searching for matching extension for mpt3sas
Found matching extension : 
"https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json"
[#] Checking runtime for required tools... [OK]

 

Once i rebooted the system i was presented with a screen "Unable to find any hard drives" or something to that effect.

 

I put a request on the TC git page and got a really great person help me out with the following comment.

 


For LSI SAS2008 cards, depending on the actual model, you might need mpt2sas (MPT Fusion SAS 2.0)
or a specific megaraid extension. I'm not 100% sure about this, but the mpt3sas extension should 
work with MPT Fusion SAS 3.0 cards (like a LSI SAS3008 card). I don't know why it defaults to it.

sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json

 

SO once i booted back into TC i ran the above addition and hey presto,rebooted and i had a working system again and data preserved too which is always nide to see.

 

Just thought i would put this out in case anyone else has the same issue of mpt3sas trying to be the big boss and not working.

 

 

 

"./rploader.sh ext bromolow-7.0.1-42218 add"

 

to understand this it need to looked into kernel versions

the above from @pocopico was for 918+, thats coming with kernel 4.4 and in that kernel the kernel-dev's merged mpt2sas and mpt3sas, so there is usually only mpt3sas (there is a option in the kernel for backward compatibility that will create a mpt2sas, but thats optional)

 

config SCSI_MPT2SAS
    tristate "Legacy MPT2SAS config option"
    default n
    select SCSI_MPT3SAS
    depends on PCI && SCSI
    ---help---
    Dummy config option for backwards compatiblity: configure the MPT3SAS
    driver instead.

 

it the same kernel 4.4 for 6.2.4 and 7.0 (just a higher number because of fixes by kernel.org,  more or less no new/better drivers)

when it comes to 3615/17 it gets more complicated (as we need separate 6.2.4 and 7.0)

3615 is kernel 3.10 on 6.2.4 and 7.0 but 3617 its 3.10 on 6.2.4 and 4.4 on 7.0

also interesting to know is that synology adds newer mpt3sas drivers into 3617 (without providing the source)

 

for 918+ that does not have native sas support its in addition, because of the changes synology made  in the source the modules created from synologys kernel where not able to detect smart values or serial number but where stable when running with hdd power down feature where jun's modules for sas support  (from non synology vanilla source?) where showing these (important) values but might loose data and destroy raids when used with hdd power down (i was able to reproduce that and documented it in the extra drivers for 6.2.3)

 

not sure how @pocopico wants to handle that mpt2/mpt3 stuff, either differ between kernel 4.4 systems and only use mpt3 sas there and mpt2/mpt3 on 3.10 systems or make all systems have mpt2/mpt3 by compiling the optional mpt2 for kernel 4.4

synology does not use the mpt2 option with kernle 4.4, 3617 with kernel 3.10 has mpt2 (v20.00.00.00) and mpt3 (v22.00.02.00) and in 7.0 with kernel 4.4 there is only mpt3 (v22.00.02.00 - SAS 2.0,SAS 3.0 HBA & SAS3.5) - infos here where used from synologys binary kernel modules in the *pat files

my suggestion would be keeping with the defaults and differ in the extension code between kernels and if mpt2 has to be used

 

info in vanilla 4.4.180 kernel from mpt3 driver (mpt3sas_base.h), its the same in syno's kernel so they use a newer mpt3sas compared to the kernel 4.4.180 (syno's mpt3sas.ko mentions SAS 3.5, thats not in the original kernel driver)

/* driver versioning info */
#define MPT3SAS_DRIVER_NAME        "mpt3sas"
#define MPT3SAS_AUTHOR "Avago Technologies <MPT-FusionLinux.pdl@avagotech.com>"
#define MPT3SAS_DESCRIPTION    "LSI MPT Fusion SAS 3.0 Device Driver"
#define MPT3SAS_DRIVER_VERSION        "09.102.00.00"
#define MPT3SAS_MAJOR_VERSION        9
#define MPT3SAS_MINOR_VERSION        102
#define MPT3SAS_BUILD_VERSION        0
#define MPT3SAS_RELEASE_VERSION    00

#define MPT2SAS_DRIVER_NAME        "mpt2sas"
#define MPT2SAS_DESCRIPTION    "LSI MPT Fusion SAS 2.0 Device Driver"
#define MPT2SAS_DRIVER_VERSION        "20.102.00.00"
#define MPT2SAS_MAJOR_VERSION        20
#define MPT2SAS_MINOR_VERSION        102
#define MPT2SAS_BUILD_VERSION        0
#define MPT2SAS_RELEASE_VERSION    00

 

i guess i will do some experiments with 918+, newer mpt3sas drivers and scsi_transport_sas support, the 918+ vm for compiling 7.0 is already up and delivers *.ko files and as tinycore does drivers in general, there is more time for specials (like better sas support in 918+ or general nvidia gpu support for use in jellyfin, ebi and plex)

Link to post
Share on other sites

I am using the same card , Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0087] . Currently with 6.2.3 . 

it uses mpt2sas . 

 

I thought this driver was part of the standard 3615xs source . 

 

When I auto build with redpill loader It adds mpt3sas . I guess I need to override this and remove it ? I'm not sure if I then need to manually add mpt2sas ?

 

 

Any advise please ?

 

 

(Box is a Microsever Gen8 )  

Link to post
Share on other sites

 

39 minutes ago, scoobdriver said:

I thought this driver was part of the standard 3615xs source . 

 

When I auto build with redpill loader It adds mpt3sas . I guess I need to override this and remove it ? I'm not sure if I then need to manually add mpt2sas ?

 

 

Any advise please ?

 

3615 = bromolow

so the advice @eXcalibre gave above should help you

its adding a extension in tinycore manually, in this case the one for mpt2sas (driver)

 

On 2/12/2022 at 12:52 PM, eXcalibre said:

I put a request on the TC git page and got a really great person help me out with the following comment.

 


For LSI SAS2008 cards, depending on the actual model, you might need mpt2sas (MPT Fusion SAS 2.0)
or a specific megaraid extension. I'm not 100% sure about this, but the mpt3sas extension should 
work with MPT Fusion SAS 3.0 cards (like a LSI SAS3008 card). I don't know why it defaults to it.

sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json

 

SO once i booted back into TC i ran the above addition and hey presto,rebooted and i had a working system again and data preserved too which is always nide to see.

 

  • Like 1
Link to post
Share on other sites

For what it worth I did add mpt3sas ans mpt2sas on my ESXi install on a HP Gen8 (ds3615xs)

But as already identified, disks size are broken.

I have 4x4To disks, and they are only shown as 2To each. So even if disks are detected I would not consider LSI card passthrough as safe.

 

 

Edited by Orphée
Link to post
Share on other sites
On 2/13/2022 at 6:21 AM, IG-88 said:

 

 

 

to understand this it need to looked into kernel versions

the above from @pocopico was for 918+, thats coming with kernel 4.4 and in that kernel the kernel-dev's merged mpt2sas and mpt3sas, so there is usually only mpt3sas (there is a option in the kernel for backward compatibility that will create a mpt2sas, but thats optional)

 

 

 

 

Is this why I can't get DS3617 to work with my LSI SAS2308 HBA (flashed DELL H710 mini) while DS3615 works just fine if I manually add the mpt2sas extension?

 

If I understand it correctly, for DS3617 with kernel 4.4, the correct driver is mpt3sas but it needs to have the backward compatibility option and the one available now doesn't have it turned on?

Link to post
Share on other sites
40 minutes ago, turbo21psi said:

but it needs to have the backward compatibility option and the one available now doesn't have it turned on?

no if you activate that option you get a mpt2sas and a mpt3sas, usually just the unifies mpt3sas should be ok

my extra.lzma for 918+ also comes with just the mpt3sas and works fine with all older sas2 contollers

Link to post
Share on other sites

Hi,

So my test confirmed latest mpt3sas drivers built by @yanjun works on ESXi (HP gen8)

but I still can't figure why no matter how you configure SataPortMap etc... the first LSI disk always appears as sdb.

No matter what, it seems the sda is "reserved" (by loader) ?

 

In ESXi I set :

- Sata controller 0

- Loader on SATA 0:0

LSI passthrough (so should be detected as Sata controller 1 I guess)

 

SataPortMap : 18

DiskIdxMap : 1000

 

Any idea ?

Link to post
Share on other sites
10 hours ago, Orphée said:

Hi,

So my test confirmed latest mpt3sas drivers built by @yanjun works on ESXi (HP gen8)

 

 
Thanks for pointing out the new mpt3sas driver build, I completely missed that posts by yanjun. Just to make sure, you mean these : https://raw.githubusercontent.com/dogodefi/mpt3sas/offical/rpext-index.json ?
I've got a LSI SAS2008 and SAS3008 which haven't been working and would like to try these drivers if they helped in your case.

And just out of curiosity : is the fact that your first disk appears as sdb a purely cosmetic problem or does it produce some kind of issues to storage management?
 

Edited by Byolock
Link to post
Share on other sites
 
Thanks for pointing out the new mpt3sas driver build, I completely missed that posts by yanjun. Just to make sure, you mean these : https://raw.githubusercontent.com/dogodefi/mpt3sas/offical/rpext-index.json ?
I've got a LSI SAS2008 and SAS3008 which haven't been working and would like to try these drivers if they helped in your case.

And just out of curiosity : is the fact that your first disk appears as sdb a purely cosmetic problem or does it produce some kind of issues to storage management?
 
@pocopico updated default repo so you don't have to worry anymore.

For MY conf, with only 4 disks, it seems to be totally cosmetic. But I can't confirm for more disks like 8+
Link to post
Share on other sites
  • 1 month later...
On 2/22/2022 at 3:03 PM, Byolock said:

 
Thanks for pointing out the new mpt3sas driver build, I completely missed that posts by yanjun. Just to make sure, you mean these : https://raw.githubusercontent.com/dogodefi/mpt3sas/offical/rpext-index.json ?
I've got a LSI SAS2008 and SAS3008 which haven't been working and would like to try these drivers if they helped in your case.

And just out of curiosity : is the fact that your first disk appears as sdb a purely cosmetic problem or does it produce some kind of issues to storage management?
 

Did you get yours to work? I've been using megaraid_sas for mine.

Link to post
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.

Guest
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.