similar to: smartctl fails after update to 5.1

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've just installed my first system with a SATA drive and I've noticed that smartctl isn't supported under libata According to the smartmontools home page, SATA will require a patch that is still in development. http://www.linuxjournal.com/article/6983#comment-126714 "The patch is still under development and it is probably best to make sure that the disk is idle before trying

Hi all. I have a CentOS server: CentOS release 5.7 (Final) 2.6.18-274.3.1.el5 x86_64 I have two SSD disks attached: smartctl -i /dev/sdc smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: INTEL SSDSA2CW120G3 Serial Number: CVPR13010957120LGN Firmware

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

I finally fixed my drive error problem. This has been going on quite a while. I've posted before with no success on getting this fixed. I was getting these errors. Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } And now for the amazing smartctl -a

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

If y'all remember the problem I posted a while back, with a 3TB drive for userspace loosing it on a server, and spitting DRDY errors, but which work on everything else. Well, enough research, and conversation, and I may have found the problem: it's a Caviar Green, meant for a desktop, and the controller in the server has issues, because it uses TLER:

> <sebastian.vuorinen@helsinki.fi> wrote: > > On Wed, 2005-04-20 at 18:34 -0700, Steve Nospam > > wrote: > > > I have to admit,I'm ignorant. I'm seeing a > > problem > > > reported in syslog (2.6.11.7 kernel debian > dist.) > > The > > > problem reported is: > > > Apr 20 20:19:53 sandbox kernel: hda: drive_cmd: >

We have a system - it's C 7 - that a while back lost three drives of a large array. The other admin here replaced the failed drives, but never went through the MegaRAID replace series of commands. I've just brought it back up and put a new filesystem on it, but here's what's odd: if I do smartctl -a -d megaraid,x /dev/sda, where x=drive number, for all the other drives, I get

Hi All, I am fairly certain that this disk is failing in my server, and I am replacing it straight away anyway. However, I'd appreciate the views of the list just to be sure as I value your opinion(s). I got these errors, once only so far, in /var/log/messages. This disk has / on it. Oct 5 08:34:47 server1 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Oct 5 08:34:47

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

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

Il 17/01/2016 19:36, Alessandro Baggi ha scritto: > Il 17/01/2016 18:46, Brandon Vincent ha scritto: >> On Sun, Jan 17, 2016 at 10:05 AM, Matt Garman >> <matthew.garman at gmail.com> wrote: >>> I'm not sure what's going on with your drive. But if it were mine, >>> I'd want >>> to replace it. If there are issues, that long smart check

On 8/5/2015 1:00 PM, Chris Murphy wrote: > On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> How would I go about pointing it at the partition? >> >> What I am currently doing is this: >> device (hd0) /dev/hdg >> root (hd0,0) >> setup (hd0) > > setup (hd1,0) > > It's hd1 if your device map is correct and

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

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

On Feb 3, 2016, at 17:10, Warren Young wrote: > smartctl can see through several different types of RAID controller to the underlying physical disks via its -d option. This is what I have: # smartctl --all /dev/sda smartctl 5.43 2012-06-30 r3573 [i686-linux-2.6.32-573.12.1.el6.i686] (local build) Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net Vendor:

On Wed, 2015-08-05 at 13:11 -0400, Bowie Bailey wrote: > > # smartctl -i /dev/hdg | grep -i sector > > Sector Size: 512 bytes logical/physical > I don't get a "Sector Size" line. > > smartctl version 5.38 [i686-redhat-linux-gnu] Copyright (C) 2002-8 Bruce > Allen On the latest Centos 5 = Centos 5.11 ~~~~~~~~~~~~~ smartctl -v smartctl 5.42

I obtained smartmontools (which includes smartctl) from the standard apt repository (i''m using nexenta however), in addition its neccessary to use the device type of sat,12 with smartctl to get it to read attributes correctly in OS afaik. Also regarding dev id''s on the system, from what i''ve seen they are assigned to ports therefor do not change, however upon changing a

Il 21/10/2016 17:20, m.roth at 5-cent.us ha scritto: > John R Pierce wrote: >> On 10/21/2016 2:03 AM, Alessandro Baggi wrote: >>> >>> My ssds are failing? >> >> SSD's wear out based on writes per block. they distribute those >> writes, but once each block has been written X number of times, they are >> no longer reliable. >> >>