> On Mon, 14 Dec 1998, Ulf Jaenicke-Roessler wrote:
[...]
> > ide: i82371 PIIX (Triton) on PCI bus 0 function 57
> > ide0: BM-DMA at 0xe800-0xe807
> > ide1: BM-DMA at 0xe808-0xe80f
> > hda: ST36531A, 6204MB w/128kB Cache, CHS=790/255/63, DMA
> > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > [...]
> > Partition check:
> > hda:hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> > hda: set_multmode: error=0x04 { DriveStatusError }
> > hda1 hda2 < hda5 hda6 hda7 hda8 hda9 >
> >
> > The current development kernel 2.1.131 doesn't show this error.
[...]
> The stable kernel still has the original settings of '0' as default.
> But his sounds like a problem for you. I believe that there is a setting
> in ide.h that will allow you to change that option; however, I am only
> relearning the stable code after years of neglect, due to SMP issues.
>
> > So I wonder if this message indicates a real error? Or is it a kernel
> > issue? I don't have any (obvious?) problem using this drive after booting.
I tried to get some information with hdparm. And I get the "DriveReady
SeekComplete Error" again:
[~] # hdparm -I /dev/hda
/dev/hda:
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
Model=TS6335A1 , FwRev=.350 , SerialNo=SG214836
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=13446/15/63, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=0(?), BuffSize=128kB, MaxMultSect=32, MultSect=32
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
CurCHS=13446/15/63, CurSects=12706470, LBA=yes
LBA CHS=790/255/63 Remapping, LBA=yes, LBAsects=12706470
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2
[~] # hdparm -i /dev/hda
/dev/hda:
HDIO_GET_IDENTITY failed: Bad address
[~] # hdparm -v /dev/hda
/dev/hda:
multcount = 0 (off)
I/O support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 790/255/63, sectors = 12706470, start = 0
[~] # hdparm -Z /dev/hda
/dev/hda:
disabling Seagate auto powersaving mode
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
HDIO_DRIVE_CMD failed: Input/output error
I have no problems so far with this fairly new drive. I've been using it
for about one month.
>From the information above, is it "safe" to use this drive?
BTW, is it normal, that the model name is byte-wise swapped?
Thanks,
Ulf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/