April 18, 20179 yr Community Expert 18 minutes ago, karlpox said: on which drives do i need to do this besides disk4? Im already running xfs_repair -L on disk4. Before or after the webGUI hang?
April 18, 20179 yr Author After the webgui hang. I also did a filesystem check with disk2 (the drive that crashed on parity check) and found no errors. Was the xfs_repair on disk4 ok in my previous post?
April 18, 20179 yr Community Expert Try to start like this, if it crashes again grab the diags on the console or xfs_repair all remaining disks.
April 18, 20179 yr Community Expert neither: xfs_repair /dev/mdX -L only if it asks, -n wont attempt to fix any issues found.
April 19, 20179 yr Author the sync completed successfully! Im copying the files now again. Thank you so much for taking the time and helping me witht his!
April 19, 20179 yr Community Expert Just don't forget to never use the Marvell ports in the future, they were the cause of all your troubles.
April 22, 20179 yr Author Yah, I didnt use them anymore. So I added cheap sata controllers to add more hard drive. I added 2x 3TB WD Red to the array. After 20mins I get an error on one of the drives. Could the cheap sata controllers be the reason? Also will this be ok if they have errors? Will they still be added to the array? sobnology-diagnostics-20170422-1502.zip
April 22, 20179 yr Community Expert It can be the Sil controller (or a cable problem) but the disk isn't very healthy, there are a lot of reallocated sectors, you should run an extended SMART test on that disk, if it passes swap cables with another disk on a different controller, if same disk fails again it's probably bad. Edited April 22, 20179 yr by johnnie.black
Archived
This topic is now archived and is closed to further replies.