kc8hnz

They both passed pre-clear for two runs, so I they are good solid drives. I think I'll wait till the monthly check.

Good morning! I just upgraded to a larger parity disk (10 TB to duel 14 TB) and going to finish the sync in a few hours. Is it worthwhile at all to do a parity check afterwards to verify everything went as planned or is it overkill and unlikely to mess up when writing the parity the first time? This is only the second time writing parity from scratch since building the server. Thanks! Jason

I was looking to expand my cache pool with a few SATA SSDs, so I attempted to move my existing four SATA HDDs to my disk shelf. (These were my first four disks before getting the shelf, hence still on SATA) What I discovered was that the SATA ports append the 'WDC_' tag on the front of the drive serial number, where as the the disk shelf drops the tag at the beginning: I overlooked this at first, and moved the drives over to the shelf only to discover on boot Unraid could not find the drives based on serial number, instead they were in unassigned devices minus the WDC_ tag. When I tried to assign them to the correct slot, they were treated as replacement disks and naturally since four drives went missing it would not mount. I swapped the drives back and the array mounted normally. So, now I am in a conundrum. I need to swap them out, but I'm thinking I need to get a spare drive and do a drive replacement one at a time, which will likely take days. Do I have any other alternative at this point?

Quick question on the Dell controllers. Did you replace both IOM6 controllers with two Dell controllers or just one and leave the second in place? I also am using the Netapp HBA with an IOM3 controller and have similar issues so am looking to perform a similar upgrade. Word to the wise: the Netapp HBA's price might be tempting, but its just not worth it....

I built my server about three months ago and originally went with a 1TB Intell 660p M.2 SSD. Alas, I didn't do my homework and didn't realize the new QLC flash is significantly less reliable over time than the older types. Out of a 200 TBW suggested lifetime, I've used 120 TBW, so needless to say I need to replace it sooner than later. Since I use it more or less as a scratch disk before writing what I need to keep to the array over night, I was thinking of going with 3-4 500 GB or 1 TB 7200 rpm standard hard disks striped at RAID 0, and make sure nothing of value is kept on them for longer than absolutely necessary. While not nvme speeds, would this approach decent SATA SSD speeds all the while eliminating the excessive wear on a SSD? Or would a heavy duty SSD like a 860 pro be more suited to my use case? Thanks for any advice!

Solved it! So turns out I had a bad interposer from the e-bay seller. Went to Best Buy and bought a extra 10TB easystore to swap the interposer to and the error followed. Swapped it out with a different one and all is well, plus got a total of 30TB getting added to the array rather than the planned 20TB 🙂

So preclear failed last night. The disk is not displaying any SMART data, so I'm wondering if there is an issue with the diskshelf oe cableing. any clues? Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: Writing signature: 0 0 2 0 0 255 255 255 1 0 0 0 255 255 255 255 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: Failed test 1: MBR signature is not valid, byte 3 [00000] != [00170] Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: array 'sectors' Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 0 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 1 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 2 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 3 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 4 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 5 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 6 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 7 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 8 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 9 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 10 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 11 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 12 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 13 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 14 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 15 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 16 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 17 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 18 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 19 -> 00000 Jan 26 14:28:30 preclear_disk_2YK9A9MD_20685: 20 -> 00000 Jan 26 14:28:31 preclear_disk_2YK9A9MD_20685: cat: /tmp/.preclear/sdg/smart_error: No such file or directory Jan 26 14:28:31 preclear_disk_2YK9A9MD_20685: error encountered, exiting...

Good evening! I've had my server up and running for three months now, but decided to expand to a disk array. I installed a Netapp X2065A-R6 hba card and connected it to a DS4243 via an official Netapp qsfp cable. Install seamed to go smoothly and I see the two new 10TB WD shucked drives. However, one of the disks lists its status as spun down, and clicking spin up does nothing. Further, when starting preclear, it currently seams to be pre-reading just fine. Any ideas whats going on here?