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, USB-connected hard disks
> > suffer these problems much more than PATA/SATA/eSATA/SCSI/SAS
> > disks do.
> >
>
> What about solid state hard drives that can be connected via USB drive? I
> heard solid state hard drives are more dependable (but expensive) than the
> usual (IDE?) ones. Does USB connection matter there too?

I haven't any experience with those, other than thumb-sized
sticks and the like. I suspect the problem is the USB connection
rather than the drive technology.

-dsr-


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120902135040.GP4974@randomstring.org">http://lists.debian.org/20120902135040.GP4974@randomstring.org

Kamaraju S Kusumanchi <raju.mailinglists@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 error<y>? yes
> Force rewrite<y>? yes
> 3) Is the drive going bad and need to be replaced?

Corresponding entries in /var/log/syslog about the inability to read
sectors from this device would indicate that there is a hardware
problem. Provided that all connections and the power supply are ok, I
would say the device is broken when there are such errors in syslog.

In case there aren't errors in syslog, I would look somewhere else
first.

Are you really still using ext2fs?


Besides, is the device in question an SSD disk connected via USB? Why
would anyone connect an SSD drive via USB? And do you get the same
errors in syslog with an SSD drive as you get with an SATA or SCSI
drive? SSDs don't really have sectors, do they?


--
Debian testing amd64


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87mx18320v.fsf@yun.yagibdah.de">http://lists.debian.org/87mx18320v.fsf@yun.yagibdah.de

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 have to connect it to the controller
directly OR You can not use what the SMART offers to You. That simple.

Personally, I do not believe that the HDD is not extractable -
speaking in general.


Sthu.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 50462eca.6327700a.6991.fffffe81@mx.google.com">htt p://lists.debian.org/50462eca.6327700a.6991.fffffe81@mx.google.com

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)


Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic

Good time of the day, Andrei.


You wrote:

> To quote an uncle of mine, one only needs a "persuader" (read:
> hammer)

You have very wise uncle! )


Sthu.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 50463907.a808700a.782f.fffffd58@mx.google.com">htt p://lists.debian.org/50463907.a808700a.782f.fffffd58@mx.google.com

lee wrote:

> Kamaraju S Kusumanchi <raju.mailinglists@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 error<y>?
>> yes Force rewrite<y>? yes
>> 3) Is the drive going bad and need to be replaced?
>
> Corresponding entries in /var/log/syslog about the inability to read
> sectors from this device would indicate that there is a hardware
> problem. Provided that all connections and the power supply are ok, I
> would say the device is broken when there are such errors in syslog.
>
> In case there aren't errors in syslog, I would look somewhere else
> first.

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 block 5384273
Aug 30 08:27:20 kusumanchi kernel: [118453.221584] Buffer I/O error on
device sdb7, logical block 5384274
Aug 30 08:27:20 kusumanchi kernel: [118453.223310] Buffer I/O error on
device sdb7, logical block 5384275
Aug 30 08:27:20 kusumanchi kernel: [118453.224973] Buffer I/O error on
device sdb7, logical block 5384276
Aug 30 08:27:20 kusumanchi kernel: [118453.226582] Buffer I/O error on
device sdb7, logical block 5384277
Aug 30 08:27:20 kusumanchi kernel: [118453.228158] Buffer I/O error on
device sdb7, logical block 5384278
Aug 30 08:27:20 kusumanchi kernel: [118453.229713] Buffer I/O error on
device sdb7, logical block 5384279



>
> Are you really still using ext2fs?

The partitions are ext3. Is there a better command to check ext3 partitions
other than ext2fs?

> Besides, is the device in question an SSD disk connected via USB? Why
> would anyone connect an SSD drive via USB? And do you get the same
> errors in syslog with an SSD drive as you get with an SATA or SCSI
> drive? SSDs don't really have sectors, do they?

No, this is not an SSD drive. It is the ordinary (IDE?) drive with an
enclosure connected via USB. I do not have any experience with SSD drives.

thanks
--
Kamaraju S Kusumanchi
http://malayamaarutham.blogspot.com/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/k27gri$7jt$1@ger.gmane.org

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. See
<http://sourceforge.net/apps/trac/smartmontools/wiki/Supported_USB-Devices>,
which tells me that lucky me, my WD Elements Desktop 2TB is supported.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120905124315.GB31962@debian

Kamaraju S Kusumanchi <raju.mailinglists@gmail.com> writes:

> lee wrote:
>
>> Kamaraju S Kusumanchi <raju.mailinglists@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 error<y>?
>>> yes Force rewrite<y>? yes
>>> 3) Is the drive going bad and need to be replaced?
>>
>> Corresponding entries in /var/log/syslog about the inability to read
>> sectors from this device would indicate that there is a hardware
>> problem. Provided that all connections and the power supply are ok, I
>> would say the device is broken when there are such errors in syslog.
>>
>> In case there aren't errors in syslog, I would look somewhere else
>> first.
>
> 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

That seems to indicate that the disk is broken. At first I thought these
messages look different from what I've seen, but googling shows quite
some agreement that messages like this tell you that the disk is
damaged.

>> Are you really still using ext2fs?
>
> The partitions are ext3. Is there a better command to check ext3 partitions
> other than ext2fs?

See man fsck ... running "fsck -t ext2" probably ends up doing the same
thing as calling the fs-type specific checking tool directly, though.


--
Debian testing amd64


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87d320s2sw.fsf@yun.yagibdah.de">http://lists.debian.org/87d320s2sw.fsf@yun.yagibdah.de

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 block 5384273
> Aug 30 08:27:20 kusumanchi kernel: [118453.221584] Buffer I/O error
> on device sdb7, logical block 5384274
> Aug 30 08:27:20 kusumanchi kernel: [118453.223310] Buffer I/O error
> on device sdb7, logical block 5384275
> Aug 30 08:27:20 kusumanchi kernel: [118453.224973] Buffer I/O error
> on device sdb7, logical block 5384276
> Aug 30 08:27:20 kusumanchi kernel: [118453.226582] Buffer I/O error
> on device sdb7, logical block 5384277
> Aug 30 08:27:20 kusumanchi kernel: [118453.228158] Buffer I/O error
> on device sdb7, logical block 5384278
> Aug 30 08:27:20 kusumanchi kernel: [118453.229713] Buffer I/O error
> on device sdb7, logical block 5384279

It seems that the *ATA-USB controller just quitted from its work
- therefore it is not the HDD failure - simply reset the controller.


Sthu.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 50483978.5086980a.14ad.0ab5@mx.google.com">http://lists.debian.org/50483978.5086980a.14ad.0ab5@mx.google.com

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 SMART, but some do. See
> <http://sourceforge.net/apps/trac/smartmontools/wiki/Supported_USB-Devices>,
> which tells me that lucky me, my WD Elements Desktop 2TB is supported.

We will hope OP is lucky also.


Sthu.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 5048395f.ed7a980a.658e.0b4b@mx.google.com">http://lists.debian.org/5048395f.ed7a980a.658e.0b4b@mx.google.com