spasmonaut

I'll add myself to the list of Fractal users, my primary Unraid rig in a Meshify 2 XL with 16 total drives (12 in the main "tower", and a pair each in the bottom two drive cages), and a Meshify 2 with 13 drives in it (I'll explain). The two drives in the rear, bottom cage (disk 10 and 13) are the warmest and idle around 39 C in my Meshify 2 XL. I just decided to throw in a USB-powered fan above those drives to see how much of a difference it makes hence the one is at 37 C, which is the top drive in that cage. My server is in a generally low state of activity when I took this (5800 X with a Noctua DH-12L and a pair of fans, 128 GB RAM, pair of NVMes and a pair of 2.5 SSDs in the rear, Quadro P2000, and LSI-9300-16i). The room is around 74 C at the moment and I do have other gear in here (network rack, PC, a few Synology servers and expansion units, and a few laptops) and is the warmest room in the house because of all of this gear. I'm currently running Noctua 140mm fans in all locations, 3 as intake on the front, one intake and one exhaust on top, and exhaust on the rear. I use a plugin to control the fans to target a temperature of 35 C for the spinning rust. Yes, I know I said 16 drives and there are only 15 at present. My second parity is currently heading back to goHardDrive for an RMA. I run 13 drives in my Meshify 2, with 9 in the case tower, and a pair each in two drive cages in the bottom. I have a Corsair SHIFT PSU with the side-mounted connectors so I could afford the space to add a second cage and squeeze in two more drives. This is the Meshify 2 RGB so I decided to deck out all fan positions with the Fractal RGB fans, configured like I did with the Noctuas on its big brother, but this server is in a slightly cooler room with better overall airflow and running a 5600G and stock AMD cooler, 48 GB of RAM, an LSI 9207-8i, and the remaining disks connected to the Asus TUF X570 Plus mobo's SATA controller. The hardware is generally milder in this machine and performing secondary storage and has slightly lower demand so overall runs cooler. Disk 7 and 8 are in the rear-bottom drive cage as you may have guessed by the temps: One final aside, and sharing as advice to any other HBA users, I have an adapter kit in each case that I got off Amazon for like $10 that allows you to pair up two 80mm fans (I bought like a half dozen Coolermaster fans) to cool the card above (or below, depending upon fan orientation and placement of the fans) and install them in a PCI mounting slot and power the fans off the motherboard headers with a Y-adapter. This setup is no taller than any other typical expansion card and only uses a single slot in your case to minimize the waste of expansion slots on your motherboard. I absolutely recommend this approach (or a similar directed airflow setup) to maintain adequate cooling for your HBA. For long-term stability, reliability, and lifetime of the hardware, and to keep performance from throttling, (not sure if these cards throttle but I'll never run into that), you must keep them cool with auxiliary cooling as the heatsink alone is not sufficient and they require active airflow to maintain longevity. A buddy of mine has cooked several cards because he also ran "desktop" cases like these that don't use server-style high airflow configurations that allowed his cards to run too hot for far too long.

I don't think I've ever made a "feature request" before for any plugins so I'm not sure if this is the right location for this or if I should put this somewhere else... I would love to be able to see drive firmware as another point of data that could be pulled in to make it very simple to see, at a glance, which of my drives would require an update that they currently don't have, etc. This is one of my favorite plugins and I'm certain it has saved me HOURS with troubleshooting and managing drive replacements in my semi-large installations.

Yeah I have a pair of 80mm fans that are directly blowing over the heatsink. They are driven at 100% duty.

It's an 8643 SAS to SATA cable and the other 3 drives on the same cable are error-free. Physical inspection has confirmed it's fully seated and no indications of a loose or poor connection. I could get a replacement just to rule it out as it's about all I've got left at this point, aside from the card itself (fingers crossed that isn't it).

The PSU is a 1000w Corsair that I bought a few months ago new so I'd be less inclined to suspect PSU but duly noted. I'm averaging about 200w of usage per the total draw on my UPS. I bought a larger PSU specifically to have ample SATA power connections to avoid using any splitters and thankfully don't have any of those in use. I concur on disliking them and have had some catastrophic failures resulting from those (burnt cables, etc.) so I strictly avoid them now. I also have this machine on a UPS to avoid any power disruptions that would interrupt the array as it's no fun waiting for a parity check for 36 hours. That's why I'm scratching my head at the moment. I've not actually experienced a "false" disk failure before with Unraid since I've only begun using it toward the beginning of the year, so short of just watch and wait and see, do I just clear the errors and restart the array to put that disk back in production?

So having experienced enough hard drive failures in my lifetime, I'm familiar with bad sectors etc. that can mean the impending death of a drive. While traveling a few days ago, I got a notification from my server that I had a disk with errors in the array: "Unraid: Unraid array errors Warning [UNRAID] - array has errors 1727017023 Array has 1 disk with read errors warning Parity disk - ST18000NE000-2YY101_ZR54FPSN (sdh) (errors 93)" I VPN'ed in to have a look and noticed that my primary parity disk had been disabled showing 93 errors (still in this status as I haven't taken any actions as of yet). Honestly, I'd rather just RMA the drive as it's got a couple of years left under warranty but I don't know that I've got a valid case for that yet. I grabbed the diagnostics to capture what was present in the log at that time and sliced out this part of the syslog to identify when the server started noticing issues with the disk. There wasn't anything eventful happening leading up to this event (nothing with high I/O activity, no tasks running, etc.) and the other 15 disks on the HBA are all humming along merrily, including 3 others on the same cable. The log showed both read and write errors: Sep 22 10:56:34 Unraid kernel: mpt3sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) ### [PREVIOUS LINE REPEATED 24 TIMES] ### Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7852 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7852 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7852 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7852 CDB: opcode=0x8a 8a 00 00 00 00 00 81 97 ce 38 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2174209592 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174209528 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7854 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7854 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7854 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7854 CDB: opcode=0x8a 8a 00 00 00 00 00 81 97 f0 f8 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2174218488 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174218424 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7855 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7855 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7855 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7855 CDB: opcode=0x88 88 00 00 00 00 00 82 26 12 b8 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2183533240 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2183533176 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7857 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7857 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7857 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7857 CDB: opcode=0x8a 8a 00 00 00 00 00 81 97 ec 80 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2174217344 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174217280 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7858 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7858 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7858 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7858 CDB: opcode=0x8a 8a 00 00 00 00 00 81 97 cb b0 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2174208944 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174208880 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7859 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7859 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7859 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7859 CDB: opcode=0x8a 8a 00 00 00 00 00 81 97 cc 00 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2174209024 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174208960 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7860 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7860 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7860 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7860 CDB: opcode=0x8a 8a 00 00 00 00 00 81 97 bf c0 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2174205888 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174205824 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7861 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7861 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7861 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7861 CDB: opcode=0x88 88 00 00 00 00 00 82 26 17 f0 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2183534576 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2183534512 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7862 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7862 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7862 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7862 CDB: opcode=0x8a 8a 00 00 00 00 00 81 97 f0 c0 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2174218432 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174218368 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7863 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7863 Sense Key : 0x2 [current] Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7863 ASC=0x4 ASCQ=0x0 Sep 22 10:56:34 Unraid kernel: sd 12:0:6:0: [sdh] tag#7863 CDB: opcode=0x8a 8a 00 00 00 00 00 81 97 f1 28 00 00 00 08 00 00 Sep 22 10:56:34 Unraid kernel: I/O error, dev sdh, sector 2174218536 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174218472 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2183534064 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2183532736 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2183535704 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174217928 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174218536 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2183533624 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2174211368 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2174209976 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2174209752 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2174209760 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174217648 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2183530080 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2203288480 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2203288488 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2203288496 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2203288504 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2203288512 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2203288520 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2203288528 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174217496 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174218160 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174218208 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=2174211384 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=4497441296 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=4497441304 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21557835288 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21557835296 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21557835304 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21557835312 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21557835416 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21557835424 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21557835432 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21557835440 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21558359576 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21558359584 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21558359592 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21558359600 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21558359704 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21558359712 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21558359720 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21558359728 Sep 22 10:56:34 Unraid kernel: md: disk0 read error, sector=21559515944 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174207352 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174208088 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2183531672 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21558359576 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21558359584 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21558359592 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21558359600 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21558359704 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21558359712 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21558359720 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21558359728 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21557835288 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21557835296 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21557835304 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21557835312 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21557835416 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21557835424 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21557835432 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21557835440 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=21559515944 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2183535704 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2183532736 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2183533176 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2183533624 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2183534064 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2183534512 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2183530080 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174209752 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174209760 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174209976 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174211368 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2174211384 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2203288480 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2203288488 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2203288496 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2203288504 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2203288512 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2203288520 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=2203288528 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=4497441296 Sep 22 10:56:34 Unraid kernel: md: disk0 write error, sector=4497441304 I kicked off an extended SMART test expecting the drive to puke on itself somewhere along the way but it completed without incident about a day later (18 TB Ironwolf Pro). I had reviewed the SMART stats as well and nothing stuck out to me to suggest the disk was actually dying: smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.106-Unraid] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST18000NE000-2YY101 Serial Number: ZR54FPSN LU WWN Device Id: 5 000c50 0dcaf1a4a Firmware Version: EN01 User Capacity: 18,000,207,937,536 bytes [18.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: Not in smartctl database 7.3/5610 ATA Version is: ACS-4 (minor revision not indicated) SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Tue Sep 24 17:34:41 2024 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Disabled ATA Security is: Disabled, NOT FROZEN [SEC1] Write SCT (Get) Feature Control Command failed: scsi error aborted command Wt Cache Reorder: Unknown (SCT Feature Control command failed) === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 559) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: (1524) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x50bd) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 076 064 044 - 38511344 3 Spin_Up_Time PO---- 089 088 000 - 0 4 Start_Stop_Count -O--CK 100 100 020 - 42 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 090 060 045 - 922022706 9 Power_On_Hours -O--CK 073 073 000 - 23895 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 100 100 020 - 15 18 Unknown_Attribute PO-R-- 100 100 050 - 0 187 Reported_Uncorrect -O--CK 100 100 000 - 0 188 Command_Timeout -O--CK 100 100 000 - 0 190 Airflow_Temperature_Cel -O---K 070 046 000 - 30 (Min/Max 29/34) 192 Power-Off_Retract_Count -O--CK 100 100 000 - 9 193 Load_Cycle_Count -O--CK 100 100 000 - 1013 194 Temperature_Celsius -O---K 030 042 000 - 30 (0 23 0 0 0) 197 Current_Pending_Sector -O--C- 100 100 000 - 0 198 Offline_Uncorrectable ----C- 100 100 000 - 0 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 1 200 Multi_Zone_Error_Rate PO---K 100 100 001 - 0 240 Head_Flying_Hours ------ 100 253 000 - 23857 (138 116 0) 241 Total_LBAs_Written ------ 100 253 000 - 239095546021 242 Total_LBAs_Read ------ 100 253 000 - 10476683578647 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 5 Ext. Comprehensive SMART error log 0x04 GPL R/O 256 Device Statistics log 0x04 SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test log 0x0a GPL R/W 8 Device Statistics Notification 0x0c GPL R/O 2048 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 768 Current Device Internal Status Data log 0x2f GPL R/O 1 Set Sector Configuration 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa1 GPL,SL VS 160 Device vendor specific log 0xa2 GPL VS 16320 Device vendor specific log 0xa4 GPL,SL VS 160 Device vendor specific log 0xa6 GPL VS 192 Device vendor specific log 0xa8-0xa9 GPL,SL VS 136 Device vendor specific log 0xab GPL VS 1 Device vendor specific log 0xad GPL VS 16 Device vendor specific log 0xb1 GPL,SL VS 160 Device vendor specific log 0xb6 GPL VS 1920 Device vendor specific log 0xbe-0xbf GPL VS 65535 Device vendor specific log 0xc1 GPL,SL VS 8 Device vendor specific log 0xc3 GPL,SL VS 24 Device vendor specific log 0xc6 GPL VS 5184 Device vendor specific log 0xc7 GPL,SL VS 8 Device vendor specific log 0xc9 GPL,SL VS 8 Device vendor specific log 0xca GPL,SL VS 16 Device vendor specific log 0xcd GPL,SL VS 1 Device vendor specific log 0xce GPL VS 1 Device vendor specific log 0xcf GPL VS 512 Device vendor specific log 0xd1 GPL VS 656 Device vendor specific log 0xd2 GPL VS 10256 Device vendor specific log 0xd4 GPL VS 2048 Device vendor specific log 0xda GPL,SL VS 1 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (5 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 23871 - # 2 Short offline Completed without error 00% 23848 - # 3 Short offline Completed without error 00% 23552 - # 4 Short offline Aborted by host 90% 23434 - # 5 Extended offline Completed without error 00% 23427 - # 6 Short offline Completed without error 00% 23398 - # 7 Short offline Completed without error 00% 23231 - # 8 Short offline Completed without error 00% 23157 - # 9 Short offline Completed without error 00% 23063 - #10 Short offline Completed without error 00% 22895 - #11 Short offline Completed without error 00% 22727 - #12 Short offline Completed without error 00% 22559 - #13 Short offline Completed without error 00% 22391 - #14 Short offline Completed without error 00% 22223 - #15 Short offline Completed without error 00% 22055 - #16 Short offline Completed without error 00% 21887 - #17 Extended offline Completed without error 00% 21798 - #18 Short offline Completed without error 00% 21719 - #19 Short offline Completed without error 00% 21551 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 522 (0x020a) Device State: Active (0) Current Temperature: 30 Celsius Power Cycle Min/Max Temperature: 29/34 Celsius Lifetime Min/Max Temperature: 23/54 Celsius Under/Over Temperature Limit Count: 0/0 SMART Status: 0xc24f (PASSED) Vendor specific: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 SCT Temperature History Version: 2 Temperature Sampling Period: 4 minutes Temperature Logging Interval: 59 minutes Min/Max recommended Temperature: 10/40 Celsius Min/Max Temperature Limit: 5/60 Celsius Temperature History Size (Index): 128 (3) Index Estimated Time Temperature Celsius 4 2024-09-19 12:14 32 ************* 5 2024-09-19 13:13 32 ************* 6 2024-09-19 14:12 31 ************ 7 2024-09-19 15:11 32 ************* 8 2024-09-19 16:10 32 ************* 9 2024-09-19 17:09 32 ************* 10 2024-09-19 18:08 31 ************ 11 2024-09-19 19:07 32 ************* 12 2024-09-19 20:06 31 ************ 13 2024-09-19 21:05 32 ************* ... ..( 6 skipped). .. ************* 20 2024-09-20 03:58 32 ************* 21 2024-09-20 04:57 31 ************ ... ..( 4 skipped). .. ************ 26 2024-09-20 09:52 31 ************ 27 2024-09-20 10:51 32 ************* ... ..( 2 skipped). .. ************* 30 2024-09-20 13:48 32 ************* 31 2024-09-20 14:47 30 *********** 32 2024-09-20 15:46 30 *********** 33 2024-09-20 16:45 31 ************ 34 2024-09-20 17:44 31 ************ 35 2024-09-20 18:43 30 *********** 36 2024-09-20 19:42 30 *********** 37 2024-09-20 20:41 31 ************ 38 2024-09-20 21:40 31 ************ 39 2024-09-20 22:39 30 *********** 40 2024-09-20 23:38 32 ************* 41 2024-09-21 00:37 31 ************ ... ..( 7 skipped). .. ************ 49 2024-09-21 08:29 31 ************ 50 2024-09-21 09:28 32 ************* 51 2024-09-21 10:27 31 ************ 52 2024-09-21 11:26 32 ************* 53 2024-09-21 12:25 31 ************ 54 2024-09-21 13:24 31 ************ 55 2024-09-21 14:23 32 ************* 56 2024-09-21 15:22 31 ************ ... ..( 2 skipped). .. ************ 59 2024-09-21 18:19 31 ************ 60 2024-09-21 19:18 32 ************* 61 2024-09-21 20:17 31 ************ 62 2024-09-21 21:16 31 ************ 63 2024-09-21 22:15 32 ************* 64 2024-09-21 23:14 31 ************ 65 2024-09-22 00:13 32 ************* 66 2024-09-22 01:12 31 ************ 67 2024-09-22 02:11 32 ************* 68 2024-09-22 03:10 31 ************ 69 2024-09-22 04:09 32 ************* 70 2024-09-22 05:08 31 ************ 71 2024-09-22 06:07 31 ************ 72 2024-09-22 07:06 32 ************* 73 2024-09-22 08:05 31 ************ 74 2024-09-22 09:04 32 ************* 75 2024-09-22 10:03 ? - 76 2024-09-22 11:02 31 ************ 77 2024-09-22 12:01 32 ************* 78 2024-09-22 13:00 32 ************* 79 2024-09-22 13:59 31 ************ 80 2024-09-22 14:58 32 ************* 81 2024-09-22 15:57 31 ************ 82 2024-09-22 16:56 31 ************ 83 2024-09-22 17:55 32 ************* 84 2024-09-22 18:54 33 ************** ... ..( 5 skipped). .. ************** 90 2024-09-23 00:48 33 ************** 91 2024-09-23 01:47 32 ************* 92 2024-09-23 02:46 33 ************** 93 2024-09-23 03:45 33 ************** 94 2024-09-23 04:44 33 ************** 95 2024-09-23 05:43 32 ************* 96 2024-09-23 06:42 32 ************* 97 2024-09-23 07:41 33 ************** 98 2024-09-23 08:40 32 ************* 99 2024-09-23 09:39 32 ************* 100 2024-09-23 10:38 33 ************** 101 2024-09-23 11:37 32 ************* 102 2024-09-23 12:36 33 ************** 103 2024-09-23 13:35 32 ************* 104 2024-09-23 14:34 33 ************** 105 2024-09-23 15:33 32 ************* 106 2024-09-23 16:32 32 ************* 107 2024-09-23 17:31 32 ************* 108 2024-09-23 18:30 31 ************ 109 2024-09-23 19:29 30 *********** 110 2024-09-23 20:28 31 ************ 111 2024-09-23 21:27 31 ************ 112 2024-09-23 22:26 30 *********** 113 2024-09-23 23:25 29 ********** 114 2024-09-24 00:24 29 ********** 115 2024-09-24 01:23 30 *********** ... ..( 5 skipped). .. *********** 121 2024-09-24 07:17 30 *********** 122 2024-09-24 08:16 29 ********** 123 2024-09-24 09:15 30 *********** ... ..( 3 skipped). .. *********** 127 2024-09-24 13:11 30 *********** 0 2024-09-24 14:10 29 ********** 1 2024-09-24 15:09 30 *********** 2 2024-09-24 16:08 29 ********** 3 2024-09-24 17:07 30 *********** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 15 --- Lifetime Power-On Resets 0x01 0x010 4 23895 --- Power-on Hours 0x01 0x018 6 239086661812 --- Logical Sectors Written 0x01 0x020 6 1168168627 --- Number of Write Commands 0x01 0x028 6 10476683370444 --- Logical Sectors Read 0x01 0x030 6 4017840734 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 23892 --- Spindle Motor Power-on Hours 0x03 0x010 4 23891 --- Head Flying Hours 0x03 0x018 4 1013 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 0 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors 0x03 0x040 4 9 --- Number of High Priority Unload Events 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion 0x04 0x018 4 0 -D- Physical Element Status Changed 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 30 --- Current Temperature 0x05 0x010 1 30 --- Average Short Term Temperature 0x05 0x018 1 34 --- Average Long Term Temperature 0x05 0x020 1 42 --- Highest Temperature 0x05 0x028 1 23 --- Lowest Temperature 0x05 0x030 1 40 --- Highest Average Short Term Temperature 0x05 0x038 1 29 --- Lowest Average Short Term Temperature 0x05 0x040 1 37 --- Highest Average Long Term Temperature 0x05 0x048 1 34 --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 60 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 5 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 116 --- Number of Hardware Resets 0x06 0x010 4 51 --- Number of ASR Events 0x06 0x018 4 1 --- Number of Interface CRC Errors 0xff ===== = = === == Vendor Specific Statistics (rev 1) == 0xff 0x008 7 0 --- Vendor Specific 0xff 0x010 7 0 --- Vendor Specific 0xff 0x018 7 0 --- Vendor Specific |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) No Defects Logged SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS Seagate FARM log (GP Log 0xa6) supported [try: -l farm] I can certainly pull the drive out and throw a battery of tests at it to see if I can instigate a failure that will be a clear sign of trouble requiring an RMA but if I can't get it to trip up again, I'm a little perplexed as to what was happening while I was away from home. Any thoughts or suggestions are welcomed.