Tong6998

This please. And the Intel C2750. Thanks and keep up the good work.

1) - Yes 2) - Let it boot 3) - Always manual update to latest pat file. NEVER AUTO.

Ok still getting the trigger error with those settings, but still finishes booting. I video'd the whole boot process to watch one thing fail that has been flying by too fast to see, and here's the only thing that failed on boot: Loading Module aacraid [FAILED] Did same thing in debug mode and got a little more: Loading Module aacraid [Failed] (bunch of illegible numbers 5.795214 I think) Adaptec aacraid driver 1.2.1.50639 Anyone know where it stores the debug log file? Looks like a temp directory but I don't know how to access it.

Thanks, I did not know this about the OS, makes sense though. Just went through my link at home, and can't seem to find the link I had with the back-plane. All I remember is there were a few people mentioning an issue and that they had replaced them through warranty from Silverstone, and one of the users mentioned his was V1.4. On another note, I have reset my bios to stock, and changed only SMART and disabled 9172, along with both serial ports, and I still get the trigger on boot error. However it does finish booting. Hmm any chance I can get you to go through your bios with a fine tooth comb?

Ok, after looking at some pictures online, the version and date for the drive cage are stamped on the back (motherboard side). For the life of me I can't find the issue I had found with the backplanes here on phone, hopefully I still have the site loaded at home.

I installed the OS on a SSD just cause I'm paranoid and old school, if the drive dies I can just replace the OS, if the raid goes out, the OS is independent of that. The backplane is actually written on the board(don't remember if it was on the inside or on the back, I'll check when I get home), they are up to 1.4 from what I googled. Apparently they have some issues/problems with the backplanes, I got the links saved at home with it, or you can Google it.

Hmmm, wondering what I might be doing wrong... Mine as SE9230+C2750 SATA2+C2750 SATA3 still gives me the trigger error but finishes booting. I wonder what settings I have different than you. Both serial ports are turned off along with 9172 and I think that's it.... I put an internal USB header adapter on the board with the thumb drive for the loader, then dropped a 16Gb ssd in it for the the OS, so that leaves me with one more internal drive for something... Too bad you can't put the OS on another thumbdrive, that would free us the 2 ports for SSD's for caching.

Update: XPEnoboot 5.2-5644.5 Bare Metal install added line to syslinux.cfg as such: APPEND iommu=pt root=/dev/md0 ihd_num=0 netif_num=4 ......... Nothing changed on boot. SE9230+SE9172+C2750 SATA2 = Working (with Trigger device plug event) SE9230+SE9172+C2750 SATA2+C2750 SATA3 = NOT Working (trigger device plug event but freezes whole system after about 45 seconds (reset button on board won't even work) SE9230+C2750 SATA2+C2750 SATA3 = Working (with Trigger device plug event) SE9230+SE9172+C2750 SATA2+C2750 SATA3= Works if C2750 SATA2 is in IDE mode but nothing will register on SATA2 or what does shows up as esata but can't do anything with it.) All the ways I tested still produce this result: =trigger device plug event=. Most modes still produce the trigger error, but after a few seconds it produces login and finishes the boot. So either way I get 10 usable ports, which way is recommended? : SE9230+SE9172+C2750 SATA2 ---or--- SE9230+C2750 SATA2+C2750 SATA3 Do you still get the "=trigger device plug event=" ? And before I start buying and loading HDD's, can I use the rest of the slots I have as a single volume with SHR without any issues? And what are you guys using for case? I got a DS380 and dang it's cramped, I just ordered a bunch of 10" sata cables to throw in there to see if it "frees up" space.

Tried this just now, still no go. Here's specifics: XPEnoboot 5.2-5644.5 Bare Metal install added line to syslinux.cfg as such: APPEND iommu=pt root=/dev/md0 ihd_num=0 netif_num=4 ......... SE9230+SE9172+C2750 SATA2 = Working SE9230+SE9172+C2750 SATA2+C2750 SATA3 = NOT Working SE9230+SE9172+C2750 SATA2+C2750 SATA3= will work if C2750 SATA2 is in IDE mode but nothing will register or what does shows up as esata but can't do anything with it.) SE9230+SE9172+C2750 SATA2 = Works but still has trigger error. All the ways I tested still produce this result: =trigger device plug event=, however, SE9230+SE9172+C2750 SATA2+C2750 SATA3 will not continue booting, freezes whole system after about 45 seconds (reset button on board won't even work). All other modes still produce the trigger error, but after a few seconds it produces login and finishes the boot. Anything anyone want me to try? This is a fresh install with nothing on it yet, so I can try everything you want me to. Just make sure you give me detailed instruction, I'm a linux noob and a xpenology virgin until last week.