X9drd-7ln4f Bios Download
Karoline
I have tried both AHCI and IDE and with both of them, when the SLES11 installer comes up, it says it sees a "BIOS RAID" disk that it wants to install onto. If I go to the Export screen in the installer, under "Hard Drives" it shows me /dev/mapper/ddf_some_long_string, /dev/sda, and /dev/sdb but says the latter two are in use.
This is a fakeraid controller. That means that in reality, it is a bog standard AHCI SATA controller that has special bios and Windows' drivers that implement software raid. Changing the bios setting between AHCI and RAID only changes the PCI Identifier of the hardware to cause Windows to load the standard AHCI driver, or the vendor specific fake raid driver instead. Linux recognizes either PCI ID as an AHCI controller and loads the AHCI driver. Hence why Linux does not care which of those settings you use.
The dmraid software package recognizes the raid metadata that the fake raid bios leaves on the disks and configures the Linux device-mapper raid driver to access the raid array. To stop this, you need to delete the raid metadata from the disks with either the bios raid utility, or by running the dmraid command with the -E switch to erase the metadata from a given disk.
Hi Im a newbie to DIY nas world. Recently I picked up a Intel Server Board S3420GP system with an Intel RAID Controller RS2WC080. I have been doing research prior to installing Unraid on this system and noted discussions around firmware crossflashing for IT mode. Have a couple of questions for those that are experienced.
a) At the moment on system boot I get a message saying the raid controller is in JBOD mode. When I press ctrl + g it doesnt go into raid bios. Guessing there is no bios flashed. Will Unraid work with this controller in JBOD mode?
unRAID handles the RAID. These cards are being used to add SATA ports to a motherboard. So, as I understand it, you do not want even JBOD mode. To unpack @Benson's reply a bit, HBA is Host Bus Adapter. An HBA adds SATA ports to a motherboard.
I don't know how important it is to have the latest firmware. I don't. Anyway, the firmware version should be part of the text that goes by during computer bootup sequence. If it doesn't, you really need to access the BIOS. The RAID level/off setting is there. I and others from what I have seen here don't load the card's BIOS as we aren't using the RAID function.
The firmware version should be part of the text that goes by during computer bootup sequence. If it doesn't, you really need to access the BIOS. The RAID level/off setting is there. I and others from what I have seen here don't load the card's BIOS as we aren't using the RAID function.
The BIOS should only need if disk under HBA will be boot or RAID/JBOD them, due to Unraid boot by USB stick, so you don't need access HBA BIOS. Some people even erase HBA's BIOS. The main point is Unraid detect it and load the driver.
Hi all, thanks for the suggestions. The reason I didn't load Unraid to try yet was I am yet to purchase the drives I'm going to put on the server. But I managed to find a spare 2.5" 60gig drive lying around so I connected it to the raid controller and loaded up Unraid. The drive was detected. Here is the extract from "system devices" page
I have onboard sata controller as well. Mine doesn't show mpt3sas for the raid controller but the I guess if the drive is recognised then I don't need to bother with flashing IT firmware. This is the raid controller splash screen on boot.
Do you recommend that I go into bios and turn off jbod? If my controller doesn't have a bios then maybe I need to load a dos based tool or something and turn off jbod mode from command line? I'm not too fussed about jbod mode as it is essentially no raid isn't it? I just want Unraid to see disks that are connected to the raid controller.
By internet search, it is expect the chips are LSI SAS2008 and also match with device info., like a 9240-8i card with Megaraid BIOS/Firmware, I would agree try flash to IT BIOS, you need follow how to flash Megaraid to IT, anyway some risk need take too.
So took the gamble and went ahead. I was particularly nervous because sas2flsh utility didn't work in DOS and sas2flash EFI utility wouldn't even run initially to back up my existing firmware because it didn't detect any LSI firmware. I read that I needed to first erase existing firmware by writing an empty firmware using megarec.exe for the sas2flash utility to be able to write a new firmware. It made sense in my head so just decided to jump over the edge. Glad I did because it worked out as I expected/hoped. Flashed firmware P16 for the moment with bios. Still waiting on hard drives to install unraid.
Anyway. I have to sacrifice this thing to the microsoft gods so I cant do unraid or any cute zfs type thing and I got super cold feet thinking about using Win server 2019 with Storage Spaces Direct on it. I found an older Fujitsu card I could do raid6 with so i will sleep better at night.
Q: I saw someone had a fan on their H310. Mine didn't get that warm just sitting there, do they heat up in operation that much? Might repaste it along with the CPU since this machine/card has 8 year old paste, give or take I'd bet.
Thank you all who have contributed to this mamooth information dump. I have tried to follow the instructions in the Wiki to convert my recently acquired IBM M1015 card to LSI SAS9211-8i but the established process failed with a "No LSI SAS adapters found!" already in step 1. Maybe the information on how to overcome this is already in one of the prior 67 pages of the thread but I did not sit down to read through it all.. I did find the a workable solution here: -serveraid-m1015-and-no-lsi-sas-adapters-found.27445/
If you encounter the "No LSI SAS adapters found!" in step 1 and when launching the LSI SAS2FLSH tool (either DOS or EFI versions) manually, it may be because newer versions of the IBM M1015 firmware prevent the card being recognized by the LSI tool. In this case you will need to:
- Manually read out the SAS address from the sticker on the back side of the card, as you aren't able to read it out with the sas2flsh.exe tool. It has the format "500605B x-xxxx-xxxx", ignore spaces and dashes and note down the sas address in format "500605Bxxxxxxxxx"
- From here you can folow the guide in the P20 package after step 3 - Run the "5ITP20.BAT" batch file in 5_LSI_P20\ folder, then 6.bat in the root folder that you modified with your sas address beforehand.
- For ease of reference and because not much is left of the guide at this point, the actual commands remaining are "SAS2FLSH -o -f 2118it.bin" to flash the P20 IT mode firmware, and "SAS2FLSH -o -sasadd 500605Bxxxxxxxxx" to set the sas address.
having hard time getting my LSI 9220-i8 card detected on my GIGABYTE z370m d3h with sas2flash.efi p20 p15 p14,. sas2flsh.exe just gives me the PAL error. I tried both PCIE ports on my mobo, It shows up in unraid
Have you tried taping the contacts? There is a detailed description somewhere in the forum. Use the search function please, I'm on tapatalk at the moment.
Maybe you have to use another board for the flash procedure.
Having read a number of articles on STH (www.servethehome.com) I noticed a lot of people had mixed experience with the standard fixes. I am going to list things that did not work before touching on the path I took to fix this. So, here are things, in order, of what I tried.
Solved, even easier in case your ports are locked and have no way to boot, download a new BIOS and follow the instructions on the TXT file for BIOS rescue.
I had no boot and that worked for me.
Unpack the zip of the bios to a USB copy just the bios to the root and rename it to:(read the txt file that comes with the bios)
insert the USB on the internal USB post and remove ALL cards or devices,
turn it on and hold CTRL+HOME , viola BIOS will load form the USB and let you copy back to the MB
I purchased a server with a Supermicro X9DRL-7F motherboard and it too had a password set on the BIOS. Like you, I went through many of the published methods in an attempt to get past that, but no luck. I found one post where the author stated he got DOS installed on a hard drive in another machine, put that into the server, then was able to use the /dev/nvram clear method. I was going to attempt that but since I could boot to a UEFI shell I went looking for a UEFI BIOS utility and found one on the AMI website. I got that on a USB key along with the newest BIOS for the motherboard and first did some queries using the utility, which all came back with correct information and no errors so I went ahead and flashed the BIOS. That worked, but unfortunately the password remained.
c80f0f1006