smartmontools isn't very verbose when talking to SAS drives. But the good/bad status that a SAS drive reports about itself is probably more reliable than the same info from a SATA drive (I've had lots of SATA drives report "I'm fine" in their SMART data while at the same time reporting fatal I/O errors to the host).
I didn't know it was a SSD. They tend to have vendor-specific SMART extensions. If it is a non-OEM drive you may be able to find information on them from the manufacturer's web site. If it is an OEM drive, things probably don't work the same.
Have you tried smartctl -x?
That's because it should be called "block size" and not "sector size". Sectors are created when HDD is manufactured, blocks are defined by controller. Many "enterprise" drives come with an option to enable T10 Data Integrity Field which makes them 520b block size. This thread explains how to disable this feature thus making these drives common 512b block size disks.You can't change the sector size of a hard drive - the sectors are created when the hard drive is manufactured and can't be changed.
You can change the NTFS cluster size (also called the "allocation unit size") of the file system using Disk Manager as shown by nikorr, but you have to reformat to do it. Using a smaller cluster size may result in a more fragmented disk and slower performance.
Format Command[ 3988.000410] sd 11:0:0:0: Attached scsi generic sg7 type 0
[ 3988.000414] sd 11:0:0:0: [sdg] Unsupported sector size 520.
[ 3988.000418] sd 11:0:0:0: [sdg] 0 512-byte logical blocks: (0 B/0 B)
[ 3988.000420] sd 11:0:0:0: [sdg] 520-byte physical blocks
[ 3988.000507] sd 11:0:0:0: [sdg] Write Protect is off
[ 3988.000510] sd 11:0:0:0: [sdg] Mode Sense: 00 3a 00 00
[ 3988.000532] sd 11:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3988.000676] sd 11:0:0:0: [sdg] Unsupported sector size 520.
[ 3988.000759] sd 11:0:0:0: [sdg] Attached SCSI disk
Scan Command# sg_format -v --format --size=512 /dev/sdg
ATA SS160511 4C3Q peripheral_type: disk [0x0]
Unit serial number: XXXXXXX
LU name: XXXXXXXXX
mode sense (10) cdb: 5a 00 01 00 00 00 00 00 fc 00
Mode Sense (block descriptor) data, prior to changes:
Number of blocks=0 [0x0]
Block size=512 [0x200]
format cdb: 04 18 00 00 00 00
format unit: Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in cdb
Format command: Illegal request sense key, apart from Invalid opcode
The host machine that is running these commands is Ubuntu 16.# sg_scan -i
/dev/sg0: scsi0 channel=0 id=0 lun=0 [em]
ATA SAMSUNG HD322GJ 0001 [rmb=0 cmdq=0 pqual=0 pdev=0x0]
/dev/sg1: scsi1 channel=0 id=0 lun=0 [em]
ATA ST3250820AS G [rmb=0 cmdq=0 pqual=0 pdev=0x0]
/dev/sg2: scsi4 channel=0 id=0 lun=0 [em]
ASUS DRW-24B1ST i 1.00 [rmb=1 cmdq=0 pqual=0 pdev=0x5]
/dev/sg3: scsi8 channel=0 id=0 lun=0 [em]
ATA Samsung SSD 850 1B6Q [rmb=0 cmdq=0 pqual=0 pdev=0x0]
/dev/sg4: scsi12 channel=0 id=0 lun=0 [em]
Kingston DataTraveler 2.0 PMAP [rmb=1 cmdq=0 pqual=0 pdev=0x0]
/dev/sg5: scsi9 channel=0 id=0 lun=0 [em]
ATA ST2000DM001-1CH1 CC24 [rmb=0 cmdq=0 pqual=0 pdev=0x0]
/dev/sg6: scsi10 channel=0 id=0 lun=0 [em]
ATA ST95005620AS SD28 [rmb=0 cmdq=0 pqual=0 pdev=0x0]
/dev/sg7: scsi11 channel=0 id=0 lun=0 [em]
ATA SS160511 4C3Q [rmb=0 cmdq=0 pqual=0 pdev=0x0]
It is a Samsung SSD branded by EMC - They had a SAS to SATA converter on them, I took it off so I could plug these into my computer. So to answer your question they are SATA. I am thinking that the EMC Firmware they have on them does not support 512 block sizes. Perhaps I can flash a new firmware. Anyone know of a way?I could not use sg_format on SATA. Is the SSD you are trying SAS or SATA?
Sent from my Nexus 6 using Tapatalk
I picked up a couple of 15K SAS drives for fun. I connected them to a LSI 9240-8i with a SFF8087 to SFF8482 cable that I found in the junk box. I think the cable came with the Dell H310's I bought a while ago.so if your HBA cannot recognize 520 sector SSD/HDD, you can try other HBAs, don't give up.