similar to: A strange situation with MegaCli64 and smartctl

Thank you for your help. Le 05/01/2015 19:10, John R Pierce a ?crit : > works here fine on the 9261, which is an OEM version of the same card > with the connectors in a different orientation... you might check your > LSI firmware revision. My firmware seems to be more up to date. Anyway, I will try to update firmware. I have to check how to do that. # dmesg |grep LSI scsi4 : LSI SAS

On 1/5/2015 7:14 AM, Philippe BOURDEU d'AGUERRE wrote: > > Since Centos 6.6 update (kernel 2.6.32-504), the controller doesn't > initialize at boot. Reverting to kernel 2.6.32-431 allows server to > boot fine. works here fine on the 9261, which is an OEM version of the same card with the connectors in a different orientation... you might check your LSI firmware revision.

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

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

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

I've got a box running C7, just updated (yesterday). It had an onboard RAID controller, and an HBA. I just installed a new, additional RAID card, all LSI. MegaCli64 only sees one controller. I can't seem to find the magic to see the others. I *know* the new card is a MegaRAID - the box it came in says so. The system sees it 1:00.0 RAID bus controller: LSI Logic / Symbios Logic SAS1078

Scott Silverman wrote: > On Tue, Jul 10, 2018 at 12:37 PM, mark <m.roth at 5-cent.us> wrote: > >> I've got a box running C7, just updated (yesterday). It had an onboard >> RAID controller, and an HBA. I just installed a new, additional RAID >> card, all LSI. >> >> MegaCli64 only sees one controller. I can't seem to find the magic to >> see

I've seen similar cases where a USB drive appears to fail but the SMART reports success. The most recent was a 500 GB disk which had internally a Seagate Barracuda SATA drive. It appeared to work well until I sent it a largish (7GB) tarball. As well as SMART I ran a surface check and exercise, all passed. The tar kept failing. I can't test further, the disk has been broken up for

On Tue Feb 16 03:35:06 PM, John R Pierce wrote: Thanks to both you and Mark Roth for chiming in and thank you for the lsi-raidinfo script. > 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, Right, that is in agreement with both

I would try the newer storcli utility instead of megacli. Thanks, Scott Silverman | IT | Simplex | 312-360-2444 230 S. LaSalle St., Suite 4-100, Chicago, IL 60604 On Tue, Jul 10, 2018 at 12:37 PM, mark <m.roth at 5-cent.us> wrote: > I've got a box running C7, just updated (yesterday). It had an onboard > RAID controller, and an HBA. I just installed a new, additional RAID

Hello, after update to 5.1 the smartctl will fail. I get this output: smartctl --all -d ata /dev/sda smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: HDS728080PLA380 Serial Number: XXXXXXXXXXXXXXXX Firmware Version: PF2OA69A User Capacity: 82.348.277.760

On 2/2/2015 10:32 AM, John R Pierce wrote: > On 2/1/2015 8:25 PM, Jatin Davey wrote: >> >> On 2/2/2015 9:25 AM, John R Pierce wrote: >>> On 2/1/2015 7:31 PM, Jatin Davey wrote: >>>> >>>> I ran your script and here is the output for it: >>>> >>>> Start of the Output*************************** >>>> [root at localhost

Hi, I get these below information. Please help me understand about "SMART Health Status: FAILURE PREDICTION THRESHOLD EXCEEDED: ascq=0x5 [asc=5d, ascq=5]" and what does that error mean. Does it mean that the SAS disk 0 is failing and has serious issues and needs to be replaced and also do i need to run health status test with different options/flags or switches. /usr/sbin/smartctl -d

On a headless C7 server (actually a pogoplug with the Redsleeve 7 distro), I have a usb attached backup drive (what other type of drives can you have on a pogoplug other than usb? :) ). I had reformated the partition as ext4: # parted /dev/sdb print Model: WD My Book 1230 (scsi) Disk /dev/sdb: 3001GB Sector size (logical/physical): 4096B/4096B Partition Table: msdos Disk Flags: Number Start

I have 15x SAS drives in a Dell MD1000 enclosure, attached to an LSI 9200-16e. This has been working well. The system is boothing off of internal drives, on a Dell SAS 6ir. I just tried to add a second storage enclosure, with 15 more SAS drives, and I got a lockup during Loading Kernel. I got the same results, whether I daisy chained the enclosures, or plugged them both directly into the LSI

Hey, guys See further below extracted output from a daily scrub showing csum errors on sdb, part of a raid1 btrfs. Looking back, it has been getting errors like this for a few days now. The disk is patently unreliable but smartctl's output implies there are no issues. Is this somehow standard faire for S.M.A.R.T. output? Here are (I think) the important bits of the smartctl output for

I've got a 1Tb USB disc that appears to be dying - eg it took about 10 days (!) to run 'badblocks -nsv /dev/sdc' and it only did less than 2% in that time. Read access became _really_ slow. So there's definitely something amiss and I've got it offline. There's no drama about the content as I have other backups and I'm resigned to junking the thing, but I'm curious

A few weeks ago, one of my servers started complaining, via smartd, that one drive had one unreadable sector. I umounted it, and ran an fsck -c, then remounted it. Error didn't go away. Now, what's really annoying is that I've gotten back to it today, and it's reporting the problem, as it has for weeks now, every half an hour. However, when I run > smartctl -q errorsonly -H -l

On 4/22/20 8:53 AM, Christopher Wensink wrote: > I had an 8 TB External USB disk plugged into the system, that I had been > using for additional space for backups, I was under the impression that > sda, sdb, sdc, and sdd were the four disks on the raid controller card, Not exactly.? If you have a RAID5 array, then you have one volume spread across the physical disks.? You can then

Happy new year ! We have a SuperMicro server with a LSI MegaRAID 9260-4i controller. Since Centos 6.6 update (kernel 2.6.32-504), the controller doesn't initialize at boot. Reverting to kernel 2.6.32-431 allows server to boot fine. The server can't boot due to a bug in LSI megaraid module. Boot log ends by a lot of lines: RESET_GEN2: retry=xxx, hostdiag=a4 I tried Centos 6.6