similar to: Smartctl & SATA

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

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:

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

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

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

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:

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

Hi, The server is running CentOS 5.8 Linux OS on Dell PowerEdge R710 having raid controller card 03:00.0 RAID bus controller: LSI Logic /Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 05) /usr/sbin/smartctl -a /dev/sda smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: DELL PERC H700 Version: 2.10 DELL

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

I noticed that the changelog for the new kernel 2.6.9-34 on the redhat enterprise watchlist states on of the fixes as; 145061 - SMART support in SATA driver (P1) Does this mean that with that kernel we should be able to interrogate SATA drives now ? Cheers, Bards.

At my physics lab we have 30 servers with 1TB disk packs. I am in need of monitoring for disk failures. I have been reading about SMART and it seems it can help. However, I am not sure what to look for if a drive is about to fail. Any thoughts about this? Is anyone using this method to predetermine disk failures? TIA

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

Ok....so after installing "smartmontools" on my CentOS machine...and connectiing this drive externally...i got positive reports from both the short and long tests...so the drive can obviously be "seen"....but when I look for it in the /dev/ directory...it doesn't show up.....I'm about to give the fdisk command line tools anonther shot....it allows me to format the

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

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

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

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