search for: adpallinfo

...rying to import the foreign configuration and bring it online. I really can't reboot the system for (literally) another month (the maintenance window); I saw the firmware interface, but for Reasons, couldn't do it then, and figured I'd be able to to it with MegaCli64, but so far, nope. -AdpAllinfo gets only one. Clues? mark

...ation and bring it online. I really can't reboot the >> system for (literally) another month (the maintenance window); I saw >> the firmware interface, but for Reasons, couldn't do it then, and >> figured I'd be able to to it with MegaCli64, but so far, nope. >> -AdpAllinfo gets only >> one. >> >> Clues? Please don't top post. > I would try the newer storcli utility instead of megacli. > Is there a std. repo for it, or is it from that guy's website? mark

...> foreign configuration and bring it online. I really can't reboot the > system for (literally) another month (the maintenance window); I saw the > firmware interface, but for Reasons, couldn't do it then, and figured I'd > be able to to it with MegaCli64, but so far, nope. -AdpAllinfo gets only > one. > > Clues? > > mark > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > -- DISCLAIMER: NOTICE REGARDING PRIVACY AND CONFIDENTIALITY? The infor...

...:0] -a0 > > MARK A DISK AS MISSING > MegaCli -pdmarkmissing -physdrv[32:0] -a0 > > MARK A DISK AS PREPARED FOR REMOVAL > MegaCli -pdprprmv -physdrv[32:0] -a0 > > Here are some easy overview commands that I run when first looking at the > storage on a system: > MegaCli -AdpAllInfo -aAll |grep -A 8 "Device Present"; > MegaCli -PDList -aALL |grep "Firmware state"; > MegaCli -PDList -aALL |grep "Media Error Count"; > MegaCli -PDList -aALL |grep "Predictive Failure Count"; > MegaCli -PDList -aALL |grep "Inquiry Data";...

...OFFLINE A DISK MegaCli -PDOffline -PhysDrv[32:0] -a0 MARK A DISK AS MISSING MegaCli -pdmarkmissing -physdrv[32:0] -a0 MARK A DISK AS PREPARED FOR REMOVAL MegaCli -pdprprmv -physdrv[32:0] -a0 Here are some easy overview commands that I run when first looking at the storage on a system: MegaCli -AdpAllInfo -aAll |grep -A 8 "Device Present"; MegaCli -PDList -aALL |grep "Firmware state"; MegaCli -PDList -aALL |grep "Media Error Count"; MegaCli -PDList -aALL |grep "Predictive Failure Count"; MegaCli -PDList -aALL |grep "Inquiry Data"; MegaCli -PDList -aA...

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. > >

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 |

...lernumber = returnControllerNumber(output) bad = False # List available controller if printcontroller: print '-- Controllers --' print '-- ID | Model' controllerid = 0 while controllerid < controllernumber: cmd = '/opt/MegaRAID/MegaCli/MegaCli64 adpallinfo a'+str(controllerid)+' nolog' output = getOutput(cmd) controllermodel = returnControllerModel(output) print 'c'+str(controllerid)+' | '+controllermodel controllerid += 1 print '' if printarray: controllerid = 0...

...lernumber = returnControllerNumber(output) bad = False # List available controller if printcontroller: print '-- Controllers --' print '-- ID | Model' controllerid = 0 while controllerid < controllernumber: cmd = '/opt/MegaRAID/MegaCli/MegaCli64 adpallinfo a'+str(controllerid)+' nolog' output = getOutput(cmd) controllermodel = returnControllerModel(output) print 'c'+str(controllerid)+' | '+controllermodel controllerid += 1 print '' if printarray: controllerid = 0...

...> > bad = False > > # List available controller > if printcontroller: > print '-- Controllers --' > print '-- ID | Model' > controllerid = 0 > while controllerid < controllernumber: > cmd = '/opt/MegaRAID/MegaCli/MegaCli64 adpallinfo > a'+str(controllerid)+' nolog' > output = getOutput(cmd) > controllermodel = returnControllerModel(output) > print 'c'+str(controllerid)+' | '+controllermodel > controllerid += 1 > print '' > > if prin...

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