RE: monitoring raid arrays

2006-06-20 Thread Ted Mittelstaedt


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Elliot Finley
Sent: Monday, June 19, 2006 9:12 AM
To: Alex Zbyslaw
Cc: freebsd-questions@freebsd.org
Subject: Re: monitoring raid arrays



- Original Message - 
From: Alex Zbyslaw [EMAIL PROTECTED]
 Elliot Finley wrote:

 How about monitoring the array on a Dell PowerEdge 2650?
 relevant dmesg output:
 
 FreeBSD 6.0-RELEASE-p2 #0: Mon Jan 16 12:27:14 MST 2006
 aacch0: AAC RAID Channel port 0xcc00-0xccff mem 
0xfccff000-0xfccf
irq
 30 at device 6.0 on pci5
 aacch1: AAC RAID Channel port 0xc800-0xc8ff mem 
0xfccfe000-0xfccfefff
irq
 31 at device 6.1 on pci5
 aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 30 at 
device 8.1 on
 pci4
 aac0: [FAST]
 aac0: Adaptec Raid Controller 2.0.0-1
 
 
 Port:   aaccli-1.0
 Path:   /usr/ports/sysutils/aaccli
 Info:   Adaptec SCSI RAID administration tool
 Maint:  [EMAIL PROTECTED]
 B-deps:
 R-deps:
 WWW:http://support.dell.com/

 Never tried it but it looks like your best bet.

Yes, I saw this too.  Doesn't work on 6.x though because of the MAKEDEV
requirement.

Elliot, did you file a PR when you ran across this problem?

Ted
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: monitoring raid arrays

2006-06-19 Thread Elliot Finley
How about monitoring the array on a Dell PowerEdge 2650?
relevant dmesg output:

FreeBSD 6.0-RELEASE-p2 #0: Mon Jan 16 12:27:14 MST 2006
aacch0: AAC RAID Channel port 0xcc00-0xccff mem 0xfccff000-0xfccf irq
30 at device 6.0 on pci5
aacch1: AAC RAID Channel port 0xc800-0xc8ff mem 0xfccfe000-0xfccfefff irq
31 at device 6.1 on pci5
aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 30 at device 8.1 on
pci4
aac0: [FAST]
aac0: Adaptec Raid Controller 2.0.0-1

- Original Message - 
From: Philippe Pegon [EMAIL PROTECTED]
To: Thierry Lacoste [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Sent: Sunday, June 18, 2006 4:06 AM
Subject: Re: monitoring raid arrays


 Thierry Lacoste wrote:
  I'm running FreeBSD 6.1 on a Compaq Proliant and a Dell PowerEdge 1800.
  They have hardware raid 1 arrays controlled respectively by a Compaq
  Smart Array 532
  controller and PERC 4/SC.
 
  Here is the relevant dmesg output on the Proliant:
  ciss0: Compaq Smart Array 532 port 0x4000-0x40ff mem
  0xf7fc-0xf7ff,0xf7ef-0xf7ef3fff irq 24 at device 3.0 on pci7
  [snip]
  da0 at ciss0 bus 0 target 0 lun 0
  da0: COMPAQ RAID 1  VOLUME OK Fixed Direct Access SCSI-0 device
  da0: 135.168MB/s transfers
  da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)
 
  Here is the relevant dmesg output on the PowerEdge:
  amr0: LSILogic MegaRAID 1.53 mem 0xf80f-0xf80f irq 37 at
  device 5.0 on pci2
  amr0: delete logical drives supported by controller
  amr0: LSILogic PERC 4/SC Firmware 351S, BIOS 1.10, 64MB RAM
  [snip]
  amr0: delete logical drives supported by controller
  amrd0: LSILogic MegaRAID logical drive on amr0
  amrd0: 139900MB (286515200 sectors) RAID 1 (optimal)
 
  What are my options to monitor the status of these arrays?

 for ciss, you can use camcontrol (in the base system) like that:

 # camcontrol inquiry da0
 pass0: COMPAQ RAID 1  VOLUME OK Fixed Direct Access SCSI-0 device
 pass0: 135.168MB/s transfers

 for amr, you can use the new port /usr/ports/sysutils/amrstat like that:

 # amrstat
 Logical volume 0optimal (16.96 GB, RAID1)
 Physical drive 0:0  online
 Physical drive 0:1  online

 
  Best regards,
  Thierry.

 --
 Philippe Pegon
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
[EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: monitoring raid arrays

2006-06-19 Thread Alex Zbyslaw

Elliot Finley wrote:


How about monitoring the array on a Dell PowerEdge 2650?
relevant dmesg output:

FreeBSD 6.0-RELEASE-p2 #0: Mon Jan 16 12:27:14 MST 2006
aacch0: AAC RAID Channel port 0xcc00-0xccff mem 0xfccff000-0xfccf irq
30 at device 6.0 on pci5
aacch1: AAC RAID Channel port 0xc800-0xc8ff mem 0xfccfe000-0xfccfefff irq
31 at device 6.1 on pci5
aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 30 at device 8.1 on
pci4
aac0: [FAST]
aac0: Adaptec Raid Controller 2.0.0-1
 


Port:   aaccli-1.0
Path:   /usr/ports/sysutils/aaccli
Info:   Adaptec SCSI RAID administration tool
Maint:  [EMAIL PROTECTED]
B-deps:
R-deps:
WWW:http://support.dell.com/

Never tried it but it looks like your best bet.

--Alex


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: monitoring raid arrays

2006-06-19 Thread Elliot Finley

- Original Message - 
From: Alex Zbyslaw [EMAIL PROTECTED]
 Elliot Finley wrote:

 How about monitoring the array on a Dell PowerEdge 2650?
 relevant dmesg output:
 
 FreeBSD 6.0-RELEASE-p2 #0: Mon Jan 16 12:27:14 MST 2006
 aacch0: AAC RAID Channel port 0xcc00-0xccff mem 0xfccff000-0xfccf
irq
 30 at device 6.0 on pci5
 aacch1: AAC RAID Channel port 0xc800-0xc8ff mem 0xfccfe000-0xfccfefff
irq
 31 at device 6.1 on pci5
 aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 30 at device 8.1 on
 pci4
 aac0: [FAST]
 aac0: Adaptec Raid Controller 2.0.0-1
 
 
 Port:   aaccli-1.0
 Path:   /usr/ports/sysutils/aaccli
 Info:   Adaptec SCSI RAID administration tool
 Maint:  [EMAIL PROTECTED]
 B-deps:
 R-deps:
 WWW:http://support.dell.com/

 Never tried it but it looks like your best bet.

Yes, I saw this too.  Doesn't work on 6.x though because of the MAKEDEV
requirement.

Elliot

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: monitoring raid arrays

2006-06-19 Thread Chad Leigh -- Shire.Net LLC


On Jun 19, 2006, at 10:12 AM, Elliot Finley wrote:


Port:   aaccli-1.0
Path:   /usr/ports/sysutils/aaccli
Info:   Adaptec SCSI RAID administration tool
Maint:  [EMAIL PROTECTED]
B-deps:
R-deps:
WWW:http://support.dell.com/

Never tried it but it looks like your best bet.


Yes, I saw this too.  Doesn't work on 6.x though because of the  
MAKEDEV

requirement.


I am not running the Dell version but the actual generic adaptec  
Linux version with the Linux compat stuff installed and it works fine  
with 6.0.  You should be able to Google and see what people did to  
make it work.  And the same thing probably? should work with the Dell  
version?


Chad


---
Chad Leigh -- Shire.Net LLC
Your Web App and Email hosting provider
chad at shire.net



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: monitoring raid arrays

2006-06-19 Thread Philippe Pegon

Elliot Finley wrote:

How about monitoring the array on a Dell PowerEdge 2650?
relevant dmesg output:

FreeBSD 6.0-RELEASE-p2 #0: Mon Jan 16 12:27:14 MST 2006
aacch0: AAC RAID Channel port 0xcc00-0xccff mem 0xfccff000-0xfccf irq
30 at device 6.0 on pci5
aacch1: AAC RAID Channel port 0xc800-0xc8ff mem 0xfccfe000-0xfccfefff irq
31 at device 6.1 on pci5
aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 30 at device 8.1 on
pci4
aac0: [FAST]
aac0: Adaptec Raid Controller 2.0.0-1


I don't know for aac, I don't use this controller. Have you tried with 
camcontrol or maybe with the ports /usr/ports/sysutils/aaccli ?


--
Philippe Pegon
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: monitoring raid arrays

2006-06-19 Thread Tamouh H.
 
 
 
 On Jun 19, 2006, at 10:12 AM, Elliot Finley wrote:
 
  Port:   aaccli-1.0
  Path:   /usr/ports/sysutils/aaccli
  Info:   Adaptec SCSI RAID administration tool
  Maint:  [EMAIL PROTECTED]
  B-deps:
  R-deps:
  WWW:http://support.dell.com/
 
  Never tried it but it looks like your best bet.
 
  Yes, I saw this too.  Doesn't work on 6.x though because of the 
  MAKEDEV requirement.
 
 I am not running the Dell version but the actual generic 
 adaptec Linux version with the Linux compat stuff installed 
 and it works fine with 6.0.  You should be able to Google and 
 see what people did to make it work.  And the same thing 
 probably? should work with the Dell version?
 
 Chad
 

The aaccli works only with certain Adaptec firmware. If the adaptec card has 
the newest firmwares (I believe the ones in April + ), the aaccli will not work.

Official Adaptec stand as it appears that they don't have storage management on 
FreeBSD.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: monitoring raid arrays

2006-06-19 Thread Chad Leigh -- Shire.Net LLC


On Jun 19, 2006, at 12:11 PM, Tamouh H. wrote:






On Jun 19, 2006, at 10:12 AM, Elliot Finley wrote:


Port:   aaccli-1.0
Path:   /usr/ports/sysutils/aaccli
Info:   Adaptec SCSI RAID administration tool
Maint:  [EMAIL PROTECTED]
B-deps:
R-deps:
WWW:http://support.dell.com/

Never tried it but it looks like your best bet.


Yes, I saw this too.  Doesn't work on 6.x though because of the
MAKEDEV requirement.


I am not running the Dell version but the actual generic
adaptec Linux version with the Linux compat stuff installed
and it works fine with 6.0.  You should be able to Google and
see what people did to make it work.  And the same thing
probably? should work with the Dell version?

Chad



The aaccli works only with certain Adaptec firmware. If the adaptec  
card has the newest firmwares (I believe the ones in April + ), the  
aaccli will not work.


Official Adaptec stand as it appears that they don't have storage  
management on FreeBSD.


I use the Linux aaccli in Linux compat mode.

Are Adaptec saying that they also don't support Linux?   I am not  
running any FreeBSD native aaccli as it was recommended to me long  
ago to run the Linux one as it had more capability than the FreeBSD  
one, which was abandoned it seems.


Btw, I updated my 2200S to the latest in May but the latest for this  
card is from 2005 so maybe it is not late enough.


Chad

---
Chad Leigh -- Shire.Net LLC
Your Web App and Email hosting provider
chad at shire.net



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: monitoring raid arrays

2006-06-18 Thread Philippe Pegon

Thierry Lacoste wrote:

I'm running FreeBSD 6.1 on a Compaq Proliant and a Dell PowerEdge 1800.
They have hardware raid 1 arrays controlled respectively by a Compaq 
Smart Array 532

controller and PERC 4/SC.

Here is the relevant dmesg output on the Proliant:
ciss0: Compaq Smart Array 532 port 0x4000-0x40ff mem 
0xf7fc-0xf7ff,0xf7ef-0xf7ef3fff irq 24 at device 3.0 on pci7

[snip]
da0 at ciss0 bus 0 target 0 lun 0
da0: COMPAQ RAID 1  VOLUME OK Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)

Here is the relevant dmesg output on the PowerEdge:
amr0: LSILogic MegaRAID 1.53 mem 0xf80f-0xf80f irq 37 at 
device 5.0 on pci2

amr0: delete logical drives supported by controller
amr0: LSILogic PERC 4/SC Firmware 351S, BIOS 1.10, 64MB RAM
[snip]
amr0: delete logical drives supported by controller
amrd0: LSILogic MegaRAID logical drive on amr0
amrd0: 139900MB (286515200 sectors) RAID 1 (optimal)

What are my options to monitor the status of these arrays?


for ciss, you can use camcontrol (in the base system) like that:

# camcontrol inquiry da0
pass0: COMPAQ RAID 1  VOLUME OK Fixed Direct Access SCSI-0 device
pass0: 135.168MB/s transfers

for amr, you can use the new port /usr/ports/sysutils/amrstat like that:

# amrstat
Logical volume 0optimal (16.96 GB, RAID1)
Physical drive 0:0  online
Physical drive 0:1  online



Best regards,
Thierry.


--
Philippe Pegon
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


monitoring raid arrays

2006-06-17 Thread Thierry Lacoste

I'm running FreeBSD 6.1 on a Compaq Proliant and a Dell PowerEdge 1800.
They have hardware raid 1 arrays controlled respectively by a Compaq Smart 
Array 532

controller and PERC 4/SC.

Here is the relevant dmesg output on the Proliant:
ciss0: Compaq Smart Array 532 port 0x4000-0x40ff mem 
0xf7fc-0xf7ff,0xf7ef-0xf7ef3fff irq 24 at device 3.0 on pci7

[snip]
da0 at ciss0 bus 0 target 0 lun 0
da0: COMPAQ RAID 1  VOLUME OK Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)

Here is the relevant dmesg output on the PowerEdge:
amr0: LSILogic MegaRAID 1.53 mem 0xf80f-0xf80f irq 37 at device 
5.0 on pci2

amr0: delete logical drives supported by controller
amr0: LSILogic PERC 4/SC Firmware 351S, BIOS 1.10, 64MB RAM
[snip]
amr0: delete logical drives supported by controller
amrd0: LSILogic MegaRAID logical drive on amr0
amrd0: 139900MB (286515200 sectors) RAID 1 (optimal)

What are my options to monitor the status of these arrays?

Best regards,
Thierry.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: monitoring raid arrays

2006-06-17 Thread Alex Zbyslaw

Thierry Lacoste wrote:



Here is the relevant dmesg output on the PowerEdge:
amr0: LSILogic MegaRAID 1.53 mem 0xf80f-0xf80f irq 37 at 
device 5.0 on pci2

amr0: delete logical drives supported by controller
amr0: LSILogic PERC 4/SC Firmware 351S, BIOS 1.10, 64MB RAM
[snip]
amr0: delete logical drives supported by controller
amrd0: LSILogic MegaRAID logical drive on amr0
amrd0: 139900MB (286515200 sectors) RAID 1 (optimal)

What are my options to monitor the status of these arrays?


From memory sysutils/megarc.  Search for LSI in the INDEX if that's wrong.

--Alex


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]