similar to: ZFS, SATA, LSI and stability

Dear All, It may be this not the correct mailing list, but I''m having a ZFS issue when a disk is failing. The system is a supermicro motherboard X8DTH-6F in a 4U chassis (SC847E1-R1400LPB) and an external SAS2 JBOD (SC847E16-RJBOD1). It makes a system with a total of 4 backplanes (2x SAS + 2x SAS2) each of them connected to a 4 different HBA (2x LSI 3081E-R (1068 chip) + 2x LSI

After applying 125205-07 on two X4500 machines running Sol10U4 and removing "set sata:sata_func_enable = 0x5" from /etc/system to re-enable NCQ, I am again observing drive disconnect error messages. This in spite of the patch description which claims multiple fixes in this area: 6587133 repeated DMA command timeouts and device resets on x4500 6538627 x4500 message logs contain multiple

Hello, I'm running FreeBSD 9.0/amd64, pure ZFS setup, one Seagate disk ST2000NM0011 SN02 on LSI Logic (mpt) controller. Yes, I know that running one disk on RAID controller is a bit weird, I have to find yet if it is possible to connect disk to internal SATA controller. About two days ago, system became SLOW. Disk usage is constantly 100%, and sometimes I'm getting swap_pager:

On Thu, 27 Oct 2016 11:25, Alessandro Baggi wrote: > Il 24/10/2016 14:05, Leonard den Ottolander ha scritto: >> On Mon, 2016-10-24 at 12:07 +0200, Alessandro Baggi wrote: >> > === START OF READ SMART DATA SECTION === >> > SMART Error Log not supported >> >> I reckon there's a <snip> between those lines. The line right after the >> first

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

Hi All, I know many of us here manage RAID on our Centos based servers so this may be of interest to us all. I ordered three new "Enterprise hard drives" this month from a well known UK online retailer. The drives arrived as new in their anti-static packaging. Before using one of the drives in a mission critical hardware raid I checked the SMART attributes and was amazed at what I

Two days ago I installed a brand new SSDNow E50 series (Enterprise) disk on a server. I intend to move the OS there. I just did the physical install and copied a few files to and from it just to see if it was OK. I left it there, waiting for an opportunity to configure it to do real work. Now I have looked at it with smartctl -a and it gives me the following info: 1 Raw_Read_Error_Rate

hi All, I''m new on the list. System: Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring Linux ctu 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux The symptom is the same with Saucy 3.9 kernel. ii btrfs-tools 0.20~git20130524~650e656-0daily13~raring1 amd64 Checksumming Copy on

Hi I keep getting these messages on this one box. There are issues with at least one of the drives in it, but since there are some 80 drives in it, that''s not really an issue. I just want to know, if anyone knows, what this kernel message mean. Anyone? Feb 5 19:35:57 prv-backup scsi: [ID 365881 kern.info] /pci at 7a,0/pci8086,340e at 7/pci1000,3140 at 0 (mpt1): Feb 5 19:35:57

I''m looking at the newly-orderable (via Sun) STEC Zeus SSDs, and they''re outrageously priced. http://www.stec-inc.com/product/zeusssd.php I just looked at the Intel X25-E series, and they look comparable in performance. At about 20% of the cost. http://www.intel.com/design/flash/nand/extreme/index.htm Can anyone enlighten me as to any possible difference between an STEC

I got the email that a drive in my 4-drive RAID10 setup failed. What are my options? Drives are WD1000FYPS (Western Digital 1 TB 3.5" SATA). mdadm.conf: # mdadm.conf written out by anaconda MAILADDR root AUTO +imsm +1.x -all ARRAY /dev/md/root level=raid10 num-devices=4 UUID=942f512e:2db8dc6c:71667abc:daf408c3 /proc/mdstat: Personalities : [raid10] md127 : active raid10 sdf1[2](F)

Hiya, Is there any reason (and anything to worry about) if disk target IDs don''t start at 0 (zero). For some reason mine are like this (3 controllers - 1 onboard and 2 PCIe); AVAILABLE DISK SELECTIONS: 0. c8t0d0 <ATA -ST9160314AS -SDM1 cyl 19454 alt 2 hd 255 sec 63> /pci at 0,0/pci10de,cb84 at 5/disk at 0,0 1. c8t1d0 <ATA -ST9160314AS -SDM1

Hello I have a strange issue, I''m having a setup with 24 disk enclosure connected with LSI3801-R. I created two pools. Pool have 24 healthy disks. I disabled LUN persistency on the LSI adapter. When I cold boot the server (power off by pulling all power cables), a warning is shown on the console during boot: .... WARNING: /pci/path/ ... (mpt0): wwn for traget has changed

Hi I am attempting to setup Xen 4.10 with kernel 4.9.86-30 ( virt7-xen-410-testing, virt7-common-testing ) on CentOS7 After installing everything, the machine was unable to boot and hung in dracut stating it could not find its root device. The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx), using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7

Hi, On Mon, 2016-10-24 at 12:07 +0200, Alessandro Baggi wrote: > === START OF READ SMART DATA SECTION === > SMART Error Log not supported I reckon there's a <snip> between those lines. The line right after the first should read something like: SMART overall-health self-assessment test result: PASSED or "FAILED" for that matter. If not try running smartctl -t short

Il 24/10/2016 14:05, Leonard den Ottolander ha scritto: > Hi, > > On Mon, 2016-10-24 at 12:07 +0200, Alessandro Baggi wrote: >> === START OF READ SMART DATA SECTION === >> SMART Error Log not supported > > I reckon there's a <snip> between those lines. The line right after the > first should read something like: > > SMART overall-health self-assessment

In a server with raid1 a first smart error was reported. Smart attributes: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time

> -----Original Message----- > From: Jason Pyeron > Sent: Saturday, February 07, 2015 22:54 > > NOTE: this is happening on Centos 6 x86_64, > 2.6.32-504.3.3.el6.x86_64 not Centos 5 > > Dell PowerEdge 2970, Seagate SATA drive, non-raid. > > I have this server which has been dying randomly, with no logs. Here is a console picture. http://i.imgur.com/ZYHlB82.jpg

NOTE: this is happening on Centos 6 x86_64, 2.6.32-504.3.3.el6.x86_64 not Centos 5 Dell PowerEdge 2970, Seagate SATA drive, non-raid. I have this server which has been dying randomly, with no logs. I had a tail -f over ssh for a week, when this just happened. Feb 8 00:10:21 thirteen-230 kernel: mptscsih: ioc0: attempting task abort! (sc=ffff880057a0a080) Feb 8 00:10:21 thirteen-230 kernel:

Il 27/10/2016 19:38, Yamaban ha scritto: > On Thu, 27 Oct 2016 11:25, Alessandro Baggi wrote: >> Il 24/10/2016 14:05, Leonard den Ottolander ha scritto: >>> On Mon, 2016-10-24 at 12:07 +0200, Alessandro Baggi wrote: >>> > === START OF READ SMART DATA SECTION === >>> > SMART Error Log not supported >>> >>> I reckon there's a