GUI Interaction with Seagate SAS Mach.2 Drives
Description
Activity
Kris Moore July 18, 2024 at 5:57 PM
Thank you for submitting this feature request! To better accommodate and gauge community interest for future versions of TrueNAS we have moved the submission process to our TrueNAS Community Forums. If this feature is still important and relevant for consideration, please refer to the links below on how to submit it for community voting and TrueNAS roadmap review.
Feature Requests Forum:
https://forums.truenas.com/c/features/12
Feature Requests FAQ:
https://forums.truenas.com/t/about-the-feature-requests-category-readme-first/8802
Alexander Motin February 26, 2024 at 5:29 PMEdited
As expected, Addressed logical unit values are different. So TrueNAS should use as unique identifiers {serial_lunid}ZKL263820000C2409P22_6000c500d9675cc70000000000000000 vs {serial_lunid}ZKL263820000C2409P22_6000c500d9675cc70001000000000000 .
Brian Rupe [X] February 26, 2024 at 5:20 PM
root@mikoshi:~# sg_vpd -p sn /dev/sda
Unit serial number VPD page:
Unit serial number: ZKL263820000C2409P22
root@mikoshi:~# sg_vpd -p sn /dev/sdb
Unit serial number VPD page:
Unit serial number: ZKL263820000C2409P22
root@mikoshi:~# sg_vpd -p di /dev/sda
Device Identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x6000c500d9675cc70001000000000000
Target port:
designator type: NAA, code set: Binary
transport: Serial Attached SCSI Protocol (SPL-4)
0x5000c500d9675cc5
designator type: Relative target port, code set: Binary
transport: Serial Attached SCSI Protocol (SPL-4)
Relative target port: 0x1
Target device that contains addressed lu:
designator type: NAA, code set: Binary
transport: Serial Attached SCSI Protocol (SPL-4)
0x5000c500d9675cc4
designator type: SCSI name string, code set: UTF-8
SCSI name string:
naa.5000C500D9675CC4
root@mikoshi:~# sg_vpd -p di /dev/sdb
Device Identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x6000c500d9675cc70000000000000000
Target port:
designator type: NAA, code set: Binary
transport: Serial Attached SCSI Protocol (SPL-4)
0x5000c500d9675cc5
designator type: Relative target port, code set: Binary
transport: Serial Attached SCSI Protocol (SPL-4)
Relative target port: 0x1
Target device that contains addressed lu:
designator type: NAA, code set: Binary
transport: Serial Attached SCSI Protocol (SPL-4)
0x5000c500d9675cc4
designator type: SCSI name string, code set: UTF-8
SCSI name string:
naa.5000C500D9675CC4
root@mikoshi:~#
Alexander Motin February 26, 2024 at 4:51 PMEdited
These drives appear to the OS as 2 LUNs from the same device resulting in a single Serial Number for the whole drive. As the GUI is using the SN as part of the Unique Identifier for the drives it results in a data collision where only the 'bottom' half of the drive shows up in the GUI to be used.
It is expected for LUNs of dual-actuator disks to have the same serial number, but they should have different LUN IDs, and TrueNAS should use concatenation of both as unique identifier. Please show output of sg_vpd -p sn /dev/sdX and sg_vpd -p di /dev/sdX for the two LUNs of a same drive.
c Weidner January 16, 2024 at 10:39 PM
Agreed 100%, although I keep seeing more scenarios pop up for the dual actuator drives. I wonder if Seagate could provide a firmware update that would allow you to distinguish the serial number on a per LUN basis.
So ya, two potential courses for the fix.
I was hoping I could get someone to engage, but time is running out to where Ima have to hand jam the new pools I need in there and not have the environment I would need to help them investigate and repro the bug.. I just hope that is not going to have further repercussions down the road.
Not sure if we should call this one a bug or a feature tho, depends on the folks working on the code or if it warrant a backport to the fix. Unfortunately I have upgraded my pools which make them non-backward compatible with SCALE (why they broke concurrency on pool version between SCALE and CORE is somewhat questionable, seems like an oversight. Maybe I should file a bug against CORE for that one.
Details
Details
Priority
LowAssignee
Reporter
More fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Additional Information: https://www.truenas.com/community/threads/drive-recognition-issue-seagate-exos-2x14.115667/
I'm working on building up a new TN server. I purchased a number of Seagate Exos 2x14 SAS drives. These drives appear to the OS as 2 LUNs from the same device resulting in a single Serial Number for the whole drive. As the GUI is using the SN as part of the Unique Identifier for the drives it results in a data collision where only the 'bottom' half of the drive shows up in the GUI to be used. The disks are present and appear to be fully operational from the OS, I am able to manually build a zpool and can write data across the pool without issue. I can do limited modifications once the zpool is imported into the GUI (ex: add a L2ARC to the pool or export/delete the pool) but other items such as Disk Management and Monitoring is unavailable.
PFR - Please update the mechanism in the GUI for tracking disks to validate LUN when multiple devices return the same SN. This would allow the TN interface to operate in the normal, expected manner for these types of disk.
Suggestion - Please amend on-line documentation to note this edge-case issue for future users who will encounter this problem or to help prevent others from making sub-optimal hardware choices for their deployments.