JorgeB

Stop array, unassign the disable disk, start array, check that the emulated disk is still mounting, stop array, re-assign the disk, start array to begin rebuilding.

Grab current diags, reboot, grab new diags and post both here.

Parity appears OK, if you haven't yet you should replace cables then you can try re-enabling parity to see if the emulated disk is better then the current one: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments are correct -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk12 -Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk -If the emulated disk mounts and contents look correct stop the array -Data on current disk12 should be in very bad shape, but if you want to check it later rebuild using a new disk.

Cache filesystem is corrupt, you should backup and re-format.

Max theoretical performance is 8 x 600MB/s, but in practice and due to overhead you should get 550/560MB/s max. You can use the slot but performance will be the same, since it will still link @ x8, even if it linked at x16 performance with 8 drives would be the same, since the limit here is the SATA speed.

You can click on the docker to go to the appropriate support thread:

Disks are formatted with type 2 protection, try removing that, you can find out how by googling it.

Pretty sure the 9260-8i can't be flashed to IT mode, you should by a non MegaRAID model, like the 9211-8i.

They should have a blue icon, try this: Unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), start array.

According to that there are two missing pool devices.

If you disable parity you can defrag them all the same time.

Ah, OK, then post current diags please.

Post diags after this.

Apr 12 19:09:38 Tower kernel: md: disk2 read error, sector=1216325224 Apr 12 19:09:38 Tower kernel: md: disk3 read error, sector=1216327048 You're having issues with multiple disks in different controllers, so possibly a power/connection problem.

With parity is what I would recommend.

Yes. Could be some compatibility issues with those disks, what are they, some white label?

Only if you disable parity, or it would be hammered and take much longer.

This is usually a flash problem or not enough RAM, should have at least 4GB.

You should get around 8 x 550MB/s on either slot, since the HBA is x8, more info below.

Difficult to see what the problem is, your visualizing Unraid which is not supported and I have no experience with, also using a RAID controller which is not recommended. Are you using SAS interposers with the SATA disks?

That file only contains individual device settings, you can change anything else in the GUI.

Kind of a strange issue, you're getting errors in multiple disks, all connected to the onboard SATA ports, and they are reported as a disk problem, try replacing those cables and/or connect those disks to the LSI instead.

Like this:

Without rebooting run a non correcting check, if more errors are found post new diags and there's a problem for sure, if not most likely the result of an unclean shutdown since last check.

That only applies when connecting the HBA to a SAS expander or backplane with a built in SAS expander, one cable=single link, two cables=dual link.