Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Supported SAS Firmwares

Western Digital Drives - The Preferred Drives of FreeNAS and TrueNAS CORE
Status
Not open for further replies.

MarioDespot

Member
Joined
Jan 20, 2016
Messages
25
As i told before i tried that. Results are same!!!!!!!

This is after upgrade to the last version of p20


sas2flash -listall
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

Adapter Selected is a LSI SAS: SAS2008(B2)

Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr
----------------------------------------------------------------------------

0 SAS2008(B2) 20.00.04.00 14.01.00.08 No Image 00:20:00:00

Finished Processing Commands Successfully.
Exiting SAS2Flash.
[root@freenas] ~# camcontrol devlist
<LENOVO-X ST900MM0006 L56Q> at scbus1 target 1 lun 0 (pass0,da0)
<IBM-ESXS AL13SEB900 SB35> at scbus1 target 2 lun 0 (pass1,da1)
<IBM-ESXS HUC109090CSS60 J2EH> at scbus1 target 3 lun 0 (pass2,da2)
<LENOVO-X ST900MM0006 L56Q> at scbus1 target 4 lun 0 (pass3,da3)
<LENOVO-X ST900MM0006 L56Q> at scbus1 target 10 lun 0 (pass4,da4)
<LENOVO-X ST900MM0006 L56Q> at scbus1 target 11 lun 0 (pass5,da5)
<Kingston DataTraveler 3.0 PMAP> at scbus3 target 0 lun 0 (pass6,da6)
[root@freenas] ~# camcontrol identify da0
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da1
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da2
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da3
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da4
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da5
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed

[root@freenas] ~# gpart show
=> 34 30277565 da6 GPT (14G)
34 8190 - free - (4M)
8224 1024 1 bios-boot (512k)
9248 30268344 2 freebsd-zfs (14G)
30277592 7 - free - (3.5k)

=> 34 1758174701 da2 GPT (838G) [CORRUPT]
34 4062 - free - (2M)
4096 4194304 1 freebsd-swap (2.0G)
4198400 1753972736 2 freebsd-zfs (836G)
1758171136 3599 - free - (1.8M)

=> 34 1758174701 da4 GPT (838G) [CORRUPT]
34 4062 - free - (2M)
4096 4194304 1 freebsd-swap (2.0G)
4198400 1753972736 2 freebsd-zfs (836G)
1758171136 3599 - free - (1.8M)

=> 34 1758174701 da5 GPT (838G) [CORRUPT]
34 4062 - free - (2M)
4096 4194304 1 freebsd-swap (2.0G)
4198400 1753972736 2 freebsd-zfs (836G)
1758171136 3599 - free - (1.8M)

=> 34 1758174701 da0 GPT (838G)
34 1758174701 - free - (838G)

=> 34 1758174701 da1 GPT (838G)
34 1758174701 - free - (838G)

[root@freenas] ~# zpool create test da0
cannot create 'test': no such pool or dataset
[root@freenas] ~# zpool create test /dev/da0
cannot create 'test': no such pool or dataset
[root@freenas] ~# zpool create test /dev/da1
cannot create 'test': no such pool or dataset

[root@freenas] ~# zpool status
pool: freenas-boot
state: ONLINE
status: One or more devices are configured to use a non-native block size.
Expect reduced performance.
action: Replace affected devices with devices that support the
configured block size, or migrate data to a properly configured
pool.
scan: none requested
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
gptid/fa17a121-b86c-11e5-973e-40f2e9df0d5a ONLINE 0 0 0 block size: 8192B configured, 8388608B native
 

jgreco

Resident Grinch
Moderator
Joined
May 29, 2011
Messages
13,021
As i told before i tried that. Results are same!!!!!!!
I suggest you settle down. As I said,

I think there's still something else amiss, but it's probably best to fix one issue at a time.
Part of problem solving is being methodical and eliminating possibilities. Anyways, be sure to keep your firmware at P20 now. That's expected to work and other things are expected to exhibit various issues, usually not serious problems, but still.

I'm actually rather curious about how your boot device came to have an 8K block size, incidentally. That's not at all normal as far as I'm aware.

The refusal to identify is very interesting. What happens if you try a SATA disk in one of the bays?

Also, maybe I'm just not seeing it, but we're missing your hardware manifest. Can you please provide some detailed specs about the system you are trying this on, particularly paying attention to the SAS components such as the backplane?
 

MarioDespot

Member
Joined
Jan 20, 2016
Messages
25
OK, as i told before i already tried with all kind of firmware's with same results !!!!

now i have this:

[root@freenas] ~# sas2flash -listall
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

Adapter Selected is a LSI SAS: SAS2008(B2)

Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr
----------------------------------------------------------------------------

0 SAS2008(B2) 20.00.04.00 14.01.00.08 No Image 00:20:00:00

Finished Processing Commands Successfully.
Exiting SAS2Flash.
[root@freenas] ~# camcontrol devlist
<LENOVO-X ST900MM0006 L56Q> at scbus1 target 1 lun 0 (pass0,da0)
<IBM-ESXS AL13SEB900 SB35> at scbus1 target 2 lun 0 (pass1,da1)
<IBM-ESXS HUC109090CSS60 J2EH> at scbus1 target 3 lun 0 (pass2,da2)
<LENOVO-X ST900MM0006 L56Q> at scbus1 target 4 lun 0 (pass3,da3)
<LENOVO-X ST900MM0006 L56Q> at scbus1 target 10 lun 0 (pass4,da4)
<LENOVO-X ST900MM0006 L56Q> at scbus1 target 11 lun 0 (pass5,da5)
<Kingston DataTraveler 3.0 PMAP> at scbus3 target 0 lun 0 (pass6,da6)
[root@freenas] ~# camcontrol identify da0
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da1
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da2
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da3
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da4
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed
[root@freenas] ~# camcontrol identify da5
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed

[root@freenas] ~# zpool create test da0
cannot create 'test': no such pool or dataset
[root@freenas] ~# zpool create test /dev/da0
cannot create 'test': no such pool or dataset
[root@freenas] ~# zpool create test /dev/da1
cannot create 'test': no such pool or dataset

[root@freenas] ~# tail /var/log/messages
Feb 2 06:47:13 freenas (da0:mps0:0:1:0): READ(10). CDB: 28 00 68 cb 9a 00 00 01 00 00
Feb 2 06:47:13 freenas (da0:mps0:0:1:0): CAM status: SCSI Status Error
Feb 2 06:47:13 freenas (da0:mps0:0:1:0): SCSI status: Check Condition
Feb 2 06:47:13 freenas (da0:mps0:0:1:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Feb 2 06:47:13 freenas (da0:mps0:0:1:0): Error 22, Unretryable error
Feb 2 06:47:13 freenas (da0:mps0:0:1:0): READ(10). CDB: 28 00 68 cb 9c 00 00 01 00 00
Feb 2 06:47:14 freenas (da0:mps0:0:1:0): CAM status: SCSI Status Error
Feb 2 06:47:14 freenas (da0:mps0:0:1:0): SCSI status: Check Condition
Feb 2 06:47:14 freenas (da0:mps0:0:1:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Feb 2 06:47:14 freenas (da0:mps0:0:1:0): Error 22, Unretryable error
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,214
In moment when i try to write anything on disks (i can create partitions with fdisk with some errors but partition table is written on hdd) like create zpool i have only errors which i couldn't find in google.
Any particular reason you are trying to do all this via CLI and not in the GUI? Also, you really never stated what version of FreeNas you are running (unless I missed that somewhere)..

Lastly, can you post the output of "sas2flash -list"? I know you already did a "-listall"; feel free to obscure/exclude the SAS Address.
 

jgreco

Resident Grinch
Moderator
Joined
May 29, 2011
Messages
13,021
Unless something obvious shakes out in his hardware manifest, which we still haven't seen, this is obscure enough (at least to me) that I'd have to go pulling out tech doc to figure out the meaning of the CDB, and I just don't have the time right now...
 

MarioDespot

Member
Joined
Jan 20, 2016
Messages
25
[root@freenas] ~# cat /etc/version
FreeNAS-9.3-STABLE-201512121950

[root@freenas] ~# sas2flash -list
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

Adapter Selected is a LSI SAS: SAS2008(B2)

Controller Number : 0
Controller : SAS2008(B2)
PCI Address : 00:20:00:00
SAS Address : 500605b-0-03de-e390
NVDATA Version (Default) : 14.01.00.08
NVDATA Version (Persistent) : 14.01.00.08
Firmware Product ID : 0x2213 (IT)
Firmware Version : 20.00.04.00
NVDATA Vendor : LSI
NVDATA Product ID : SAS9211-8i
BIOS Version : N/A
UEFI BSD Version : N/A
FCODE Version : N/A
Board Name : SAS9211-8i
Board Assembly : N/A
Board Tracer Number : N/A

Finished Processing Commands Successfully.
Exiting SAS2Flash.
 

MarioDespot

Member
Joined
Jan 20, 2016
Messages
25
my boot device is USB stick in dedicated hyper-visor usb port.
any sata drive working fine
anu NL SAS iz same as SAS (no go)
 

MarioDespot

Member
Joined
Jan 20, 2016
Messages
25
and why i use cli. i'm guy who started with computers in 1981'st long time before click era. yes, i use win gui and linux x on my personal computer, but any work on server side (switch, server, storage, etc) is more configurable through cli and of course more verbose. In gui a have nothing, nether clue what is going on with this case. here i have log files to see what is going on
 

jgreco

Resident Grinch
Moderator
Joined
May 29, 2011
Messages
13,021
That's not a hardware manifest. That's a description of a few things in your system.

we're missing your hardware manifest. Can you please provide some detailed specs about the system you are trying this on, particularly paying attention to the SAS components such as the backplane?
Anyways, at this point, I'm going to be out of the office for awhile and probably won't be participating in this thread any further, as doing this sort of debugging/researching is difficult on a laptop. You may wish to submit a bug report to see if maybe a developer can look into the error message. My best guess is that those drives may have something unusual about them, such as custom (RAID array?) firmware, or there's something odd about the backplane, or possibly that the P20 driver has some previously-unrecognized issue. But faced with a user who is evading questions about the hardware platform in use, that raises other questions, and I wouldn't be totally shocked to find out it is something else entirely.
 

MarioDespot

Member
Joined
Jan 20, 2016
Messages
25
I suggest you settle down. As I said,



Part of problem solving is being methodical and eliminating possibilities. Anyways, be sure to keep your firmware at P20 now. That's expected to work and other things are expected to exhibit various issues, usually not serious problems, but still.

I'm actually rather curious about how your boot device came to have an 8K block size, incidentally. That's not at all normal as far as I'm aware.

The refusal to identify is very interesting. What happens if you try a SATA disk in one of the bays?

Also, maybe I'm just not seeing it, but we're missing your hardware manifest. Can you please provide some detailed specs about the system you are trying this on, particularly paying attention to the SAS components such as the backplane?
all kind of sata drives (3.5', 2.5', server or desktop, any size, 500GB, 1TB, ...) are working fine w/o any problem

server raid ctrl ibm fru: 46C8933, and that is LSI SAS9220-8i

sas cables ibm fru: 81Y6476 two pieces

sas bacplane ibm fru 90Y5875 8 pac 2.5-inch hard disk drive backplane assembly
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,214
lol, coffee is needed too.. This one is a little perplexing. Components seem technically sound. Just thinking that if the HBA and drives work on a different system without issue, then it would help narrow it down a bit. Of course, I am not using SAS or NLSAS so I can't compare too much.

I have a few small 2.5" SAS drives, might slap a couple in a test system to see, but if that were an issue I am sure it would have been brought up a long time ago.
 

jgreco

Resident Grinch
Moderator
Joined
May 29, 2011
Messages
13,021
Right, but to date we still haven't even been told what the rest of this system is. Also, judging from the backplane part number, it seems like there's probably an SAS expander involved, see

http://www.itcreations.com/view_product.asp?product_id=44853

and I didn't see any evidence of that in the camcontrol devlist, which I'd normally expect to see. For example an LSI will usually show up as "<LSI SAS2X36 ${version}>.*,ses0)"

So your earlier thoughts about eliminating the backplane from the equation was probably a very good idea, too bad SAS makes that so hard to do.

I have a few small 2.5" SAS drives, might slap a couple in a test system to see, but if that were an issue I am sure it would have been brought up a long time ago.
I actually wonder about that. For the most part, we've been steering people at SATA drives because the cost for the WD Red or Seagate NAS class drives is so much less expensive than the nearline SAS or enterprise SATA (or whatever you want to call the SATA version of a NL-SAS drive) stuff. 7200RPM isn't really that helpful with ZFS.

Unfortunately I only have one 2.5" SAS drive free here and I think it may be dead, and I don't have any P20 controllers anyways. So if you do get an opportunity to test with some 2.5" SAS drives, that'd be helpful to the discussion. We largely stopped deploying SAS drives ~5 years ago back when it became clear that SSD was a better option for fast storage and SATA HDD was suitable for most of our large storage needs,
 

MarioDespot

Member
Joined
Jan 20, 2016
Messages
25
Right, but to date we still haven't even been told what the rest of this system is. Also, judging from the backplane part number, it seems like there's probably an SAS expander involved, see

http://www.itcreations.com/view_product.asp?product_id=44853

and I didn't see any evidence of that in the camcontrol devlist, which I'd normally expect to see. For example an LSI will usually show up as "<LSI SAS2X36 ${version}>.*,ses0)"

So your earlier thoughts about eliminating the backplane from the equation was probably a very good idea, too bad SAS makes that so hard to do.



I actually wonder about that. For the most part, we've been steering people at SATA drives because the cost for the WD Red or Seagate NAS class drives is so much less expensive than the nearline SAS or enterprise SATA (or whatever you want to call the SATA version of a NL-SAS drive) stuff. 7200RPM isn't really that helpful with ZFS.

Unfortunately I only have one 2.5" SAS drive free here and I think it may be dead, and I don't have any P20 controllers anyways. So if you do get an opportunity to test with some 2.5" SAS drives, that'd be helpful to the discussion. We largely stopped deploying SAS dryears ago back when it became clear that SSD was a better option for fast storage and SATA HDD was suitable for most of our large storage needs,

as i told earlier, in same server, same raid ctrl, same cables, same backplane i tried sas drives 300GB/15K/6BbSAS from 2012. year and they worked fine but they are 3.5" and i can't put then in server normally.
newer sas drives 2.5" 900GB/10K/6GbSAS, produced last year, from different vendors (toshiba, seagate, hitachi) doesn't work
all sata drives works correctly
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,214
Here is the best I can do. Located an older Dell Savvio 15K 146GB 2.5" SAS drive. I have a Dell C2100/FS12-TY 12 Bay that currently is running "FreeNAS-9.3-Nightlies-201601280300" (was trying a fix for an IPMI possible bug fix...).

Anyways, bays/trays can do either 3.5" or 2.5" so I will throw a mixture at it and see what I get. HBA is a H200 that has been crossflashed and has the latest P20:
Code:
~# sas2flash -list
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2008(B2)

        Controller Number              : 0
        Controller                     : SAS2008(B2)
        PCI Address                    : 00:05:00:00
        SAS Address                    : 099152d-0-0099-217d
        NVDATA Version (Default)       : 14.01.00.08
        NVDATA Version (Persistent)    : 14.01.00.08
        Firmware Product ID            : 0x2213 (IT)
        Firmware Version               : 20.00.04.00
        NVDATA Vendor                  : LSI
        NVDATA Product ID              : SAS9211-8i
        BIOS Version                   : 07.39.00.00
        UEFI BSD Version               : N/A
        FCODE Version                  : N/A
        Board Name                     : SAS9211-8i
        Board Assembly                 : N/A
        Board Tracer Number            : N/A

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.


Also, there is a firmware update for the SAS Drive from Dell (dated Nov 15, 2013) that I can apply to the SAS Drive later (want to see how it detects as-is right now).

This is a "test box" right now, so we can run the Stable version as well if needed.

Will post back in a bit with some test results (sorry I don't have any newer SAS/NLSAS drives).
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,862
Can you attach a Debug. System->Advanced->Save debug (button at bottom).
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,214
Okay, here is what I have done thus far:
  • Attached 3 differnet drives to my test system:
    • "dao" = 146 GB 2.5" SAS Drive
    • "da1" = 3 TB 3.5" SATA Drive
    • "da2" = 320 GB 2.5" SATA Drive
  • Created a mirror using da0 and da1 (should have used da2 instead, but oh well...)
upload_2016-2-5_9-18-28.png
  • Created a CIFS Share
upload_2016-2-5_9-38-37.png

  • Created a test file and wrote to it, then viewed it on a Windows machine
upload_2016-2-5_9-52-47.png


Grabbed some info:

Code:
[root@ASC-FNDEV] ~# camcontrol devlist
<SEAGATE ST9146852SS HT64>         at scbus0 target 8 lun 0 (pass0,da0)
<ATA ST9320312AS BSM2>             at scbus0 target 9 lun 0 (da2,pass5)
<ATA ST3000NC000 CE02>             at scbus0 target 21 lun 0 (pass1,da1)
<LSI CORP Bobcat 6A07>             at scbus0 target 23 lun 0 (ses0,pass2)
<SanDisk SSD SATA 5000 2.5 1.13>   at scbus1 target 0 lun 0 (ada0,pass3)
<SanDisk SSD SATA 5000 2.5 1.13>   at scbus2 target 0 lun 0 (ada1,pass4)

Code:
[root@ASC-FNDEV] ~# camcontrol identify da0
camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed

Code:
[root@ASC-FNDEV] ~# camcontrol identify da1
pass1: <ST3000NC000 CE02> ATA-8 SATA 3.x device
pass1: 600.000MB/s transfers, Command Queueing Enabled

protocol  ATA/ATAPI-8 SATA 3.x
device model  ST3000NC000
firmware revision  CE02
serial number  Z1F34V90
WWN  5000c50050b141a4
cylinders  16383
heads  16
sectors/track  63
sector size  logical 512, physical 4096, offset 0
LBA supported  268435455 sectors
LBA48 supported  5860533168 sectors
PIO supported  PIO4
DMA supported  WDMA2 UDMA6
media RPM  7200

Feature  Support  Enabled  Value  Vendor
read ahead  yes  yes
write cache  yes  yes
flush cache  yes  yes
overlap  no
Tagged Command Queuing (TCQ)  no  no
Native Command Queuing (NCQ)  yes  32 tags
NCQ Queue Management  no
NCQ Streaming  no
Receive & Send FPDMA Queued  no
SMART  yes  yes
microcode download  yes  yes
security  yes  no
power management  yes  yes
advanced power management  no  no
automatic acoustic management  no  no
media status notification  no  no
power-up in Standby  no  no
write-read-verify  yes  no  0/0x0
unload  no  no
general purpose logging  yes  yes
free-fall  no  no
Data Set Management (DSM/TRIM) no
Host Protected Area (HPA)  yes  no  5860533168/5860533168

Code:
[root@ASC-FNDEV] ~# camcontrol identify da2
pass5: <ST9320312AS 0002BSM2> ATA-8 SATA 1.x device
pass5: 150.000MB/s transfers, Command Queueing Enabled

protocol  ATA/ATAPI-8 SATA 1.x
device model  ST9320312AS
firmware revision  0002BSM2
serial number  5WV03RET
WWN  5000c5002582e1a3
cylinders  16383
heads  16
sectors/track  63
sector size  logical 512, physical 4096, offset 0
LBA supported  268435455 sectors
LBA48 supported  625142448 sectors
PIO supported  PIO4
DMA supported  WDMA2 UDMA6
media RPM  5799

Feature  Support  Enabled  Value  Vendor
read ahead  yes  yes
write cache  yes  yes
flush cache  yes  yes
overlap  no
Tagged Command Queuing (TCQ)  no  no
Native Command Queuing (NCQ)  yes  32 tags
NCQ Queue Management  no
NCQ Streaming  no
Receive & Send FPDMA Queued  no
SMART  yes  yes
microcode download  yes  yes
security  yes  no
power management  yes  yes
advanced power management  yes  yes  128/0x80
automatic acoustic management  no  no
media status notification  no  no
power-up in Standby  no  no
write-read-verify  yes  no  0/0x0
unload  yes  yes
general purpose logging  yes  yes
free-fall  no  no
Data Set Management (DSM/TRIM) no
Host Protected Area (HPA)  yes  no  625142448/625142448
HPA - Security  no

Code:
[root@ASC-FNDEV] ~# smartctl -i /dev/da0
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p31 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:  SEAGATE
Product:  ST9146852SS
Revision:  HT64
User Capacity:  146,815,733,760 bytes [146 GB]
Logical block size:  512 bytes
Rotation Rate:  15000 rpm
Form Factor:  2.5 inches
Logical Unit id:  0x5000c50043adce5f
Serial number:  6TB2TSGS
Device type:  disk
Transport protocol:  SAS (SPL-3)
Local Time is:  Fri Feb  5 08:26:20 2016 EST
SMART support is:  Available - device has SMART capability.
SMART support is:  Enabled
Temperature Warning:  Disabled or Not Supported

Code:
[root@ASC-FNDEV] ~# smartctl -i /dev/da1
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p31 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:  Seagate Constellation CS
Device Model:  ST3000NC000
Serial Number:  Z1F34V90
LU WWN Device Id: 5 000c50 050b141a4
Firmware Version: CE02
User Capacity:  3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:  512 bytes logical, 4096 bytes physical
Rotation Rate:  7200 rpm
Form Factor:  3.5 inches
Device is:  In smartctl database [for details use: -P show]
ATA Version is:  ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:  Fri Feb  5 08:27:06 2016 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Code:
[root@ASC-FNDEV] ~# smartctl -i /dev/da2
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p31 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:  Seagate Momentus 5400.7 (AF)
Device Model:  ST9320312AS
Serial Number:  5WV03RET
LU WWN Device Id: 5 000c50 02582e1a3
Firmware Version: 0002BSM2
User Capacity:  320,072,933,376 bytes [320 GB]
Sector Sizes:  512 bytes logical, 4096 bytes physical
Rotation Rate:  5799 rpm
Device is:  In smartctl database [for details use: -P show]
ATA Version is:  ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 1.5 Gb/s
Local Time is:  Fri Feb  5 08:27:30 2016 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Code:
[root@ASC-FNDEV] ~# diskinfo -v /dev/da0
/dev/da0
  512  # sectorsize
  146815733760  # mediasize in bytes (136G)
  286749480  # mediasize in sectors
  0  # stripesize
  0  # stripeoffset
  17849  # Cylinders according to firmware.
  255  # Heads according to firmware.
  63  # Sectors according to firmware.
  6TB2TSGS  # Disk ident.
  id1,enc@n500065b36789abfd/type@0/slot@c/elmdesc@HDD_11  # Physical path

Code:
[root@ASC-FNDEV] ~# diskinfo -v /dev/da1
/dev/da1
  512  # sectorsize
  3000592982016  # mediasize in bytes (2.7T)
  5860533168  # mediasize in sectors
  4096  # stripesize
  0  # stripeoffset
  364801  # Cylinders according to firmware.
  255  # Heads according to firmware.
  63  # Sectors according to firmware.
  Z1F34V90  # Disk ident.
  id1,enc@n500065b36789abfd/type@0/slot@b/elmdesc@HDD_10  # Physical path

Code:
[root@ASC-FNDEV] ~# diskinfo -v /dev/da2
/dev/da2
  512  # sectorsize
  320072933376  # mediasize in bytes (298G)
  625142448  # mediasize in sectors
  4096  # stripesize
  0  # stripeoffset
  38913  # Cylinders according to firmware.
  255  # Heads according to firmware.
  63  # Sectors according to firmware.
  5WV03RET  # Disk ident.
  id1,enc@n500065b36789abfd/type@0/slot@a/elmdesc@HDD_09  # Physical path

Thinking about trying to update the SAS Drive Firmware and then see if I have any issues. Can even wipe it all and re-run the test again. Only thing I have see thus far is the same error from "camcontrol identify" when ran against the SAS Drive.

I didn't list system specs, but if needed I can (everyone should know that I run Dell PowerEdge C2100/FS12-TY Servers by now though...)
Let me know if there are any other things anyone can think of I should try.
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,214
Well, I updated the SAS Drive Firmware:
upload_2016-2-5_13-2-10.png

Destroyed the Dataset/Volume, created a new mirror using the two smaller drives. Create a new Volume and CIFS Share; then wrote a file to it:

upload_2016-2-5_13-11-42.png


Sorry, I am not able to re-create the issue... Maybe I need a newer SAS to test with (mine has a DOM of 10/2011..)
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,214
Wondering if there is some funkiness with IBM Servers? They seem to have some type of "SAS/SATA hard drive update" that lists a ton of drives. I could understand if this were firmware updates, but the "Change History" is huge..

OP, is your Server updated with IBM's most recent Firmware/BIOS/etc.?
 

niveous

Newbie
Joined
Feb 10, 2016
Messages
1
To chime in here, I have the same problem with IBM branded Seagate ST9300605SS (300GB SAS2) disks with the mps driver (m1015 crossflashed with p20) in an IBM 3650 m3. I'm assuming it's some sort of firmware issue, although with IBM having cutoff firmware updates without a valid support contract I've been unable to test newer firmware. Perhaps disk firmware's are available. Currently I've been relegated to using them on a sas1068e controller, which is only a SAS1 controller.
 

jgreco

Resident Grinch
Moderator
Joined
May 29, 2011
Messages
13,021
That certainly suggests some general firmware issue to me.
 
Status
Not open for further replies.
Top