jang430

It seems I may have found the root cause. The power I used to connect to the drives that are causing problems came from a molex to sata splitter because I don't have enough sata power. When I connected the Molex from the PSU and the Molex from this splitter, I may have not connected them securely. Though there's power, it seems whatever drive I'm connecting to it is encountering problems. I've changed Sata cables, connected to onboard ports. I've changed to other onboard ports also, until I finally looked at this sata power issue. I tried to secure the 2 molex sides properly, and so far, I've finished my parity rebuilding, I've attached other drives to this same power connector, and performed heavy transfers using Unbalance plugin, so far so good. Never would have suspected this if I didn't ran out of other things to troubleshoot already.

Indeed, the whole share will not fit a single disk. So I have to go down to subfolder level so it can split up across disks?

Hi. I've got 2 TB data on a 4 TB drive. I'd like to move out the data to 2 units of 1 TB drive, both just finished pre-clearing. It won't fit. I've also added another 1 TB drive to the destination, also free of data, though not recently pre-cleared. All are using XFS. My share level is 3, Media/ HDMovies/Movies/Movie_names/Movie_files. I've been trying to plan, and it says it's not enough. It asks me to check minimum space for share, 1 changed it to 1 GB. Still it won't work. Don't know where to start looking. How do I proceed to scatter the files in my 4 TB drive? Is there any log I can provide to request for help?

Ok. Noted. Thanks. Will investigate further. Sent from my iPhone using Tapatalk

When you say connection problem, do you mean maybe how the card is seated, or maybe not seated properly? Also, whether the cables are connected to the drives properly? The hba is in a case node 804 that has front and back fans in the motherboard chamber. Though due to planning to upgrade drives, I kept case open, apart from fans in front and back still functioning. Is this not enough? Sent from my iPhone using Tapatalk

If I did that, it is not because I made it. Where do you do or undo that? Never tried safe mode, since I never thought it was any of the containers and plug-ins causing the problem. Sent from my iPhone using Tapatalk

Though the parity is directly connected onboard, the drive that it is reading from is connected to the hba controller. Could this also cause that to happen? The case is currently wide open and air cooled. Sent from my iPhone using Tapatalk

Parity disk is brand new though. Recently passed Pre clearing. Sent from my iPhone using Tapatalk

I have accessed shows from the array. It seems without any heavy transfer or access, the array seems to be working fine. I am afraid to do anything heavy right now. Hope you can help point out possible cause to these issues

I interrupted the rebuilding of parity and just restarted the NAS. I don’t see any parity now, but array is working fine, I don’t see any errors in the main page. What could this possibly be? tower-diagnostics-20190818-0538.zip

While rebuilding parity, I am seeing a lot of errors, though the array is accessible. Is this normal? Could it finally be my Dell Perc H310 that is causing problems? Any way to find out? I'm using new SFF-8087 cables already. tower-diagnostics-20190818-0437.zip

Hi. I suffered 2 drive failures. 1 of them is the parity, and another 1 is data drive. Since I will have to rebuild parity, I will take this opportunity to assign drives to the array. I've taken the data drive that failed, and copied the contents to a new drive (Drive X). I want to add Drive X to the array, before it starts rebuilding parity. I want to keep all data in all other drives, and Drive X. Do I just assign Drive X to a new slot, assign a drive to parity, do a new config, and start?

I can see files being copied since the other drive is increasing in size. It's also in unassigned, not joined in array. Sent from my iPhone using Tapatalk

I would have preferred moving, but unintentionally, I must have selected copy instead. How can I verify before deleting files?

Great plan @johnnie.black I hope I can get some files out of disk3 still.

so as you can see, I have disk 3 that's currently disabled due to drive failed. What steps do I start with to recover as much as possible :D?

Hi. This is the new diagnostics with parity connected directly to M/B. Also swapped the PSU connector with another drive. tower-diagnostics-20190814-2334.zip

I've done some further testing. I've switched power between drives, still the same problem. I've connected the parity drive directly to M/B instead of connected to HBA controller, (using regular sata cable) still having the same problems. I'm attaching a screenshot here. My Drive 3 is also disabled since I think it died first before the parity. Won't array start without parity? Any suggestion what to do next?

Thanks. Will investigate further.

so parity drive has issue? it's one of the older drives as well.

OK. Using new cable already. But will remove from case, and try again.. Is it possible that it's a PSU problem?

So I got a new set of cables, just arrived today. No mess. Connected the cables, and now, I have only 1 drive says mounting. Nothing happening. Array not started. Please help. Attaching diagnostics. BTW, changed to a different slot of PCIe already. tower-diagnostics-20190814-1218.zip

@itimpi, reseating the hba controller didn't help. but unrolling my SFF8087 breakout cable did. Now, able to access my array without problems. It also performed a parity check, and found 0 errors. Could it be possible that both my SFF8087 cables failed at the same time? To be honest, I highly doubt it. But I don't have additional cables to troubleshoot. My cables since long, were a bit rolled. But it has been like that before. I've only removed, and reseated my HBA controller. Don't know why this happened.

BTW, I forgot to mention that it starts out ok. No errors. I can even access shares, then after a few minutes, those errors showed. I've removed it, and placed it well once again. But ok, will move slots this time. Any other suggestions from other members? Hope this is not the end of my HBA Thanks itimpi

Reads are 22,617,230,667,232, Writes are 22,617,230,667,232. And of course, thousands of errors. Aug 10 21:12:27 Tower kernel: md: disk1 read error, sector=39195248 Aug 10 21:12:27 Tower kernel: md: disk2 read error, sector=39195248 Aug 10 21:12:27 Tower kernel: md: disk3 read error, sector=39195248 Aug 10 21:12:27 Tower kernel: md: disk4 read error, sector=39195248 Aug 10 21:12:27 Tower kernel: md: disk7 read error, sector=39195248 Aug 10 21:12:27 Tower kernel: md: disk8 read error, sector=39195248 Aug 10 21:12:27 Tower kernel: md: disk9 read error, sector=39195248 Aug 10 21:12:27 Tower kernel: md: disk0 read error, sector=39195248 Aug 10 21:12:27 Tower kernel: md: disk1 read error, sector=39195256 Aug 10 21:12:27 Tower kernel: md: disk2 read error, sector=39195256 Aug 10 21:12:27 Tower kernel: md: disk3 read error, sector=39195256 Aug 10 21:12:27 Tower kernel: md: disk4 read error, sector=39195256 Aug 10 21:12:27 Tower kernel: md: disk7 read error, sector=39195256 Aug 10 21:12:27 Tower kernel: md: disk8 read error, sector=39195256 Not sure if it's my HBA controller that I removed, and installed back again. Before that, it was ok. No spare HBA. As for the SFF-8087 cable, using 2 cables for 7 drives. Can't be possible that all drives are failing if 1 of the cables are defective. tower-diagnostics-20190810-1324.zip