Diverge Posted May 16, 2014 Share #1 Posted May 16, 2014 Any experts out there know why this would be happening? [ 0.946148] mpt2sas version 13.100.00.00 loaded [ 0.946272] scsi0 : Fusion MPT SAS Host [ 0.947094] mpt2sas 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 0.947167] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6118604 kB) [ 0.947583] mpt2sas 0000:03:00.0: irq 72 for MSI/MSI-X [ 0.947806] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 72 [ 0.947808] mpt2sas0: iomem(0x00000000fd4fc000), mapped(0xffffc900080f0000), size(16384) [ 0.947810] mpt2sas0: ioport(0x0000000000004000), size(256) [ 1.072962] mpt2sas0: Allocated physical memory: size(7418 kB) [ 1.072964] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 1.072965] mpt2sas0: Scatter Gather Elements per IO(128) [ 1.132059] mpt2sas0: LSISAS2008: FWVersion(18.00.00.00), ChipRevision(0x03), BiosVersion(07.35.00.00) [ 1.132062] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 1.132138] mpt2sas0: sending port enable !! [ 1.136060] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b004f0ff80), phys(8) [ 1.143506] mpt2sas0: port enable: SUCCESS [ 1.145393] scsi 0:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A80 PQ: 0 ANSI: 6 [ 1.145397] scsi 0:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x50014ee003bb2b5f) [ 1.145399] scsi 0:0:0:0: SATA: enclosure_logical_id(0x500605b004f0ff80), slot(0) [ 1.145493] scsi 0:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 1.145496] scsi 0:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 1.145605] syno_disk_type_get: disk driver 'Fusion MPT SAS Host' [ 1.145607] syno_disk_type_get: Got UNKNOWN port type 3 [ 1.145611] sd_probe: Got UNKNOWN disk sda with index 0 [ 1.146047] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 1.146145] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 1.146147] sd 0:0:0:0: [sda] 4096-byte physical blocks --------------------------------------------------------------------- [ 1.619124] mpt2sas version 13.100.00.00 unloading [ 1.620886] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 1.620908] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00 [ 1.623997] mpt2sas0: removing handle(0x000c), sas_addr(0x4433221103000000) [ 1.628784] sd 0:0:1:0: [sdb] Synchronizing SCSI cache [ 1.628803] sd 0:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 [ 1.632105] mpt2sas0: removing handle(0x0009), sas_addr(0x4433221100000000) [ 1.637083] sd 0:0:2:0: [sdc] Synchronizing SCSI cache [ 1.637101] sd 0:0:2:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00 [ 1.639341] mpt2sas0: removing handle(0x000b), sas_addr(0x4433221101000000) [ 1.644550] sd 0:0:3:0: [sdd] Synchronizing SCSI cache [ 1.644568] sd 0:0:3:0: [sdd] Result: hostbyte=0x01 driverbyte=0x00 [ 1.647608] mpt2sas0: removing handle(0x000a), sas_addr(0x4433221102000000) [ 1.651126] mpt2sas0: sending message unit reset !! [ 1.652819] mpt2sas0: message unit reset: SUCCESS [ 1.653146] mpt2sas 0000:03:00.0: PCI INT A disabled --------------------------------------------------------------------- [ 1.806736] mpt2sas version 13.100.00.00 loaded [ 1.806840] scsi1 : Fusion MPT SAS Host [ 1.807685] mpt2sas 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1.807755] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6118604 kB) [ 1.808185] mpt2sas 0000:03:00.0: irq 72 for MSI/MSI-X [ 1.808368] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 72 [ 1.808370] mpt2sas0: iomem(0x00000000fd4fc000), mapped(0xffffc90008090000), size(16384) [ 1.808371] mpt2sas0: ioport(0x0000000000004000), size(256) [ 1.923993] mpt2sas0: Allocated physical memory: size(7418 kB) [ 1.923995] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 1.923996] mpt2sas0: Scatter Gather Elements per IO(128) [ 1.982958] mpt2sas0: LSISAS2008: FWVersion(18.00.00.00), ChipRevision(0x03), BiosVersion(07.35.00.00) [ 1.982961] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 1.983037] mpt2sas0: sending port enable !! [ 1.986919] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b004f0ff80), phys(8) [ 1.993404] mpt2sas0: port enable: SUCCESS [ 1.995399] scsi 1:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A80 PQ: 0 ANSI: 6 [ 1.995403] scsi 1:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x50014ee003bb2b5f) [ 1.995405] scsi 1:0:0:0: SATA: enclosure_logical_id(0x500605b004f0ff80), slot(0) [ 1.995523] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 1.995528] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 1.995698] syno_disk_type_get: disk driver 'Fusion MPT SAS Host' [ 1.995700] syno_disk_type_get: Got UNKNOWN port type 3 [ 1.995703] sd_probe: Got UNKNOWN disk sdb with index 1 [ 1.996024] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 1.996213] sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 1.996215] sd 1:0:0:0: [sdb] 4096-byte physical blocks basically on boot, mpt2sas loads, finds all drives on scsi0, sets them up as sda, sdb, sdc, sdd. Then further into boot, it unloads/reloads driver, resets the card, finds all the drives on scsi1 (not 0 this time), and sets them up starting at sdb, instead of sda. I'm testing LSI controller support for nanoboot. So any help from experts would be appreciated Link to comment Share on other sites More sharing options...
Moogs Posted May 17, 2014 Share #2 Posted May 17, 2014 I think I saw the same behavior in GnoBoot. I never looked at the logs but the first drive is not the first one in the order. This happens on two identical machines with the exact same disk load pattern. Not sure why but never sweated it. This is with a flashed 9211 LSI 8i card. Link to comment Share on other sites More sharing options...
Diverge Posted May 17, 2014 Author Share #3 Posted May 17, 2014 Yeah, I found someone else that had the same issue with gnoboot. gnoboot 10.4 works fine for me. I suspect 10.5 has this bug. Nanoboot was able to fix it, so expect a release with it working soon (my guess). Link to comment Share on other sites More sharing options...
Trantor Posted May 17, 2014 Share #4 Posted May 17, 2014 [ 0.946148] mpt2sas version 13.100.00.00 loaded Maybe a newer version will solve this ? (latest is v18) Link to comment Share on other sites More sharing options...
Diverge Posted May 17, 2014 Author Share #5 Posted May 17, 2014 [ 0.946148] mpt2sas version 13.100.00.00 loaded Maybe a newer version will solve this ? (latest is v18) There's actually a newer version (v19). I'm not sure why newer ones aren't used, but it was fixed using same old one (13.1). Link to comment Share on other sites More sharing options...
Trantor Posted May 17, 2014 Share #6 Posted May 17, 2014 Did you know what changes have been made ? Link to comment Share on other sites More sharing options...
Diverge Posted May 17, 2014 Author Share #7 Posted May 17, 2014 Did you know what changes have been made ? nope, you'd need to ask sancome. Or ask gnoboot what he changed from 10.4 to 10.5 to break it (but it seems he's MIA). edit: basically when fixed, it doesn't do that unload/reload of driver, reset of card, and re-init of the drives (only initializes them once). Link to comment Share on other sites More sharing options...
mheloy Posted July 3, 2014 Share #8 Posted July 3, 2014 Hi, Is the LSI LSI 9211-8i usable for the Nanoboot-5.0.3.1 DSM 5.0-4493 I'm planning to buy one soon, and will be used in my PROD XPEnology running out of ports Link to comment Share on other sites More sharing options...
wenlez Posted July 3, 2014 Share #9 Posted July 3, 2014 The LSI 9211-8i is fulling working. i have one myself. My issue is, my 1st drive starts from 4th HD. Link to comment Share on other sites More sharing options...
stanza Posted July 3, 2014 Share #10 Posted July 3, 2014 Any drives connected to a sas controller will BEGIN AFTER any onboard SATA ports.... Unless you disable the onboard ports in the bios, but depending on which xpenology version your running.... It might work fine without any SATA drives attached....eg Trantors latest HBA version.... But other versions need at least ONE drive on a SATA port for DSM to load onto. . Link to comment Share on other sites More sharing options...
mheloy Posted July 5, 2014 Share #11 Posted July 5, 2014 Awesome... will order soon...but I have a different problem at the moment. Will post a new topic Link to comment Share on other sites More sharing options...
Recommended Posts