August 7, 20169 yr After a bunch of my old 3TB HDDs started failing on me. I decided to buy myself a bunch of completely new drives. Planned on replacing that cache too, and so I decided it'd make more sense to just copy everything across from the array, rather than rebuild (because my parity was dying, and another HDD looked like it was worse that the one that had failed on me). So now, a week later. I've copied all my data across. Once it had finished, I stopped my array. But it... crashed on me. I'd stopped the array a few times, to pull old HDDs out and put a new one in and this was the first time it'd done it to me. So after waiting a few minutes, and getting no response. I figured I'd just had reset the server. Turned it back on, and now it's doing a parity sync. The sync is running really really slow, currently at 17Mb/s but changed from between 12-20Mbs. Currently going to take another 2 days, 2 hours, 33 minutes to complete (4TB drives). I guess it's running slow because it seems to be correcting every single sector. In the 5 hours and 7 minutes, it's managed to check/correct 901 GB (22.5 %). Wondering if anyone can see figure out what is going on here? And what my next options would be? Just let it run and hopefully it will fix it? Not entirely sure which part of the syslog will be helpful here. I tried copying it all but apparently there is a 20000 character limit.
August 7, 20169 yr Community Expert Sounds like you are doing a parity check instead of a parity sync. A parity check will read parity and if it is incorrect it will write the correction, which is counted as a parity error. What you should have done is a parity sync (build), which would just write parity without reading it, and you wouldn't get any parity errors. And a parity sync is in fact what would be required after creating a new array from copying your data to new disks, since parity is based on the bits stored at each position on the disks, which will not be the same when you just copy the files since where they end up on the disk will depend on a lot of factors. How exactly did you get it to do a parity check instead of a parity build (sync)? Did you tell it to trust your array? If so, that was not correct, since you parity wasn't in sync after what you did. You can stop, new config, and let it build parity. That should be a lot faster than correcting all parity.
August 7, 20169 yr Author There aren't any settings (that I'm aware of), that I'd changed. When I got these HDDs I set it up as a compltely brand new array, as I was changing the cache too, I figured it'd make more sense to build a completely new array as I'd have to set all the apps up again anyway. New config file on the USB stick too. So I've created new array, and I've been putting the old HDDs back (not part of the array), and using unnasigned devices to copy everything back over manually. So, this is technically the first parity check I've done. I presume when Unraid seemed to hang on me, stopped responding, and I had to do a hard reset, that's what's caused this to happen. When I created the array (this was a week ago). When I put the HDDs the process I seem to remember is creating the array, then it told me I needed to format each HDD. I don't remember (not entirely sure), if it did a parity sync to begin with, I presume this wwas done automatically? Here's everything from the system log, minus text. Aug 6 22:20:08 Tower kernel: ata4.00: failed to get NCQ Send/Recv Log Emask 0x1 Aug 6 22:20:08 Tower kernel: ata4.00: failed to get NCQ Send/Recv Log Emask 0x1 Aug 6 22:20:20 Tower rpc.statd[1640]: Version 1.2.8 starting Aug 6 22:20:20 Tower sm-notify[1641]: Version 1.2.8 starting Aug 6 22:20:20 Tower rpc.statd[1640]: Failed to read /var/lib/nfs/state: Success Aug 6 22:20:20 Tower sshd[1660]: Server listening on 0.0.0.0 port 22. Aug 6 22:20:21 Tower emhttp: unRAID System Management Utility version 6.1.9 Aug 6 22:20:21 Tower kernel: md: unRAID driver 2.5.3 installed Aug 6 22:20:21 Tower kernel: mdcmd (1): import 0 8,32 3907018532 ST4000DM000-1F2168_Z306CB0F Aug 6 22:20:21 Tower kernel: md: import disk0: [8,32] (sdc) ST4000DM000-1F2168_Z306CB0F size: 3907018532 Aug 6 22:20:21 Tower kernel: mdcmd (2): import 1 8,48 3907018532 ST4000DM000-1F2168_Z306CAJP Aug 6 22:20:21 Tower kernel: md: import disk1: [8,48] (sdd) ST4000DM000-1F2168_Z306CAJP size: 3907018532 Aug 6 22:20:21 Tower kernel: mdcmd (3): import 2 8,96 3907018532 ST4000DM000-1F2168_Z306CAND Aug 6 22:20:21 Tower kernel: md: import disk2: [8,96] (sdg) ST4000DM000-1F2168_Z306CAND size: 3907018532 Aug 6 22:20:21 Tower kernel: mdcmd (4): import 3 8,80 3907018532 ST4000DM000-1F2168_Z306CARR Aug 6 22:20:21 Tower kernel: md: import disk3: [8,80] (sdf) ST4000DM000-1F2168_Z306CARR size: 3907018532 Aug 6 22:20:21 Tower kernel: mdcmd (5): import 4 8,112 3907018532 ST4000DM000-1F2168_Z306CAK7 Aug 6 22:20:21 Tower kernel: md: import disk4: [8,112] (sdh) ST4000DM000-1F2168_Z306CAK7 size: 3907018532 Aug 6 22:20:21 Tower kernel: mdcmd (6): import 5 8,128 3907018532 ST4000DM000-1F2168_Z306CB0J Aug 6 22:20:21 Tower kernel: md: import disk5: [8,128] (sdi) ST4000DM000-1F2168_Z306CB0J size: 3907018532 Aug 6 22:20:21 Tower kernel: mdcmd (7): import 6 8,144 3907018532 ST4000DM000-1F2168_Z306CADF Aug 6 22:20:21 Tower kernel: md: import disk6: [8,144] (sdj) ST4000DM000-1F2168_Z306CADF size: 3907018532 Aug 6 22:20:21 Tower kernel: mdcmd (: import 7 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (9): import 8 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (10): import 9 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (11): import 10 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (12): import 11 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (13): import 12 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (14): import 13 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (15): import 14 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (16): import 15 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (17): import 16 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (18): import 17 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (19): import 18 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (20): import 19 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (21): import 20 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (22): import 21 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (23): import 22 0,0 Aug 6 22:20:21 Tower kernel: mdcmd (24): import 23 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (25): spinup 0 Aug 6 22:20:22 Tower kernel: mdcmd (26): spinup 1 Aug 6 22:20:22 Tower kernel: mdcmd (27): spinup 2 Aug 6 22:20:22 Tower kernel: mdcmd (28): spinup 3 Aug 6 22:20:22 Tower kernel: mdcmd (29): spinup 4 Aug 6 22:20:22 Tower kernel: mdcmd (30): spinup 5 Aug 6 22:20:22 Tower kernel: mdcmd (31): spinup 6 Aug 6 22:20:22 Tower kernel: md: unRAID driver removed Aug 6 22:20:22 Tower kernel: md: unRAID driver 2.5.3 installed Aug 6 22:20:22 Tower kernel: mdcmd (1): import 0 8,32 3907018532 ST4000DM000-1F2168_Z306CB0F Aug 6 22:20:22 Tower kernel: md: import disk0: [8,32] (sdc) ST4000DM000-1F2168_Z306CB0F size: 3907018532 Aug 6 22:20:22 Tower kernel: mdcmd (2): import 1 8,48 3907018532 ST4000DM000-1F2168_Z306CAJP Aug 6 22:20:22 Tower kernel: md: import disk1: [8,48] (sdd) ST4000DM000-1F2168_Z306CAJP size: 3907018532 Aug 6 22:20:22 Tower kernel: mdcmd (3): import 2 8,96 3907018532 ST4000DM000-1F2168_Z306CAND Aug 6 22:20:22 Tower kernel: md: import disk2: [8,96] (sdg) ST4000DM000-1F2168_Z306CAND size: 3907018532 Aug 6 22:20:22 Tower kernel: mdcmd (4): import 3 8,80 3907018532 ST4000DM000-1F2168_Z306CARR Aug 6 22:20:22 Tower kernel: md: import disk3: [8,80] (sdf) ST4000DM000-1F2168_Z306CARR size: 3907018532 Aug 6 22:20:22 Tower kernel: mdcmd (5): import 4 8,112 3907018532 ST4000DM000-1F2168_Z306CAK7 Aug 6 22:20:22 Tower kernel: md: import disk4: [8,112] (sdh) ST4000DM000-1F2168_Z306CAK7 size: 3907018532 Aug 6 22:20:22 Tower kernel: mdcmd (6): import 5 8,128 3907018532 ST4000DM000-1F2168_Z306CB0J Aug 6 22:20:22 Tower kernel: md: import disk5: [8,128] (sdi) ST4000DM000-1F2168_Z306CB0J size: 3907018532 Aug 6 22:20:22 Tower kernel: mdcmd (7): import 6 8,144 3907018532 ST4000DM000-1F2168_Z306CADF Aug 6 22:20:22 Tower kernel: md: import disk6: [8,144] (sdj) ST4000DM000-1F2168_Z306CADF size: 3907018532 Aug 6 22:20:22 Tower kernel: mdcmd (: import 7 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (9): import 8 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (10): import 9 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (11): import 10 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (12): import 11 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (13): import 12 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (14): import 13 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (15): import 14 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (16): import 15 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (17): import 16 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (18): import 17 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (19): import 18 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (20): import 19 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (21): import 20 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (22): import 21 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (23): import 22 0,0 Aug 6 22:20:22 Tower kernel: mdcmd (24): import 23 0,0 Aug 6 22:20:22 Tower avahi-daemon[3642]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Aug 6 22:20:24 Tower kernel: md: unRAID driver removed Aug 6 22:20:24 Tower kernel: md: unRAID driver 2.5.3 installed Aug 6 22:20:24 Tower kernel: mdcmd (1): import 0 8,32 3907018532 ST4000DM000-1F2168_Z306CB0F Aug 6 22:20:24 Tower kernel: md: import disk0: [8,32] (sdc) ST4000DM000-1F2168_Z306CB0F size: 3907018532 Aug 6 22:20:24 Tower kernel: mdcmd (2): import 1 8,48 3907018532 ST4000DM000-1F2168_Z306CAJP Aug 6 22:20:24 Tower kernel: md: import disk1: [8,48] (sdd) ST4000DM000-1F2168_Z306CAJP size: 3907018532 Aug 6 22:20:24 Tower kernel: mdcmd (3): import 2 8,96 3907018532 ST4000DM000-1F2168_Z306CAND Aug 6 22:20:24 Tower kernel: md: import disk2: [8,96] (sdg) ST4000DM000-1F2168_Z306CAND size: 3907018532 Aug 6 22:20:24 Tower kernel: mdcmd (4): import 3 8,80 3907018532 ST4000DM000-1F2168_Z306CARR Aug 6 22:20:24 Tower kernel: md: import disk3: [8,80] (sdf) ST4000DM000-1F2168_Z306CARR size: 3907018532 Aug 6 22:20:24 Tower kernel: mdcmd (5): import 4 8,112 3907018532 ST4000DM000-1F2168_Z306CAK7 Aug 6 22:20:24 Tower kernel: md: import disk4: [8,112] (sdh) ST4000DM000-1F2168_Z306CAK7 size: 3907018532 Aug 6 22:20:24 Tower kernel: mdcmd (6): import 5 8,128 3907018532 ST4000DM000-1F2168_Z306CB0J Aug 6 22:20:24 Tower kernel: md: import disk5: [8,128] (sdi) ST4000DM000-1F2168_Z306CB0J size: 3907018532 Aug 6 22:20:24 Tower kernel: mdcmd (7): import 6 8,144 3907018532 ST4000DM000-1F2168_Z306CADF Aug 6 22:20:24 Tower kernel: md: import disk6: [8,144] (sdj) ST4000DM000-1F2168_Z306CADF size: 3907018532 Aug 6 22:20:24 Tower kernel: mdcmd (: import 7 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (9): import 8 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (10): import 9 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (11): import 10 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (12): import 11 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (13): import 12 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (14): import 13 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (15): import 14 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (16): import 15 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (17): import 16 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (18): import 17 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (19): import 18 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (20): import 19 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (21): import 20 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (22): import 21 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (23): import 22 0,0 Aug 6 22:20:24 Tower kernel: mdcmd (24): import 23 0,0 Aug 6 22:20:28 Tower kernel: md: unRAID driver removed Aug 6 22:20:28 Tower kernel: md: unRAID driver 2.5.3 installed Aug 6 22:20:29 Tower kernel: mdcmd (1): import 0 8,32 3907018532 ST4000DM000-1F2168_Z306CB0F Aug 6 22:20:29 Tower kernel: md: import disk0: [8,32] (sdc) ST4000DM000-1F2168_Z306CB0F size: 3907018532 Aug 6 22:20:29 Tower kernel: mdcmd (2): import 1 8,48 3907018532 ST4000DM000-1F2168_Z306CAJP Aug 6 22:20:29 Tower kernel: md: import disk1: [8,48] (sdd) ST4000DM000-1F2168_Z306CAJP size: 3907018532 Aug 6 22:20:29 Tower kernel: mdcmd (3): import 2 8,96 3907018532 ST4000DM000-1F2168_Z306CAND Aug 6 22:20:29 Tower kernel: md: import disk2: [8,96] (sdg) ST4000DM000-1F2168_Z306CAND size: 3907018532 Aug 6 22:20:29 Tower kernel: mdcmd (4): import 3 8,80 3907018532 ST4000DM000-1F2168_Z306CARR Aug 6 22:20:29 Tower kernel: md: import disk3: [8,80] (sdf) ST4000DM000-1F2168_Z306CARR size: 3907018532 Aug 6 22:20:29 Tower kernel: mdcmd (5): import 4 8,112 3907018532 ST4000DM000-1F2168_Z306CAK7 Aug 6 22:20:29 Tower kernel: md: import disk4: [8,112] (sdh) ST4000DM000-1F2168_Z306CAK7 size: 3907018532 Aug 6 22:20:29 Tower kernel: mdcmd (6): import 5 8,128 3907018532 ST4000DM000-1F2168_Z306CB0J Aug 6 22:20:29 Tower kernel: md: import disk5: [8,128] (sdi) ST4000DM000-1F2168_Z306CB0J size: 3907018532 Aug 6 22:20:29 Tower kernel: mdcmd (7): import 6 8,144 3907018532 ST4000DM000-1F2168_Z306CADF Aug 6 22:20:29 Tower kernel: md: import disk6: [8,144] (sdj) ST4000DM000-1F2168_Z306CADF size: 3907018532 Aug 6 22:20:29 Tower kernel: mdcmd (: import 7 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (9): import 8 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (10): import 9 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (11): import 10 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (12): import 11 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (13): import 12 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (14): import 13 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (15): import 14 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (16): import 15 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (17): import 16 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (18): import 17 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (19): import 18 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (20): import 19 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (21): import 20 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (22): import 21 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (23): import 22 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (24): import 23 0,0 Aug 6 22:20:29 Tower kernel: mdcmd (25): spinup 0 Aug 6 22:20:29 Tower kernel: mdcmd (26): spinup 1 Aug 6 22:20:29 Tower kernel: mdcmd (27): spinup 2 Aug 6 22:20:29 Tower kernel: mdcmd (28): spinup 3 Aug 6 22:20:29 Tower kernel: mdcmd (29): spinup 4 Aug 6 22:20:29 Tower kernel: mdcmd (30): spinup 5 Aug 6 22:20:29 Tower kernel: mdcmd (31): spinup 6 Aug 6 22:20:29 Tower kernel: mdcmd (32): set md_num_stripes 1280 Aug 6 22:20:29 Tower kernel: mdcmd (33): set md_write_limit 768 Aug 6 22:20:29 Tower kernel: mdcmd (34): set md_sync_window 384 Aug 6 22:20:29 Tower kernel: mdcmd (35): set spinup_group 0 0 Aug 6 22:20:29 Tower kernel: mdcmd (36): set spinup_group 1 0 Aug 6 22:20:29 Tower kernel: mdcmd (37): set spinup_group 2 0 Aug 6 22:20:29 Tower kernel: mdcmd (38): set spinup_group 3 0 Aug 6 22:20:29 Tower kernel: mdcmd (39): set spinup_group 4 0 Aug 6 22:20:29 Tower kernel: mdcmd (40): set spinup_group 5 0 Aug 6 22:20:29 Tower kernel: mdcmd (41): set spinup_group 6 0 Aug 6 22:20:29 Tower kernel: mdcmd (42): start STOPPED Aug 6 22:20:29 Tower kernel: md1: running, size: 3907018532 blocks Aug 6 22:20:29 Tower kernel: md2: running, size: 3907018532 blocks Aug 6 22:20:29 Tower kernel: md3: running, size: 3907018532 blocks Aug 6 22:20:29 Tower kernel: md4: running, size: 3907018532 blocks Aug 6 22:20:29 Tower kernel: md5: running, size: 3907018532 blocks Aug 6 22:20:29 Tower kernel: md6: running, size: 3907018532 blocks Aug 6 22:20:32 Tower kernel: mdcmd (43): check CORRECT Aug 6 22:20:32 Tower kernel: md: recovery thread woken up ... Aug 6 22:20:32 Tower kernel: md: recovery thread checking parity... Aug 6 22:20:32 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks. Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011536 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011544 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011552 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011560 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011568 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011576 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011584 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011592 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011600 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011608 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011616 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011624 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011632 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011640 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011648 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011656 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011664 Aug 6 22:21:40 Tower kernel: md: correcting parity, sector=21011672 Aug 6 22:21:40 Tower kernel: md: correcting parity, stopped logging
August 7, 20169 yr Community Expert You probably checked the "My parity is already valid" checkbox by mistake when you first created the array and the initial parity sync was never done, you can let the parity check finish but it will be a lot faster to do another new config and let the parity sync run.
August 7, 20169 yr Community Expert ...So, this is technically the first parity check I've done... Your subject line, and your first post said sync, and now you are saying check instead. And your syslog also says check. As we have already said, I don't think you ever did a sync, so parity was never right and you are going to be correcting it all unless you new config and build (sync) parity.
August 8, 20169 yr Author Cancelled the parity check/sync last night. Whichever it was. Planning on putting three of my old drives back in the server. As three of them were showing good in my last configuration/build before I purchase the new HDDs I'm using now. Anyway, I pretty much kept a log of everything on my old setup. Took a screenshot of the array/configuration so I could easily check which drives were good and which were the bad ones. But I took the screenshot of it under 'main' and not 'dashboard'. So now I don't know. Anyway, I've got the S.M.A.R.T. report from each of the drives. Are the most important things I'm looking at here reallocated sector count and reported uncorrect? They're the things I seem to remember my old set up warning me about. I'm pressuming the W1F1QYSN, W1F1QSND and Z1F1JVMB are the better drives. Here they are: Z1F1MT0C # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 111 99 6 Pre-fail Always Never 39577376 3 Spin up time 0x0003 94 93 0 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 20 Old age Always Never 522 5 Reallocated sector count 0x0033 100 100 10 Pre-fail Always Never 0 7 Seek error rate 0x000f 60 58 30 Pre-fail Always Never 12888491745 9 Power on hours 0x0032 73 73 0 Old age Always Never 24465 (2y, 9m, 15d, 9h) 10 Spin retry count 0x0013 100 100 97 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 20 Old age Always Never 89 183 Runtime bad block 0x0032 99 99 0 Old age Always Never 1 184 End-to-end error 0x0032 100 100 99 Old age Always Never 0 187 Reported uncorrect 0x0032 77 77 0 Old age Always Never 23 188 Command timeout 0x0032 100 100 0 Old age Always Never 0 0 0 189 High fly writes 0x003a 84 84 0 Old age Always Never 16 190 Airflow temperature cel 0x0022 62 42 45 Old age Always In the past 38 (0 156 45 30 0) 191 G-sense error rate 0x0032 100 100 0 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 0 Old age Always Never 80 193 Load cycle count 0x0032 88 88 0 Old age Always Never 25247 194 Temperature celsius 0x0022 38 58 0 Old age Always Never 38 (0 17 0 0 0) 197 Current pending sector 0x0012 100 100 0 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 0 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 0 Old age Always Never 0 240 Head flying hours 0x0000 100 253 0 Old age Offline Never 9112h+27m+02.949s 241 Total lbas written 0x0000 100 253 0 Old age Offline Never 23358484972 242 Total lbas read 0x0000 100 253 0 Old age Offline Never 3.97593E+11 W1F1QYSN # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 117 99 6 Pre-fail Always Never 163246672 3 Spin up time 0x0003 94 94 0 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 20 Old age Always Never 665 5 Reallocated sector count 0x0033 100 100 10 Pre-fail Always Never 0 7 Seek error rate 0x000f 62 59 30 Pre-fail Always Never 12890550925 9 Power on hours 0x0032 69 69 0 Old age Always Never 27389 (3y, 1m, 15d, 5h) 10 Spin retry count 0x0013 100 100 97 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 20 Old age Always Never 106 183 Runtime bad block 0x0032 100 100 0 Old age Always Never 0 184 End-to-end error 0x0032 100 100 99 Old age Always Never 0 187 Reported uncorrect 0x0032 100 100 0 Old age Always Never 0 188 Command timeout 0x0032 100 100 0 Old age Always Never 0 0 0 189 High fly writes 0x003a 100 100 0 Old age Always Never 0 190 Airflow temperature cel 0x0022 71 42 45 Old age Always In the past 29 (0 70 29 26 0) 191 G-sense error rate 0x0032 100 100 0 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 0 Old age Always Never 75 193 Load cycle count 0x0032 87 87 0 Old age Always Never 26447 194 Temperature celsius 0x0022 29 58 0 Old age Always Never 29 (0 16 0 0 0) 197 Current pending sector 0x0012 100 100 0 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 0 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 186 0 Old age Always Never 19 240 Head flying hours 0x0000 100 253 0 Old age Offline Never 9580h+47m+58.494s 241 Total lbas written 0x0000 100 253 0 Old age Offline Never 27427266878 242 Total lbas read 0x0000 100 253 0 Old age Offline Never 4.42502E+11 W1F1QSND # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 117 99 6 Pre-fail Always Never 163592672 3 Spin up time 0x0003 94 94 0 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 20 Old age Always Never 582 5 Reallocated sector count 0x0033 100 100 10 Pre-fail Always Never 0 7 Seek error rate 0x000f 66 60 30 Pre-fail Always Never 5007660 9 Power on hours 0x0032 69 69 0 Old age Always Never 27374 (3y, 1m, 14d, 14h) 10 Spin retry count 0x0013 100 100 97 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 20 Old age Always Never 110 183 Runtime bad block 0x0032 100 100 0 Old age Always Never 0 184 End-to-end error 0x0032 100 100 99 Old age Always Never 0 187 Reported uncorrect 0x0032 100 100 0 Old age Always Never 0 188 Command timeout 0x0032 100 100 0 Old age Always Never 0 0 0 189 High fly writes 0x003a 95 95 0 Old age Always Never 5 190 Airflow temperature cel 0x0022 69 43 45 Old age Always In the past 31 (0 23 31 26 0) 191 G-sense error rate 0x0032 100 100 0 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 0 Old age Always Never 87 193 Load cycle count 0x0032 88 88 0 Old age Always Never 24756 194 Temperature celsius 0x0022 31 57 0 Old age Always Never 31 (0 16 0 0 0) 197 Current pending sector 0x0012 100 100 0 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 0 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 0 Old age Always Never 34 240 Head flying hours 0x0000 100 253 0 Old age Offline Never 9044h+59m+10.607s 241 Total lbas written 0x0000 100 253 0 Old age Offline Never 17446265236 242 Total lbas read 0x0000 100 253 0 Old age Offline Never 4.14948E+11 Z1F1JVMB # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 118 99 6 Pre-fail Always Never 197471880 3 Spin up time 0x0003 94 94 0 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 20 Old age Always Never 518 5 Reallocated sector count 0x0033 100 100 10 Pre-fail Always Never 0 7 Seek error rate 0x000f 60 59 30 Pre-fail Always Never 17183647663 9 Power on hours 0x0032 73 73 0 Old age Always Never 24493 (2y, 9m, 16d, 13h) 10 Spin retry count 0x0013 100 100 97 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 20 Old age Always Never 83 183 Runtime bad block 0x0032 99 99 0 Old age Always Never 1 184 End-to-end error 0x0032 100 100 99 Old age Always Never 0 187 Reported uncorrect 0x0032 100 100 0 Old age Always Never 0 188 Command timeout 0x0032 100 100 0 Old age Always Never 0 0 0 189 High fly writes 0x003a 100 100 0 Old age Always Never 0 190 Airflow temperature cel 0x0022 71 40 45 Old age Always In the past 29 (0 153 29 27 0) 191 G-sense error rate 0x0032 100 100 0 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 0 Old age Always Never 74 193 Load cycle count 0x0032 88 88 0 Old age Always Never 25385 194 Temperature celsius 0x0022 29 60 0 Old age Always Never 29 (0 17 0 0 0) 197 Current pending sector 0x0012 100 100 0 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 0 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 0 Old age Always Never 0 240 Head flying hours 0x0000 100 253 0 Old age Offline Never 9186h+14m+47.913s 241 Total lbas written 0x0000 100 253 0 Old age Offline Never 29197556346 242 Total lbas read 0x0000 100 253 0 Old age Offline Never 4.03462E+11 Z1F4VWB5 # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 114 83 6 Pre-fail Always Never 76954368 3 Spin up time 0x0003 93 93 0 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 20 Old age Always Never 83 5 Reallocated sector count 0x0033 98 98 10 Pre-fail Always Never 2152 7 Seek error rate 0x000f 64 60 30 Pre-fail Always Never 3023804 9 Power on hours 0x0032 84 84 0 Old age Always Never 14538 (1y, 7m, 27d, 18h) 10 Spin retry count 0x0013 100 100 97 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 20 Old age Always Never 68 183 Runtime bad block 0x0032 100 100 0 Old age Always Never 0 184 End-to-end error 0x0032 100 100 99 Old age Always Never 0 187 Reported uncorrect 0x0032 1 1 0 Old age Always Never 200 188 Command timeout 0x0032 100 94 0 Old age Always Never 0 0 8 189 High fly writes 0x003a 21 21 0 Old age Always Never 79 190 Airflow temperature cel 0x0022 71 42 45 Old age Always In the past 29 (0 76 29 26 0) 191 G-sense error rate 0x0032 100 100 0 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 0 Old age Always Never 68 193 Load cycle count 0x0032 88 88 0 Old age Always Never 24023 194 Temperature celsius 0x0022 29 58 0 Old age Always Never 29 (0 17 0 0 0) 197 Current pending sector 0x0012 100 91 0 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 91 0 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 198 0 Old age Always Never 66 240 Head flying hours 0x0000 100 253 0 Old age Offline Never 9016h+41m+10.933s 241 Total lbas written 0x0000 100 253 0 Old age Offline Never 12262031546 242 Total lbas read 0x0000 100 253 0 Old age Offline Never 3.23161E+11
August 8, 20169 yr Yes, those 3 drives look fine. I'd do a New Config, and include those 3 drives along with your new drives in the config, but do NOT assign a parity drive. Then Start the array, and confirm you can see the data on those 3 drives okay; and that the new drives you included are formatted and ready to use. If not, you can format those drives -- assuming you did not have any data on them from your aborted attempt. Once the array looks good, NOW Stop the array and assign your parity drive (or drives if you're going to use 6.2). Be CERTAIN you assign the correct drives as the parity drive(s) => NOT one of your old drives that has data on it. Then Start the array and it will do the initial Parity Sync. Be CERTAIN you DO NOT check the "parity is already valid" box => I suspect that's what you did incorrectly before.
Archived
This topic is now archived and is closed to further replies.