Greetings everyone,
I am very new to the unraid party. I just made the move from Synology to unraid when I snagged a deal on some hardware. Things have been going very well for the most part. I have several docker containers and a gaming vm working just how I want. I have 8 10TB drives for my system. 4 that I used to seed the server and 4 that will be coming from my Synology. I haven't actually inserted the 4 from the Synology yet as I was waiting to make sure I have all the kinks ironed out first in case I need to roll back.
Since I have (or will have) 8 disks in my array and my mobo only has 8 sata headers, I figured I had better get a SAS controller so that I can expand when I'm ready to. I have a friend that gifted me an LSI 9207 card that he pulled from some box he didn't need anymore.
My issue arises when I insert my LSI 9207 and try to start my array. The server boots up and unraid seems to be happy until I actually start the array. When the array is started it seems that my configuration files go out the window. My dark unraid theme changes back to default, my temperature sensors change back to Celsius, my shares all disappear, docker and vms are disabled...you get the idea. With the LSI card in place, I am not able to stop the array once it has been started. I am able to perform a clean shutdown though. If I remove the LSI card then I can start/stop my array all day long and my configuration stays in place.
I did manage to pull the syslog and diagnostics with the LSI card inserted, and I think I can see the issue in syslog. I will attach the full zips to this thread, but I'll paste the interesting piece that stands out to me. It is in regards to my flash drive that is hosting unraid. From what I've seen in other unraid threads, usually when you see read errors on your unraid flash drive you should replace it. However, I don't think this is symptomatic of a bad flash drive since I know the cause of the problem is inserting the LSI card and the solution is removing the LSI card.
Aug 12 20:04:19 Tower root: cp: cannot create regular file '/boot/config': Input/output error
Aug 12 20:04:19 Tower kernel: FAT-fs (sda1): FAT read failed (blocknr 169)
Aug 12 20:04:21 Tower root: Starting Samba: /usr/sbin/nmbd -D
Aug 12 20:04:21 Tower root: /usr/sbin/smbd -D
Aug 12 20:04:21 Tower root: /usr/sbin/winbindd -D
Aug 12 20:04:21 Tower kernel: fat__get_entry: 310 callbacks suppressed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29364) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29365) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29366) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29367) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29368) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29369) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29370) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29371) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29372) failed
Aug 12 20:04:21 Tower kernel: FAT-fs (sda1): Directory bread(block 29373) failed
On a side note, the LSI card is running version 17 and is already in IT mode. I did attach a drive to the card and before I start the array, I can see my drive as I would expect to in the unassigned devices section. For most of my testing, I don't even have the SAS cable attached to the card. So I don't think this is an issue with any of the drives. I know that I can update the software on the card to 20, but was hoping to avoid doing that unless there was a good reason.
Any input would be greatly appreciated. Thank you in advance.
-Ed
tower-diagnostics-20190813-0043.zip
tower-syslog-20190813-0109.zip