Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

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

bad sectors on disk

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

Contents

  bad sectors on disk Ritesh Raj Sarraf <rrs@researchut.com> - 2016-02-09 10:00 +0100
    Re: bad sectors on disk Hans <hans.ullrich@loop.de> - 2016-02-09 10:20 +0100
    Re: bad sectors on disk "Thomas Schmitt" <scdbackup@gmx.net> - 2016-02-09 11:20 +0100
      Re: bad sectors on disk Ritesh Raj Sarraf <rrs@researchut.com> - 2016-02-09 12:00 +0100
        Re: bad sectors on disk "Thomas Schmitt" <scdbackup@gmx.net> - 2016-02-09 13:00 +0100
          Re: bad sectors on disk Eike Lantzsch <zp6cge@gmx.net> - 2016-02-09 13:30 +0100
            Re: bad sectors on disk Eike Lantzsch <zp6cge@gmx.net> - 2016-02-09 13:50 +0100
          Re: bad sectors on disk Ritesh Raj Sarraf <rrs@researchut.com> - 2016-02-10 15:20 +0100
            Re: bad sectors on disk "Thomas Schmitt" <scdbackup@gmx.net> - 2016-02-10 15:40 +0100
        Re: bad sectors on disk jdd <jdd@dodin.org> - 2016-02-09 13:10 +0100
    Re: bad sectors on disk Jonathan Dowland <jmtd@debian.org> - 2016-02-09 16:20 +0100
    Re: bad sectors on disk David Christensen <dpchrist@holgerdanske.com> - 2016-02-09 20:30 +0100
      Re: bad sectors on disk "Thomas Schmitt" <scdbackup@gmx.net> - 2016-02-09 21:00 +0100
    Re: [computers] bad sectors on disk TWS Admin <tws@wilderness.org.au> - 2016-02-11 05:00 +0100
      Re: [computers] bad sectors on disk Joseph Loo <jloo20111002@gmail.com> - 2016-02-11 05:10 +0100
        Re: [computers] bad sectors on disk David Wright <deblis@lionunicorn.co.uk> - 2016-02-12 05:20 +0100
          Re: bad sectors on disk "Thomas Schmitt" <scdbackup@gmx.net> - 2016-02-12 08:50 +0100
            Re: bad sectors on disk Gene Heskett <gheskett@shentel.net> - 2016-02-12 09:30 +0100
              SATA cables David Christensen <dpchrist@holgerdanske.com> - 2016-02-12 18:30 +0100
                Re: SATA cables Ric Moore <wayward4now@gmail.com> - 2016-02-14 01:20 +0100
                  Re: SATA cables Gene Heskett <gheskett@shentel.net> - 2016-02-14 02:00 +0100
                  Re: SATA cables David Christensen <dpchrist@holgerdanske.com> - 2016-02-14 05:40 +0100
                    Re: SATA cables Ric Moore <wayward4now@gmail.com> - 2016-02-14 17:30 +0100
            Re: bad sectors on disk Ritesh Raj Sarraf <rrs@researchut.com> - 2016-02-16 14:40 +0100
              Re: bad sectors on disk Ritesh Raj Sarraf <rrs@researchut.com> - 2016-02-16 15:00 +0100
              Re: bad sectors on disk "Thomas Schmitt" <scdbackup@gmx.net> - 2016-02-16 15:10 +0100
          Re: [computers] bad sectors on disk jdd <jdd@dodin.org> - 2016-02-12 09:30 +0100

Page 2 of 2 — ← Prev page 1 [2]

#164151 — Re: SATA cables

On Saturday 13 February 2016 19:15:31 Ric Moore wrote:

> On 02/12/2016 12:21 PM, David Christensen wrote:
> > On 02/12/2016 12:24 AM, Gene Heskett wrote:
>
> ...
>
> >  > 'hot red' colored wire in a mic cable that always broke, ...
> >  > After a year or 2, there was no wire remaining in that tubing,
> >  > just a reddish copper dust!
> >
> > Wow.  Somebody didn't understand chemistry/ metallurgy.  I'd suspect
> > the copper before the insulation (or the jacket), but only a
> > chemical assessment would tell.
>
> I personally know that Gene hails back to the days when real men used
> soldering irons in the TV broadcast industry. On another list Gene
> made the same claim about 5 years ago. All of my drives were acting
> flakey, so I took his hint and replaced the cables with black ones. No
> more problems.

> As far as the chemistry goes, if the red dye contained 
> an oxidizer, then the heat from the amperage flowing in the cable
> would cause gassing and a faster oxidation rate.

Maybe Ric, but the current in the mic cables was perhaps 20 milliamps in 
a 22 or 24 gauge wire. The red wire was normally used for the PtT 
switch, which either ran the transmit/receive relay, or did it even more 
dependably with electronic switching. I wouldn't say zero heating, but 
it wouldn't be detectable by any instruments you or I can muster for the 
task.

Essentially ditto for the sata cables, thats all signaling stuff, and 
even at a 3Ghz data rate, again even the wave currant would not exceed 
20 mills, for perhaps 10% of the time in a well designed circuit.

So IMCO, and as a C.E.T., heating of the cable from anything but nearby 
heat radiated INTO it, is miniscule in the grand picture. I do NOT know 
whats in that hot red dye, but wrap it around a copper conductor and 
youi have signed its eventual death warrant.

> Copper does oxidize 
> quite readily. I spent 26 years in the chemical industry and a 20
> degree rise above room temperature would cause some of our caustics to
> eat everything that attempted to pump them. So, while someone might
> not know chemistry/metallurgy, it might not be Gene. Ric

Thanks for the backup Ric, its appreciated.

Hows the phantom leg doing?  Well I hope.  I still have both feet, but I 
am paying attention to the glucose test results /most/ of the time.  Its 
my back, kidneys, and prostate that worry me, in that order.

Some marching orders from Grandpa Gene, Take care.  And keep the other 
leg, ya hear?
 
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]

#164152 — Re: SATA cables

On 02/13/2016 04:15 PM, Ric Moore wrote:
> ... All of my drives were acting flakey,
> so I took his hint and replaced the cables with black ones.

What make and model?


David

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

#164158 — Re: SATA cables

On 02/13/2016 11:36 PM, David Christensen wrote:
> On 02/13/2016 04:15 PM, Ric Moore wrote:
>> ... All of my drives were acting flakey,
>> so I took his hint and replaced the cables with black ones.
>
> What make and model?

Heh, that was 5 years ago, but they are still in use. :) 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]

#164236

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

On Fri, 2016-02-12 at 08:42 +0100, Thomas Schmitt wrote:
> Hi,
> 
> Ritesh Raj Sarraf wrote:
> > > >     From the report, it says that there are 0 bad blocks. So is
> this a
> > > >     bug in e2fsprogs ?
> 
> David Wright wrote:
> > Does one I/O error mean that you have a bad block necessarily?
> 
> I personally do not believe in a bad spot here, but in a bad bus.
> Throwing out blocks which fall victim to a bus glitch would then
> unnecessarily kill files and reduce disk capacity.

Taking the thread further.

A couple days ago, I removed the smartmontools package. I suspected
that that may be causing trouble. For the last couple days, my klog was
clean and I was tempted to report.

But just now, I got a more enhanced scsi error, this time. Does it
suggest bad sectors ?

Thomas: In the last responses, you asked if there was any Sense key.
This time, I do have them.

[498597.450874] blk_update_request: critical medium error, dev sda,
sector 3632093759
[498601.069250] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00
driverbyte=0x08
[498601.077151] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] 
[498601.082621] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x0 
[498601.087452] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 d8 7d 5a 8f 00
00 08 00
[498601.094711] blk_update_request: critical medium error, dev sda,
sector 3632093839
[498604.422352] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00
driverbyte=0x08
[498604.430263] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] 
[498604.435766] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x0 
[498604.440543] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 d8 7d 5a 8f 00
00 08 00
[498604.447824] blk_update_request: critical medium error, dev sda,
sector 3632093839
[498607.715027] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00
driverbyte=0x08
[498607.722919] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] 
[498607.728444] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x0 
[498607.733232] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 d8 7d 5a 8f 00
00 08 00
[498607.740485] blk_update_request: critical medium error, dev sda,
sector 3632093839


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

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

#164238

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

On Tue, 2016-02-16 at 19:00 +0530, Ritesh Raj Sarraf wrote:
> A couple days ago, I removed the smartmontools package. I suspected
> that that may be causing trouble. For the last couple days, my klog
> was
> clean and I was tempted to report.

I installed smartmontools again, and ran some commands manually. And
have some concerning report. And I think the reporting may be correct
because where my HDD is located, temperature may be high.


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

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

#164241

Hi,

Ritesh Raj Sarraf wrote:
> Thomas: In the last responses, you asked if there was any Sense key.
> This time, I do have them.
> 
> [498601.069250] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
> [498601.077151] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] 
> [498601.082621] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x0 
> [498601.087452] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 d8 7d 5a 8f 00 00 08 00
> [498601.094711] blk_update_request: critical medium error, dev sda, sector 3632093839
> ...
> [498604.440543] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 d8 7d 5a 8f 00 00 08 00
> ...
> [498607.733232] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 d8 7d 5a 8f 00 00 08 00

This one looks much more like a conventional bad spot.

- Other than previously, "driverbyte" is not 0 but 8.
  This means that the disk firmware indicated SCSI Sense Data
  (i.e. error codes) [1]:
    "0x08 | DRIVER_SENSE   | had sense information available"

- "Sense Key : 0x3" categorizes the problem as error of the medium.
  "ASC=0x11 ASCQ=0x0" means according to [2]:
    "UNRECOVERED READ ERROR 

- This time, the error happens reproducibly at the same block address
  0xd87d5a8f = 3632093839.
  (The first line of your log snippet shows decimal address 3632093759.
   Is this the end of another group of failed "CDB: opcode=0x28" ?)


> Does it suggest bad sectors ?

I'd say that this is something different than your previous problem.
If the following command reliably reports i/o error and causes messages
in the system log, then badblock scan and treatment would be indicated:

  dd if=/dev/sda of=/dev/null bs=512 count=1 skip=3632093839

Especially since the volatile errors did not show up any more.


[1] http://www.tldp.org/HOWTO/archived/SCSI-Programming-HOWTO/SCSI-Programming-HOWTO-21.html#ss21.5
[2] http://www.tldp.org/HOWTO/archived/SCSI-Programming-HOWTO/SCSI-Programming-HOWTO-22.html#ss22.1


Have a nice day :)

Thomas

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

#164099 — Re: [computers] bad sectors on disk

Le 12/02/2016 05:12, David Wright a écrit :

>
> I can't see any point in running badblocks and not putting any bad
> blocks that it finds into the badblock inode. So running
>

inode is related to filesystem, so any repartitioning needs to re-run 
badblocks and can be as long as one day. I often noticed than badblocks 
are not a number and grouped. It's then possible to isolate them in a 
special partition small and never used - I use these disks only for 
experiment

jdd

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web