LSI SAS2008 mps(4) 4TB disk only shows 2TB on CURRENT r255089

[Sam Fourman Jr.]

On Sat, Aug 31, 2013 at 1:07 PM, Sam Fourman Jr. <sfourman at gmail.com> wrote:

> Hello list
>
> I have two issues that may in fact be both related to the LSI SAS2008 card
> or
> the mps(4) driver.
>
> this server is running FreeBSD 10.0-CURRENT #0 r255089
>
>
> 1) All of the SSD disks are showing up at SATA2 300MB's
>     but the card is in fact a 6GB Sata3 card..
>
> 2) a Westren Digital 4TB disk only shows 2TB (connected to the LSI
> controller)
>
> full dmesg here
> https://gist.github.com/sfourman/6399419
>
> full pciconf here
> https://gist.github.com/sfourman/6399454
>
>
>
> Below is some disk info,
>
>
> $ sudo camcontrol identify da6
> pass6: <WDC WD4000FYYZ-01UL1B0 01.01K01> ATA-8 SATA 3.x device
> pass6: 300.000MB/s transfers, Command Queueing Enabled
>
> protocol              ATA/ATAPI-8 SATA 3.x
> device model          WDC WD4000FYYZ-01UL1B0
> firmware revision     01.01K01
> serial number         WD-WCC130721596
> WWN                   50014ee25de95b67
> cylinders             16383
> heads                 16
> sectors/track         63
> sector size           logical 512, physical 512, offset 0
> LBA supported         268435455 sectors
> LBA48 supported       7814037168 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
> 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            yes no
> write-read-verify              no no
> unload                         yes yes
> free-fall                      no no
> Data Set Management (DSM/TRIM) no
> Host Protected Area (HPA)      yes      no      7814037168/7814037168
> HPA - Security                 no
> $
>
>
> sudo gpart create -s gpt /dev/da6
> da6 created
> $ gpart show
> =>       34  234441581  da0  GPT  (111G)
>          34        128    1  freebsd-boot  (64k)
>         162  224395136    2  freebsd-ufs  (107G)
>   224395298    8388608    3  freebsd-swap  (4.0G)
>   232783906    1657709       - free -  (809M)
>
> =>        34  4294967227  da6  GPT  (2T)
>           34  4294967227       - free -  (2T)
>
>
> $ sudo gpart add -a 4k -t freebsd-zfs -l backup da6
> da6p1 added
> $
> $
> $
> $
> $
> $ gpart show
> =>       34  234441581  da0  GPT  (111G)
>          34        128    1  freebsd-boot  (64k)
>         162  224395136    2  freebsd-ufs  (107G)
>   224395298    8388608    3  freebsd-swap  (4.0G)
>   232783906    1657709       - free -  (809M)
>
> =>        34  4294967227  da6  GPT  (2T)
>           34           6       - free -  (3.0k)
>           40  4294967216    1  freebsd-zfs  (2T)
>   4294967256           5       - free -  (2.5k)
> --
>
> Sam Fourman Jr.
>


 is it possible that the problem is in the cam layer and not the mps(4)
driver?

-- 

Sam Fourman Jr.