Groups > linux.debian.user > #177310 > unrolled thread

How to fix I/O errors?

Started by	Marc Shapiro <marcnshap@gmail.com>
First post	2017-02-02 22:10 +0100
Last post	2017-02-06 22:30 +0100
Articles	20 — 9 participants

Back to article view | Back to linux.debian.user

  How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 22:10 +0100
    Re: How to fix I/O errors? <tomas@tuxteam.de> - 2017-02-02 22:30 +0100
      Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 22:50 +0100
        Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 23:20 +0100
    Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-03 07:30 +0100
      Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 08:40 +0100
        Re: How to fix I/O errors? Mark Fletcher <mark27q1@gmail.com> - 2017-02-03 16:00 +0100
          Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 22:40 +0100
            Re: How to fix I/O errors? Jonathan Dowland <jmtd@debian.org> - 2017-02-07 12:00 +0100
      Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 22:50 +0100
        Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-04 08:20 +0100
          Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-06 22:20 +0100
            Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 23:40 +0100
        Re: How to fix I/O errors? Ric Moore <wayward4now@gmail.com> - 2017-02-04 16:20 +0100
          Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-04 20:20 +0100
            Re: How to fix I/O errors? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-02-06 17:00 +0100
              Re: How to fix I/O errors? Gene Heskett <gheskett@shentel.net> - 2017-02-06 18:30 +0100
                Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 22:30 +0100
                Re: How to fix I/O errors? Felix Miata <mrmazda@earthlink.net> - 2017-02-06 23:20 +0100
              Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 22:30 +0100

#177310 — How to fix I/O errors?

From	Marc Shapiro <marcnshap@gmail.com>
Date	2017-02-02 22:10 +0100
Subject	How to fix I/O errors?
Message-ID	<t6wNI-No-25@gated-at.bofh.it>

I apologize for this being so long, but since the problem occurs 
sporadically I wanted to get as much information in this post as 
possible because I don't know when it will happen again.

This problem started a bout two weeks ago.  I woke up to find a black 
screen and a kernel panic.  I rebooted and was presented with many fsck 
errors that could not be handled automatically so I ran it manually, as 
directed.  I took all the defaults.  Any time that I was shown a file 
name it seemed to be a flash file in my daughters /home directory or 
otherwise related to flash. Afterwards, the only partition that I found 
anything in lost+found was /home and all of the files there were, 
indeed, showing my daughter as owner.  I shutdown and rebooted to get 
everything clean and it seemed good for a while.  Since then, however, 
every day or two things just stop working properly.  Menus cease to do 
anything, pages don't load in the browser, etc.  If I exit from X and 
work at a console, some commands (like ls) seem to work fine, others do 
not, giving me I/O error messages.  I can't even do a typescript, or 
redirect the output to a file that I could attach here, since I just get 
errors.  I can't even do a ctl-alt-del to reboot, as I get an error saying:

INIT: cannot execute "/sbin/shutdown"


I have no choice but to power down with the power button, which I really 
don't like to do.

It happened again, today, and I manually copied down the errors so I 
hope that I got it all correct.  This is what I did before shutting down:

marc@quixote:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,relatime,size=10240k,nr_inodes=3081484,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=2472496k,mode=755)
/dev/sda2 on / type ext3 (ro,relatime,errors=remount-ro,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
pstore on /sys/fs/pstore type pstore (rw,relatime)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=6622700k)
/dev/mapper/vg1-home on /home type ext3 (ro,relatime,data=ordered)
/dev/mapper/vg1-tmp--jessie on /tmp type ext3 (ro,relatime,data=ordered)
/dev/mapper/vg1-usr--jessie on /usr type ext3 (ro,relatime,data=ordered)
/dev/mapper/vg1-usrlocal on /usr/local type ext3 (ro,relatime,data=ordered)
/dev/mapper/vg1-photos on /usr/local/photos type ext3 
(rw,relatime,data=ordered)
/dev/mapper/vg1-vDisks on /usr/local/vdisks type ext3 
(rw,relatime,data=ordered)
/dev/mapper/vg1-var--jessie on /var type ext3 (ro,relatime,data=ordered)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,size=12k)
cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755)
systemd on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/x86_64-linux-gnu/systemd-shim-cgroup-release-agent,name=systemd)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=2472496k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Note that almost all real filesystems are readonly.


I logged out and back in as root.  From /root I attempted to copy a text 
file to /usr/local/photos (which still shows as rw):


cp wheezy1.script /usr/local/photos

[] sd: 0:0:0:0: [sda] Unhandled error code

[] sd: 0:0:0:0: [sda]

[] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

[] sd: 0:0:0:0: [sda] CDB:

[] Read(10): 28 00 00 3e bc 68 00 00 08 00

[] end_request: I/O error, dev sda, sector 4111464

[] sd: 0:0:0:0: [sda] Unhandled error code

[] sd: 0:0:0:0: [sda]

[] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

[] sd: 0:0:0:0: [sda] CDB:

[] Read(10): 28 00 00 3e bc 68 00 00 08 00

[] end_request: I/O error, dev sda, sector 4111464

-bash /bin/cp: Input/output error


NOTE: all the empty brackets on the left actually had timestamps in 
them.  The same is true in all following cases, as well.


I then changed directory to /usr/local/photos and tried to create a new 
file with touch:


touch tempfile

[] Write(10): 2a 00 08 56 9e 0c 00 00 08 00

[] sd: 0:0:0:0: [sda] Unhandled error code

[] sd: 0:0:0:0: [sda]

[] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

[] sd: 0:0:0:0: [sda] CDB:

[] Read(10): 28 00 08 56 05 1c 00 00 08 00

[] sd: 0:0:0:0: [sda] Unhandled error code

[] sd: 0:0:0:0: [sda]

[] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

[] sd: 0:0:0:0: [sda] CDB:


Finally, I tried to unmount /home with the intention of remounting it to 
see if it would come back as rw:


umount /home

[] sd: 0:0:0:0: [sda] Unhandled error code

[] sd: 0:0:0:0: [sda]

[] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

[] sd: 0:0:0:0: [sda] CDB:

[] Write(10) 2a 00 00 75 5e 0c 00 00 08 00

[] end_request: I/O error, dev sda, sector 209018380

[] Buffer I/O errpr on device dm-6, logical block 0

[] lost page write due to I/O error on dm-6

[] EXT4-fs error (device dm-6): ext4_put_super: 795: Couldn't clean up 
the journal


NOTE: NONE of my filesystems are EXT4.  They are ALL EXT3.

Due to the errors I did not try to remount /home.

Then I shutdown with the power button and rebooted.  Everything is 
working, now.  All the filesystems that should be rw are rw, but within 
a day or two this will almost certainly happen again.


If anyone can give me a clue how to correct this I would be most 
grateful.  If further info is necessary it will probably have to wait 
until this happens again.

BTW: I have plenty of space available in the LV, so I could create a new 
partition for /home and copy everything from the current partition while 
it is not giving me errors, if that is likely to fix the problem, but I 
would still like to know just went wrong and how to prevent it in the 
future.

Marc

[toc] | [next] | [standalone]

#177312

From	<tomas@tuxteam.de>
Date	2017-02-02 22:30 +0100
Message-ID	<t6x73-V3-9@gated-at.bofh.it>
In reply to	#177310

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Feb 02, 2017 at 01:05:47PM -0800, Marc Shapiro wrote:
> I apologize for this being so long, but since the problem occurs
> sporadically I wanted to get as much information in this post as
> possible because I don't know when it will happen again.

If I were you, I'd take a backup ASAP and double-check whether one
of your disks is dying. Perhaps there's some hint in /var/log/messages,

It might just be a lose cable.

Proceed carefully. If at all possible don't mount your disks read/write
until yon know more.

(Perhaps boot off an external medium, CDROM or USB stick).

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliTongACgkQBcgs9XrR2ka/BwCfXGGdH/hABiXZEG/nSFMR3QRJ
rhUAn1wC8V3ZJdqbdEQzV0McASFyNiZE
=vTyi
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#177313

From	Marc Shapiro <marcnshap@gmail.com>
Date	2017-02-02 22:50 +0100
Message-ID	<t6xqq-11U-13@gated-at.bofh.it>
In reply to	#177312

On 02/02/2017 01:19 PM, tomas@tuxteam.de wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, Feb 02, 2017 at 01:05:47PM -0800, Marc Shapiro wrote:
>> I apologize for this being so long, but since the problem occurs
>> sporadically I wanted to get as much information in this post as
>> possible because I don't know when it will happen again.
> If I were you, I'd take a backup ASAP and double-check whether one
> of your disks is dying. Perhaps there's some hint in /var/log/messages,
>
> It might just be a lose cable.
>
> Proceed carefully. If at all possible don't mount your disks read/write
> until yon know more.
>
> (Perhaps boot off an external medium, CDROM or USB stick).
>
> Regards
> - -- tomás
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAliTongACgkQBcgs9XrR2ka/BwCfXGGdH/hABiXZEG/nSFMR3QRJ
> rhUAn1wC8V3ZJdqbdEQzV0McASFyNiZE
> =vTyi
> -----END PGP SIGNATURE-----
>
I was on the system last night until close to midnight with no 
problems.  There were only 3 lines for yesterday in /var/log/messages 
and one for just after midnight. libflashplayer seems to be 
segfaulting.  Nothing then until 11:41:30 this morning, which seems to 
be when I rebooted.


Feb  1 07:35:03 quixote rsyslogd: [origin software="rsyslogd" 
swVersion="8.4.2" x-pid="1993" x-info="http://www.rsyslog.com"] rsyslogd 
was HUPed
Feb  1 13:22:19 quixote kernel: [102750.350970] plugin-containe[2161]: 
segfault at 15a5ed4cb3c4 ip 00007fc269bf9412 sp 00007ffc8f383c68 error 6 
in libflashplayer.so[7fc269588000+107a000]
Feb  1 21:24:46 quixote kernel: [131744.689533] usblp0: removed
Feb  2 00:00:04 quixote kernel: [141077.771903] plugin-containe[4968]: 
segfault at 1ccfdd1123c4 ip 00007f3b59df9412 sp 00007ffc2fe526d8 error 6 
in libflashplayer.so[7f3b59788000+107a000]
Feb  2 11:41:30 quixote rsyslogd: [origin software="rsyslogd" 
swVersion="8.4.2" x-pid="2055" x-info="http://www.rsyslog.com"] start
Feb  2 11:41:30 quixote kernel: [    0.000000] Initializing cgroup 
subsys cpuset
Feb  2 11:41:30 quixote kernel: [    0.000000] Initializing cgroup 
subsys cpu
Feb  2 11:41:30 quixote kernel: [    0.000000] Initializing cgroup 
subsys cpuacct
Feb  2 11:41:30 quixote kernel: [    0.000000] Linux version 
3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 
(Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29)
Feb  2 11:41:30 quixote kernel: [    0.000000] Command line: 
BOOT_IMAGE=Jessie ro root=UUID=1a16b577-6751-412e-ba89-ca0718922385
Feb  2 11:41:30 quixote kernel: [    0.000000] e820: BIOS-provided 
physical RAM map:
<SNIP>

[toc] | [prev] | [next] | [standalone]

#177315

From	Marc Shapiro <marcnshap@gmail.com>
Date	2017-02-02 23:20 +0100
Message-ID	<t6xTs-1sC-19@gated-at.bofh.it>
In reply to	#177313

On 02/02/2017 01:40 PM, Marc Shapiro wrote:
> On 02/02/2017 01:19 PM, tomas@tuxteam.de wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Thu, Feb 02, 2017 at 01:05:47PM -0800, Marc Shapiro wrote:
>>> I apologize for this being so long, but since the problem occurs
>>> sporadically I wanted to get as much information in this post as
>>> possible because I don't know when it will happen again.
>> If I were you, I'd take a backup ASAP and double-check whether one
>> of your disks is dying. Perhaps there's some hint in /var/log/messages,
>>
>> It might just be a lose cable.
>>
>> Proceed carefully. If at all possible don't mount your disks read/write
>> until yon know more.
>>
>> (Perhaps boot off an external medium, CDROM or USB stick).
>>
>> Regards
>> - -- tomás
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.12 (GNU/Linux)
>>
>> iEYEARECAAYFAliTongACgkQBcgs9XrR2ka/BwCfXGGdH/hABiXZEG/nSFMR3QRJ
>> rhUAn1wC8V3ZJdqbdEQzV0McASFyNiZE
>> =vTyi
>> -----END PGP SIGNATURE-----
>>
> I was on the system last night until close to midnight with no 
> problems.  There were only 3 lines for yesterday in /var/log/messages 
> and one for just after midnight. libflashplayer seems to be 
> segfaulting.  Nothing then until 11:41:30 this morning, which seems to 
> be when I rebooted.
>
>
> Feb  1 07:35:03 quixote rsyslogd: [origin software="rsyslogd" 
> swVersion="8.4.2" x-pid="1993" x-info="http://www.rsyslog.com"] 
> rsyslogd was HUPed
> Feb  1 13:22:19 quixote kernel: [102750.350970] plugin-containe[2161]: 
> segfault at 15a5ed4cb3c4 ip 00007fc269bf9412 sp 00007ffc8f383c68 error 
> 6 in libflashplayer.so[7fc269588000+107a000]
> Feb  1 21:24:46 quixote kernel: [131744.689533] usblp0: removed
> Feb  2 00:00:04 quixote kernel: [141077.771903] plugin-containe[4968]: 
> segfault at 1ccfdd1123c4 ip 00007f3b59df9412 sp 00007ffc2fe526d8 error 
> 6 in libflashplayer.so[7f3b59788000+107a000]
> Feb  2 11:41:30 quixote rsyslogd: [origin software="rsyslogd" 
> swVersion="8.4.2" x-pid="2055" x-info="http://www.rsyslog.com"] start
> Feb  2 11:41:30 quixote kernel: [    0.000000] Initializing cgroup 
> subsys cpuset
> Feb  2 11:41:30 quixote kernel: [    0.000000] Initializing cgroup 
> subsys cpu
> Feb  2 11:41:30 quixote kernel: [    0.000000] Initializing cgroup 
> subsys cpuacct
> Feb  2 11:41:30 quixote kernel: [    0.000000] Linux version 
> 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 
> (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29)
> Feb  2 11:41:30 quixote kernel: [    0.000000] Command line: 
> BOOT_IMAGE=Jessie ro root=UUID=1a16b577-6751-412e-ba89-ca0718922385
> Feb  2 11:41:30 quixote kernel: [    0.000000] e820: BIOS-provided 
> physical RAM map:
> <SNIP>
>
The previous time that I had to reboot was two days ago.  The lines in 
/var/log/messages just prior to that reboot also point to segfaults in 
libflashplayer:

Jan 30 11:59:06 quixote kernel: [134871.151137] traps: 
plugin-containe[5434] general protection ip:7fc9105543aa sp:7ffef51c4240 
error:0 in libflashplayer.so[7fc90fe88000+107a000]
Jan 30 18:19:27 quixote kernel: [157729.969257] plugin-containe[32057]: 
segfault at 1a8 ip 00007f2657a2bfd9 sp 00007ffe71fb7d20 error 4 in 
libflashplayer.so[7f2657388000+107a000]
Jan 30 18:24:53 quixote kernel: [158056.527557] plugin-containe[352]: 
segfault at 1a8 ip 00007fa9c7f2bfd9 sp 00007ffca4961bc0 error 4 in 
libflashplayer.so[7fa9c7888000+107a000]
Jan 30 18:25:53 quixote kernel: [158116.346494] plugin-containe[723]: 
segfault at 237e0f7743c4 ip 00007f3d694f9412 sp 00007fffba01eed8 error 6 
in libflashplayer.so[7f3d68e88000+107a000]
Jan 31 08:53:21 quixote rsyslogd: [origin software="rsyslogd" 
swVersion="8.4.2" x-pid="1993" x-info="http://www.rsyslog.com"] start
Jan 31 08:53:21 quixote kernel: [    0.000000] Initializing cgroup 
subsys cpuset
Jan 31 08:53:21 quixote kernel: [    0.000000] Initializing cgroup 
subsys cpu
Jan 31 08:53:21 quixote kernel: [    0.000000] Initializing cgroup 
subsys cpuacct
Jan 31 08:53:21 quixote kernel: [    0.000000] Linux version 
3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 
(Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29)
Jan 31 08:53:21 quixote kernel: [    0.000000] Command line: auto 
BOOT_IMAGE=Jessie ro root=UUID=1a16b577-6751-412e-ba89-ca0718922385
Jan 31 08:53:21 quixote kernel: [    0.000000] e820: BIOS-provided 
physical RAM map:


According to adobe.com I currently have version 24.0.0.186 installed and 
the latest version available is 24.0.0.194.  I don't know if the update 
to 24.0.0.186 coincides with the start of my problems, or not.


Marc

[toc] | [prev] | [next] | [standalone]

#177330

From	David Christensen <dpchrist@holgerdanske.com>
Date	2017-02-03 07:30 +0100
Message-ID	<t6FxD-6j7-5@gated-at.bofh.it>
In reply to	#177310

On 02/02/17 13:05, Marc Shapiro wrote:
> I apologize for this being so long, but since the problem occurs
> sporadically I wanted to get as much information in this post as
> possible because I don't know when it will happen again.
...

What operating system are you running?  Please paste the following 
command into a root shell, run it, and then paste both the command and 
the output into your reply:

# cat /etc/debian_version; uname -a

Did you make any hardware, software, or configuration changes 
immediately prior to the initial event?

What is the make and model of the disk drive(s) that are having problems?

Have you looked at the SMART reports?  Please paste the following 
command into a root shell, run it once for each drive (replacing 
/dev/sdX with the corresponding device name), and paste both the command 
and the output into your reply:

# smartctl -x /dev/sdX

Have you downloaded and run the manufacturer diagnostic utilities for 
all your drives?  What do they say?

David

p.s. here are the links for the Intel, Seagate, and Western Digital 
drive diagnostics.  If your drive(s) are another brand, please find 
their tool and reply with the URL:

http://www.intel.com/content/www/us/en/support/solid-state-drives/ssd-software/intel-ssd-toolbox.html

http://www.seagate.com/support/downloads/seatools/

http://support.wdc.com/downloads.aspx?DL

[toc] | [prev] | [next] | [standalone]

#177331

From	Marc Shapiro <marcnshap@gmail.com>
Date	2017-02-03 08:40 +0100
Message-ID	<t6GDn-6W7-13@gated-at.bofh.it>
In reply to	#177330

On 02/02/2017 10:23 PM, David Christensen wrote:
> On 02/02/17 13:05, Marc Shapiro wrote:
>> I apologize for this being so long, but since the problem occurs
>> sporadically I wanted to get as much information in this post as
>> possible because I don't know when it will happen again.
> ...
>
> What operating system are you running?  Please paste the following 
> command into a root shell, run it, and then paste both the command and 
> the output into your reply:
>
> # cat /etc/debian_version; uname -a

root:/var/log# cat /etc/debian_version; uname -a
8.6
Linux quixote 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 
(2016-02-29) x86_64 GNU/Linux

>
>
> Did you make any hardware, software, or configuration changes 
> immediately prior to the initial event?
No.
>
>
> What is the make and model of the disk drive(s) that are having problems?
>
>
        *-disk
              description: ATA Disk
              product: ST31000528AS
              vendor: Seagate
              physical id: 0.0.0
              bus info: scsi@0:0.0.0
              logical name: /dev/sda
              version: CC3E
              serial: 5VP9QSWJ
              size: 931GiB (1TB)
              capabilities: partitioned partitioned:dos
              configuration: ansiversion=5 logicalsectorsize=512 
sectorsize=512 signature=0000575f


> Have you looked at the SMART reports?  Please paste the following 
> command into a root shell, run it once for each drive (replacing 
> /dev/sdX with the corresponding device name), and paste both the 
> command and the output into your reply:
>
> # smartctl -x /dev/sdX
root:/var/log# smartctl -x /dev/sda

bash: smartctl: command not found

What package would this be in?

>
>
> Have you downloaded and run the manufacturer diagnostic utilities for 
> all your drives?  What do they say?
>
>
> David
>
>
> p.s. here are the links for the Intel, Seagate, and Western Digital 
> drive diagnostics.  If your drive(s) are another brand, please find 
> their tool and reply with the URL:
>
> http://www.intel.com/content/www/us/en/support/solid-state-drives/ssd-software/intel-ssd-toolbox.html 
>
>
> http://www.seagate.com/support/downloads/seatools/
I see download links for DOS and Windows, nothiong for Linux
>
> http://support.wdc.com/downloads.aspx?DL
>

[toc] | [prev] | [next] | [standalone]

#177342

From	Mark Fletcher <mark27q1@gmail.com>
Date	2017-02-03 16:00 +0100
Message-ID	<t6Nvb-2PE-15@gated-at.bofh.it>
In reply to	#177331

On Thu, Feb 02, 2017 at 11:34:03PM -0800, Marc Shapiro wrote:
> 
> >Have you looked at the SMART reports?  Please paste the following command
> >into a root shell, run it once for each drive (replacing /dev/sdX with the
> >corresponding device name), and paste both the command and the output into
> >your reply:
> >
> ># smartctl -x /dev/sdX
> root:/var/log# smartctl -x /dev/sda
> 
> bash: smartctl: command not found
> 
> What package would this be in?
> 

apt-file search smartctl 

shows this is in package smartmontools (in Jessie, I assume same in 
other flavours)

Also it is installed in /usr/sbin which a non-root user doesn't usually 
have on their path, which implies it may have to be executed as root. 
The # in the sample command line also implies that, but just in case it 
wasn't obvious...

Mark

[toc] | [prev] | [next] | [standalone]

#177363

From	Marc Shapiro <marcnshap@gmail.com>
Date	2017-02-03 22:40 +0100
Message-ID	<t6TKi-7ml-9@gated-at.bofh.it>
In reply to	#177342

On 02/03/2017 06:50 AM, Mark Fletcher wrote:
> On Thu, Feb 02, 2017 at 11:34:03PM -0800, Marc Shapiro wrote:
>>> Have you looked at the SMART reports?  Please paste the following command
>>> into a root shell, run it once for each drive (replacing /dev/sdX with the
>>> corresponding device name), and paste both the command and the output into
>>> your reply:
>>>
>>> # smartctl -x /dev/sdX
>> root:/var/log# smartctl -x /dev/sda
>>
>> bash: smartctl: command not found
>>
>> What package would this be in?
>>
> apt-file search smartctl
>
> shows this is in package smartmontools (in Jessie, I assume same in
> other flavours)
>
> Also it is installed in /usr/sbin which a non-root user doesn't usually
> have on their path, which implies it may have to be executed as root.
> The # in the sample command line also implies that, but just in case it
> wasn't obvious...
>
> Mark
>
I had been trying as root (see above).  I do not have smartmontools 
currently installed.  If I remember correctly, that is only going to be 
useful if it was already installed so the daemon could be capturing data 
when the problem occurred.  Is that correct, or am I thinking of a 
different package?


Marc

[toc] | [prev] | [next] | [standalone]

#177522

From	Jonathan Dowland <jmtd@debian.org>
Date	2017-02-07 12:00 +0100
Message-ID	<t8bF8-1Lm-3@gated-at.bofh.it>
In reply to	#177363

[Multipart message — attachments visible in raw view] — view raw

On Fri, Feb 03, 2017 at 01:38:58PM -0800, Marc Shapiro wrote:
> I had been trying as root (see above).  I do not have smartmontools
> currently installed.  If I remember correctly, that is only going to be
> useful if it was already installed so the daemon could be capturing data
> when the problem occurred.  Is that correct, or am I thinking of a different
> package?

Different package maybe. The HDDs themselves maintain the logs, smartctl merely
prints them. If you had it installed already, you might have local logs from it
that would tell you when a problem was first noticed, but that's about it.

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.

[toc] | [prev] | [next] | [standalone]

#177364

From	Marc Shapiro <marcnshap@gmail.com>
Date	2017-02-03 22:50 +0100
Message-ID	<t6TTX-7qD-9@gated-at.bofh.it>
In reply to	#177330

On 02/02/2017 10:23 PM, David Christensen wrote:
>
> Have you downloaded and run the manufacturer diagnostic utilities for 
> all your drives?  What do they say?
>
I have now downloaded and run Seagate's tools and it does show a does 
show a disk error.  Since it stops on the first error I do not know if 
this is an isolated error, or a more systematic problem.

Automatic Write Reallocation Enable (AWRE) is on by default, but 
Automatic Read Reallocation Enable (ARRE) is off.  If I set ARRE on and 
then run the long test (which reads all sectors sequentially), will that 
reallocate any bad sectors and mark them as such?  Is this a safe thing 
to do?

Marc

[toc] | [prev] | [next] | [standalone]

#177373

From	David Christensen <dpchrist@holgerdanske.com>
Date	2017-02-04 08:20 +0100
Message-ID	<t72NA-5vS-9@gated-at.bofh.it>
In reply to	#177364

On 02/03/17 13:47, Marc Shapiro wrote:
> On 02/02/2017 10:23 PM, David Christensen wrote:
>>
>> Have you downloaded and run the manufacturer diagnostic utilities for
>> all your drives?  What do they say?
>>
> I have now downloaded and run Seagate's tools and it does show a does
> show a disk error.  Since it stops on the first error I do not know if
> this is an isolated error, or a more systematic problem.
>
> Automatic Write Reallocation Enable (AWRE) is on by default, but
> Automatic Read Reallocation Enable (ARRE) is off.  If I set ARRE on and
> then run the long test (which reads all sectors sequentially), will that
> reallocate any bad sectors and mark them as such?  Is this a safe thing
> to do?

Beware that failures have a way of escalating faster than you expect.

Do you have a good backup of the drive?

If not and the data has high value, do not power up the drive.  Pack it 
properly and send it to a professional recovery service.

 >> http://www.seagate.com/support/downloads/seatools/
 > I see download links for DOS and Windows, nothiong for Linux

It is common for Wintel-centric tools to only run on Windows.  It's good 
to keep an operational Windows system drive around.  Mobile docks make 
swapping drives easy.

Sometimes you get lucky and the tool is a live CD:

www.seagate.com/files/www-content/support-content/downloads/seatools/_shared/downloads/SeaToolsDOS223ALL.ISO

 > If I remember correctly, [SMART] is
 > only going to be useful if it was already installed so the daemon
 > could be capturing data when the problem occurred.  Is that correct,
 > or am I thinking of a different package?

https://en.wikipedia.org/wiki/S.M.A.R.T.

SMART is built-in to the firmware of the HDD/SSD; the drive 
microcontroller does most of the work.  Using the right tools, you can 
pull SMART information out of the microcontroller and/or adjust tunable 
SMART parameters.  As the drive is failing, you especially want those 
reports.  If you post them here, people can tell you all kinds of 
interesting things about your drive.

 > I have now downloaded and run Seagate's tools and it does show a does
 > show a disk error.  Since it stops on the first error I do not know if
 > this is an isolated error, or a more systematic problem.

Take a picture of the screen with a digital camera (or phone), and then 
type the exact screen contents into a reply.

David

[toc] | [prev] | [next] | [standalone]

#177502

From	Marc Shapiro <marcnshap@gmail.com>
Date	2017-02-06 22:20 +0100
Message-ID	<t7YRB-1TU-47@gated-at.bofh.it>
In reply to	#177373

On 02/03/2017 11:13 PM, David Christensen wrote:
> On 02/03/17 13:47, Marc Shapiro wrote:
>> On 02/02/2017 10:23 PM, David Christensen wrote:
>>>
>>> Have you downloaded and run the manufacturer diagnostic utilities for
>>> all your drives?  What do they say?
>>>
>> I have now downloaded and run Seagate's tools and it does show a does
>> show a disk error.  Since it stops on the first error I do not know if
>> this is an isolated error, or a more systematic problem.
>>
>> Automatic Write Reallocation Enable (AWRE) is on by default, but
>> Automatic Read Reallocation Enable (ARRE) is off.  If I set ARRE on and
>> then run the long test (which reads all sectors sequentially), will that
>> reallocate any bad sectors and mark them as such?  Is this a safe thing
>> to do?
>
> Beware that failures have a way of escalating faster than you expect.
>
>
> Do you have a good backup of the drive?
>
>
> If not and the data has high value, do not power up the drive. Pack it 
> properly and send it to a professional recovery service.
>
>
> >> http://www.seagate.com/support/downloads/seatools/
> > I see download links for DOS and Windows, nothiong for Linux
>
> It is common for Wintel-centric tools to only run on Windows. It's 
> good to keep an operational Windows system drive around. Mobile docks 
> make swapping drives easy.
>
>
> Sometimes you get lucky and the tool is a live CD:
>
> www.seagate.com/files/www-content/support-content/downloads/seatools/_shared/downloads/SeaToolsDOS223ALL.ISO 
>
>
>
> > If I remember correctly, [SMART] is
> > only going to be useful if it was already installed so the daemon
> > could be capturing data when the problem occurred.  Is that correct,
> > or am I thinking of a different package?
>
> https://en.wikipedia.org/wiki/S.M.A.R.T.
>
> SMART is built-in to the firmware of the HDD/SSD; the drive 
> microcontroller does most of the work.  Using the right tools, you can 
> pull SMART information out of the microcontroller and/or adjust 
> tunable SMART parameters.  As the drive is failing, you especially 
> want those reports.  If you post them here, people can tell you all 
> kinds of interesting things about your drive.
>
>
> > I have now downloaded and run Seagate's tools and it does show a does
> > show a disk error.  Since it stops on the first error I do not know if
> > this is an isolated error, or a more systematic problem.
>
> Take a picture of the screen with a digital camera (or phone), and 
> then type the exact screen contents into a reply.
>
>
> David
>
I am pasting the result of smartctl -x /dev/sda below as I have no real 
clue what to do with the information, but I have a few questions first.

1) I have purchased a new, very similar, Seagate 1TB drive and I plan to 
install it and copy the whole system to the new drive. What is the best 
way to do this copy since I don't wangt to copy bad sectors?

2) Once I have verified that the new drive boots and everything is 
running properly I am hoping to reformat the old drive.  This should 
reallocate the bad sectors IIRC.  I then would like to set up a raid 
with both drives (keeping a close eye on the old drive).  The 
feasibility of this, I would guess, depends on what the posted smartctl 
information tells someone who knows what to look for.

3) As I understand it, the above mentioned raid should be safe since, 
even if the old drive deteriorates further, the system can run on just 
the new drive.  Is that correct?


Here is the smafrtctl output:


$ sudo smartctl -x /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.12
Device Model:     ST31000528AS
Serial Number:    5VP9QSWJ
LU WWN Device Id: 5 000c50 03e5ccb5c
Firmware Version: CC3E
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Mon Feb  6 12:57:05 2017 PST

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/213891en

SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM level is:     0 (vendor specific), recommended: 254
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unknown

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)    Offline data collection activity
                     was completed without error.
                     Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121)    The previous self-test 
completed having
                     the read element of the test failed.
Total time to complete Offline
data collection:         (  600) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                     Auto Offline data collection on/off support.
                     Suspend Offline collection upon new
                     command.
                     Offline surface scan supported.
                     Self-test supported.
                     Conveyance Self-test supported.
                     Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                     power-saving mode.
                     Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                     General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 175) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x103f)    SCT Status supported.
                     SCT Error Recovery Control supported.
                     SCT Feature Control supported.
                     SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
   1 Raw_Read_Error_Rate     POSR--   117   095   006    - 165391146
   3 Spin_Up_Time            PO----   095   093   000    -    0
   4 Start_Stop_Count        -O--CK   100   100   020    -    406
   5 Reallocated_Sector_Ct   PO--CK   072   072   036    -    1181
   7 Seek_Error_Rate         POSR--   087   060   030    - 656506200
   9 Power_On_Hours          -O--CK   048   048   000    -    46195
  10 Spin_Retry_Count        PO--C-   100   100   097    -    0
  12 Power_Cycle_Count       -O--CK   100   100   020    -    203
183 Runtime_Bad_Block       -O--CK   092   092   000    -    8
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   011   011   000    -    89
188 Command_Timeout         -O--CK   100   097   000    - 51540394008
189 High_Fly_Writes         -O-RCK   100   100   000    -    0
190 Airflow_Temperature_Cel -O---K   070   049   045    -    30 (Min/Max 
27/32)
194 Temperature_Celsius     -O---K   030   051   000    -    30 (0 20 0 0 0)
195 Hardware_ECC_Recovered  -O-RC-   034   003   000    - 165391146
197 Current_Pending_Sector  -O--C-   093   083   000    -    310
198 Offline_Uncorrectable   ----C-   093   083   000    -    310
199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    26
240 Head_Flying_Hours       ------   100   253   000    -    46718 (49 76 0)
241 Total_LBAs_Written      ------   100   253   000    - 1725386978
242 Total_LBAs_Read         ------   100   253   000    - 265479204
                             ||||||_ K auto-keep
                             |||||__ C event count
                             ||||___ R error rate
                             |||____ S speed/performance
                             ||_____ O updated online
                             |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01       GPL,SL  R/O      1  Summary SMART error log
0x02       GPL,SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      5  Ext. Comprehensive SMART error log
0x06       GPL,SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09       GPL,SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa1       GPL,SL  VS      20  Device vendor specific log
0xa2       GPL     VS    2248  Device vendor specific log
0xa8       GPL,SL  VS     129  Device vendor specific log
0xa9       GPL,SL  VS       1  Device vendor specific log
0xb0       GPL     VS    2928  Device vendor specific log
0xbd       GPL     VS     252  Device vendor specific log
0xbe-0xbf  GPL     VS   65535  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 89 (device log contains only the most recent 20 errors)
     CR     = Command Register
     FEATR  = Features Register
     COUNT  = Count (was: Sector Count) Register
     LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
     LH     = LBA High (was: Cylinder High) Register    ]   LBA
     LM     = LBA Mid (was: Cylinder Low) Register      ] Register
     LL     = LBA Low (was: Sector Number) Register     ]
     DV     = Device (was: Device/Head) Register
     DC     = Device Control Register
     ER     = Error register
     ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 89 [8] occurred at disk power-on lifetime: 46170 hours (1923 days 
+ 18 hours)
   When the command that caused the error occurred, the device was 
active or idle.

   After command completion occurred, registers were:
   ER -- ST COUNT  LBA_48  LH LM LL DV DC
   -- -- -- == -- == == == -- -- -- -- --
   40 -- 51 00 00 00 0f 96 00 29 00 00 00  Error: UNC at LBA = 
0xf96002900 = 66941102336

   Commands leading to the command that caused the error were:
   CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time 
Command/Feature_Name
   -- == -- == -- == == == -- -- -- -- --  --------------- 
--------------------
   42 00 00 02 00 00 0f 96 00 29 00 40 00     09:03:21.547  READ VERIFY 
SECTOR(S) EXT
   42 00 00 02 00 00 0f 38 00 28 00 e0 00     09:03:21.123  READ VERIFY 
SECTOR(S) EXT
   42 00 00 02 00 00 0f 44 00 18 00 e0 00     09:03:16.898  READ VERIFY 
SECTOR(S) EXT
   42 00 00 02 00 00 0f 52 00 08 00 e0 00     09:03:12.615  READ VERIFY 
SECTOR(S) EXT
   42 00 00 02 00 00 0e 60 00 f8 00 e0 00     09:03:08.339  READ VERIFY 
SECTOR(S) EXT

Error 88 [7] occurred at disk power-on lifetime: 46169 hours (1923 days 
+ 17 hours)
   When the command that caused the error occurred, the device was 
active or idle.

   After command completion occurred, registers were:
   ER -- ST COUNT  LBA_48  LH LM LL DV DC
   -- -- -- == -- == == == -- -- -- -- --
   40 -- 51 00 00 00 0f 96 00 29 00 00 00  Error: UNC at LBA = 
0xf96002900 = 66941102336

   Commands leading to the command that caused the error were:
   CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time 
Command/Feature_Name
   -- == -- == -- == == == -- -- -- -- --  --------------- 
--------------------
   42 00 00 02 00 00 0f 96 00 29 00 e0 00     08:31:35.660  READ VERIFY 
SECTOR(S) EXT
   42 00 00 02 00 00 0f 94 00 29 00 40 00     08:31:35.026  READ VERIFY 
SECTOR(S) EXT
   42 00 00 02 00 00 0f cc 00 21 00 e0 00     08:31:32.951  READ VERIFY 
SECTOR(S) EXT
   42 00 00 02 00 00 0f dc 00 11 00 e0 00     08:31:28.721  READ VERIFY 
SECTOR(S) EXT
   42 00 00 02 00 00 0f e8 00 01 00 e0 00     08:31:24.439  READ VERIFY 
SECTOR(S) EXT

Error 87 [6] occurred at disk power-on lifetime: 46161 hours (1923 days 
+ 9 hours)
   When the command that caused the error occurred, the device was 
active or idle.

   After command completion occurred, registers were:
   ER -- ST COUNT  LBA_48  LH LM LL DV DC
   -- -- -- == -- == == == -- -- -- -- --
   40 -- 51 00 00 00 0f a7 00 29 f8 00 00  Error: UNC at LBA = 
0xfa70029f8 = 67226315256

   Commands leading to the command that caused the error were:
   CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time 
Command/Feature_Name
   -- == -- == -- == == == -- -- -- -- --  --------------- 
--------------------
   60 00 00 00 08 00 0f a7 00 29 f8 40 00  2d+13:14:24.209  READ FPDMA 
QUEUED
   61 00 00 00 10 00 19 ed 00 45 9c 40 00  2d+13:14:24.209  WRITE FPDMA 
QUEUED
   61 00 00 00 10 00 19 96 00 45 1c 40 00  2d+13:14:24.209  WRITE FPDMA 
QUEUED
   61 00 00 00 10 00 19 f9 00 19 a4 40 00  2d+13:14:24.209  WRITE FPDMA 
QUEUED
   61 00 00 00 50 00 19 0c 00 43 2c 40 00  2d+13:14:24.209  WRITE FPDMA 
QUEUED

Error 86 [5] occurred at disk power-on lifetime: 46161 hours (1923 days 
+ 9 hours)
   When the command that caused the error occurred, the device was 
active or idle.

   After command completion occurred, registers were:
   ER -- ST COUNT  LBA_48  LH LM LL DV DC
   -- -- -- == -- == == == -- -- -- -- --
   40 -- 51 00 00 00 0f a7 00 29 f8 00 00  Error: UNC at LBA = 
0xfa70029f8 = 67226315256

   Commands leading to the command that caused the error were:
   CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time 
Command/Feature_Name
   -- == -- == -- == == == -- -- -- -- --  --------------- 
--------------------
   60 00 00 00 08 00 0f a7 00 29 f8 40 00  2d+13:14:20.983  READ FPDMA 
QUEUED
   60 00 00 00 08 00 0f a8 00 29 08 40 00  2d+13:14:20.982  READ FPDMA 
QUEUED
   60 00 00 00 08 00 0f a8 00 29 00 40 00  2d+13:14:20.975  READ FPDMA 
QUEUED
   60 00 00 00 08 00 0f a0 00 29 08 40 00  2d+13:14:20.974  READ FPDMA 
QUEUED
   60 00 00 00 08 00 0f 9f 00 29 f8 40 00  2d+13:14:20.965  READ FPDMA 
QUEUED

Error 85 [4] occurred at disk power-on lifetime: 46161 hours (1923 days 
+ 9 hours)
   When the command that caused the error occurred, the device was 
active or idle.

   After command completion occurred, registers were:
   ER -- ST COUNT  LBA_48  LH LM LL DV DC
   -- -- -- == -- == == == -- -- -- -- --
   40 -- 51 00 00 00 0f 98 00 29 84 00 00  Error: WP at LBA = 
0xf98002984 = 66974656900

   Commands leading to the command that caused the error were:
   CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time 
Command/Feature_Name
   -- == -- == -- == == == -- -- -- -- --  --------------- 
--------------------
   61 00 00 00 08 00 19 0c 00 43 24 40 00  2d+13:14:17.731  WRITE FPDMA 
QUEUED
   60 00 00 00 08 00 0f 98 00 29 80 40 00  2d+13:14:17.730  READ FPDMA 
QUEUED
   ea 00 00 00 00 00 00 00 00 00 00 a0 00  2d+13:14:17.730  FLUSH CACHE EXT
   b0 00 da 00 00 00 00 4f 00 c2 00 00 00  2d+13:14:17.678  SMART RETURN 
STATUS
   60 00 00 00 08 00 0f 98 00 29 78 40 00  2d+13:14:17.650  READ FPDMA 
QUEUED

Error 84 [3] occurred at disk power-on lifetime: 46161 hours (1923 days 
+ 9 hours)
   When the command that caused the error occurred, the device was 
active or idle.

   After command completion occurred, registers were:
   ER -- ST COUNT  LBA_48  LH LM LL DV DC
   -- -- -- == -- == == == -- -- -- -- --
   40 -- 51 00 00 00 0f 98 00 29 4c 00 00  Error: UNC at LBA = 
0xf9800294c = 66974656844

   Commands leading to the command that caused the error were:
   CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time 
Command/Feature_Name
   -- == -- == -- == == == -- -- -- -- --  --------------- 
--------------------
   60 00 00 00 08 00 0f 98 00 29 48 40 00  2d+13:14:14.358  READ FPDMA 
QUEUED
   ea 00 00 00 00 00 00 00 00 00 00 a0 00  2d+13:14:14.358  FLUSH CACHE EXT
   b0 00 d1 00 01 00 00 4f 00 c2 00 00 00  2d+13:14:14.351  SMART READ 
ATTRIBUTE THRESHOLDS [OBS-4]
   27 00 00 00 00 00 00 00 00 00 00 e0 00  2d+13:14:14.291  READ NATIVE 
MAX ADDRESS EXT [OBS-ACS-3]
   ec 00 00 00 00 00 00 00 00 00 00 a0 00  2d+13:14:14.290 IDENTIFY DEVICE

Error 83 [2] occurred at disk power-on lifetime: 46161 hours (1923 days 
+ 9 hours)
   When the command that caused the error occurred, the device was 
active or idle.

   After command completion occurred, registers were:
   ER -- ST COUNT  LBA_48  LH LM LL DV DC
   -- -- -- == -- == == == -- -- -- -- --
   40 -- 51 00 00 00 0f 98 00 29 3c 00 00  Error: WP at LBA = 
0xf9800293c = 66974656828

   Commands leading to the command that caused the error were:
   CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time 
Command/Feature_Name
   -- == -- == -- == == == -- -- -- -- --  --------------- 
--------------------
   61 00 00 00 08 00 19 0b 00 43 bc 40 00  2d+13:14:11.084  WRITE FPDMA 
QUEUED
   60 00 00 00 08 00 0f 98 00 29 38 40 00  2d+13:14:11.083  READ FPDMA 
QUEUED
   ea 00 00 00 00 00 00 00 00 00 00 a0 00  2d+13:14:11.083  FLUSH CACHE EXT
   e5 00 00 00 00 00 00 00 00 00 00 00 00  2d+13:14:11.082  CHECK POWER MODE
   27 00 00 00 00 00 00 00 00 00 00 e0 00  2d+13:14:11.022  READ NATIVE 
MAX ADDRESS EXT [OBS-ACS-3]

Error 82 [1] occurred at disk power-on lifetime: 46161 hours (1923 days 
+ 9 hours)
   When the command that caused the error occurred, the device was 
active or idle.

   After command completion occurred, registers were:
   ER -- ST COUNT  LBA_48  LH LM LL DV DC
   -- -- -- == -- == == == -- -- -- -- --
   40 -- 51 00 00 00 0f 98 00 29 10 00 00  Error: WP at LBA = 
0xf98002910 = 66974656784

   Commands leading to the command that caused the error were:
   CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time 
Command/Feature_Name
   -- == -- == -- == == == -- -- -- -- --  --------------- 
--------------------
   61 00 00 00 08 00 19 96 00 45 14 40 00  2d+13:14:07.755  WRITE FPDMA 
QUEUED
   61 00 00 00 50 00 19 0b 00 43 6c 40 00  2d+13:14:07.755  WRITE FPDMA 
QUEUED
   61 00 00 00 08 00 19 f9 00 19 9c 40 00  2d+13:14:07.754  WRITE FPDMA 
QUEUED
   61 00 00 00 08 00 19 c8 00 19 34 40 00  2d+13:14:07.754  WRITE FPDMA 
QUEUED
   61 00 00 00 08 00 19 a4 00 19 94 40 00  2d+13:14:07.754  WRITE FPDMA 
QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining 
LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90% 46194         
254384128
# 2  Short offline       Completed without error       00% 8020         -

SMART Selective self-test log data structure revision number 1
  SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
     1        0        0  Not_testing
     2        0        0  Not_testing
     3        0        0  Not_testing
     4        0        0  Not_testing
     5        0        0  Not_testing
Selective self-test flags (0x0):
   After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       522 (0x020a)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    31 Celsius
Power Cycle Min/Max Temperature:     27/32 Celsius
Lifetime    Min/Max Temperature:     20/51 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        59 minutes
Min/Max recommended Temperature:     14/55 Celsius
Min/Max Temperature Limit:           10/60 Celsius
Temperature History Size (Index):    128 (116)

Index    Estimated Time   Temperature Celsius
  117    2017-02-01 07:56    27  ********
  118    2017-02-01 08:55    27  ********
  119    2017-02-01 09:54    27  ********
  120    2017-02-01 10:53    30  ***********
  ...    ..(  7 skipped).    ..  ***********
    0    2017-02-01 18:45    30  ***********
    1    2017-02-01 19:44    28  *********
    2    2017-02-01 20:43    28  *********
    3    2017-02-01 21:42    28  *********
    4    2017-02-01 22:41    29  **********
    5    2017-02-01 23:40    28  *********
    6    2017-02-02 00:39    29  **********
    7    2017-02-02 01:38    29  **********
    8    2017-02-02 02:37    31  ************
    9    2017-02-02 03:36    31  ************
   10    2017-02-02 04:35    28  *********
   11    2017-02-02 05:34    28  *********
   12    2017-02-02 06:33     ?  -
   13    2017-02-02 07:32    27  ********
  ...    ..(  3 skipped).    ..  ********
   17    2017-02-02 11:28    27  ********
   18    2017-02-02 12:27    29  **********
   19    2017-02-02 13:26    31  ************
   20    2017-02-02 14:25    30  ***********
   21    2017-02-02 15:24    31  ************
   22    2017-02-02 16:23    30  ***********
   23    2017-02-02 17:22    30  ***********
   24    2017-02-02 18:21    30  ***********
   25    2017-02-02 19:20    28  *********
   26    2017-02-02 20:19    30  ***********
   27    2017-02-02 21:18    30  ***********
   28    2017-02-02 22:17    28  *********
   29    2017-02-02 23:16    28  *********
   30    2017-02-03 00:15    29  **********
   31    2017-02-03 01:14    28  *********
   32    2017-02-03 02:13    28  *********
   33    2017-02-03 03:12    29  **********
   34    2017-02-03 04:11    29  **********
   35    2017-02-03 05:10    31  ************
   36    2017-02-03 06:09    29  **********
   37    2017-02-03 07:08    28  *********
   38    2017-02-03 08:07    27  ********
  ...    ..(  2 skipped).    ..  ********
   41    2017-02-03 11:04    27  ********
   42    2017-02-03 12:03    29  **********
   43    2017-02-03 13:02    32  *************
   44    2017-02-03 14:01    31  ************
   45    2017-02-03 15:00    28  *********
   46    2017-02-03 15:59    29  **********
   47    2017-02-03 16:58    29  **********
   48    2017-02-03 17:57    30  ***********
   49    2017-02-03 18:56    29  **********
   50    2017-02-03 19:55    30  ***********
   51    2017-02-03 20:54    29  **********
   52    2017-02-03 21:53    28  *********
   53    2017-02-03 22:52    28  *********
   54    2017-02-03 23:51    27  ********
   55    2017-02-04 00:50    28  *********
  ...    ..(  2 skipped).    ..  *********
   58    2017-02-04 03:47    28  *********
   59    2017-02-04 04:46    31  ************
   60    2017-02-04 05:45    30  ***********
   61    2017-02-04 06:44    29  **********
   62    2017-02-04 07:43    28  *********
   63    2017-02-04 08:42    28  *********
   64    2017-02-04 09:41    28  *********
   65    2017-02-04 10:40    30  ***********
   66    2017-02-04 11:39    29  **********
   67    2017-02-04 12:38    30  ***********
   68    2017-02-04 13:37    29  **********
   69    2017-02-04 14:36    31  ************
   70    2017-02-04 15:35    30  ***********
   71    2017-02-04 16:34    31  ************
   72    2017-02-04 17:33    29  **********
   73    2017-02-04 18:32    29  **********
   74    2017-02-04 19:31    30  ***********
   75    2017-02-04 20:30     ?  -
   76    2017-02-04 21:29    31  ************
   77    2017-02-04 22:28     ?  -
   78    2017-02-04 23:27    31  ************
   79    2017-02-05 00:26    31  ************
   80    2017-02-05 01:25    30  ***********
   81    2017-02-05 02:24    29  **********
  ...    ..(  5 skipped).    ..  **********
   87    2017-02-05 08:18    29  **********
   88    2017-02-05 09:17    30  ***********
   89    2017-02-05 10:16    30  ***********
   90    2017-02-05 11:15    29  **********
   91    2017-02-05 12:14    29  **********
   92    2017-02-05 13:13    30  ***********
   93    2017-02-05 14:12    32  *************
   94    2017-02-05 15:11    32  *************
   95    2017-02-05 16:10    31  ************
   96    2017-02-05 17:09    31  ************
   97    2017-02-05 18:08     ?  -
   98    2017-02-05 19:07    31  ************
   99    2017-02-05 20:06    31  ************
  100    2017-02-05 21:05    31  ************
  101    2017-02-05 22:04    29  **********
  102    2017-02-05 23:03    30  ***********
  103    2017-02-06 00:02    30  ***********
  104    2017-02-06 01:01    29  **********
  105    2017-02-06 02:00    29  **********
  106    2017-02-06 02:59    28  *********
  107    2017-02-06 03:58    27  ********
  108    2017-02-06 04:57    27  ********
  109    2017-02-06 05:56    28  *********
  110    2017-02-06 06:55    28  *********
  111    2017-02-06 07:54    28  *********
  112    2017-02-06 08:53    30  ***********
  113    2017-02-06 09:52    29  **********
  114    2017-02-06 10:51    27  ********
  115    2017-02-06 11:50    27  ********
  116    2017-02-06 12:49    31  ************

SCT Error Recovery Control:
            Read: Disabled
           Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
0x0001  2            0  Command failed due to ICRC error
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS

[toc] | [prev] | [next] | [standalone]

#177507

From	David Christensen <dpchrist@holgerdanske.com>
Date	2017-02-06 23:40 +0100
Message-ID	<t8070-2C6-23@gated-at.bofh.it>
In reply to	#177502

On 02/06/17 13:15, Marc Shapiro wrote:
> I am pasting the result of smartctl -x /dev/sda below as I have no real
> clue what to do with the information, but I have a few questions first.
>
> 1) I have purchased a new, very similar, Seagate 1TB drive and I plan to
> install it and copy the whole system to the new drive.

It sounds like you don't have a backup of the failing 1 TB drive (?).


Do you have a file server with ~1 TB of free space?  RAID?


Run memtest86+ for 24+ hours to verify that you don't have a memory problem.


Use SeaTools to wipe the new 1 TB drive and run the short and long 
tests.  Stop if anything fails.


> What is the best
> way to do this copy since I don't wangt to copy bad sectors?

I've done it with 'dd' in the past, but will use 'ddrescue' in the future.


> 2) Once I have verified that the new drive boots

I'd do a fresh install on a 16+ GB SSD (USB flash drives also work).  A 
recovered system disk image is too uncertain.


> and everything is running properly

As I understand it, the drive microcontroller calculates and stores a 
checksum with every sector (block).  That's one way it knows that a 
block is bad upon reading.  So, when you copy out whatever blocks you 
can get, you probably won't have errors in those blocks.


But, files and directories are stored on one or more sectors.  Depending 
upon your file system, fsck may or may not find the missing blocks.


When you're done, the destination disk is likely to be missing files 
and/or directories.


> I am hoping to reformat the old drive.  This should
> reallocate the bad sectors IIRC.  I then would like to set up a raid
> with both drives (keeping a close eye on the old drive).The
> feasibility of this, I would guess, depends on what the posted smartctl
> information tells someone who knows what to look for.
>
> 3) As I understand it, the above mentioned raid should be safe since,
> even if the old drive deteriorates further, the system can run on just
> the new drive.  Is that correct?

Once you've copied out whatever blocks you can get, use SeaTools to wipe 
the old 1 TB drive and run short and long tests.  If all three pass, I 
might be tempted to re-use the drive.


If it fails to wipe and has plaintext, destroy it with a sledge hammer. 
(Wear safety glasses!)


If it wipes but fails the short or long tests, recycle it.


> Here is the smafrtctl output:
...
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED

Interesting, given that the drive failed SeaTools (short test?).


> General SMART Values:
> Offline data collection status:  (0x82)    Offline data collection activity
>                     was completed without error.
>                     Auto Offline Data Collection: Enabled.
> Self-test execution status:      ( 121)    The previous self-test
> completed having
>                     the read element of the test failed.

Matches SeaTools result.


> Total time to complete Offline
> data collection:         (  600) seconds.
...
> SMART Attributes Data Structure revision number: 10
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
>   1 Raw_Read_Error_Rate     POSR--   117   095   006    - 165391146
>   3 Spin_Up_Time            PO----   095   093   000    -    0
>   4 Start_Stop_Count        -O--CK   100   100   020    -    406
>   5 Reallocated_Sector_Ct   PO--CK   072   072   036    -    1181
>   7 Seek_Error_Rate         POSR--   087   060   030    - 656506200
>   9 Power_On_Hours          -O--CK   048   048   000    -    46195
>  10 Spin_Retry_Count        PO--C-   100   100   097    -    0
>  12 Power_Cycle_Count       -O--CK   100   100   020    -    203
> 183 Runtime_Bad_Block       -O--CK   092   092   000    -    8
> 184 End-to-End_Error        -O--CK   100   100   099    -    0
> 187 Reported_Uncorrect      -O--CK   011   011   000    -    89
> 188 Command_Timeout         -O--CK   100   097   000    - 51540394008
> 189 High_Fly_Writes         -O-RCK   100   100   000    -    0
> 190 Airflow_Temperature_Cel -O---K   070   049   045    -    30 (Min/Max
> 27/32)
> 194 Temperature_Celsius     -O---K   030   051   000    -    30 (0 20 0
> 0 0)
> 195 Hardware_ECC_Recovered  -O-RC-   034   003   000    - 165391146
> 197 Current_Pending_Sector  -O--C-   093   083   000    -    310
> 198 Offline_Uncorrectable   ----C-   093   083   000    -    310
> 199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    26
> 240 Head_Flying_Hours       ------   100   253   000    -    46718 (49
> 76 0)
> 241 Total_LBAs_Written      ------   100   253   000    - 1725386978
> 242 Total_LBAs_Read         ------   100   253   000    - 265479204
>                             ||||||_ K auto-keep
>                             |||||__ C event count
>                             ||||___ R error rate
>                             |||____ S speed/performance
>                             ||_____ O updated online
>                             |______ P prefailure warning

I have yet to find a good explanation for reading smartctl reports. 
This post gives some clues:

https://ubuntuforums.org/showthread.php?t=2192335
Here are the statistics for my ST3000DM001:


Here is my ST3000DM001 for comparison:

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
   1 Raw_Read_Error_Rate     POSR--   115   099   006    -    90256224
   3 Spin_Up_Time            PO----   094   094   000    -    0
   4 Start_Stop_Count        -O--CK   100   100   020    -    577
   5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
   7 Seek_Error_Rate         POSR--   063   060   030    -    1955231
   9 Power_On_Hours          -O--CK   096   096   000    -    3552
  10 Spin_Retry_Count        PO--C-   100   100   097    -    0
  12 Power_Cycle_Count       -O--CK   100   100   020    -    576
183 Runtime_Bad_Block       -O--CK   100   100   000    -    0
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   100   100   000    -    0
188 Command_Timeout         -O--CK   100   100   000    -    0
189 High_Fly_Writes         -O-RCK   100   100   000    -    0
190 Airflow_Temperature_Cel -O---K   070   059   045    -    30 (Min/Max 
19/30)
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    0
192 Power-Off_Retract_Count -O--CK   100   100   000    -    35
193 Load_Cycle_Count        -O--CK   100   100   000    -    1323
194 Temperature_Celsius     -O---K   030   041   000    -    30 (0 17 0 0)
197 Current_Pending_Sector  -O--C-   100   100   000    -    0
198 Offline_Uncorrectable   ----C-   100   100   000    -    0
199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    0
240 Head_Flying_Hours       ------   100   253   000    -    269092585999820
241 Total_LBAs_Written      ------   100   253   000    -    2338230420
242 Total_LBAs_Read         ------   100   253   000    -    19882466886


These statistics for your drive look suspicious:

Reallocated_Sector_Ct
Reported_Uncorrect
Runtime_Bad_Block


...
> SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
> Device Error Count: 89 (device log contains only the most recent 20 errors)

That's not good.  Mine says:

No Errors Logged


> SMART Extended Self-test Log Version: 1 (1 sectors)
> Num  Test_Description    Status                  Remaining
> LifeTime(hours)  LBA_of_first_error
> # 1  Short offline       Completed: read failure       90% 46194

This could be SeaTools (?).


Let us know how it turns out.


David

[toc] | [prev] | [next] | [standalone]

#177392

From	Ric Moore <wayward4now@gmail.com>
Date	2017-02-04 16:20 +0100
Message-ID	<t7ai5-2gx-9@gated-at.bofh.it>
In reply to	#177364

On 02/03/2017 04:47 PM, Marc Shapiro wrote:
> On 02/02/2017 10:23 PM, David Christensen wrote:
>>
>> Have you downloaded and run the manufacturer diagnostic utilities for
>> all your drives?  What do they say?
>>
> I have now downloaded and run Seagate's tools and it does show a does
> show a disk error.  Since it stops on the first error I do not know if
> this is an isolated error, or a more systematic problem.

I'm looking at a Seagate 750 gig drive that went south on me with a pile 
of errors. Good luck getting Seagate to give a good gosh darn. In the 
past I have had mixed results replacing the drive motherboard. I saved 
two out of three. I doubt I will buy anything Seagate makes in the 
future. Ric

-- 
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

[toc] | [prev] | [next] | [standalone]

#177414

From	David Christensen <dpchrist@holgerdanske.com>
Date	2017-02-04 20:20 +0100
Message-ID	<t7e2l-4XW-11@gated-at.bofh.it>
In reply to	#177392

On 02/04/17 07:18, Ric Moore wrote:
> I'm looking at a Seagate 750 gig drive that went south on me with a pile
> of errors. Good luck getting Seagate to give a good gosh darn. In the
> past I have had mixed results replacing the drive motherboard. I saved
> two out of three. I doubt I will buy anything Seagate makes in the
> future.

Everything electrical and mechanical fails.  It's just a question of 
when, followed by whether or not you're prepared.

I've found (and heard) that the worst thing I can do to a HDD is put it 
on the shelf and let it rot.  I've had more than a few that failed 
shortly after being put into a computer.

David

[toc] | [prev] | [next] | [standalone]

#177483

From	Joe Pfeiffer <pfeiffer@cs.nmsu.edu>
Date	2017-02-06 17:00 +0100
Message-ID	<t7TRT-6RC-7@gated-at.bofh.it>
In reply to	#177414

David Christensen <dpchrist@holgerdanske.com> writes:

> On 02/04/17 07:18, Ric Moore wrote:
>> I'm looking at a Seagate 750 gig drive that went south on me with a pile
>> of errors. Good luck getting Seagate to give a good gosh darn. In the
>> past I have had mixed results replacing the drive motherboard. I saved
>> two out of three. I doubt I will buy anything Seagate makes in the
>> future.
>
> Everything electrical and mechanical fails.  It's just a question of
> when, followed by whether or not you're prepared.
>
>
> I've found (and heard) that the worst thing I can do to a HDD is put
> it on the shelf and let it rot.  I've had more than a few that failed
> shortly after being put into a computer.

I hadn't heard this...  I've got a drive I've been keeping as a cold
spare.  Am I better off (in the sense of "is it more likely to actually
be useable when I need it") installing it and adding it to one of my
RAID1 arrays?  Can you point me to an article about it?

[toc] | [prev] | [next] | [standalone]

#177491

From	Gene Heskett <gheskett@shentel.net>
Date	2017-02-06 18:30 +0100
Message-ID	<t7VgZ-80j-1@gated-at.bofh.it>
In reply to	#177483

On Monday 06 February 2017 10:22:54 Joe Pfeiffer wrote:

> David Christensen <dpchrist@holgerdanske.com> writes:
> > On 02/04/17 07:18, Ric Moore wrote:
> >> I'm looking at a Seagate 750 gig drive that went south on me with a
> >> pile of errors. Good luck getting Seagate to give a good gosh darn.
> >> In the past I have had mixed results replacing the drive
> >> motherboard. I saved two out of three. I doubt I will buy anything
> >> Seagate makes in the future.
> >
> > Everything electrical and mechanical fails.  It's just a question of
> > when, followed by whether or not you're prepared.
> >
> >
> > I've found (and heard) that the worst thing I can do to a HDD is put
> > it on the shelf and let it rot.  I've had more than a few that
> > failed shortly after being put into a computer.
>
> I hadn't heard this...  I've got a drive I've been keeping as a cold
> spare.  Am I better off (in the sense of "is it more likely to
> actually be useable when I need it") installing it and adding it to
> one of my RAID1 arrays?  Can you point me to an article about it?

That cold spare will eventually develop stiction, seizing the parked haed 
to the surface of the disk solidly enough that the disk motor cannot 
break it loose to spin the disk up.  Such is best treated by hooking up 
the cables, but holding the drive in your hand so that you can turn on 
the power, and within a couple seconds, give the drive a good sideways 
blow on a corner with the ball of the wrist so the drive housing/casting 
is caused to rotate a few degrees around the axis of the disk, breaking 
the stiction so the spindle motor can spin it up. The theory is that the 
drive frame rotates when you drive it by hitting the corner, but the 
disk doesn't, breaking the stiction seal.

Based on my experience here, with terabyte drives, they seem to be better 
off spinning even when not in active service. I have one old terabyte 
drive thats had 25 bad, re-allocated clusters, since the first time I 
had smartctl do an extended self test on it several years ago. It still 
has 25 reallocated sectors this day, with (word wrapped):
 5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  
Always       -       25
and
  9 Power_On_Hours          0x0032   030   030   000    Old_age   
Always       -       61430

And that drive gets beat on every night as its my backup disk containing 
all the virtual tapes amanda uses.

In terms of spin time, thats 6.997490303 years.  And thats a Seagate 
Barracuda drive, which has a horrible reputation according to these 
mailing lists.

One secret though. When that drive was new to me, I went to the seagate 
web site and downloaded a cd image for that model that updated its 
firmware. As I already had a linux install on it, I applied it to that 
drive with a bit of trepidation. But worry wasn't needed, I didn't lose 
a byte of the install. But a side benefit was that the drives speed was 
nearly doubled.

If you can afford the time, I highly recommend putting the latest 
firmware in it before putting it in service. Who knows how long its been 
on the dealers warehouse shelf, but the dealer bought 10,000 when they 
were announced. And the initial shipment can be guaranteed to have been 
bagged with Alpha rated firmware in it.  Always update new drives is the 
message from this elderly (82) user.  You won't regret it.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#177503

From	David Christensen <dpchrist@holgerdanske.com>
Date	2017-02-06 22:30 +0100
Message-ID	<t7Z1g-1XE-33@gated-at.bofh.it>
In reply to	#177491

On 02/06/17 09:28, Gene Heskett wrote:
> That cold spare will eventually develop stiction, seizing the parked haed
> to the surface of the disk solidly enough that the disk motor cannot
> break it loose to spin the disk up.  Such is best treated by hooking up
> the cables, but holding the drive in your hand so that you can turn on
> the power, and within a couple seconds, give the drive a good sideways
> blow on a corner with the ball of the wrist so the drive housing/casting
> is caused to rotate a few degrees around the axis of the disk, breaking
> the stiction so the spindle motor can spin it up. The theory is that the
> drive frame rotates when you drive it by hitting the corner, but the
> disk doesn't, breaking the stiction seal.

Yowza!  I haven't experienced (realized?) a head-stuck-to-platter 
problem, but I'll keep your technique in mind if all else fails.


David

[toc] | [prev] | [next] | [standalone]

#177505

From	Felix Miata <mrmazda@earthlink.net>
Date	2017-02-06 23:20 +0100
Message-ID	<t7ZND-2v6-1@gated-at.bofh.it>
In reply to	#177491

Gene Heskett composed on 2017-02-06 12:28 (UTC-0500):

> That cold spare will eventually develop stiction, seizing the parked haed
> to the surface of the disk solidly enough that the disk motor cannot
> break it loose to spin the disk up.  Such is best treated by hooking up
> the cables, but holding the drive in your hand so that you can turn on
> the power, and within a couple seconds, give the drive a good sideways
> blow on a corner with the ball of the wrist so the drive housing/casting
> is caused to rotate a few degrees around the axis of the disk, breaking
> the stiction so the spindle motor can spin it up. The theory is that the
> drive frame rotates when you drive it by hitting the corner, but the
> disk doesn't, breaking the stiction seal.

The other theory is the motor got too weak to start the platters in motion. It 
wouldn't surprise me that these things have separate electronics for startup and 
for maintain, and that something in startup simply expires to cause spinup failure.

The first HD I ever bought, a 3.5" "full-height" SCSI-I 80MB Seagate in 1990, 
acquired the won't spin up problem a month after its 12 month warranty expired. 
I avoided the problem a long time via a UPS, but eventually an extended power 
outage claimed it permanently.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#177504

From	David Christensen <dpchrist@holgerdanske.com>
Date	2017-02-06 22:30 +0100
Message-ID	<t7Z1g-1XE-37@gated-at.bofh.it>
In reply to	#177483

On 02/06/17 07:22, Joe Pfeiffer wrote:
> David Christensen <dpchrist@holgerdanske.com> writes:
>> I've found (and heard) that the worst thing I can do to a HDD is put
>> it on the shelf and let it rot.  I've had more than a few that failed
>> shortly after being put into a computer.
>
> I hadn't heard this...  I've got a drive I've been keeping as a cold
> spare.  Am I better off (in the sense of "is it more likely to actually
> be useable when I need it") installing it and adding it to one of my
> RAID1 arrays?  Can you point me to an article about it?

I don't know of a particular article.  I just have personal experience 
and advice from other people (including a relative who worked for a HDD 
manufacturer).


David

[toc] | [prev] | [standalone]

csiph-web

How to fix I/O errors?

Contents

#177310 — How to fix I/O errors?

#177312

#177313

#177315

#177330

#177331

#177342

#177363

#177522

#177364

#177373

#177502

#177507

#177392

#177414

#177483

#177491

#177503

#177505

#177504