Yeah, this sounds like a totally different problem I appreciate these forums’ help before I commit a lot of coin into a project. You can switch cards, but use the same firmware or newer if same version is not available. Then a 2nd controller failed and I’ve sent the past 4 replacements back. Only a burn-in test for a few days reveals if a card will be stable under load. Not aware of any method of detecting the status for this RAID.
|Date Added:||18 October 2015|
|File Size:||62.24 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
To me, this sounds like a problem with microcode – i’ve seen some drivers for things like sound cards, soft raids, video cards, etc download some sort of microcode to the card when turning it on.
There is then a notice that the 3ware bios is not installed from what I have been able to determine, where I am not booting from the raid controller, this is a non-issue. I had some uvuntu with Adaptec SA.
Ive had excellent results uuntu the 3ware se. See the section about using their disk manager in solitudo. These are the kernel errors we see: Perhaps I should share this with 3Ware.
Suspicious Activity Detected
Some info on using 3ware raid cards in modern, common motherboards: Response queue large empty failed during reset sequence. Then a 2nd controller failed and I’ve 96650se the past 4 replacements back. I’ve got a stable of 3Ware SE cards and swapping is easy. We’ve ordered a new one, but I’m worried that if we replace the card it won’t recognize the existing array.
Finally we pulled it out of the Silicon Mechanics machine and stuck it in the Fedora machine. Is the information about the array written to the drives? Now, when we turn the machine on, the bios option rom that normally kicks in before the bootloader doesn’t show up, none of the drives start, and when the OS tries to access the device, it just times out.
I happened to do some repetitive booting in a machine that had a S-8 and it appears to have suffered the same fate. Anybody else having this problem may want to try the same.
[ubuntu] Adding 3Ware SE – Drives not seen by OS
The low profile SE cards are later made and they work fine in modern uefi, etc. It’s quite painless to swap 3ware cards. When the systems boots, after the BIOS loads, a message is displayed with the card name and firmware revision.
Do ensure the firmware is no older then the old card as far as you can determineand you probably want to try and keep within the same series if possible. It’s one of the fist things I do when I see something like this now. The ‘sg’ module must be loaded for it to work, the cli program segfaults without it.
I came 3warre an article for the from 3ware saying how to fix it. Anything else I should try? I realize I’m bringing this back from the dead, but yes, 3Ware cards do store the information about the array setup on the first few blocks of the drives.
This is a must when maintaining a lot of machines using for ubuntuu a serial line console. Command-line utilities are packaged for Debian as dpt-i2o-raidutils. The driver is in the main kernel as of 2. We took the card out of the machine and stuck it in a completely different machine running something redhat with very new drivers.
Well, you really have to see it. Re-seat the care – remove, and reinsert – and it magically comes back to life. Hosting provided by Metropolitan Area Network Darmstadt. According to the 3ware forums Ubuntu has native support in the server version for this card. Minimum status information is OK or degraded i. Firstly, I’m new to Servers, Hardware and Raid, so please be gentle. RAID status can be obtained via the mpt-status tool.