SAS drives are shown as unknown type

[ptr727]

Hi, I just installed 4 x SAS3 drives in ZFS mirror config.
The disks UI shows the type as unknown, and the serial number shows the WWN not the serial number.
smartctl does identify the disks as SAS3, and does show the correct serial number.

1) How do I get the disk type to correctly show as "Hard Disk"?
2) And the serial number to be the drive serial not WWN?

root@server-2:~# smartctl --all /dev/sdi
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.44-1-pve] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUH721010AL4200
Revision:             A21D
Compliance:           SPC-4
User Capacity:        10,000,831,348,736 bytes [10.0 TB]
Logical block size:   4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca26a2aa050
Serial number:        2TGSERND
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Thu Jun 25 14:42:25 2020 PDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     37 C
Drive Trip Temperature:        85 C

Manufactured in week 03 of year 2018
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  73
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  74
Elements in grown defect list: 0

Vendor (Seagate Cache) information
  Blocks sent to initiator = 1645744226304

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0        0         0         0        345       1252.961           0
write:         0        0         0         0         58      10002.311           0
verify:        0        0         0         0         20          0.006           0

Non-medium error count:        0

No Self-tests have been logged

 

[mira]

What do cat /sys/block/sdd/queue/rotational and udevadm info -p /sys/block/sdd --query all | grep ID_ATA_ROTATION_RATE_RPM return?

 

[ptr727]

root@server-2:~# cat /sys/block/sdd/queue/rotational
1
root@server-2:~# udevadm info -p /sys/block/sdd --query all | grep ID_ATA_ROTATION_RATE_RPM
root@server-2:~# udevadm info -p /sys/block/sdd --query all
P: /devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:0/expander-0:0/port-0:0:2/end_device-0:0:2/target0:0:2/0:0:2:0/block/sdd
N: sdd
L: 0
S: disk/by-id/scsi-35000cca26a47aed4
S: disk/by-id/wwn-0x5000cca26a47aed4
S: disk/by-path/pci-0000:02:00.0-sas-exp0x500304800914683f-phy4-lun-0
E: DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:0/expander-0:0/port-0:0:2/end_device-0:0:2/target0:0:2/0:0:2:0/block/sdd
E: DEVNAME=/dev/sdd
E: DEVTYPE=disk
E: MAJOR=8
E: MINOR=48
E: SUBSYSTEM=block
E: USEC_INITIALIZED=10726858
E: ID_SCSI=1
E: ID_VENDOR=HGST
E: ID_VENDOR_ENC=HGST\x20\x20\x20\x20
E: ID_MODEL=HUH721010AL4200
E: ID_MODEL_ENC=HUH721010AL4200\x20
E: ID_REVISION=A21D
E: ID_TYPE=disk
E: ID_SERIAL=35000cca26a47aed4
E: ID_SERIAL_SHORT=5000cca26a47aed4
E: ID_WWN=0x5000cca26a47aed4
E: ID_WWN_WITH_EXTENSION=0x5000cca26a47aed4
E: ID_SCSI_SERIAL=2TH8E3LD
E: ID_BUS=scsi
E: ID_PATH=pci-0000:02:00.0-sas-exp0x500304800914683f-phy4-lun-0
E: ID_PATH_TAG=pci-0000_02_00_0-sas-exp0x500304800914683f-phy4-lun-0
E: ID_PART_TABLE_UUID=678bbdb3-39b9-d240-a48a-a8e787b94c04
E: ID_PART_TABLE_TYPE=gpt
E: DEVLINKS=/dev/disk/by-id/scsi-35000cca26a47aed4 /dev/disk/by-id/wwn-0x5000cca26a47aed4 /dev/disk/by-path/pci-0000:02:00.0-sas-exp0x500304800914683f-phy4-lun-0
E: TAGS=:systemd:

root@server-2:~#

 

[mira]

That's the reason why. We use the ID_ATA_ROTATION_RATE_RPM value to set the type to 'hdd'. If it doesn't exist we fall back to 'unknown'.

 

[ptr727]

Ok, so it is a bug in the UI code then that looks for an ATA attribute that is typically not present for SAS drives, i.e. ID_ATA is not 1?
How about looking for ID_DISK, or using info from smartctl (and please add disk temperature)?

 

[mira]

How is your disk connected? Directly or behind an expander perhaps?

 

[ptr727]

SAS3 HBA to SAS3 backplane to SAS3 drive, typical config, really should not make a difference.
Same config works with SATA drives, and obviously SATA is ATA so the SATA disks on the same chassis is detected as hard drives.
The key here is that ID_ATA is missing, SAS drive not SATA drive, so you should not use ATA attributes on SAS drives.

 

[mira]

I've missed that somehow, but your disks are behind an expander:

E: DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:0/expander-0:0/port-0:0:2/end_device-0:0:2/target0:0:2/0:0:2:0/block/sdd

If the expander doesn't pass all the information to the OS, there's not much you can do.

 

[ptr727]

This has nothing to do with the expander not passing anything through.
In this same chassis over the same expander SATA drives are correctly identified.
The problem is the use of `ID_ATA_ROTATION_RATE_RPM`, it is not a reliable method to identify disk types.

`ID_ATA_ROTATION_RATE_RPM` is an ATA attribute that is not found in all drives, especially not in SAS drives, as in SAS is SCSI not ATA.
If the `ID_ATA` attribute is not present, do not look for other ATA attributes, use a different technique.

E.g. I have shown that `smartctl` does correctly determine the drive type and attributes.
E.g. you could use `cat /sys/block/sdd/queue/rotational`.
E.g. you could use `lsblk -d -o name,rota`

But using `ID_ATA_ROTATION_RATE_RPM` is unreliable, and will not work with SAS drives.

 

[BORNXenon]

I have the same issue.
All of my disks show as 'unknown' and I don't get any SMART values. The all show as 'OK' in the S.M.A.R.T. column, but clicking 'Show S.M.A.R.T. values' shows a pop-up with only the following information:

Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Elements in grown defect list: 0[CODE]

The disks are 300GB 10K SAS disks running off a 9200-8i HBA in IT Mode

root@mrpve2:~# cat /sys/block/sda/queue/rotational
1
root@mrpve2:~# udevadm info -p /sys/block/sda --query all | grep ID_ATA_ROTATION_RATE_RPM
root@mrpve2:~# udevadm info -p /sys/block/sda --query all
P: /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host4/port-4:0/end_device-4:0/target4:0:0/4:0:0:0/block/sda
N: sda
L: 0
S: disk/by-id/lvm-pv-uuid-KETq1i-2Obf-hlhK-dIWX-86TO-w9z1-unHaQq
S: disk/by-id/scsi-350000393e8182430
S: disk/by-path/pci-0000:01:00.0-sas-phy3-lun-0
S: disk/by-id/wwn-0x50000393e8182430
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host4/port-4:0/end_device-4:0/target4:0:0/4:0:0:0/block/sda
E: DEVNAME=/dev/sda
E: DEVTYPE=disk
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=3954300
E: ID_SCSI=1
E: ID_VENDOR=TOSHIBA
E: ID_VENDOR_ENC=TOSHIBA\x20
E: ID_MODEL=MBF2300RC
E: ID_MODEL_ENC=MBF2300RC\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=5208
E: ID_TYPE=disk
E: ID_SERIAL=350000393e8182430
E: ID_SERIAL_SHORT=50000393e8182430
E: ID_WWN=0x50000393e8182430
E: ID_WWN_WITH_EXTENSION=0x50000393e8182430
E: ID_SCSI_SERIAL=EB07PC3054W4
E: ID_BUS=scsi
E: ID_PATH=pci-0000:01:00.0-sas-phy3-lun-0
E: ID_PATH_TAG=pci-0000_01_00_0-sas-phy3-lun-0
E: ID_FS_UUID=KETq1i-2Obf-hlhK-dIWX-86TO-w9z1-unHaQq
E: ID_FS_UUID_ENC=KETq1i-2Obf-hlhK-dIWX-86TO-w9z1-unHaQq
E: ID_FS_VERSION=LVM2 001
E: ID_FS_TYPE=LVM2_member
E: ID_FS_USAGE=raid
E: SYSTEMD_READY=1
E: SYSTEMD_ALIAS=/dev/block/8:0
E: SYSTEMD_WANTS=lvm2-pvscan@8:0.service
E: DEVLINKS=/dev/disk/by-id/lvm-pv-uuid-KETq1i-2Obf-hlhK-dIWX-86TO-w9z1-unHaQq /dev/disk/by-id/scsi-350000393e8182430 /dev/disk/by-path/pci-0000:01:00.0-sas-phy3-lun-0 /dev/disk/by-id/wwn-0x50000393e8182430
E: TAGS=:systemd:

 

[chipbreak]

Im having the same problem where my drive is showing up with the device id of: scsi-35000c50058fbc697 and device type unknown.

my goal is to pass the sas drive through to my truenas vm but when i use the command: qm set 526 -scsi10 /dev/disk/by-id/scsi-35000c50058fb9147.

reply:
volume /dev/disk/by-id/scsi-35000c50058fbc697 does not exist

 

[gbschenkel]

Hi i just installed 5x HUH728080AL4200, 8TB version of the same disks used from @ptr727, they are 4kn disks, using SAS3 HBA Card, but I am still using a SAS1 backpanel(trying to find a cheap SAS3).
I saw the Type Unknown is a still a issued today on Proxmox fully updated. I like to know if this can affect the storage in someway, because I made a RAIDZ2 pool, and am waiting for more 3x disks to arrive to install in this pool.
Also are some posts related to 4kn blocksize (https://forum.proxmox.com/threads/how-to-do-4kn-virtio-disks.96809/#post-419427) are they a issue?

 

[gbschenkel]

I have checked the git.proxmox.com and found the the perl module which checks the type of disk installed, if someone has perl skill, maybe could try submit a patch for it, or at least share it to patch locally for who want it. https://git.proxmox.com/?p=pve-storage.git;a=blob;f=PVE/Diskmanage.pm

 

[hacman]

Same issue - SAS disks show unknown, SATA shows as expected. Both types of disks connected the same way.

 

[LnxBil]

I like to know if this can affect the storage in someway, because I made a RAIDZ2 pool, and am waiting for more 3x disks to arrive to install in this pool.

No, it does not. How the PVE UI sees disks is totally independent to the storage system you use.

Same issue - SAS disks show unknown, SATA shows as expected. Both types of disks connected the same way.

cosmetic misinformation. Ignore it. Even RAID volumes don't get correctly detected.