search for: megaclisas

i'm configuring a storage server with CentOS 6.2, it uses a LSI MegaRAID SAS controller, I'm using LSI's megacli to configure the storage... Any ideas on how to get drive failure notifications out of this system? I'm configuring hot spares but I'd still like some sort of notification when a drive has failed so the spare can be replaced. -- john r pierce

Does anyone know what program can be used to query the RAID status from the OS for an on-board LSI SAS 2308-4i? On this page: http://docs.avagotech.com/docs/12351997 there is a curious note on the left that reads: "Integrated MegaRAID support available upon request" After one mostly fruitless round of chatting with LSI/Avago/Broadcom and one completely fruitless round of chatting

On 1/30/2015 1:53 AM, Gordon Messmer wrote: > On 01/29/2015 05:07 AM, Jatin Davey wrote: >> Yes , it is a SATA disk. I am not sure of the speed. Can you tell me >> how to find out this information ? Additionally we are using RAID 10 >> configuration with 4 disks. > > What RAID controller are you using? > > # lspci | grep RAID [Jatin] [root at localhost ~]# lspci |

...8:17 | 2-0-7 | ST33000650NS 0003 | Online, Spun Up disk 8:18 | x-x-x | ST33000650NS 0003 | Hotspare, Spun down disk 8:19 | x-x-x | ST33000650NS 0003 | Hotspare, Spun down (yes, that system has 20 disks, in 3 raids + 2 hot spares) *****************start of my script*********** #!/usr/bin/python # megaclisas-status 0.6 # renamed lsi-raidinfo # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This progra...

...nline, Spun Up disk 8:17 | 2-0-7 | Z291VSX8ST33000650NS 0003 | Online, Spun Up disk 8:18 | x-x-x | Z291VTS7ST33000650NS 0003 | Hotspare, Spun down disk 8:19 | x-x-x | Z291VT3HST33000650NS 0003 | Hotspare, Spun down the script that does this is here... # more bin/lsi-raidinfo #!/usr/bin/python # megaclisas-status 0.6 # renamed lsi-raidinfo # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This progra...

...ig btrfs filesystem, or a bunch of smaller ones stiched together. In any case, it should be very easy to get better performance here. I think someone else mentioned that you should look at your dovecot backend, and you should move to the fastest one you can find. Good luck! John Miloslav> # megaclisas-status Miloslav> -- Controller information -- Miloslav> -- ID | H/W Model | RAM | Temp | BBU | Firmware Miloslav> c0 | AVAGO MegaRAID SAS 9361-8i | 1024MB | 72C | Good | FW: Miloslav> 24.16.0-0082 Miloslav> -- Array information -- Miloslav> -- ID | T...

...Spun Up > disk 8:18 | x-x-x | ST33000650NS 0003 | Hotspare, Spun down > disk 8:19 | x-x-x | ST33000650NS 0003 | Hotspare, Spun down > > (yes, that system has 20 disks, in 3 raids + 2 hot spares) > > *****************start of my script*********** > #!/usr/bin/python > > # megaclisas-status 0.6 > # renamed lsi-raidinfo > # > # This program is free software; you can redistribute it and/or modify > # it under the terms of the GNU General Public License as published by > # the Free Software Foundation; either version 2 of the License, or > # (at your option) any...

...nce here. I hope I've made it clear above. > I think someone else mentioned that you should look at your dovecot > backend, and you should move to the fastest one you can find. > > Good luck! > John Thank you for your time and advices! Kind regards Milo > Miloslav> # megaclisas-status > Miloslav> -- Controller information -- > Miloslav> -- ID | H/W Model | RAM | Temp | BBU | Firmware > Miloslav> c0 | AVAGO MegaRAID SAS 9361-8i | 1024MB | 72C | Good | FW: > Miloslav> 24.16.0-0082 > > Miloslav> -- Array informat...

...ives (the 838G ones in a list below) and increase a free space by rebalace. I think, it helped a little bit, not not so rapidly. Is this a reasonable setup and use case for btrfs RAID-10? If so, are there some recommendations to achieve better performance? Thank you. With kind regards Milo # megaclisas-status -- Controller information -- -- ID | H/W Model | RAM | Temp | BBU | Firmware c0 | AVAGO MegaRAID SAS 9361-8i | 1024MB | 72C | Good | FW: 24.16.0-0082 -- Array information -- -- ID | Type | Size | Strpsz | Flags | DskCache | Status | OS Path | CacheCad...

...nce here. I hope I've made it clear above. > I think someone else mentioned that you should look at your dovecot > backend, and you should move to the fastest one you can find. > > Good luck! > John Thank you for your time and advices! Kind regards Milo > Miloslav> # megaclisas-status > Miloslav> -- Controller information -- > Miloslav> -- ID | H/W Model??????????????????| RAM????| Temp | BBU????| Firmware > Miloslav> c0????| AVAGO MegaRAID SAS 9361-8i | 1024MB | 72C??| Good?? | FW: > Miloslav> 24.16.0-0082 > > Miloslav> -- Array informat...

...gt; I think someone else mentioned that you should look at your dovecot >> backend, and you should move to the fastest one you can find. >> >> Good luck! >> John Miloslav> Thank you for your time and advices! Miloslav> Kind regards Miloslav> Milo Miloslav> # megaclisas-status Miloslav> -- Controller information -- Miloslav> -- ID | H/W Model | RAM | Temp | BBU | Firmware Miloslav> c0 | AVAGO MegaRAID SAS 9361-8i | 1024MB | 72C | Good | FW: Miloslav> 24.16.0-0082 >> Miloslav> -- Array information -- Miloslav> -...

On Thursday 02 November 2017 14:10:25 Bowie Bailey wrote: > If you want raid 5 or 6, then you should get a hardware controller. For > raid 1, mdadm should work just fine.? I would suggest trying it before > buying a raid controller.? If it works for you, you save a few hundred > dollars and you have one less piece of hardware to worry about. > > I haven't looked at them in

I just had an IBM in a remote location with a hardware raid1 have both drives go bad. With local machines I probably would have caught it from the drive light before the 2nd one died... What is the state of the art in linux software monitoring for this? Long ago when that box was set up I think the best I could have done was a Java GUI tool that IBM had for their servers - and that seemed like