scsirastools-developers — Developer list for scsirastools raid1 project

RE: [Scsirastools-developers] [PATCH] support more device types in sgcommon

[Cress, A. R <and...@in...>]

Thanks Nate,

I merged this in and will put out a new release soon.

Andy=20

-----Original Message-----
From: scs...@li...
[mailto:scs...@li...] On Behalf
Of Dailey, Nate
Sent: Tuesday, May 10, 2005 3:41 PM
To: 'scs...@li...'
Cc: Dailey, Nate
Subject: [Scsirastools-developers] [PATCH] support more device types in
sgcommon

I don't know if anyone else would find this useful, but...

The following patch adds a few peripheral device types to the
devtype_array
in sgcommon. Without this change, I couldn't issue commands (bus reset,
for
example) in sgdiag via an enclosure services device.

I also made a change to remove a check on "devstat[0] > DEVT_MAX"
because
the same check is performed again just a few lines below.

This patch is against scsirastools 1.4.14.

Nate Dailey
Stratus Technologies

[Scsirastools-developers] [PATCH] support more device types in sgcommon

[Dailey, N. <Nat...@st...>]

I don't know if anyone else would find this useful, but...

The following patch adds a few peripheral device types to the devtype_array
in sgcommon. Without this change, I couldn't issue commands (bus reset, for
example) in sgdiag via an enclosure services device.

I also made a change to remove a check on "devstat[0] > DEVT_MAX" because
the same check is performed again just a few lines below.

This patch is against scsirastools 1.4.14.

Nate Dailey
Stratus Technologies

[Scsirastools-developers] [PATCH] support more devices in sgdiag and check devlist array bo unds

[Dailey, N. <Nat...@st...>]

I hit a segmentation fault in sgdiag on a system with more than 32 devices.
It turns out that there's no bounds checking on the devlist array, so
additional devices trample on memory outside the devlist. The attached patch
prevents writing outside the bounds of the array, and also ups the number of
devices.

It looks like the same problem exists in sgdefects, sgdskfl, and sgmode, but
I haven't tested them to verify.

This patch is against scsirastools 1.4.14.

Nate Dailey
Stratus Technologies

[Scsirastools-developers] scsirastools 1.4.14 is released

[Cress, A. R <and...@in...>]

scsirastools-1.4.14 is now available on http://scsirastools.sf.net.=20
=20
This release was to fix bug 1167994 wrt the Makefiles.=20

1.4.14 =3D released 04/27/05, updated 04/27/05=20
   doc/Makefile.am     new, for automake extensions=20
   files/Makefile.am   new, for automake extensions=20
   mdadm.d/Makefile.am new, for automake extensions=20
   configure.in        update for doc/Makefile, files/Makefile

Andy=20

[Scsirastools-developers] scsirastools 1.4.3 is released

[Cress, A. R <and...@in...>]

A new scsirastools-1.4.13 tarball and rpms have been released at
http://scsirastools.sf.net.

This fixes a bug in the sgraid init.d script, which was introduced in
1.4.11 (Sorry).

Details:
1.4.13 =3D released 02/10/05, updated 02/10/05
  sgraid           fixed bug in start (from 1.4.11), thought already
started
  Makefile.am      Fixed make tarball to do 'make distclean', not
distclean-am.

Andy


Andy Cress                 =20
Senior Software Engineer    and...@in...
Intel Corporation, Columbia Design Center, CBA1
100 Center Point Cir., Suite 200, Columbia, SC 29210
http://ipmiutil.sf.net   http://scsirastools.sf.net
BTW, I speak for myself, not for Intel Corp.
"Do not merely look out for your own personal interests, but also for
the interests of others." Phil 2:4

[Scsirastools-developers] scsirastools 1.4.12 is released

[Cress, A. R <and...@in...>]

The scsirastools-1.4.12 version is now released.
See http://scsirastools.sf.net for tarball, rpms, etc.

Changes:
1.4.12 =3D released 02/04/05, updated 02/02/05
  doc/Makefile          changes for /usr/share/man
  doc/scsirastools.spec changes for /usr/share/man, change for rpm -U

Andy

[Scsirastools-developers] scsirastools 1.4.11 is released

[Cress, A. R <and...@in...>]

A new version 1.4.11 of SCSI RAS Tools has been released.=20
See http://scsirastools.sf.net for rpms and more info.
=20
The changes since 1.4.9 are:=20
1.4.10 =3D released 11/10/04, updated 08/03/04=20
         sgraidmon v1.25 if sense 2:4:1, try start_unit before
device_reset,=20
         also check more conditions in safte_inserted=20
         sgraidmon v1.26 write to log in quit() before exiting=20
1.4.11 =3D released 02/02/05, updated 01/31/05=20
         sgmode v1.9 added decodemodebuf to decode certain mode pages=20
         sgraid modified startup script for SuSE, /var/lock file.

Andy

[Scsirastools-developers] RE: sgdiag, STOP_UNIT, and ATA-in-USB caddies

[Alex B. <ale...@as...>]

Hi Andy -

On Mon, 22 Nov 2004, Cress, Andrew R wrote:

> You could test it by using sgdiag:
> c - to compose a command
> 4 = length
> E4   (or 99)
> 00
> 00
> 00
> Response Data Length = 2 (this length probably doesn't matter)
> Output Data Length = 0
>
> Then, if it works, you can see how this is coded in sgdiag.c and make
> your own version of the program with a special ATA sleep option.

Thanks for the prompt reply. Unfortunately, no dice. I've no clue as to
whether it's Linux's usb-storage layer or the USB/1394->ATA bridge (it's a
Prolific-branded chipset) that's failing to pass the command on.

I guess I'll just have to live with it for now. Ah well. :-)

> Andy

Cheers,
Alex.

>
> -----Original Message-----
> From: Alex Butcher [mailto:ale...@as...]
> Sent: Saturday, November 20, 2004 9:27 AM
> To: Cress, Andrew R
> Subject: RE: sgdiag, STOP_UNIT, and ATA-in-USB caddies
>
>
> Hi Andy -
>
> On Thu, 18 Nov 2004, Cress, Andrew R wrote:
>
>> You may need to contact Maxtor to get a tool or API function that will
>> accept the spin down for ATA.  If there is a command that the ATA
> device
>> will accept, it could be sent via sg encapsulation, I think.  In fact,
>> the 'c' option would allow such a command to be composed.
>
> According to the source for hdparm and
> <http://my.execpc.com/~geezer/osd/misc/ata-idle.c>, the equivalent
> command
> is SLEEP, which is defined as 0xe6 or 0x99.
>
> hdparm does the following to send a drive to sleep:
>
>         if (set_sleepnow) {
> #ifndef WIN_SLEEPNOW1
> #define WIN_SLEEPNOW1 0xE6
> #endif
> #ifndef WIN_SLEEPNOW2
> #define WIN_SLEEPNOW2 0x99
> #endif
>                 unsigned char args1[4] = {WIN_SLEEPNOW1,0,0,0};
>                 unsigned char args2[4] = {WIN_SLEEPNOW2,0,0,0};
>                 if (get_sleepnow)
>                         printf(" issuing sleep command\n");
>                 if (ioctl(fd, HDIO_DRIVE_CMD, &args1)
>                  && ioctl(fd, HDIO_DRIVE_CMD, &args2))
>                         perror(" HDIO_DRIVE_CMD(sleep) failed");
>         }
>
> With the exception of Seagate, these commands appear to be standard ATA.
> Now, any ideas on how I can construct an equivalent SCSI CDB?
>
>> Andy
>
> Cheers,
> Alex.
>
>>
>> -----Original Message-----
>> From: Alex Butcher [mailto:ale...@as...]
>> Sent: Thursday, November 18, 2004 2:12 PM
>> To: Cress, Andrew R
>> Subject: sgdiag, STOP_UNIT, and ATA-in-USB caddies
>>
>>
>> Hi -
>>
>> I've been looking for a tool to spin down the various ATA discs that I
>> have
>> USB caddies. scsi-spin and scsi-idle use an ioctl that's deprecated
>> under
>> Linux kernel 2.6.9 (the kernel logs a message saying to port to
> SG_IO),
>> but
>> your sgdiag appears to fit the bill. Unfortunately, when I try to send
>> the
>> STOP_UNIT command, I get the following:
>>
>>
> ========================================================================
>> ==
>>                 sgdiag utility v1.12 for SCSI disks
>>               ******************************************
>> Log file /var/log/sgdiag.log is open, debug=0
>>
>> Num Name [bus:ch:id:lun] Type Vendor Device_Model     FW   Serial#
> Size
>>  0 /dev/sg0 [1:0:0:0] Disk  Maxtor 5 3073U6           DA62  [em]
>>
>> c = Compose Command to send  1 = Do bug 1 (sense_len = 18)
>> r = Reset SCSI bus           2 = Do bug 2 (INQ hang)
>> i = Special Ser# Inquiries   3 = Do bug 3 (fmt w short timeout)
>> f = Format SCSI disk         w = Wipe SCSI disk (fmt wo glist)
>> s = Start Unit               d = Send Diagnostic self-test
>> t = sTop Unit
>> Enter Selection ('q' to quit) : t
>>
>> Device Num (0 to 0) : 0
>> Issuing stop_unit for /dev/sg0
>> stop_unit: Check Condition Driver_status=0x08
> (DRIVER_SENSE,SUGGEST_OK)
>> sense error, key=05 asc=20 ascq=00 Illegal Request, Invalid command
>> operation code
>> Info valid=0, Current
>> stop_unit complete, status = -2
>>
> ========================================================================
>> ==
>>
>> I know this is not the intended use of this tool, but I'd appreciate
>> your
>> opinions on what's up, and whether it's possible to workaround it.
>> Normally,
>> I'd use hdparm -Y to spin down ATA drives, but as they show up as
>> pseudo-SCSI
>> devices when used with Linux's usb-storage driver, hdparm refuses to
>> handle
>> them. :-(
>>
>> Best Regards,
>> Alex.
>>
>
>

-- 
Alex Butcher      Brainbench MVP for Internet Security: www.brainbench.com
Bristol, UK                      Need reliable and secure network systems?
PGP/GnuPG ID:0x271fd950                         <http://www.assursys.com/>

[Scsirastools-developers] RE: sgdiag, STOP_UNIT, and ATA-in-USB caddies

[Cress, A. R <and...@in...>]

Alex,

You could test it by using sgdiag:
c - to compose a command
4 =3D length
E4   (or 99)
00
00
00
Response Data Length =3D 2 (this length probably doesn't matter)
Output Data Length =3D 0 =20

Then, if it works, you can see how this is coded in sgdiag.c and make
your own version of the program with a special ATA sleep option.

Andy

-----Original Message-----
From: Alex Butcher [mailto:ale...@as...]=20
Sent: Saturday, November 20, 2004 9:27 AM
To: Cress, Andrew R
Subject: RE: sgdiag, STOP_UNIT, and ATA-in-USB caddies


Hi Andy -

On Thu, 18 Nov 2004, Cress, Andrew R wrote:

> You may need to contact Maxtor to get a tool or API function that will
> accept the spin down for ATA.  If there is a command that the ATA
device
> will accept, it could be sent via sg encapsulation, I think.  In fact,
> the 'c' option would allow such a command to be composed.

According to the source for hdparm and
<http://my.execpc.com/~geezer/osd/misc/ata-idle.c>, the equivalent
command
is SLEEP, which is defined as 0xe6 or 0x99.

hdparm does the following to send a drive to sleep:

         if (set_sleepnow) {
#ifndef WIN_SLEEPNOW1
#define WIN_SLEEPNOW1 0xE6
#endif
#ifndef WIN_SLEEPNOW2
#define WIN_SLEEPNOW2 0x99
#endif
                 unsigned char args1[4] =3D {WIN_SLEEPNOW1,0,0,0};
                 unsigned char args2[4] =3D {WIN_SLEEPNOW2,0,0,0};
                 if (get_sleepnow)
                         printf(" issuing sleep command\n");
                 if (ioctl(fd, HDIO_DRIVE_CMD, &args1)
                  && ioctl(fd, HDIO_DRIVE_CMD, &args2))
                         perror(" HDIO_DRIVE_CMD(sleep) failed");
         }

With the exception of Seagate, these commands appear to be standard ATA.
Now, any ideas on how I can construct an equivalent SCSI CDB?

> Andy

Cheers,
Alex.

>
> -----Original Message-----
> From: Alex Butcher [mailto:ale...@as...]
> Sent: Thursday, November 18, 2004 2:12 PM
> To: Cress, Andrew R
> Subject: sgdiag, STOP_UNIT, and ATA-in-USB caddies
>
>
> Hi -
>
> I've been looking for a tool to spin down the various ATA discs that I
> have
> USB caddies. scsi-spin and scsi-idle use an ioctl that's deprecated
> under
> Linux kernel 2.6.9 (the kernel logs a message saying to port to
SG_IO),
> but
> your sgdiag appears to fit the bill. Unfortunately, when I try to send
> the
> STOP_UNIT command, I get the following:
>
>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> =3D=3D
>                 sgdiag utility v1.12 for SCSI disks
>               ******************************************
> Log file /var/log/sgdiag.log is open, debug=3D0
>
> Num Name [bus:ch:id:lun] Type Vendor Device_Model     FW   Serial#
Size
>  0 /dev/sg0 [1:0:0:0] Disk  Maxtor 5 3073U6           DA62  [em]
>
> c =3D Compose Command to send  1 =3D Do bug 1 (sense_len =3D 18)
> r =3D Reset SCSI bus           2 =3D Do bug 2 (INQ hang)
> i =3D Special Ser# Inquiries   3 =3D Do bug 3 (fmt w short timeout)
> f =3D Format SCSI disk         w =3D Wipe SCSI disk (fmt wo glist)
> s =3D Start Unit               d =3D Send Diagnostic self-test
> t =3D sTop Unit
> Enter Selection ('q' to quit) : t
>
> Device Num (0 to 0) : 0
> Issuing stop_unit for /dev/sg0
> stop_unit: Check Condition Driver_status=3D0x08
(DRIVER_SENSE,SUGGEST_OK)
> sense error, key=3D05 asc=3D20 ascq=3D00 Illegal Request, Invalid =
command
> operation code
> Info valid=3D0, Current
> stop_unit complete, status =3D -2
>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> =3D=3D
>
> I know this is not the intended use of this tool, but I'd appreciate
> your
> opinions on what's up, and whether it's possible to workaround it.
> Normally,
> I'd use hdparm -Y to spin down ATA drives, but as they show up as
> pseudo-SCSI
> devices when used with Linux's usb-storage driver, hdparm refuses to
> handle
> them. :-(
>
> Best Regards,
> Alex.
>

--=20
Alex Butcher      Brainbench MVP for Internet Security:
www.brainbench.com
Bristol, UK                      Need reliable and secure network
systems?
PGP/GnuPG ID:0x271fd950
<http://www.assursys.com/>

RE: [Scsirastools-developers] Question about defect lists.

[Cress, A. R <and...@in...>]

Stanislav,

The sgdefects utility will retrieve the count of bad sectors by default,
and will also output the list of values for each sector in the log file
if the option "-v" is used.
This does only apply to SCSI disks.  I don't know if this same function
is possible for IDE disks, but SCSI disks do have many more support &
management functions than do IDE disks.

I was targeting SCSI disks for these utilities, with the assumption that
those who are most interested in high availability and server management
would opt for SCSI disks over IDE disks.  However, I know that some
bladed systems have laptop-style IDE disks, due to the form-factor. =20

Andy Cress

-----Original Message-----
From: scs...@li...
[mailto:scs...@li...] On Behalf
Of Stanislav Semakin
Sent: Tuesday, July 13, 2004 3:18 AM
To: scs...@li...
Subject: [Scsirastools-developers] Question about defect lists.


Dear developers,

Permit me to ask you a question which concerns the scsirastools
marginally.
I need to get access to the bad sectors after remapping process which
addresses, I've learned by now, are in such tables as p-list and g-list=20
but I still don't
know if my task is practicable. I found only the ATA standards and=20
low-level
commands for the hdd and no other information. So during the searching
I've come out to your project. As I understand to get defect list is=20
possible
for the scsi devices but would it be for the ordinary ide?
Thank you.

Regards,
Stanislav



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20
digital self defense, top technical experts, no vendor pitches,=20
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Scsirastools-developers mailing list
Scs...@li...
https://lists.sourceforge.net/lists/listinfo/scsirastools-developers

[Scsirastools-developers] Question about defect lists.

[Stanislav S. <sse...@cs...>]

Dear developers,

Permit me to ask you a question which concerns the scsirastools marginally.
I need to get access to the bad sectors after remapping process which
addresses, I've learned by now, are in such tables as p-list and g-list 
but I still don't
know if my task is practicable. I found only the ATA standards and 
low-level
commands for the hdd and no other information. So during the searching
I've come out to your project. As I understand to get defect list is 
possible
for the scsi devices but would it be for the ordinary ide?
Thank you.

Regards,
Stanislav

[Scsirastools-developers] scsirastools 1.4.8 is released

[Cress, A. R <and...@in...>]

A new version 1.4.8 of scsirastools has now been released.  The changes
are listed below.

1.4.8 =3D update 06/10/04
  doc/UserGuide    added more about customizing /sbin/mdevt
  doc/sgraidmon.8  added more about mdevt and mdevents log
  files/mdevt      check for alarm cmd error if no IPMI driver
  doc/scsirastools.spec  show message about 'sgraid start' at
postinstall

[Scsirastools-developers] scsirastools 1.4.7 is released

[Cress, A. R <and...@in...>]

There is a new scsirastools version 1.4.7 released on sourceforge now.
Only one functional change was made, to move the location of the sgraid=20
script from /etc/rc.d/init.d to /etc/init.d for better LSB compliance.

See http://scsirastools.sf.net for the latest tarball and rpms.

Andy Cress

RE: [Scsirastools-developers] location of sgraid

[Cress, A. R <and...@in...>]

Jochen,

Good point. =20
In SuSE Linux that is particularly important.  I was doing the build on
RedHat, where the two are symlink'ed together, but I will make that
change to put it in /etc/init.d, which will be better. =20
Thanks for pointing this out.

Andy

-----Original Message-----
From: scs...@li...
[mailto:scs...@li...] On Behalf
Of Jochen Kirn
Sent: Tuesday, May 11, 2004 5:34 AM
To: scs...@li...
Subject: [Scsirastools-developers] location of sgraid


Hi *,

I'm wondering why sgraid (as of v1.4.6 rpm) is placed in
/etc/rc.d/init.d/=20
by default and NOT in /etc/init.d ?

Isn't /etc/init.d/ more LSB conform and most other=20
deamon rpm package put their start/stop script in /etc/init.d by
default.


Jochen

--=20
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info



-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to=20
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3
_______________________________________________
Scsirastools-developers mailing list
Scs...@li...
https://lists.sourceforge.net/lists/listinfo/scsirastools-developers

[Scsirastools-developers] location of sgraid

[Jochen K. <J....@gm...>]

Hi *,

I'm wondering why sgraid (as of v1.4.6 rpm) is placed in /etc/rc.d/init.d/ 
by default and NOT in /etc/init.d ?

Isn't /etc/init.d/ more LSB conform and most other 
deamon rpm package put their start/stop script in /etc/init.d by default.


Jochen

-- 
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info

[Scsirastools-developers] scsirastools 1.4.6 is released

[Cress, A. R <and...@in...>]

I have released scsirastools 1.4.6 today, there is only one change,
which is a=20
bugfix for Chesnee mBMC platforms' disk fault LED. =20

Andy

1.4.6 =3D update 04/22/04
  files/mdevt:     fixed mBMC disk fault LED logic on Fail not to check
$4

RE: [Scsirastools-developers] scsirastools 1.4.0 is released

[Cress, A. R <and...@in...>]

I have released scsirastools 1.4.5 today, the detailed change list is
below.
The purpose was to support setting the disk fault LED on a new platform
that
did not have SAF-TE support.  A separate tool (borrowed from
panicsel.sf.net) is=20
included to do this.

Andy

1.4.5 =3D update 02/22/04
  files/sgraid:    added chkconfig enabling
  files/alarms:    added tool for setting disk fault LEDs on mBMC
platforms
  files/Makefile:  added alarms tool
  doc/scsirastools.spec added alarms tool
  doc/UserGuide    added info about alarms tool

[Scsirastools-developers] scsirastools 1.4.0 is released

[Cress, A. R <and...@in...>]

This set of changes is to differentiate between DevFS and scsidev (which
also uses /dev/scsi/).
See http://scsirastools.sourceforge.net

ChangeLog:
scsirastools 1.4.0 = update 04/10/03
- src/getmd.c: use errno.h instead of extern int errno;
- src/sgcommon.c: detect DEVFS with /dev/scsi/host0 instead of just
/dev/scsi
- src/sgraidmon.c: detect DEVFS with /dev/scsi/host0 instead of just
/dev/scsi
- files/sgraid: detect DEVFS with /dev/scsi/host0 also

[Scsirastools-developers] scsirastools 1.3.8 is released (with automake)

[Cress, A. R <and...@in...>]

This release includes changes to conform the scsirastools utilitiy source to
autoconf/automake portability standards. Scsirastools 1.3.8 also includes
the following changes: 

- sgraidmon 1.18: change mdevt_Check error to warning & point to sgraid
script,
                  check for non-ascii chars in inquiry if impostor
- files/sgraid: changed init script for DevFS partition names
- doc/UserGuide: updated section 4 with newer raid config scripts
- files/md*.sh: added raid config scripts to source files
- INSTALL added (was README.src), updated mdf & lod file descriptions

For more information and downloads, see http://scsirastools.sourceforge.net

Andy

[Scsirastools-developers] scsirastools 1.3.7 released

[Cress, A. R <and...@in...>]

scsirastools 1.3.7 has been released.

This version includes some major rework of the disk hot-swap service
(sgraidmon v1.17) to fix bugs found while testing with alpha HSBPs and
various end cases, plus a new kernel patch needed for hot-swap with software
raid on RH AS 2.1 kernels. 

ChangeLog summary: 
1.3.7 = update 03/12/03 
- sgcommon.c: display more inquiry data for emulated (USB) devices 
- sgraidmon 1.17: fixed mdstat for failure if md0 not root, 
      display more inquiry data for emulated (USB) devices, 
      reorganized scandev, mdstat, getmd logic 
- mdevt (for sgraidmon): dont wipe each partition, not needed 
- kern/2.4.9-e.3/raid_oops.patch: ported raid_oops to RH AS 2.1

Andy

[Scsirastools-developers] LSI53C10xx

[invictus r. <inv...@ho...>]

hi,
Is there any work going on in the hardening of LSI53C10XX based HBA ...
Or , is the patch already available ??
I could only gather patches for adaptec based HBA.......

Thanks a lot for hearing


regards
rm




_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* 
http://join.msn.com/?page=features/junkmail

RE: [Scsirastools-developers] SGDIAG -F

[Cress, A. R <and...@in...>]

Ronny,

Yes, the format does erase all data on the hard disk device specified.  Your
motherboard is fine, just the hard disk is affected.  
sgdiag option 'f' does a SCSI low-level format of your hard disk.  I believe
the man page describes it ok, but let me know if it should say more.
Perhaps an additional warning/confirmation should be added to the utility
itself.

Stopping a SCSI format in the middle is a bad thing.  The partition table is
in the first sector of the disk, and that has already been cleared, so it
becomes rather difficult to recover anything from a partially formatted
disk.  If it was your root disk, then you will need other boot media to
re-format the disk before you reinstall the OS.  Or, your SCSI adapter may
support doing a format from its BIOS.  Adaptec allows you to press Ctrl-A
during post and it has Disk Utilities to do a format of a disk from the
BIOS.  After completing a full format, you will then be able to reinstall
that disk with an OS.

Let me know if you need further help with how to get reinstalled.

Andy

-----Original Message-----
From: Ronny Fang [mailto:yi...@co...] 
Sent: Monday, January 20, 2003 3:00 PM
To: scs...@li...
Subject: [Scsirastools-developers] SGDIAG -F


Hello, What exactly does the SGDIAG -F option do?  I ran that, stopped it
before it finished because I thought it would erase all data on my HD.  Now,
my system wont' boot and it's suspected that the motherboard has been fried.

Regards,
Ronny



-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Scsirastools-developers mailing list
Scs...@li...
https://lists.sourceforge.net/lists/listinfo/scsirastools-developers

[Scsirastools-developers] SGDIAG -F

[Ronny F. <yi...@co...>]

Hello, What exactly does the SGDIAG -F option do?  I ran that, stopped it
before it finished because I thought it would erase all data on my HD.  Now,
my system wont' boot and it's suspected that the motherboard has been fried.

Regards,
Ronny

[Scsirastools-developers] RE: Quantum disk firmware update

[Cress, A. R <and...@in...>]

Shanu,

The sense key message shows "Illegal Request" for the Write Buffer command.
This could be one of several things:
  1) The device cannot handle SCSI commands this large (377k).
or
  2) The command was truncated or malformed so that it appeared incomplete.
or 
  3) Some devices return this sense code if the model number in the image 
     does not match the device model number.

For (1) it would be an issue to take back to Quantum, asking how does this
disk device expect to download firmware?  Most disks use one big buffer like
this, but some require a fragmented, iterative download algorithm.  I've
downloaded firmware images as large as 600k with this tool, so it is within
a normal range.  
For (2), it could be a software bug, but the fact that the DOS Quantum tool
provided gets the same error would weigh against this.  It could be a
cabling/termination problem, or it could be an issue with the adapter
handling large SCSI commands.  Which SCSI adapter was involved? 
For (3), this seems like the most likely case.  You can also do a "strings"
on the image file to see if there is a model string there that matches.  You
can check with Quantum/Maxtor to verify the image.  The sgdskfl should also
explictly check this, but I just noticed that Quantum wasn't in my list of
vendors that support this.  This will be changed in the next cut.  

RE "servo image":
Some disk devices have the capability to download a servo image as well as a
firmware image.
The servo controls the mechanical/physical operation of the disk (comparable
to BIOS on a PC), while the firmware handles higher level logic, including
the SCSI protocol.  

-----Original Message-----
From: Shanker Balan [mailto:sh...@ex...] 
Sent: Wednesday, January 08, 2003 3:15 AM
To: Linux-SCSI
Subject: Re: Seagate Cheetah: Firmware, Bugs, Compatibility?

[...]

I got a similar sense error while trying to flash using the Quantum supplied
"DL_scsi.exe" under DOS.

Andrew, any idea what might be the problem here? Also whats a "Servo
image"?

Here is paste from "sgdskfl" run:

Log file /var/log/sgdskfl.log is open, debug=0

Num Name [bus:ch:id:lun] Type Vendor   Device_Model     FW__ Serial#_
Servo___
0 /dev/sg0 [0:0:0:0] Disk  QUANTUM  ATLAS10K3_18_SCA 020W 34220894
1 /dev/sg1 [0:0:1:0] Disk  QUANTUM  ATLAS10K3_73_SCA 020W 34820965
2 /dev/sg2 [0:0:2:0] Disk  QUANTUM  ATLAS10K3_73_SCA 020W 34820635

Enter Selection ('d' to download, 'q' to quit) : d

Device Num (0 to 2) : 2
Selected 2: [0:2] QUANTUM ATLAS10K3_73_SCA020W34820635
Reading image file atlas10k.lod, size = 377167
No servo image
Device [2] is ready for download
Starting download process for 1 disk.
Downloading Firmware image to disk 2 Wed Jan  8 13:40:52 2003
Current sg_cmd_done_bh00:00: sense key Illegal Request
write_buffer: Check Condition Driver_status=0x08 (DRIVER_SENSE,SUGGEST_OK)
sense error, key=05 asc=26 ascq=80 Illegal Request
Info valid=0, Current
[2] Error -2 in writing buffer
Press ENTER to continue

-- Shanu
http://shankerbalan.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to maj...@vg...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Scsirastools-developers] Intel Confidential page markings on documents

[James L. <Jim...@en...>]

I'd like to point out that the "Design Doc" from 
http://scsirastools.sourceforge.net/
has "Intel Confidential" page markings. Can someone please post
a cleaned up document?

Thanks,
Jim Litchfield
--------------