Need Suggestons on SCSI drives "not ready"
- From: "Steve M. Fabac, Jr." <smfabac@xxxxxxx>
- Date: Sat, 21 Jun 2008 15:26:35 -0500
I have a client running SCO 5.0.5 with DPT 3754U2 RAID
controller with two disks in RAID1.
The problem occurred when the client's building lost power and
the UPS battery expired after it ran down. No, there was
no signaling cable to the SCO box and therefore no way to
detect the power failure. (This will be rectified).
But the problem is the two Seagate 140G 15K cheetah drives.
They are down hard and won't come up. These are brand new
drives and have only been in the machine for a week.
I pulled the drives and replaced them with a single drive on
the DPT controller, booted the Microlite RE2 media and restored
the system from the previous night's nightly backup tape.
Seagate says get an RMA and they will replace the drives. However,
I would like to get them working so that I can grab the log files
and application data files (one days worth of orders and shipping,
since the last backup, not enough value to send the drives to a
data recovery service).
Also, I would like to get the drives back up for the knowledge on
how to do it in the future.
The problem is when you boot the system with the failed drives and
press Ctl-D to enter the DPT RAID configuration utility, the drives
are seen but are listed with the block size field showing "no media."
(This normally shows 512 bytes). THE DPT controller lists the drives
as "optimal" and not "failed." Also, the SCSI activity light on the
drive carrier is "on" solid and never goes out.
When I connected the SCA cage to the on-board Adpatec U160 controller
and booted the system, the U160 splash screen shows the drives on
their respective ID's but then adds: "Failed Start Unit Request."
Pressing Ctl-A to enter Adaptec Easy SCSI configuration screen and
selecting SCSI utilities shows the drives but trying to verify the
drive results in:
SCSI CDB sent: 03 00 00 0E 00 70 00 02 00
SCSI Controller Status: 00h No SCSI Controller Error
Target Status: 02h Check condition
Sense Key: 02h Not Ready
Sense Code: 04h
Sense Code Qualifier: 00h
The fdisk layout has a 300 track DOS partition from track 1 to track 300
with the active SCO boot partition starting at track 301. If this were
an IDE disk, I would stomp on the first 10 or so tracks, and then recreate
the fdisk partition layout and then the Divvy tables without creating
new file systems. However, since the disk is SCSI and won't respond to the
"start unit request" I can't read or write to the disk with any tools I
have: Booting a DOS floppy with config.sys containing device=aspi8u2.sys
(device driver for Ultra2 and Ultra160 class host adapters) does not
provide access to the disk.
I'm hopeful that someone on the group has experience with this problem and
can point me to recovery tools that I can get to wake these disks back up.
And FYI: Calling Adaptec technical support on the DPT 3754U2 controllers
was a bust. The customer service agent indicated that "Adaptec does no provide
technical support on obsolete products. You may be able to find some help in the
Adaptec ASK database."
Seagate technical support advised me to download the Seagate SeaTools boot ISO
image but that again only talks to IDE drives. They have a SeaTools Enterprise
edition that runs under Windows or Linux but that requires that your SCSI
disk and controller be installed in a Windows or Linux system. Not an option
for me.
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
.
- Follow-Ups:
- Re: Need Suggestons on SCSI drives "not ready"
- From: Pepe
- Re: Need Suggestons on SCSI drives "not ready"
- From: Bob Bailin
- Re: Need Suggestons on SCSI drives "not ready"
- From: Glenn
- Re: Need Suggestons on SCSI drives "not ready"
- Prev by Date: Re: SCO 505 "mount: cannot stat '/dev/dsk/f03ht'"
- Next by Date: Re: Need Suggestons on SCSI drives "not ready"
- Previous by thread: SCO 505 "mount: cannot stat '/dev/dsk/f03ht'"
- Next by thread: Re: Need Suggestons on SCSI drives "not ready"
- Index(es):
Relevant Pages
|
Loading