Re: Possible faulty drive
From: Richard Brodie (R.Brodie_at_rl.ac.uk)
Date: 03/31/05
- Next message: JF Mezei: "Re: test- please ignoe"
- Previous message: Phillip Helbig---remove CLOTHES to reply: "Re: ports 135, 445, 139 and 1433"
- In reply to: Jeff Cameron: "Re: Possible faulty drive"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 31 Mar 2005 10:07:38 +0100
"Jeff Cameron" <roktsci@comcast.net> wrote in message news:BE70BAB7.A861%roktsci@comcast.net...
> > Port Status x0000032C DEVCMDERR - device command error
> > SCSI Command Opcode x12 Inquiry
> > Command Data
> > x00
> > x00
> > x00
> > xFF
> > x00
> This section of the SCSI command indicates that the driver is requesting
> what I believe to be device geometry information.
Actually, it's just asking for basic device information. Essentially the same stuff
as SHOW DEVICE shows: device type, manufacturer id etc. It must have
worked (once) to load the disk driver at all though.
> I'm also confused as to why the command is 5 bytes instead of 4. Most narrow
> SCSI commands are two 16 bit words.
6 bytes is the smallest command size, which this is (including the 0x12).
I would start looking at the simple things: cabling, termination, bus length
(and width). There doesn't appear to be a clean data path.
- Next message: JF Mezei: "Re: test- please ignoe"
- Previous message: Phillip Helbig---remove CLOTHES to reply: "Re: ports 135, 445, 139 and 1433"
- In reply to: Jeff Cameron: "Re: Possible faulty drive"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|