ipreferpie

Just want to chime in and say that I’ve been having the exact same issues since upgrading to 6.12.4. Thanks for bringing this topic up

Well noted and thanks for clarifying on this.

Hi there, I’ve been trying to import several zpools from TrueNAS mostly successfully. Namely, I can import both my zpools with multiple mirror vdevs (mirror-0 + mirror-1) without any problems. But when I try to import a mixed vdev pool (mirror-0 + raidz1-1), it shows that the drives are unmountable during import. Is there a way for unRAID to allow/override this limitation? Many thanks!

Thank you for the tip on that. I’ll give that a try and report back soon. Another thing I notice is that when I do a Macrium backup from my laptop to my unRAID server, the GUI hangs until the backup is finished. I checked my CPU and mem load it never goes above 60%. I wonder if it can be I/O or network issue? But then, the max transfer rate is only around 90MB/s on a 10GBps network & SSD cache.

Hi, my apologies for the delay. It took some time for me to address the issue. My SD card died, so I found a replacement. After which, I also fixed up having the docker system in folder format in a ZFS drive and changed it to a docker BTRFS image. Unfortunately, the system still hangs after ~48 hours. I've attached my diagnostics and log for review. Many thanks for your help! hk-homelab-diagnostics-20231002-1040.zip syslog-127.0.0.1.log

I recently updated my server to 6.12.4, but it seems to hang after 1-2 days of normal operation. I've rebooted it to safe mode while running a parity check in maintenance mode, which was stable for 3 days. It seems like it may be a plug-in issue but can't find the root. I've attached diagnostics for referral. Many thanks in advance! hk-homelab-diagnostics-20230915-1548.zip

Hi, recently had a power outage and upon restarting, I did a parity sync. It came up with 11470 errors after completion. I ran it a 2nd time and am getting the same 11470 errors. The funny thing is that I have been experiencing 0 individual disk errors. Disk 6 has 48 reallocated sector counts but that's about it. I'm worried about the array but not sure what my next steps should be in pinpointing the problem. Any help would be much appreciated! hk-homelab-diagnostics-20200930-0902.zip

thanks for the heads up. And after the extended SMART, it does confirm my fear. That's unfortunate since I bought it in new condition from STH forums but it lacked warranty. Trying to work out something with the seller

Hi there, I recently bought an OEM Seagate EXOS 14 a month ago and got the following errors: Reallocated sector count 1848 Reported uncorrect 493 Current pending sector 1840 Offline uncorrectable 1840 These were all highlighted in yellow and unRAID took this disk offline to be emulated in parity. I ran a SMART self test which completed w/o errors. Is it likely a disk problem or an issue w/ my SATA cables? Just want to see how I should proceed to be safe. Many thanks! edit: after conducting an extended test, it did come out with errors. I've attached the file for reference. hk-homelab-smart-20200701-1913.zip

Yeah, it really started after upgrading to 6.8.0. The thing is that I rebuilt docker.img multiple times to no avail. I think it's too late to roll back to 6.7.x no that I upgraded twice. The likelihood and immediacy of unRAID hanging is dependent on which docker containers I'm running, I feel. Not proven yet, but I have to turn on one container at a time to run for 2-4 days to ensure it's really working and then add another one. I'm starting to do that now, but it's slow going and not really targetted. I hope someone here w/ more experience can look into the diagnostics and see what's happening.

I've been using unRaid since 6.1 with no many issues and am running 6.8.1 now. But for the last 6 weeks, I've been encountering constant hanging. I noticed that this happens only when Docker is enabled. Without it enabled, there's no problem, but after having Docker running and some containers running (i.e. sabNZBD, Plex, Sonarr, influx, etc.) the system would start having a super high CPU utilization and then would start hanging. This usually takes anywhere from 2-36 hours of running the Docker containers. I would then try to stop processes that are on docker using "kill -9". After that, I'd try to "umount -l /mnt/cache" which would cause the shell to hang. If I skip these steps and try "poweroff" or "powerdown" the script would run, but get stuck at "Forcing shutdown..." after waiting 90 sec for the graceful shutdown option. I have to physically power off and start again. I run a parity check which usually shows 0 errors. But after startup up some containers, the problems persist. I tried checking the files on my /mnt/cache and try moving or syncing files on Krusader. It shows me a small number of /appdata files are corrupt (influx/wal etc which I wasn't even running). So I copied those that could be read and reformatted the cache drives and moved the files back and also deleting/rebuilding docker.img. But the problem still persists. I'm really frustrated at the problem and can't come close to any solution. I think likely it's something happening in the docker containers but don't know what. Can anyone help me on this please? I've attached my diagnostics FYI. Many thanks. hk-homelab-diagnostics-20200125-2100.zip

Hi, I've been using unRAID stably for 5+ years and I've been encountering constant daily hangs over the past week. I can't tell if it's because I upgraded to 6.8 or something else. I was running a parity check overnight and in the morning, the web UI and all the docker containers would be unresponsive. I'm running it on ESXi, so I'd check to console to run "poweroff" to safely shutdown. It'd always get stuck so I would have to force the VM to shutdown. After booting up, I'd run a parity check to see if things are ok and the hanging cycle starts again. I can't tell what's causing this. I've attached the diagnostics. Many thanks in advance! hk-homelab-diagnostics-20200102-1418.zip

got it, thanks! reformatted and all looks good again after a scrub

so I gave it a try, but I got: BLKDISCARD ioctl failed: Remote I/O error should I take it offline and run BLKDISCARD again?

got! thanks

thanks! so basically, can I 1) move my files on to the array, 2) take the pair of cache drives offline, 3) format, 4) then reintroduce it back as new cache drives, 5) move the data back from array to cache?

Hi, after a kernel panic and a hard reset, I conducted a BTRFS scrub on my RAID1 cache pool. What I got were 4 uncorrectable errors. I deleted the docker.img and conducted SMART tests on both SSDs without issue. But upon running the scrub again, I still get the same 4 errors. I'm not sure if it's a hardware problem and how I should proceed to fix this. Below are the logs and attached is the diagnostics. Many thanks. Cache 1: Nov 10 16:13:09 HK-HomeLab kernel: BTRFS warning (device dm-10): checksum error at logical 530594066432 on dev /dev/mapper/sdn1, physical 458653364224, root 5, inode 118530799, offset 28672, length 4096, links 1 (path: appdata/binhex-plexpass/Plex Media Server/Metadata/TV Shows/2/902b34d01d1d00699de74ef41aa4a378087be30.bundle/Contents/com.plexapp.agents.thetvdb/seasons/5/episodes/13/thumbs/66948d605b6a303889512aaaad8668cb4b5d7106) Nov 10 16:13:09 HK-HomeLab kernel: BTRFS error (device dm-10): bdev /dev/mapper/sdn1 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 Nov 10 16:13:09 HK-HomeLab kernel: BTRFS error (device dm-10): unable to fixup (regular) error at logical 530594066432 on dev /dev/mapper/sdn1 Nov 10 16:13:09 HK-HomeLab kernel: BTRFS warning (device dm-10): checksum error at logical 530594070528 on dev /dev/mapper/sdn1, physical 458653368320, root 5, inode 118530799, offset 32768, length 4096, links 1 (path: appdata/binhex-plexpass/Plex Media Server/Metadata/TV Shows/2/902b34d01d1d00699de74ef41aa4a378087be30.bundle/Contents/com.plexapp.agents.thetvdb/seasons/5/episodes/13/thumbs/66948d605b6a303889512aaaad8668cb4b5d7106) Nov 10 16:13:09 HK-HomeLab kernel: BTRFS error (device dm-10): bdev /dev/mapper/sdn1 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 Nov 10 16:13:09 HK-HomeLab kernel: BTRFS error (device dm-10): unable to fixup (regular) error at logical 530594070528 on dev /dev/mapper/sdn1 Cache 2: Nov 10 15:59:58 HK-HomeLab kernel: BTRFS warning (device dm-10): checksum error at logical 530594066432 on dev /dev/mapper/sdd1, physical 36651855872, root 5, inode 118530799, offset 28672, length 4096, links 1 (path: appdata/binhex-plexpass/Plex Media Server/Metadata/TV Shows/2/902b34d01d1d00699de74ef41aa4a378087be30.bundle/Contents/com.plexapp.agents.thetvdb/seasons/5/episodes/13/thumbs/66948d605b6a303889512aaaad8668cb4b5d7106) Nov 10 15:59:58 HK-HomeLab kernel: BTRFS error (device dm-10): bdev /dev/mapper/sdd1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Nov 10 15:59:58 HK-HomeLab kernel: BTRFS error (device dm-10): unable to fixup (regular) error at logical 530594066432 on dev /dev/mapper/sdd1 Nov 10 15:59:58 HK-HomeLab kernel: BTRFS warning (device dm-10): checksum error at logical 530594070528 on dev /dev/mapper/sdd1, physical 36651859968, root 5, inode 118530799, offset 32768, length 4096, links 1 (path: appdata/binhex-plexpass/Plex Media Server/Metadata/TV Shows/2/902b34d01d1d00699de74ef41aa4a378087be30.bundle/Contents/com.plexapp.agents.thetvdb/seasons/5/episodes/13/thumbs/66948d605b6a303889512aaaad8668cb4b5d7106) Nov 10 15:59:58 HK-HomeLab kernel: BTRFS error (device dm-10): bdev /dev/mapper/sdd1 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Nov 10 15:59:58 HK-HomeLab kernel: BTRFS error (device dm-10): unable to fixup (regular) error at logical 530594070528 on dev /dev/mapper/sdd1 hk-homelab-diagnostics-20191110-0837.zip

Much appreciated on the advice. I'll go ahead and do this last bit and see if anything works, but am mentally prepared for a full loss. And to be doubly sure (which is a stupid question) -- there's no way to roll back the changes in parity after it was reflected in the format followed by an immediate shutdown, right? I haven't turned on my array yet since I'm scared of further changes in parity. But if I can't explore this option, I might as well just turn it on and see what important data I truly lost. Not knowing what is really killing me.

Thanks everyone for the help so far. So the worst case scenario is real in that the format was reflected in parity. I guess there's absolutely no way to roll back the parity changes despite my taking it offline after the format. I've downloaded UFS Explorer Pro and did a lost file scan, but it all came back as wrong files (ZIPs, RARs, Apple icons) while they mostly should've been photo and video files. Is there something wrong that I'm not inputting correctly (LUKs decrypt or file name type) since this was a BTRFS encrypted format that was reformatted to BTRFS encrypted again. Many thanks -- I just trying to figure out options carefully before I do anything else. Decryption and scan elements were aes256-xts-plain64 and UTF-8 Unicode

Thanks for all the responses so far. I was really wishing that I can find a solution to rebuild from parity, but it really looks like that as soon as I formatted while the array was online, it wiped the data off parity simultaneously. I've downloaded UFS Pro and it'll take 38hrs to scan of lost files. I really hope that I can manage to find all the ones I lost -- EUR600 is a lot, but for family photos, I'll have to bite the bullet and consider it as a very expensive lesson.

Hi there, I did something really stupid. My unRAID system froze so I rebooted it. Upon restarting the array, I saw that on one of my 14TB disks, it showed unreadable file system and contents were emulated. Because I just flew back from a work trip and severely jetlagged, I did a cursory lookup of how to fix it but didn't follow instructions properly. Basically, I thought I was going to format the disk and unRAID will automatically rebuild it (instead of first taking the disk off the array first). Groggily, I checked the "reformat disk" option while unRAID was conducting a parity check after the reboot. After a minute, I felt something wasn't right. I went to take a look and it, and it showed that the 14TB drive now is all free space. unRAID total disk utilization went from 83% full to 69% full in my array, meaning I lost data. As well, that disk after formatting read it's 99% free space. When it was emulated before formatting, it read 3% free space. I panicked, stopped the parity check and immediately took the array offline. Is there anything I can do now to recover the 14TB I stupidly formatted? Any help would be great. Or is there anything I can do to rebuild from parity? I'd try that, but it it looks like somehow the format also wrote into parity. I've attached diagnostics just in case. My earlier thinking was that since the array was running, if I clicked format, it wouldn't have wiped 14TB from my array, but instead kept the contents emulated while formatting the unreadable drive. Would unRAID let me wipe 14TB of existing data while the array is running? I'm afraid to restart the array since I might overwrite even more data now. This is really disheartening and a lesson learned. There's around 10yrs plus of family photos that I might have lost in my stupidity. edit: forgot the mention that the formatted drive was an encrypted BTRFS format. I have the passkey, but not to sure how to recover the files if it comes to that. hk-homelab-diagnostics-20191103-0409.zip

thanks! will do. Running preclear again now

smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.41-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST14000NM0018-2H4101 Serial Number: ZHZ2YVY9 LU WWN Device Id: 5 000c50 0b611b906 Firmware Version: SN02 User Capacity: 14,000,519,643,136 bytes [14.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 [for details use: -P showall] ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5 SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Oct 6 16:33:29 2019 CST 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: ( 567) 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: (1281) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x70bd) 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-- 083 065 044 - 223835136 3 Spin_Up_Time PO---- 091 091 000 - 0 4 Start_Stop_Count -O--CK 100 100 020 - 14 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 074 060 045 - 22839207 9 Power_On_Hours -O--CK 100 100 000 - 66 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 100 100 020 - 14 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 053 048 040 - 47 (Min/Max 39/49) 192 Power-Off_Retract_Count -O--CK 100 100 000 - 1 193 Load_Cycle_Count -O--CK 100 100 000 - 61 194 Temperature_Celsius -O---K 047 052 000 - 47 (0 27 0 0 0) 195 Hardware_ECC_Recovered -O-RC- 083 009 000 - 223835136 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 - 0 200 Multi_Zone_Error_Rate PO---K 100 100 001 - 0 240 Head_Flying_Hours ------ 100 253 000 - 56 (91 206 0) 241 Total_LBAs_Written ------ 100 253 000 - 36842077208 242 Total_LBAs_Read ------ 100 253 000 - 47624375787 ||||||_ 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 0x15 GPL R/W 1 Rebuild Assist 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 - 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 24 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 0xbe-0xbf GPL VS 65535 Device vendor specific log 0xc1 GPL,SL VS 8 Device vendor specific log 0xc3 GPL,SL VS 32 Device vendor specific log 0xc9 GPL,SL VS 8 Device vendor specific log 0xca GPL,SL VS 16 Device vendor specific log 0xd1 GPL VS 336 Device vendor specific log 0xd2 GPL VS 10000 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 Short offline Completed without error 00% 59 - 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: 47 Celsius Power Cycle Min/Max Temperature: 38/49 Celsius Lifetime Min/Max Temperature: 26/52 Celsius Under/Over Temperature Limit Count: 0/6 SCT Temperature History Version: 2 Temperature Sampling Period: 3 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 (92) Index Estimated Time Temperature Celsius 93 2019-10-01 10:46 ? - ... ..( 33 skipped). .. - 127 2019-10-02 20:12 ? - 0 2019-10-02 21:11 51 ******************************** 1 2019-10-02 22:10 ? - 2 2019-10-02 23:09 26 ******* 3 2019-10-03 00:08 ? - 4 2019-10-03 01:07 28 ********* 5 2019-10-03 02:06 ? - 6 2019-10-03 03:05 39 ******************** 7 2019-10-03 04:04 ? - 8 2019-10-03 05:03 41 ********************** 9 2019-10-03 06:02 ? - 10 2019-10-03 07:01 45 ************************** 11 2019-10-03 08:00 ? - 12 2019-10-03 08:59 47 **************************** 13 2019-10-03 09:58 ? - 14 2019-10-03 10:57 48 ***************************** 15 2019-10-03 11:56 ? - 16 2019-10-03 12:55 49 ****************************** 17 2019-10-03 13:54 ? - 18 2019-10-03 14:53 48 ***************************** 19 2019-10-03 15:52 ? - 20 2019-10-03 16:51 47 **************************** 21 2019-10-03 17:50 ? - 22 2019-10-03 18:49 47 **************************** 23 2019-10-03 19:48 ? - 24 2019-10-03 20:47 47 **************************** 25 2019-10-03 21:46 ? - 26 2019-10-03 22:45 47 **************************** 27 2019-10-03 23:44 48 ***************************** 28 2019-10-04 00:43 47 **************************** 29 2019-10-04 01:42 46 *************************** 30 2019-10-04 02:41 46 *************************** 31 2019-10-04 03:40 45 ************************** 32 2019-10-04 04:39 45 ************************** 33 2019-10-04 05:38 45 ************************** 34 2019-10-04 06:37 44 ************************* 35 2019-10-04 07:36 44 ************************* 36 2019-10-04 08:35 44 ************************* 37 2019-10-04 09:34 46 *************************** 38 2019-10-04 10:33 47 **************************** 39 2019-10-04 11:32 47 **************************** 40 2019-10-04 12:31 45 ************************** 41 2019-10-04 13:30 46 *************************** 42 2019-10-04 14:29 46 *************************** 43 2019-10-04 15:28 47 **************************** 44 2019-10-04 16:27 46 *************************** 45 2019-10-04 17:26 44 ************************* 46 2019-10-04 18:25 45 ************************** 47 2019-10-04 19:24 46 *************************** 48 2019-10-04 20:23 45 ************************** 49 2019-10-04 21:22 45 ************************** 50 2019-10-04 22:21 45 ************************** 51 2019-10-04 23:20 44 ************************* 52 2019-10-05 00:19 45 ************************** 53 2019-10-05 01:18 48 ***************************** 54 2019-10-05 02:17 47 **************************** 55 2019-10-05 03:16 48 ***************************** 56 2019-10-05 04:15 48 ***************************** 57 2019-10-05 05:14 48 ***************************** 58 2019-10-05 06:13 49 ****************************** 59 2019-10-05 07:12 49 ****************************** 60 2019-10-05 08:11 49 ****************************** 61 2019-10-05 09:10 48 ***************************** ... ..( 2 skipped). .. ***************************** 64 2019-10-05 12:07 48 ***************************** 65 2019-10-05 13:06 49 ****************************** 66 2019-10-05 14:05 51 ******************************** 67 2019-10-05 15:04 52 ********************************* 68 2019-10-05 16:03 51 ******************************** 69 2019-10-05 17:02 50 ******************************* ... ..( 3 skipped). .. ******************************* 73 2019-10-05 20:58 50 ******************************* 74 2019-10-05 21:57 49 ****************************** 75 2019-10-05 22:56 49 ****************************** 76 2019-10-05 23:55 48 ***************************** 77 2019-10-06 00:54 48 ***************************** 78 2019-10-06 01:53 48 ***************************** 79 2019-10-06 02:52 45 ************************** 80 2019-10-06 03:51 43 ************************ 81 2019-10-06 04:50 43 ************************ 82 2019-10-06 05:49 42 *********************** 83 2019-10-06 06:48 41 ********************** 84 2019-10-06 07:47 39 ******************** 85 2019-10-06 08:46 ? - 86 2019-10-06 09:45 38 ******************* 87 2019-10-06 10:44 43 ************************ 88 2019-10-06 11:43 49 ****************************** 89 2019-10-06 12:42 49 ****************************** 90 2019-10-06 13:41 48 ***************************** 91 2019-10-06 14:40 47 **************************** 92 2019-10-06 15:39 47 **************************** SCT Error Recovery Control: Read: 100 (10.0 seconds) Write: 100 (10.0 seconds) Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 14 --- Lifetime Power-On Resets 0x01 0x010 4 66 --- Power-on Hours 0x01 0x018 6 36845190168 --- Logical Sectors Written 0x01 0x020 6 35981659 --- Number of Write Commands 0x01 0x028 6 47624375787 --- Logical Sectors Read 0x01 0x030 6 57531168 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 64 --- Spindle Motor Power-on Hours 0x03 0x010 4 58 --- Head Flying Hours 0x03 0x018 4 61 --- 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 0 --- 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 47 --- Current Temperature 0x05 0x010 1 45 --- Average Short Term Temperature 0x05 0x018 1 - --- Average Long Term Temperature 0x05 0x020 1 52 --- Highest Temperature 0x05 0x028 1 0 --- Lowest Temperature 0x05 0x030 1 48 --- Highest Average Short Term Temperature 0x05 0x038 1 45 --- Lowest Average Short Term Temperature 0x05 0x040 1 - --- Highest Average Long Term Temperature 0x05 0x048 1 - --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 60 --- Specified Maximum Operating Temperature 0x05 0x060 4 60 --- Time in Under-Temperature 0x05 0x068 1 5 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 2 --- Number of Hardware Resets 0x06 0x010 4 0 --- Number of ASR Events 0x06 0x018 4 0 --- 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 ST14000NM0018-2H4101_ZHZ2YVY9-20191006-1633.txt

Hi there, I just got a new 14TB drive to add to my array as I've been doing over the years. Pre-read and zeroing works fine, but I got a error midway through the post-read check. Here's what I have: ErrorWarningSystemArrayLogin DOWNLOAD Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 4925433+0 records in Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 4925432+0 records out Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 10329379569664 bytes (10 TB, 9.4 TiB) copied, 45729.5 s, 226 MB/s Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 4926344+0 records in Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 4926343+0 records out Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 10331290075136 bytes (10 TB, 9.4 TiB) copied, 45739.9 s, 226 MB/s Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 4927261+0 records in Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 4927260+0 records out Oct 06 03:44:40 preclear_disk_ZHZ2YVY9_17584: Post-Read: dd output: 10333213163520 bytes (10 TB, 9.4 TiB) copied, 45750.3 s, 226 MB/s Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: S.M.A.R.T.: 5 Reallocated_Sector_Ct 0 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: S.M.A.R.T.: 9 Power_On_Hours 53 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: S.M.A.R.T.: 187 Reported_Uncorrect 0 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: S.M.A.R.T.: 190 Airflow_Temperature_Cel 48 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: S.M.A.R.T.: 197 Current_Pending_Sector 0 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: S.M.A.R.T.: 198 Offline_Uncorrectable 0 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: S.M.A.R.T.: 199 UDMA_CRC_Error_Count 0 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] Spinning up disk... Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] 4096-byte physical blocks Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] Write Protect is off Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] Mode Sense: 7f 00 10 08 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] Attached SCSI disk Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: ST14000NM0018-2H4101_ZHZ2YVY9 (sdj) 512 27344764928 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: Resuming preclear of disk 'sdj' Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 23 50 b8 00 00 00 02 00 00 00 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: print_req_error: I/O error, dev sdj, sector 592492544 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#3 CDB: opcode=0x88 88 00 00 00 00 00 23 50 b4 00 00 00 04 00 00 00 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: print_req_error: I/O error, dev sdj, sector 592491520 Oct 06 03:44:42 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Oct 06 03:44:43 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 23 50 aa 00 00 00 04 00 00 00 Oct 06 03:44:43 preclear_disk_ZHZ2YVY9_17584: syslog: print_req_error: I/O error, dev sdj, sector 592488960 Oct 06 03:44:43 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Oct 06 03:44:43 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#2 CDB: opcode=0x88 88 00 00 00 00 00 23 50 b2 00 00 00 02 00 00 00 Oct 06 03:44:43 preclear_disk_ZHZ2YVY9_17584: syslog: print_req_error: I/O error, dev sdj, sector 592491008 Oct 06 03:44:43 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Oct 06 03:44:43 preclear_disk_ZHZ2YVY9_17584: syslog: sd 33:0:9:0: [sdj] tag#1 CDB: opcode=0x88 88 00 00 00 00 00 23 50 ae 00 00 00 04 00 00 00 Oct 06 03:44:43 preclear_disk_ZHZ2YVY9_17584: syslog: print_req_error: I/O error, dev sdj, sector 592489984 The HDD passed the SMART tests with no errors. Should I worry about the drive? Or likely an issue with the cables? It's attached via 2 SFF8087 cables an IBM M1015 to a Supermicro SAS2 backplane in my 3U 16 drive chassis. This is the first time happening and don't know if it's an a) HDD, b) cable, or c) software plugin problem. Many thanks! edit: forgot to mention that I was running a parity check concurrently

Hey thanks for the quick diagnosis. Just past its warranty too for the WD Red regretfully -- going to buy a replacement in that case. Much appreciated!