thus Peter Peltonen spake:
> I have now partially solved my problem:
>
> On Wed, Mar 9, 2011 at 5:55 PM, Peter Peltonen
> wrote:
>> I need to do a new CentOS net install on a new server having the
>> Supermicro X7DVL-3 motherboard:
>
> [...]
>
>> So I assume the controller is not supported and
Hi Peter,
I too was very undecided about using the LSI 1068e (on-board many supermicro
boards) in production for this very reason. The problem is that chipset is
basically unsupported by LSI and updates to it are sometimes necessary to
maintain compatibility. The driver won't build sometimes on up
I have now partially solved my problem:
On Wed, Mar 9, 2011 at 5:55 PM, Peter Peltonen wrote:
> I need to do a new CentOS net install on a new server having the
> Supermicro X7DVL-3 motherboard:
[...]
> So I assume the controller is not supported and I need a binary driver
> for it. For 1068e i
On Mar 10, 2011, at 6:33 PM, Ross Walker wrote:
> On Mar 10, 2011, at 3:49 PM, John R Pierce wrote:
>
>> On 03/10/11 12:40 PM, Les Mikesell wrote:
>>> I thought there were also problems in layers like lvm that keep the OS
>>> from knowing exactly what happened. And a lot of software that shoul
On Mar 10, 2011, at 3:49 PM, John R Pierce wrote:
> On 03/10/11 12:40 PM, Les Mikesell wrote:
>> I thought there were also problems in layers like lvm that keep the OS
>> from knowing exactly what happened. And a lot of software that should
>> fsync at certain points probably doesn't because lin
On 03/10/11 12:40 PM, Les Mikesell wrote:
> I thought there were also problems in layers like lvm that keep the OS
> from knowing exactly what happened. And a lot of software that should
> fsync at certain points probably doesn't because linux has historically
> handled it badly.
thats another pr
On 3/10/2011 1:50 PM, John R Pierce wrote:
>
> battery backed writeback caches on raid controllers flush any pending
> data to the disks when power is restored. if for some reason they
> can't, they flag an error
I know what they are supposed to do - I was just wondering if it happens
in practi
John R Pierce wrote on Thu, 10 Mar 2011 10:19:00 -0800:
> but they don't have any battery back write-back cache
not true, there's a slot on the card to plug a battery pack.
Kai
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman
On 03/10/11 11:36 AM, Les Mikesell wrote:
> Sure, UPS's fail, plugs get pulled, etc., but the cards and internal
> batteries most likely have their own failure modes. Or the whole box
> can fry at once. Did you have any way to tell if your battery-backed
> saved any data as the disks lost power o
On 3/10/2011 1:01 PM, John R Pierce wrote:
> On 03/10/11 10:56 AM, Les Mikesell wrote:
>> How important is the card-level battery if you have a UPS and a scheme
>> to monitor it and do a graceful shutdown before it fails?
>
> how important is your data? if your system *never* crashes, and you're
On 03/10/11 10:56 AM, Les Mikesell wrote:
> How important is the card-level battery if you have a UPS and a scheme
> to monitor it and do a graceful shutdown before it fails?
how important is your data? if your system *never* crashes, and you're
not running something like a database server depe
On 3/10/2011 12:19 PM, John R Pierce wrote:
>
>>> That controller doesn't really support RAID, what you're getting is
>>> commonly called FakeRAID
>> If you are referring to the 1068E, that is completely wrong.
>
> They do have basic hardware raid, with an embedded control processor,
> but they don
On 03/10/11 8:35 AM, Kai Schaetzl wrote:
> RedShift wrote on Thu, 10 Mar 2011 17:05:02 +0100:
>
>> That controller doesn't really support RAID, what you're getting is
>> commonly called FakeRAID
> If you are referring to the 1068E, that is completely wrong.
They do have basic hardware raid, with a
Google for "LSI M1068E". There are a few interesting postings on the first
result page, all people with heavy problems to get it working.
You have an M1068E which doesn't seem to be the same as 1068E, at least
not on the firmware side. You *need* the MegaRAID driver. The built-in
won't work.
Ka
Peter Peltonen wrote on Thu, 10 Mar 2011 19:08:14 +0200:
> 2) If I need to use the binary driver by LSI, how do I proceed with
> kernel updates?
The download is quite large and you will notice that there is a dkms rpm
in it, amongst a lot of other stuff. dkms can cater with updates, AFAIK.
It r
On Thu, Mar 10, 2011 at 6:35 PM, Kai Schaetzl wrote:
> RedShift wrote on Thu, 10 Mar 2011 17:05:02 +0100:
>
>> That controller doesn't really support RAID, what you're getting is
>> commonly called FakeRAID
>
> If you are referring to the 1068E, that is completely wrong.
The vendor who built the
RedShift wrote on Thu, 10 Mar 2011 17:05:02 +0100:
> That controller doesn't really support RAID, what you're getting is
> commonly called FakeRAID
If you are referring to the 1068E, that is completely wrong.
Kai
___
CentOS mailing list
CentOS@cento
Peter Peltonen wrote on Wed, 9 Mar 2011 17:55:04 +0200:
> http://www.supermicro.com/products/motherboard/xeon1333/5000V/X7DVL-3.cfm
>
> Based on that info I assume the board having a "8x SAS Ports via LSI
> 1068E Controller".
Well, did you check at the LSI site for the controller/card that *is*
Peter Peltonen wrote on Thu, 10 Mar 2011 10:12:48 +0200:
> Should this controller be supported by CentOS5.5 without a driver disk?
Yes, but maybe not in this specific card. For instance, I get this from
lspci:
02:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-
Express Fusi
On 03/09/11 16:55, Peter Peltonen wrote:
> I need to do a new CentOS net install on a new server having the
> Supermicro X7DVL-3 motherboard:
>
>http://www.supermicro.com/products/motherboard/xeon1333/5000V/X7DVL-3.cfm
>
> Based on that info I assume the board having a "8x SAS Ports via LSI
> 1
> Here are some pics of the RAID configuration:
>
>http://www.knuka.org/raid1.jpg
>http://www.knuka.org/raid2.jpg
It does indeed look configured...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
On Wed, Mar 9, 2011 at 7:40 PM, Tom H wrote:
> On Wed, Mar 9, 2011 at 11:51 AM, wrote:
>> Peter Peltonen wrote:
>>> On Wed, Mar 9, 2011 at 6:33 PM, wrote:
Peter Peltonen wrote:
>
> Based on that info I assume the board having a "8x SAS Ports via LSI
> 1068E Controller". We rec
On 3/9/2011 12:10 PM, Peter Peltonen wrote:
> Hi,
>
> On Wed, Mar 9, 2011 at 6:57 PM, Les Mikesell wrote:
>> Some controllers want to map arrays to volumes and present the volumes
>> to the OS instead of drives, so you have to go through the motions of
>> assigning the resources to volumes and ini
> Based on that info I assume the board having a "8x SAS Ports via LSI
> 1068E Controller". We received the server with 3 drives + 1 spare as
> hw RAID-5 preinstalled. During bootup I see that the drives are
> initialised and everything seems ok.
>
> The issue I am facing is that when trying to ins
On Wed, Mar 9, 2011 at 11:51 AM, wrote:
> Peter Peltonen wrote:
>> On Wed, Mar 9, 2011 at 6:33 PM, wrote:
>>> Peter Peltonen wrote:
Based on that info I assume the board having a "8x SAS Ports via LSI
1068E Controller". We received the server with 3 drives + 1 spare as
hw RA
> Hmm, I am not sure if I understand you correctly: are you saying
>That in the firmware configuration there might be an option that
>makes the disks invisible for the OS?
No, not as such. You just have to define the arrays: sssign the drives as
needed. It's a rare thing that a factory will set up
Hmm, I am not sure if I understand you correctly: are you saying that
in the firmware configuration there might be an option that makes the
disks invisible for the OS?
Most controllers have a firmware you can enter at boot with a keystroke.
Once in, you create/prepare arrays or single drives, whic
Hi,
On Wed, Mar 9, 2011 at 6:57 PM, Les Mikesell wrote:
> Some controllers want to map arrays to volumes and present the volumes
> to the OS instead of drives, so you have to go through the motions of
> assigning the resources to volumes and initializing them even if you
> only want one disk in t
On 3/9/2011 10:47 AM, Peter Peltonen wrote:
>
>> I recently had a problem like that with a Dell box. The trick is that with
>> a hardware controller, it supercedes software RAID. What you need to do is
>> go into the firmware controller configuration on boot, before you get to
>> grub, and make sur
Peter Peltonen wrote:
> Hi and thanks for your reply,
>
> On Wed, Mar 9, 2011 at 6:33 PM, wrote:
>> Peter Peltonen wrote:
>>> Based on that info I assume the board having a "8x SAS Ports via LSI
>>> 1068E Controller". We received the server with 3 drives + 1 spare as
>>> hw RAID-5 preinstalled. D
Hi and thanks for your reply,
On Wed, Mar 9, 2011 at 6:33 PM, wrote:
> Peter Peltonen wrote:
>> Based on that info I assume the board having a "8x SAS Ports via LSI
>> 1068E Controller". We received the server with 3 drives + 1 spare as
>> hw RAID-5 preinstalled. During bootup I see that the dri
Peter Peltonen wrote:
> I need to do a new CentOS net install on a new server having the
> Supermicro X7DVL-3 motherboard:
>
> http://www.supermicro.com/products/motherboard/xeon1333/5000V/X7DVL-3.cfm
>
> Based on that info I assume the board having a "8x SAS Ports via LSI
> 1068E Controller". We
I need to do a new CentOS net install on a new server having the
Supermicro X7DVL-3 motherboard:
http://www.supermicro.com/products/motherboard/xeon1333/5000V/X7DVL-3.cfm
Based on that info I assume the board having a "8x SAS Ports via LSI
1068E Controller". We received the server with 3 drives
33 matches
Mail list logo
