Charles Curley wrote: > I have a brand new NVME device, details below, in a brand new computer.
You might, but that's not what the details you show us are saying. > smartd just started returning pending sector errors. > > A recent extended (long) test run since the first reported pending > sector returned no errors. > > How worried should I be? > > > Device Model: NS256GSSD330 > Serial Number: W3ZK047027T > Firmware Version: V0823A0 > User Capacity: 256,060,514,304 bytes [256 GB] > Sector Size: 512 bytes logical/physical > Rotation Rate: Solid State Device > Form Factor: mSATA That says this is a SATA device, not an NVMe device. Looking up the device model shows me this: https://smarthdd.com/database/Netac-SSD-256GB/S0626A0/ which confirms: SATA in an M.2 form factor, not NVMe. > ATA Version is: ACS-2 T13/2015-D revision 3 > SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) > Local Time is: Tue Jan 2 15:27:45 2024 MST > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > > … > > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining LifeTime(hours) > LBA_of_first_error > # 1 Extended offline Completed without error 00% 764 - > # 2 Short offline Completed without error 00% 116 - > > > root@tiassa:~# journalctl -u smartmontools.service | grep unreadable > Jan 02 13:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently > unreadable (pending) sectors > Jan 02 13:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently > unreadable (pending) sectors > Jan 02 14:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently > unreadable (pending) sectors > Jan 02 14:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently > unreadable (pending) sectors > Jan 02 15:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently > unreadable (pending) sectors These are logged at suspiciously even times, like something is looking at the disk every 30 minutes exactly. Note that "currently unreadable" sometimes means "the disk is too busy to get back to us" and sometimes means "there's damage on the disk". The disk's onboard controller should map around damage automatically. Do you have any other symptoms? Anything interesting in the SMART variables? -dsr-
