Re: bad sectors on disk

2016-02-16 Thread Thomas Schmitt
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]  >

Re: bad sectors on disk

2016-02-16 Thread Ritesh Raj Sarraf
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

Re: bad sectors on disk

2016-02-16 Thread Ritesh Raj Sarraf
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? >

Re: bad sectors on disk

2016-02-12 Thread Gene Heskett
On Friday 12 February 2016 02:42:19 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

Re: bad sectors on disk

2016-02-11 Thread Thomas Schmitt
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

Re: bad sectors on disk

2016-02-10 Thread Thomas Schmitt
Hi, Ritesh Raj Sarraf wrote: > I've seen the same message again, today. but at different locations. > [...] there are no other message about any sense code. One point for the theory of volatile bus problems. The disk itself seems happy. Maybe its bus controller is not. Did i already mention

Re: bad sectors on disk

2016-02-10 Thread Ritesh Raj Sarraf
Hello Thomas, On Tue, 2016-02-09 at 12:53 +0100, Thomas Schmitt wrote: >  > > Linux pi 4.1.16-v7+ #833 SMP Wed Jan 27 14:32:22 GMT 2016 armv7l > GNU/Linux > > The source code where i find the message text in my Sid kernel > is not depending on the CPU architecture. So it is supposed to be > in

Re: bad sectors on disk

2016-02-09 Thread David Christensen
On 02/09/2016 12:57 AM, Ritesh Raj Sarraf wrote: On my RPi2, I saw the following reported by my kernel. ... This got me worried so I ran an fsck on my drive. Following is the report. ... SEAGATE: * FILE SYSTEM WAS MODIFIED * ... I suggest that you download Seagate's Seatools for

Re: bad sectors on disk

2016-02-09 Thread Thomas Schmitt
Hi, Ritesh Raj Sarraf's kernel wrote: > [156278.815976] sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 > driverbyte=0x00 > [156278.823864] sd 1:0:0:0: [sdb] CDB: opcode=0x28 28 00 9a 40 04 47 00 00 08 > 00 > [156278.831152] blk_update_request: I/O error, dev sdb, sector 2587886663

Re: bad sectors on disk

2016-02-09 Thread Hans
> > >From the report, it says that there are 0 bad blocks. So is this a bug in > > e2fsprogs ? Please correct me, if I am wrong. As far as I know, bad sectors are blanked out by the hardware itself. If bad sectors are detected, the software tries to read and then move the data to a good

Re: bad sectors on disk

2016-02-09 Thread Ritesh Raj Sarraf
Hello Thomas, Thank you for your response. On Tue, 2016-02-09 at 11:17 +0100, Thomas Schmitt wrote: > Hi, > > Ritesh Raj Sarraf's kernel wrote: > > [156278.815976] sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: > > hostbyte=0x00 driverbyte=0x00 > > [156278.823864] sd 1:0:0:0: [sdb] CDB: opcode=0x28

Re: bad sectors on disk

2016-02-09 Thread Jonathan Dowland
It would be interesting to check your drive's SMART data to see if that has reported any errors. You might be able to do this with smartctl from the smartmontools package, depending on which USB bridge you have. I recently uploaded a new version of the package to unstable, but I do not know

Re: bad sectors on disk

2016-02-09 Thread Thomas Schmitt
Hi, > Thank you for your response. Purely selfish. :) I want to know about cabling problems. > Linux pi 4.1.16-v7+ #833 SMP Wed Jan 27 14:32:22 GMT 2016 armv7l GNU/Linux The source code where i find the message text in my Sid kernel is not depending on the CPU architecture. So it is supposed

Re: bad sectors on disk

2016-02-09 Thread Eike Lantzsch
On Tuesday 09 February 2016 09:25:40 Eike Lantzsch wrote: > Hi Ritesh Raj Sarraf > > Just a thought - my two cents: > > On Tuesday 09 February 2016 12:53:04 Thomas Schmitt wrote: > > Hi, > > > > > Thank you for your response. > > > > Purely selfish. :) > > I want to know about cabling

Re: bad sectors on disk

2016-02-09 Thread Eike Lantzsch
Hi Ritesh Raj Sarraf Just a thought - my two cents: On Tuesday 09 February 2016 12:53:04 Thomas Schmitt wrote: > Hi, > > > Thank you for your response. > > Purely selfish. :) > I want to know about cabling problems. > > > Linux pi 4.1.16-v7+ #833 SMP Wed Jan 27 14:32:22 GMT 2016 armv7l

Re: bad sectors on disk

2016-02-09 Thread jdd
Le 09/02/2016 11:54, Ritesh Raj Sarraf a écrit : I am hoping the fsck results are reliable. I only tried the "-c" read- only option. The other was with "-cc" which would also perform a read/write test. try http://dodin.info/wiki/pmwiki.php?n=Doc.TesterUnDisqueDur it's in french, but the

Re: bad sectors on disk

2016-02-09 Thread Thomas Schmitt
Hi, David Christensen wrote: > http://www.seagate.com/support/downloads/seatools/ > convert a bootable CD ISO image into a bootable hybrid ISO/USB image > https://www.turnkeylinux.org/blog/iso2usb This will not work, i fear, because the ISO is not bootable via an isohybrid capable ISOLINUX boot