Morveus

I understand now! I sent the forward breakout cables back to the seller and bought reverse breakout cables. I'm a bit relieved Thanks

Hi, I just received my new rackmount chassis (https://www.xcase.co.uk/collections/4u-rackmount-cases/products/x-case-extra-value-rm-424-24-hotswap-bays), moved the hardware into the case and plugged my first 11 disks. I'm currently using three brand new "SFF8087 to 4x SATA" cables (https://www.amazon.fr/gp/product/B00S7KTWPE) to connect the first rows of disks to the motherboard and to some old SATA RAID controllers. The server turns on correctly, the 11 first disk tray LEDs are lit (blue), but not a single disk is detected by the motherboard. unRAID then loads successfully, obviously showing all disks as missing. Did I choose the wrong SAS to SATA breakout cables? What else should I check? I tried removing the old SATA controllers and only using the motherboard's SATA ports to begin with, but still no luck. The mobo is an Asus P8H77-V with an Intel Core i5. Thank you for your help Edit: I'm guessing its because of the cables, from what I gather the ones I bought are meant to connect 4 SATA drives to a controller, and not a SAS backplane to a controller like I'm doing right now...

Hi ! Yesterday one of my drive has been disabled without me having the time to notice problems (it had been returning errors for about a week, according to the log ; unRAID disabled the disk avec 10k errors). The first thing I did was to stop the machine, check the cables and restart the server. unRAID then tried to check the parity, found parity sync errors, and after a few hours the disk was disabled again (after exactly 1733 errors). Here are the errors : First, parity sync errors Then "ata" errors : And finally : (hundreds of occurrences) (a few occurrences) I'm getting a new disk tomorrow, but I'm worried about those parity sync errors. From what I could understand, there are two possible scenarios: 1) It's the disk that has those errors, in that case when rebuilding on a new disk I won't loose data 2) It's the parity disk that has errors, in that case if I rebuild on a new disk, data corruption will ensue. Is that correct ? I'm pretty sure that the faulty disk isn't completely dead, and could be plugged into a computer to recover some files. In the event of scenario #2 happening in a few days (after rebuilding), how can I compare data from the "old" disk with data from the "new, rebuilt" disk and replace corrupt files if needed? (I'm thinking "recursive MD5 check" for instance, but don't know where to start). Thank you! Edit : adding attachment "syslog" syslog.txt

I would be interested too.

Well, that'd be nice !

Hi and thank you both for your replies. I'm taking note that I need the new preclear script for unRAID 6. I wouldn't have thought of that. Using a spare laptop is a great idea. I happen to have a few unused laptops with eSATA ports, I'll be giving it a try ! Thank you !

Hi, One of my 2TB disks is dying, so I'm going to replace it this week with a 4TB disk. I would like to preclear the new 4TB using an USB adapter. I've already done this, the preclear went through without any problem, but after installing the hard drive on a SATA port and powering the machine on, it's like unRAID had "forgotten" about this disk. I had to clear it again (plugged to a SATA port) before adding it to the array. Is preclearing using an USB to SATA adapter possible? My problem is that I don't have any free SATA port, so I'd like to leave the array running while preclearing new disks since it takes days to clear a 4TB HDD. I'm asking this before trying mostly because of the very long time it would take to "check" if it works. Thank you!