search for: megacity

On Fri, January 20, 2017 7:00 pm, Cameron Smith wrote: > Hi Valeri, > > > Before you pull a drive you should check to make sure that doing so > won't kill the whole array. Wow! What did I say to make you treat me as an ultimate idiot!? ;-) All my comments, at least in my own reading, we about things you need to do to make sure when you hot unplug bad drive it is indeed failed

Hi Valeri, Before you pull a drive you should check to make sure that doing so won't kill the whole array. MegaCli can help you prevent a storage disaster and can let you have more insight into your RAID and the status of the virtual disks and the disks than make up each array. MegaCli will let you see the health and status of each drive. Does it have media errors, is it in predictive

On Fri, January 20, 2017 5:16 pm, Joseph L. Casale wrote: >> This is why before configuring and installing everything you may want to >> attach drives one at a time, and upon boot take a note which physical >> drive number the controller has for that drive, and definitely label it >> so >> y9ou will know which drive to pull when drive failure is reported. > >

Triple Release Day! James Wan, from the Solaris Quality Engineering group, has released the Megacli test suite. More information on Megacli test suite can be found at: http://opensolaris.org/os/community/storage/tests/ http://src.opensolaris.org/source/xref/test/ontest-stc2/src/suites/storage/megacli/README http://src.opensolaris.org/source/xref/test/ontest-stc2/src/suites/storage/megacli/

On Fri, May 6, 2016 1:36 pm, m.roth at 5-cent.us wrote: > Got a new box I'm trying to set up. I configured the RAID from the > firmware, but "fast initialize" was sitting there at 0% (it's about 43 or > 45TB). The first time I tried this, I said background, and rebooted the > system. > > And the stupid annoying alarm started up as the system came up. > >

On Fri, May 6, 2016 4:19 pm, m.roth at 5-cent.us wrote: > Valeri Galtsev wrote: >> >> On Fri, May 6, 2016 1:36 pm, m.roth at 5-cent.us wrote: >>> Got a new box I'm trying to set up. I configured the RAID from the >>> firmware, but "fast initialize" was sitting there at 0% (it's about 43 >>> or 45TB). The first time I tried this, I said

Got a new box I'm trying to set up. I configured the RAID from the firmware, but "fast initialize" was sitting there at 0% (it's about 43 or 45TB). The first time I tried this, I said background, and rebooted the system. And the stupid annoying alarm started up as the system came up. This time, having *finally* figured out how to set up hot spares from the WebBIOS, I suspended

On 1/30/2015 9:44 AM, John R Pierce wrote: > On 1/29/2015 7:21 PM, Jatin Davey wrote: >> [root at localhost ~]# lspci | grep RAID >> 05:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 >> 3108 [Invader] (rev 02) > > to get info out of those, you need to install MegaCli64 from LSI > Logic, which has the ugliest command lines and output you've

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

I am having an issue with Megacli when adding or removing virtual disks. I will post a link to fpaste that has the issue shown. In brief whenever i add, or remove, a virtual disk via MegaCli the attempt succeeds and the adapter is configured but the OS remounts dm-0 in read only. dm-0 is my root lv. This issue does not happen if i boot into the default, non Xen, CentOS kernel. On stock

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 |

Hey, anyone using an LSI MegaRAID experienced "disappearing drives"...? We installed 6 new C6 servers, each with a Supermicro SMC2108 (LSI MegaRAID) controllers and 3 PX-128M5Pro SSDs ( RAID1 + hostswap). 2 weeks (and almost no activity on it, since not in production, apart from installation) later, megacli sees (based on the slot numbers): - on one server: only the 2nd disk of the RAID

Valeri Galtsev wrote: > > On Fri, May 6, 2016 1:36 pm, m.roth at 5-cent.us wrote: >> Got a new box I'm trying to set up. I configured the RAID from the >> firmware, but "fast initialize" was sitting there at 0% (it's about 43 >> or 45TB). The first time I tried this, I said background, and >> rebooted the system. >> >> And the stupid

On 5/6/2016 11:36 AM, m.roth at 5-cent.us wrote: > Got a new box I'm trying to set up. I configured the RAID from the > firmware, but "fast initialize" was sitting there at 0% (it's about 43 or > 45TB). The first time I tried this, I said background, and rebooted the > system. > > And the stupid annoying alarm started up as the system came up. > > This

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

On 2/16/2016 3:23 PM, Zube wrote: > Does anyone know what program can be used to query the RAID status > from the OS for an on-board LSI SAS 2308-4i? the 2308 isn't actually a megaraid, its a simple SAS HBA that has an optional raid mode IF its flashed with IR firmware... this only supports raid 0/1/10. I always(!) flash these with the IT firmware that turns them back into a

On 1/29/2015 7:21 PM, Jatin Davey wrote: > [root at localhost ~]# lspci | grep RAID > 05:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 > 3108 [Invader] (rev 02) to get info out of those, you need to install MegaCli64 from LSI Logic, which has the ugliest command lines and output you've ever seen. I use the python script below, which I put in

We're looking for tools to be used in monitoring the PERC H800 arrays on a set of database servers running CentOS 5.5. We've installed most of the OMSA (Dell monitoring) suite. Our current alerting is happening through SNMP, though it's a bit hit or miss (we apparently missed a couple of earlier predictive failure alerts on one drive). OMSA conflicts with mega-cli, though we may

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