February 8, 201313 yr Motherboard claims it's a "MAXIMUS V GENE" (never heard of it) with 8GB of RAM, 2.9GHz dual core CPU, Intel gigabit NIC, 8 onboard 6 Gbps SATA ports, and 2 SAS cards both reporting "PCI-E x8, Bandwidth Usage: 5.0 Gbps" with an unknown number of SATA ports. It's a lot of machine just to make a shared flash drive available on the network! This entire NAS is providing network access to only a couple of hundred megabytes of free storage! No issues noted, but you haven't tested it yet. A better test is to load it up with drives, build parity, then run a parity check.
February 8, 201313 yr Author What I did was to change the board to the Gene V board and then run the free a version of unraid with all hdd disconnected. I did this to make sure everything loaded properly on the new gene v board. If you say the syslog is good that I shall start the server with my normal unraid pro USB!
February 8, 201313 yr I know, but it just looked funny there, all those capabilities and not a single hard drive! Time to load it up and go! I could not tell much about the SAS cards, as both identified themselves to the kernel, but neither exposed any drive slots. I'm normally used to seeing an indication of empty slots, but this syslog did not acknowledge any slots, empty or otherwise. However that may be normal for this card when empty.
February 8, 201313 yr Author I pluged everything back in and now it's saying reboot and select proper boot device etc. even though it was booting the free unraid fine. Now what do I do?
February 8, 201313 yr Author My fault. Forget to set the boot order. Attached is my new syslog. Anything to worry about? New_Text_Document.txt
February 8, 201313 yr Looks fine, except it's an even older UnRAID release, with an older mvsas driver. I would upgrade to RC11. I would recommend any user with any SAS cards to stay up-to-date with UnRAID releases, because none of these SAS drivers look very mature to me, although they are improving.
February 8, 201313 yr Author The problem is RC6, RC8a makes one hdd red ball during parity checks. Therefore I am worried that RC11a will do the same thing. RC5 does not do this and I have been running rc5 for ages.
Archived
This topic is now archived and is closed to further replies.