From: Wakko Warner <wakko@animx.eu.org>
To: Richard Scobie <richard@sauce.co.nz>
Cc: linux-scsi@vger.kernel.org
Subject: Re: mptsas problem
Date: Sun, 6 Apr 2008 21:04:53 -0400 [thread overview]
Message-ID: <20080407010453.GA1952@animx.eu.org> (raw)
In-Reply-To: <47F95F5C.500@sauce.co.nz>
Richard Scobie wrote:
> > I recall seeing some of this problem on the list a few days ago, but
> I > can't remember what the subject was and was unable to find the thread.
>
> You are perhaps thinking of this:
>
> http://marc.info/?l=linux-scsi&m=120696978819085&w=2
Yes.
> but it seems to be a different issue.
Ok.
> From the message you posted, it looks as though there may be a problem
> with sda.
It's working fine with /sys/block/sd[abc]/device/queue_depth = 1 (on boot up,
as stated before, it's 64)
I performed the same copy again with queue_depth=1 after the array rebuilt.
It worked fine then. No errors.
> Does smartctl -a -d ata /dev/sda show any obvious problems?
smartctl doesn't work on sd[a-d] at all:
# smartctl -a -d ata /dev/sdd
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)
A mandatory SMART command failed: exiting. To continue, add one or more '-T
permissive' options.
# smartctl -a -d ata -T permissive /dev/sdd
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)
=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number: [No Information Found]
Firmware Version: [No Information Found]
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 1
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sun Apr 6 21:02:45 2008 EDT
SMART is only available in ATA Version 3 Revision 3 or greater.
We will try to proceed in spite of this.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
Checking for SMART support by trying SMART ENABLE command.
Error SMART Enable failed: Invalid argument
SMART ENABLE failed - this establishes that this device lacks SMART functionality.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
#
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
next prev parent reply other threads:[~2008-04-07 1:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 23:40 mptsas problem Richard Scobie
2008-04-07 1:04 ` Wakko Warner [this message]
2008-04-13 13:00 ` Douglas Gilbert
2008-04-13 14:39 ` James Bottomley
2008-04-13 14:31 ` James Bottomley
2008-04-13 16:48 ` Wakko Warner
2008-04-13 16:58 ` James Bottomley
2008-04-13 17:06 ` Wakko Warner
2008-04-13 17:37 ` James Bottomley
2008-04-13 20:49 ` Wakko Warner
2008-04-14 18:16 ` Moore, Eric
2008-04-14 21:34 ` Wakko Warner
2008-04-15 17:26 ` Moore, Eric
2008-04-15 22:49 ` Wakko Warner
2008-04-13 22:22 ` Douglas Gilbert
2008-04-13 23:51 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2008-04-06 19:56 Wakko Warner
[not found] ` <0631C836DBF79F42B5A60C8C8D4E8229F64FC1@NAMAIL2.ad.lsil.com>
2008-04-07 1:07 ` Wakko Warner
2008-04-07 11:36 ` Bernd Schubert
2008-04-07 15:16 ` Moore, Eric
2008-04-07 16:54 ` Wakko Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080407010453.GA1952@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-scsi@vger.kernel.org \
--cc=richard@sauce.co.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox