senser errors.

Kevin Foote kevin.foote at
Tue Jan 9 13:32:31 CST 2007

Thanks for that explanation on all that scsi talk.

>What I find interesting is that location is very near the end of a
>"73 GB" disk.  In fact, it may be the last block

The kernel reports 143374650 512-byte hdwr sectors before it gets into all
the sense errors ...
So would this actually be the end or would the sectors in my errors be the
actual end ??

I found one other person via these archives that had a similar issue
with these drives (ST373454LC) the firmware supplied by dell fixed his

A firmware update is what dell recommended to me as well.

Do you or anyothers have any thoughts on updating the firmware on a disk
with data on it.
Since I do a md raid then I could alwase yank the mirror and update the
firmware see if it changes


> Message: 3
> Date: Thu, 4 Jan 2007 02:50:39 -0500
> From: "Ben Scott" <dragonhawk at>
> Subject: Re: sense errors..
> To: Linux-PowerEdge at
> Message-ID:
>         <155dc4110701032350l5fd1a06k27f46f82ca22429 at>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> On 1/2/07, Kevin Foote <kevin.foote at> wrote:
> > hostX kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB: ...
>   Error on controller (card) zero, channel (bus) zero, target zero,
> logical unit zero.  "CDB" stands for "Command Descriptor Block" (or
> something like that) and is only useful to people who know the SCSI
> protocol in binary.
> > hostX kernel: Info fld=0x88b8f17, Current sda: sense key Medium Error
>   In SCSI-land, "sense" is the mechanism for reporting detailed
> information.  The target (disk) just reports that it had an error; the
> initiator (computer) has to then ask the target for the "sense data"
> to find out the details about the error.
>   "Medium Error" means the target (disk) reported a problem with the
> physical medium (i.e., the disk itself).  Note that this is just what
> the target reported, not necessarily what is actually wrong.  Hardware
> can have bugs, too.
> > hostX kernel: Additional sense: Data synchronization mark error
>   "Data synchronization mark error" is the specific error code.  I've
> never seen that before and have no idea what it means.  Google mostly
> finds listings of that error in the SCSI spec documents.
>   So that's a weird one.  It seems to happy a lot, though.  That's not
> good.
> > hostX kernel: end_request: I/O error, dev sda, sector 143363863
>   That's being reported by the higher levels of the kernel.  It
> basically means that it tried to read block 143363863 and it failed
> ("I/O error").  The more specific problem has already been logged.
>   What I find interesting is that location is very near the end of a
> "73 GB" disk.  In fact, it may be the last block.  In fact, it may be
> *beyond* the last block.  In other words, the system may be trying to
> read beyond the end of the disk.  There's a few different reasons why
> that might happen (e.g., corrupt file system, corrupt partition table,
> faulty disk capacity identification), but it's something to keep in
> mind.
>   If you can afford to lose the contents of a disk, try a destructive
> write test:
> badblocks -s -v -w /dev/sda
> > hostX kernel: Additional sense: Unrecovered read error
>   That doesn't sound good either.
> -- Ben
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Linux-PowerEdge mailing list