-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bob Richards wrote:
I have a similar issue, only it is with a Dell server which has 6 SCSI
drives in a hardware raid array. The controller is a Dell PERC 2/Si.
Is there an equivalent monitor utility for this as well? I am currently
running:
On Sun, 25 Nov 2007 08:45:46 +
Matthew Seaman [EMAIL PROTECTED] wrote:
... it's a rebadged Adaptec RAID controller using
the aac
Wonderful; I can now look into and play with the RAID system without
taking the OS off-line and going to the bios.
Thanks!
Bob
--
_
/o\
// \\ The ASCII
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/07 12:39 PM, Ted Mittelstaedt wrote:
The output of idacontrol show will show if one of the
hard disks in the SmartArray has failed. Your choice with
a hardware array is to either run it with redundancy or not.
(ie: raid5 or mirroring or
On Sun, 25 Nov 2007 08:45:46 +
Matthew Seaman [EMAIL PROTECTED] wrote:
sysutils/aaccli aaccli-1.0 Adaptec SCSI RAID administration
As I said in my previous post, this is EXACTLY what was wanted.
Installation of aaccli was a snap. My only problem was the total lack
of
hair-pulling, running of
diagnostics, and so on.
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of David Newman
Sent: Sunday, November 25, 2007 2:58 PM
To: Ted Mittelstaedt
Cc: freebsd-questions@freebsd.org
Subject: Re: dealing with a failing drive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/07 9:08 PM, Ted Mittelstaedt wrote:
There are two physical disks in the server. bus 1 target 0 and
bus 1 target 1. Those ARE the physical disks. If one of them
has failed instead of:
Sync, Ultra2, Wide - Configured in a logical
Sent: Monday, November 19, 2007 8:44 AM
To: freebsd-questions@freebsd.org
Subject: Re: dealing with a failing drive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/18/07 11:30 PM, Ted Mittelstaedt wrote:
Hi David, apologies to Jerry for jumping in.
Compaq uses several RAID
Compaq uses several RAID cards most are under the so-called
SmartArray using the ida driver. If this is yours, you can
use a utility called idacontrol that can monitor the array,
Interesting discussion!
I have a similar issue, only it is with a Dell server which has 6 SCSI
drives in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/18/07 11:30 PM, Ted Mittelstaedt wrote:
idacontrol show | grep Status
IF status is fully up it will say:
Status: Logical drive ok
And that's what it does say. So far so good...
...but then each time I run idacontrol I get this in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/18/07 11:30 PM, Ted Mittelstaedt wrote:
Hi David, apologies to Jerry for jumping in.
Compaq uses several RAID cards most are under the so-called
SmartArray using the ida driver. If this is yours, you can
use a utility called idacontrol
On Nov 16, 2007 5:05 PM, Douglas Rodriguez [EMAIL PROTECTED] wrote:
I've been getting the following message repeating continuously:
ad1:FAILURE - READ_DMA status=51READY, DSC, ERROR
error=1ILLEGAL_LENGTH LBA=216026367
g_vfs_done():ad1s1[READ(offset = 110605467648, length =
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jerry
McAllister
Sent: Monday, November 12, 2007 8:04 AM
To: David Newman
Cc: freebsd-questions@freebsd.org
Subject: Re: dealing with a failing drive
On Sat, Nov 10, 2007 at 05:22:06PM -0800
I've been getting the following message repeating continuously:
ad1:FAILURE - READ_DMA status=51READY, DSC, ERROR
error=1ILLEGAL_LENGTH LBA=216026367
g_vfs_done():ad1s1[READ(offset = 110605467648, length = 16384)]error=5
ad1:FAILURE - READ_DMA status=51READY, DSC, ERROR
Douglas Rodriguez wrote:
I've been getting the following message repeating continuously:
ad1:FAILURE - READ_DMA status=51READY, DSC, ERROR
error=1ILLEGAL_LENGTH LBA=216026367
g_vfs_done():ad1s1[READ(offset = 110605467648, length = 16384)]error=5
ad1:FAILURE - READ_DMA status=51READY,
From: David Newman [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
On 11/12/07 8:14 AM, Jerry McAllister wrote:
An update: After doing what you suggest (leaving in the good disk,
adding a new disk, RAID rebuilding) I still got soft write errors --
with *either one* of the disks I
From: Jerry McAllister [EMAIL PROTECTED]
Sent: Monday, November 12, 2007 12:53
On Mon, Nov 12, 2007 at 09:26:38AM -0800, David Newman wrote:
On 11/12/07 8:14 AM, Jerry McAllister wrote:
An update: After doing what you suggest (leaving in the good disk,
adding a new disk, RAID rebuilding)
On Sat, Nov 10, 2007 at 05:22:06PM -0800, David Newman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd welcome suggestions on how (or whether) to try to revive a SCSI
drive that's failing.
to answer 'whether': don't. Get your stuff off from it as
soon as possible and nuke it if
On Sun, Nov 11, 2007 at 07:56:52AM -0800, David Newman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/07 9:09 PM, Modulok wrote:
I'd welcome suggestions on how (or whether) to try to revive a SCSI
drive that's failing.
It depends on how valuable the data on the array
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/07 8:14 AM, Jerry McAllister wrote:
An update: After doing what you suggest (leaving in the good disk,
adding a new disk, RAID rebuilding) I still got soft write errors --
with *either one* of the disks I tried.
Then I tried putting
On Mon, Nov 12, 2007 at 09:26:38AM -0800, David Newman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/07 8:14 AM, Jerry McAllister wrote:
An update: After doing what you suggest (leaving in the good disk,
adding a new disk, RAID rebuilding) I still got soft write errors
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/07 9:09 PM, Modulok wrote:
I'd welcome suggestions on how (or whether) to try to revive a SCSI
drive that's failing.
It depends on how valuable the data on the array is, and more
importantly, how much funding you have at your disposal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd welcome suggestions on how (or whether) to try to revive a SCSI
drive that's failing.
This is on FreeBSD 6.2-RELENG on a Compaq Proliant DL320, onboard RAID
and two SCSI drives in a RAID1 array.
Today this system rebooted and hung on Compaq's
I'd welcome suggestions on how (or whether) to try to revive a SCSI
drive that's failing.
It depends on how valuable the data on the array is, and more
importantly, how much funding you have at your disposal to fix the
problem. If it were me, I would set aside the bad disk, connect a new
disk to
Hello,
I've got a drive that i'm uncertain if it's failing. It is making an
occational clicking noise, which is getting more frequent. I installed
smartmontools and tried to start them, output below:
#smartctl -a /dev/ad0
smartctl version 5.37 [i386-portbld-freebsd6.1] Copyright (C) 2002-6
Subject: replacing failing drive
Hello,
I've got a drive that i'm uncertain if it's failing. It is making an
occational clicking noise, which is getting more frequent. I installed
smartmontools and tried to start them, output below:
#smartctl -a /dev/ad0
smartctl version 5.37 [i386-portbld
25 matches
Mail list logo
