Data Integrity Feature needs better handling
Description
Problem/Justification
Impact
Activity
Bug Clerk last week
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Bug Clerk last week
Thank you for this report, feature requests are now handled via our forums. We recommend creating a post here: https://forums.truenas.com/c/features/12
Bug Clerk last week
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Bug Clerk last week
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Details
Details
Assignee
Triage TeamReporter
Jaime HalscottLabels
Fix versions
Affects versions
Priority
UndefinedMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
When you attempt to use a SAS drive with TrueNAS and it has the Data Integrity Feature set in it, as is often the case with Dell OEM drives, it fails with the message that it cannot use the drives and then mostly gibberish error text.
There should be a solution to correct such disks en masse. I know that we can use the sg_format command with various switches, but that is a one-by-one process and the shell/login times out long before you do it, so you have to work around that by enabling SSH and using multiple sessions or some other command line to do a batch.
The GUI should have an option to show you incompatible drives and offer a solution along with a way to apply that to the affected drives.
Session ID: 8650e09d-ba1c-ea0e-96ab-e3ef61a1375d