Custom Query (1556 matches)

Please add the Seagate ST14000NM001G-2KJ103 Model.

Datasheet: ​https://www.seagate.com/files/www-content/datasheets/pdfs/exos-x16-DS2011-1-1904US-en_US.pdf

User Manual: ​https://www.seagate.com/www-content/product-content/enterprise-hdd-fam/exos-x-16/en-us/docs/100845789f.pdf

Use AC_LINK_IFELSE instead of AC_COMPILE_IFELSE to check for stack-protector availability as some compilers could missed the needed library (-lssp or -lssp_nonshared) at linking step:

/home/giuliobenetti/autobuild/run/instance-3/output-1/host/bin/x86_64-linux-g++ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -Wall -W -Wformat=2 -fstack-protector-strong -o smartctl smartctl.o atacmdnames.o atacmds.o ataidentify.o ataprint.o dev_ata_cmd_set.o dev_intelliprop.o dev_interface.o dev_jmb39x_raid.o json.o knowndrives.o nvmecmds.o nvmeprint.o scsicmds.o scsiata.o scsinvme.o scsiprint.o utility.o os_linux.o cciss.o dev_areca.o -lselinux /home/giuliobenetti/autobuild/run/instance-3/output-1/host/opt/ext-toolchain/bin/../lib/gcc/x86_64-buildroot-linux-uclibc/8.3.0/../../../../x86_64-buildroot-linux-uclibc/bin/ld: cannot find -lssp_nonshared /home/giuliobenetti/autobuild/run/instance-3/output-1/host/opt/ext-toolchain/bin/../lib/gcc/x86_64-buildroot-linux-uclibc/8.3.0/../../../../x86_64-buildroot-linux-uclibc/bin/ld: cannot find -lssp

Fixes:

• ​http://autobuild.buildroot.org/results/0de9f2a69fa2a39164211299f8a429d2fec6935a

Hi,

On the HGST SS300 (SAS SSD), smartctl won't display the drive physical block size if the drive just went through a soft reset (tested on r5031) :

root@rescue:~# smartctl -i /dev/sg22 | grep -i block
Logical block size:   512 bytes
Physical block size:  4096 bytes
root@rescue:~# sg_reset -d /dev/sg22
root@rescue:~# smartctl -i /dev/sg22 | grep -i block
Logical block size:   512 bytes
root@rescue:~# 

If we try to read the capacity using another tool, a Unit Attention is raised on the first command issued after the reset :

root@rescue:~# sg_reset -d /dev/sg22
root@rescue:~# sg_readcap -l /dev/sg22
read capacity (16):  Fixed format, current;  Sense key: Unit Attention
 Additional sense: Bus device reset function occurred
READ CAPACITY (16) failed: Unit attention
root@rescue:~# sg_readcap -l /dev/sg22
Read Capacity results:
   Protection: prot_en=0, p_type=0, p_i_exponent=0
   Logical block provisioning: lbpme=1, lbprz=1
   Last logical block address=781422767 (0x2e9390af), Number of logical blocks=781422768
   Logical block length=512 bytes
   Logical blocks per physical block exponent=3 [so physical block length=4096 bytes]
   Lowest aligned logical block address=0
Hence:
   Device size: 400088457216 bytes, 381554.1 MiB, 400.09 GB

I enclosed the output of "smartctl -r scsiioctl -i /dev/sg22", and it looks like smartctl will fallback to a READ CAPACITY(10) when the first READ CAPACITY(16) failed :

>>>> do_scsi_cmnd_io: sg_io_ver=3
 [read capacity(16): 9e 10 00 00 00 00 00 00 00 00 00 00 00 20 00 00 ]
  scsi_status=0x2, sg_transport_status=0x0, sg_driver_status=0x8
  sg_info=0x1  sg_duration=4 milliseconds  resid=32
  status=2: sense_key=6 asc=29 ascq=3
scsiGetSize: READ CAPACITY(16) failed, res=8
>>>> do_scsi_cmnd_io: sg_io_ver=3
 [read capacity(10): 25 00 00 00 00 00 00 00 00 00 ]
  scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0
  sg_info=0x0  sg_duration=0 milliseconds  resid=0

This could probably be fixed by retrying the READ CAPACITY(16) when a Unit Attention is raised, but I don't know if this specific case is easy to detect ?

Feel free to ask if you need more details.