March 2, 20188 yr Hi Guys, I've been using unRAID for 5 years or more. I finally decided to move from my PCI-X controllers to a LSI 9201-16i. I installed the controller and moved one drive over. The server came back up, but I get a red X for the status of the drive. I stopped the array, unassigned and reassigned the drive and I still get the red X for the status of the drive. I can go into the drive details and see the smart data for the drive and what not. I can even unassign and reassign the drive to the second parity drive slot if I wanted to, don't worry I didn't. This just seems really weird to me as I thought that moving to a new controller would be relatively painless. Any help or pointers that you can give me would be greatly appreciated.
March 2, 20188 yr Community Expert The red X means that a write to the drive has failed and is now no longer consistent with parity. The way to clear the red X is to rebuild the drive. Simply unassigning and re-assigning the drive will not achieve this. Normally moving the drives over is painless as long as the new controller recognises the serial number of the drive the same way (which appears to be the case here as unRAID is not complaining about it being the wrong disk. Not sure why you have the red X in this case. Since it is the drive that you moved over It could be something to do with the new controller or the cabling to the drive. Cabling tends to be the commonest cause.
Archived
This topic is now archived and is closed to further replies.