Everything posted by master.h
-
LSI Controller FW updates IR/IT modes
I also have a Dell PERC H310, and was having some issues with it. It would boot just fine in my test system (an old Asus P5N-D) but would not boot in either of my newer systems (Asus P7P55D-E Pro or a MSI 970A-G46). I ended up finding this post by MHzTweaker: http://lime-technology.com/forum/index.php?topic=28727.msg256252#msg256252 I ended up having to put a strip of electrical tape over pins B5 and B6 which apparently do this: As soon as I got that electrical tape on, they are booting just fine. Fireball3 posted here: http://lime-technology.com/forum/index.php?topic=12767.msg259006#msg259006 that he was able to flash to P16 firmware. I was not able to do so using his toolset. At the end of this post is a link to my dropbox that has the zip file I used to flash my card to Dell HBA IT firmware. I have also attached a picture of exactly the pins that need covered with the electrical tape. https://www.dropbox.com/s/4jednhrzbnt2tj6/Flash%20Dell%20PERC%20H310%20for%20unRAID%20-%20Custom%20instructions.zip
-
[Solved] PERC H310 causing system not to boot
SOLVED! Solved solved solved! I can across this post from MHzTweaker: http://lime-technology.com/forum/index.php?topic=28727.msg256252#msg256252. In turn, he had posted this link: http://yannickdekoeijer.blogspot.com/2012/04/modding-dell-perc-6-sas-raidcontroller.html Sure enough, after sticking a piece of electrical tape over pins B5 and B6, the card now boots on all of my systems. Attached is a picture. Once I had flashed the card, literally the electrical tape was the thing to get it to work. I've attached a picture of the card, and below is a link to the zip file I used to flash the card. Instructions are in the file. I'll also update the LSI controller thread. https://www.dropbox.com/s/l4kadyukkh2w497/Flash%20Dell%20PERC%20H310%20for%20unRAID.zip
-
[Solved] PERC H310 causing system not to boot
Still no luck. Followed your suggestions, still no boot. I have tried all available PCI2 x16 slots in all of my machines. Only works on the old Asus P5N-D. I tried it in a third system with an AMD board, exact same results (this board doesn't have the memOK feature though). I even have a second, non-flashed H310 that performs exactly the same as the one I flashed (except in the working system, it goes through the BIOS of the card and doesn't work with unraid). Won't boot on the two other systems.
-
[Solved] PERC H310 causing system not to boot
I removed and re-seated both the card and the RAM multiple times, each with the same results: no booting when the H310 is installed. After the first couple times reseating the card, I stopped screwing it in and just let it sit there. I tried removing 3 sticks of RAM and running with one stick in slot B1 with the same results. I will try tonight though running with one stick at a time in each slot and post back with results.
-
[Solved] PERC H310 causing system not to boot
I flashed a H310 with dell HBA firmware using my test system (ASUS P5N-D, 8GB PC2 RAM, Intel Core 2 Duo) and everything went flawless. However, when I moved the RAID card over to my main system (ASUS P7P55D-E Pro, 10GB PC3 RAM, Intel Core i3), it will not even boot. Everything powers on, but it never goes to BIOS or anything. There is a feature on my motherboard called the "MemOK" light. It's an LED that lights up whenever it detects a memory issue. This light comes on every single time I try to boot with the H310 installed. If I remove the H310 and literally touch nothing else, the system starts up fine. Put the H310 back in, light comes on, system won't boot. Does anyone have any ideas?
-
VirtualBox Plugin for unRAID v5 and v6
Please post the output of: VBoxManage list vms Here it is: root@Saidin:~# VBoxManage list vms "<inaccessible>" {7640ff16-f7ea-46a1-900e-527a2bd11992} "SaidinW7VM" {e7894331-f286-4fe4-b803-f41e060d01f1}
-
VirtualBox Plugin for unRAID v5 and v6
I have an issue where a blank VM is showing up in the settings page (see attachment). I think what happened was I manually deleted the VM folder from its disk location, not using phpvirtualbox. The VM doesn't show up in phpvirtualbox, however. I'm sure it's something simple like deleting a setting or config file somewhere, but I can't for the life of me find it...