Re: Dead brand new SCSI drive?

From: Steve Schreiber (sschreibATTmagmaDOTTca)
Date: 02/14/04

  • Next message: Edward Alfert: "Re: Dead brand new SCSI drive?" 
    Date: Sat, 14 Feb 2004 13:52:42 -0500

    Edward Alfert wrote:
    > Steve Schreiber <sschreibATTmagmaDOTTca> wrote in
    > news:m8KdnbqZhdLqwLPdRVn-uQ@magma.ca:
    >
    >
    >>Hey,
    >>
    >> Any chance it is a termination problem? I have had that before,
    >> and
    >>that's what the problem was. Just forgot the stupid terminator!
    >
    >
    > The terminator is permanently attached to the cable. The cable has
    > connectors for 4 harddrives. This is the cable that came with the Dell
    > server. So I do not believe this is my problem.
    >
    > I do notice that the harddrives have "Termination Power" jumpers. All four
    > drives have this jumper on. The two drives that came from installed from
    > Dell had them on the "on" position so when I added the two new drives I
    > left them "on" also.
    >
    > But in readining the Maxtor documentation for the dirve, it says, "TP -
    > Termination Power: Pins 27-28 - Termination power ensures that there is a
    > sufficient power level along the entire SCSI bus. It is recommended that
    > the final device on the SCSI bus have the Termination Power jumper
    > installed. All devices in between the host and final device typically have
    > no jumper on Termination Power. Note that Termination Power is not the
    > same as on-board termination, which this drive does not support.".
    >
    > It does not say that all devices in between the host and final device "have
    > to have" the jumper off. It says that "typically" it has it off. But I
    > guess I can try removing the Termination Power Jumper from the middle two
    > drives and see if this fixes my problem. But, remember that all 3 Fujitsu
    > are working with all having this jumper on.
    >
    >
    >>Might want to make sure the terminator has the right impedance to,
    >>have had those problems before as well. It is giving an I/O error on
    >>sector 0, can you try plowing a disk label onto it?
    >
    >
    > I'm sorry but you lost me there. If you can give me the command to put a
    > "disk label" on the drive, I can then do a man on the command or do some
    > research. But without knowing which command to use, I'm at a loss.
    >
    >
    >>zero the disk
    >>maybe(dd)?
    >
    >
    > I'll do some research on dd to see how to do that. Thanks for the pointer.
    >
    >
    >>Just throwing thing out for you...
    >> S.
    >
    >
    > Thanks for your help.
    >
    >
    Hey,

            I noticed the error you posted in your first email:

    Feb 14 12:11:02 blue kernel: Device 08:30 not ready.
    Feb 14 12:11:02 blue kernel: I/O error: dev 08:30, sector 0

    I am not certain (maybe someone could verify) if this is the maj/min
    number this error is refering to 8:30, on my system, 8,30 is sdb14.

    brw-rw---- 1 root disk 8, 30 Jan 30 2003 sdb14

    Your :
            8 48 143666192 sdd 7 21 56 0 0 0 0 0 0 0 0

    line matches up to my device files. Is there anyway your devices files
    are mucked up? Unless someone can verify that is what the error is,
    this may not be of much help... but you can take a look at it and maybe
    determine for yourself.

    To zero a disk with `dd` issue: `dd if=/dev/zero of=/dev/<device> bs=512
    count=(x)` <device> in your case would be /dev/sdd, and (x) is pretty
    much whatever you want... As for putting in a disklabel, I am not
    certain how to do it on Linux. fdisk should have (?) a 'default'
    disklabel it can put to the disk. Some Unix equivs. have problems with
    disk with no disklabeling on them, so have this feature (although I
    would assume that Linux would not have these problems since it is not
    brain-damaged as most propriatary Unix flavours). Something else to
    look at. The only other problem I have had with SCSI drives that really
    screwed me up was the Adaptec built-in low level format tool. I
    canceled out of it once about half way though (an hour in) and I
    couldn't do anything with the disk until I went through the whole
    process again-but letting it finish! I don't suppose you formatted it
    with this tool did you?

            S. 

    -- 
--> GNU/Linux is user friendly... it's just picky about its friends.
  • Next message: Edward Alfert: "Re: Dead brand new SCSI drive?"

    Relevant Pages

    • Re: Errors during shadow set merge
      ... I have been getting errors during shadow set merges since I bought ... If you don't have a service contract, order a replacement disk ... Or it could be a problem with SCSI bus termination, ...
      (comp.os.vms)
    • Re: mobile rack termination question
      ... attach both disks to an internal SCSI bus, ... What automatic termination. ... the disk is detected during boot, ... Since when do drives do autotermination. ...
      (comp.periphs.scsi)
    • Re: SCSI Problem
      ... > the one with the termination. ... Now when the system boots I get the ... The controller is an Adaptec 2940UW. ... configuration software shows one disk on ID 0 and the controller on ID ...
      (freebsd-questions)
    • Re: Trying to rescue a hard disk -- weired feedback??
      ... The broken hard disk is a dual boot SCSI disk that worked. ... to recover the data by switching the electronics between the drives. ... more then 2 devices providing termination or if they ate not at each ...
      (Fedora)
    • Re: Importing Dynamic Disks
      ... tryed several other ghosting tools and they all give me a block error. ... The Seagate drive i have for some reason does not support self termination. ... I dont think it had a RAID setup, as when i tryed importing the drive there ... >> dynamic disk. ...
      (microsoft.public.windowsxp.help_and_support)