Steel275

I had a similar problem with my card (granted, that was a Marvell 6480 card, not the same as yours). But my card turned out not to have any firmware on it at all (no joke), which is why it never "booted". After I flashed a proper firmware, it worked perfectly. Not sure if this is a possible scenario in your case, of if you just have a dodgy riser.

Yes, the other one also contained a different utility, but I went with this one. It turns out that the card HAD NO FIRMWARE AT ALL! Not sure how that is possible, or how that works, but I guess it just runs in a "bypass" mode or something. After flashing 3.1.0.21, I get messages and setup utility during boot, the disks spin up and XPEnology works! Thanks a lot!

Ok, no luck cold booting with onboard SATA off. Aha, that might do the trick. I don't get any messages from the Marvell controller at all during boot (which confused, there's usually something). I wil try it. Yes, Marvell 6480 is on there. I suspected as much. I'm not going to run more than that, so that's ok.

*UPDATE* I have now spent the evening digging through debug.log, dmesg and BIOS. It seems there are several problems here: 1. When ever i start the machine from powered off, the drives don't spin up until the mvsas driver is loaded by xpenology. As it does this, it doesn't wait long enough for the disks to spin up and initialize (I found that SATA drives are slower to finish than SAS drives, this might be part of it?). And since XPEnology doesn't seem to work well with hot swap, it never detects the remaining drives. Hence the "configuration lost" message, since it detects disks missing. Is there any way of extending this timeout? If I then reboot or reset the machine, everything is working after boot. No configuration is actually lost. 2. The SAS card in combination with the onboard SATA controller (total 8 + 6 = 14 possible drives) somehow crashes the disk handler on boot (general protection fault) as it reaches drive 13. The stack trace shows SetSCSIHostLedStatusBy9235GPIOandAHCISGPIO being the culprit. I have logs saved if anyone is interested. I disabled the onboard SATA controller, and now the machine boots as it should and detects all eight drives. I still need to test cold booting after doing all this, but the server is expanding a volume at the moment. I'll be back!

I have created the USB stick using the IMG file and dd. Maybe I should try using the ISO and Unetbootin instead... Does XPEnology write anything to the USB stick? Since you can use and ISO, my guess is "no"? I have re-written the USB stick several times already, but only from the IMG file.

I have installed XPEnology on my newly built NAS. It works perfectly, until I reboot. It seems that a normal reboot is fine, but if the server is turned off and on again, all configuration is lost. I get the reinstall screen when I access the NAS and have to start over again. The data is still there, the volumes are detected, but all config is reset. Is this fixable, and why does it happen? Also, if I use more than 6 drives, only 6 are detected (different 6 every reboot... ). Hardware: * Gigabyte B85M-DS3H-A motherboard * Pentium G3258 CPU * 8 GB DDR3 RAM * Supermicro AOC-SASLP-MV8 SAS HBA controller (Marvell 6480 chip) * Supermicro SC825 case with 8x hotswap drives.