lee wrote:
Kamaraju S Kusumanchi raju.mailingli...@gmail.com writes:
When I ran
$sudo e2fsck -c -c -f -v /dev/sdb7
I am getting a lot of errors such as
Error reading block 18022401 (Attempt to read block from filesystem
resulted
in short read) while reading inode and block bitmaps.
On Tue, Sep 04, 2012 at 11:39:37PM +0700, Sthu Deus wrote:
You have to understand: You have to connect it to the controller
directly OR You can not use what the SMART offers to You. That simple.
This is not actually true. Yes, the majority of USB hard drives do not support
SMART, but some do.
Kamaraju S Kusumanchi raju.mailingli...@gmail.com writes:
lee wrote:
Kamaraju S Kusumanchi raju.mailingli...@gmail.com writes:
When I ran
$sudo e2fsck -c -c -f -v /dev/sdb7
I am getting a lot of errors such as
Error reading block 18022401 (Attempt to read block from filesystem
Good time of the day, Jon.
Thank You for Your correction.
You wrote:
You have to understand: You have to connect it to the controller
directly OR You can not use what the SMART offers to You. That
simple.
This is not actually true. Yes, the majority of USB hard drives do
not support
Good time of the day, Kamaraju.
You wrote:
Yes, there are I/O errors in syslog such as
Aug 30 08:27:20 kusumanchi kernel: [118453.218041] Buffer I/O error
on device sdb7, logical block 5384272
Aug 30 08:27:20 kusumanchi kernel: [118453.219839] Buffer I/O error
on device sdb7, logical
Good time of the day, Kamaraju.
You wrote:
May be I am missing something here. The USB hard drive I am talking
is very similar to http://www.amazon.com/Iomega-Prestige-Portable-
SuperSpeed-35192/dp/B004NIAG5E/ref=cm_cr_pr_product_top . The case
can't be removed.
You have to understand: You
On Ma, 04 sep 12, 23:39:37, Sthu Deus wrote:
Personally, I do not believe that the HDD is not extractable -
speaking in general.
To quote an uncle of mine, one only needs a persuader (read: hammer)
:D
Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
Good time of the day, Andrei.
You wrote:
To quote an uncle of mine, one only needs a persuader (read:
hammer) :D
You have very wise uncle! :o)
Sthu.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Thu, Aug 30, 2012 at 11:40:55PM -0400, Kamaraju S Kusumanchi wrote:
Dan Ritter wrote:
On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote:
4) What might have caused this problem and how to prevent it in the
future?
I don't know, but in my experience,
Kamaraju S Kusumanchi raju.mailingli...@gmail.com writes:
When I ran
$sudo e2fsck -c -c -f -v /dev/sdb7
I am getting a lot of errors such as
Error reading block 18022401 (Attempt to read block from filesystem resulted
in short read) while reading inode and block bitmaps. Ignore errory?
Federico Alberto Sayd wrote:
Did you try to diagnose your hardrive with smartmontools? Smartmontools
uses S.M.A.R.T.[1] technology included in harddrives, and displays info
about predictable failures, time of use, etc.
Regards
[1] http://en.wikipedia.org/wiki/S.M.A.R.T.
$smartctl -a
Good time of the day, Kamaraju.
You wrote:
$smartctl -a /dev/sdb
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.0.0-1-686-pae] (local
build) Copyright (C) 2002-11 by Bruce Allen,
http://smartmontools.sourceforge.net
/dev/sdb: Unknown USB bridge [0x059b:0x0571 (0x000)]
Smartctl: please
Sthu Deus wrote:
You will not be able to do so until You connect Your drive to computer
directly - i.e. through PATA/SATA cable.
This is an external USB hard drive. The only connection it has is USB. So, I
guess in this case smartctl is not much useful.
--
Kamaraju S Kusumanchi
On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote:
1) Does this mean there are badblocks on my hard drive?
Yes.
2) Am I correct in choosing yes to both these questions or is there a
better way?
Yes.
3) Is the drive going bad and need to be replaced?
Yes.
4) What
On Thursday 30 August 2012 19:17:14 Kamaraju S Kusumanchi wrote:
Sthu Deus wrote:
You will not be able to do so until You connect Your drive to computer
directly - i.e. through PATA/SATA cable.
This is an external USB hard drive. The only connection it has is USB. So,
I guess in this case
Kamaraju, You wrote:
You will not be able to do so until You connect Your drive to
computer directly - i.e. through PATA/SATA cable.
This is an external USB hard drive. The only connection it has is
USB. So, I guess in this case smartctl is not much useful.
And You can not disassemble
Sthu Deus wrote:
Kamaraju, You wrote:
You will not be able to do so until You connect Your drive to
computer directly - i.e. through PATA/SATA cable.
This is an external USB hard drive. The only connection it has is
USB. So, I guess in this case smartctl is not much useful.
And
Dan Ritter wrote:
On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote:
4) What might have caused this problem and how to prevent it in the
future?
I don't know, but in my experience, USB-connected hard disks
suffer these problems much more than PATA/SATA/eSATA/SCSI/SAS
When I ran
$sudo e2fsck -c -c -f -v /dev/sdb7
I am getting a lot of errors such as
Error reading block 18022401 (Attempt to read block from filesystem resulted
in short read) while reading inode and block bitmaps. Ignore errory? yes
Force rewritey? yes
Error reading block 19562497 (Attempt to
On 28/08/12 10:28, Kamaraju S Kusumanchi wrote:
When I ran
$sudo e2fsck -c -c -f -v /dev/sdb7
I am getting a lot of errors such as
Error reading block 18022401 (Attempt to read block from filesystem resulted
in short read) while reading inode and block bitmaps. Ignore errory? yes
Force
20 matches
Mail list logo
