Add a forceNVME flag to openSeaChest
Description
Problem/Justification
None
Impact
None
Activity
Show:
Bug Clerk February 14, 2024 at 8:32 PM
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.
Ameer Hamza February 14, 2024 at 6:19 PMEdited
Upstream PR:
Complete
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Ameer HamzaReporter
Ameer HamzaOriginal estimate
Time remaining
0m
Fix versions
Priority
UndefinedKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created February 13, 2024 at 7:00 PM
Updated May 30, 2024 at 7:16 PM
Resolved February 14, 2024 at 8:32 PM
openSeaChest does not have the option to force recognize a drive as NVMe like other protocols unless it reads the prefix. The NVMe drives connected through Trimode HBA appear as SCSI disks, which makes seaChest to communicate with them through the
sginterface instead of SCSI. Add a flag to force recognize the drive as NVMe.