Added a new NVME pool (single vdev); Existing SMART tasks set for "All Disks" Ignore Them
Description
Problem/Justification
Impact
Attachments
Activity
John T Davis 4 days ago
, I’m not seeing any scrub record for the entire QuickDrawer NVME pool in zpool status, so it’s never been scrubbed even though it’s scheduled to do so.
For SMART testing, after more than a week no daily or weekly SMART test results have appeared in smartctl’s output, nor in the TrueNAS' GUI’s SMART test history. The only results are for the manual test I ran on the pool.
The only SMART test results for the NVME pool are the manual long tests I ran just to make sure the tests could actually run. The boot pool also isn’t running any SMART tests (a single NVME disk pool).
Bug Clerk 4 days ago
how did you determine the 2 newly added nvme drives were not being tested?
Bonnie Follweiler last week
Good Morning .
This ticket has been moved into our queue to review.
An engineering representative will update with any further questions or details in the near future.
John T Davis last weekEdited
Hello! I have a bit more information for this. My weekly scrub tasks were set to execute last night, including one for the NVME pool. The HDD pool task executed without issue, however, the NVME pool did not scrub.
These are the tasks that are automatically created and enabled by TrueNAS when a pool is added.
EDIT @ Monday, March 10, 2025: I just ran the command below.
Details
Details
Assignee
TrueNAS Backend TriageReporter
John T DavisComponents
Fix versions
Affects versions
Priority
LowMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Hello,
I have a system that has always been set up with a single 4-way mirror pool (8 HDDs). I have two Periodic SMART Tests configured for All Disks (short every 24 hours; long once a week). This arrangement has worked perfectly for scheduled SMART tests since I set it up.
I just added a new pool, with a single mirror VDEV (m.2 NVME).
Expected behavior: the existing SMART jobs would start automatically testing the NVME, as they are members of "All Disks."
Observed behavior:
1. Scheduled SMART tests ignore the NVME (both long and short scheduled tests).
2. Both NVME are able to run manual SMART long tests without a problem.
This seems like it must be a bug. It seems like the scheduled tasks didn't update their disk lists either when the m.2 disks were added or when I created the NVME pool.
I suspect everything would work as expected if I deleted the SMART jobs and re-added them, but I don't think that's how it's meant to work.
Session ID: f5a09500-935b-bbf2-028b-16d908933c72