- 论坛徽章:
- 0
|
***********配置情况*****
************************
************************
e450 + A1000(053h255e) + e450
solaris7
raid5 + legato HA+ 2.2
************************
************************
************************
在两台机器执行ｆｏｒｍａｔ命令的情况
// ------e450*server2*------------
#format
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>;
/pci@1f,4000/scsi@3/sd@0.0
1. c2t5d0 <Symbios-StorEDGEA1000-0301 cyl 43084 alt 2 hd 64 sec 64>;
/pseudo/rdnexus@2/rdriver/5.0
Speify disk (enter itsnumber):1
1
selecting c2t5d0
[disk unformated]
Disk not labeled, label it now?
// ------e450*server1*------------
#format
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>;
/pci@1f,4000/scsi@3/sd@0.0
1. c3t5d0 <Symbios-StorEDGEA1000-0301 cyl 43084 alt 2 hd 64 sec 64>;
/pseudo/rdnexus@3/rdriver/5.0
Speify disk (enter itsnumber):1
1
selecting c3t5d0
[disk unformated]
Disk not labeled, label it now?
************************
**其他错误**************
************************
Aug 1 14:43:08 server2.com unix: WARNING: /pci@4,4000/scsi@3/sd@5,0 (sd35):
Aug 1 14:43:08 server2.com i/o to invalid geometry
Aug 1 14:43:08 server2.com
Areturning an Errored I/O, with errno 5, on fsserver1_001, Lun 0, sector 49er is
6482560 512 byte blocks.com unix: Vendor 'Symbios', product 'StorEDGE', 17
Aug 2 11:05:22 server2.com raid: AEN event Host
Aug 2 11:05:22 server2.com raid: AEN event Host
Aug 2 11:05:22 server2.com raid: AEN event Host
Aug 2 11:05:22 server2.com raid: ASC=A0 ASCQ=
Aug 2 11:05:22 server2.com raid: ASC=A0 ASCQ=
Aug 2 11:05:22 server2.com raid: ASC=A0 ASCQ=
Aug 2 11:05:22 server2.com raid: Sense=700006
000000000000000000800000082C00000000000000000000
010200000004000000000000000000000000000000000000
000000000000000000000000000000000000000000000C30
Aug 2 11:05:22 server2.com raid: Sense=700006
000000000000000000800000082C00000000000000000000
010200000004000000000000000000000000000000000000
000000000000000000000000000000000000000000000C30
0C3038303130342F3230303933330000000000000000000000000000000000000000000000000000
执行ｍｏｕｎｔ 命令
mount /dev/dsk/c3t5d0s2 /a1000
报设备不存在
在控制台下，可看到ｓｃｉｓ设备
执行ｒｍ６显示的信息
************************
**执行rm6**************
************Status*****
Hardware Message
Date: 08/02/2004 Time: 11:11:09
RAID Module: fsserver1_001
Controller: c3t5d0
Sense Key: 06
ASC/ASCQ Code: A000
Affected Component: -
Affected Tray: -
Affected Logical Unit: 0
____________________________________________________________________
Probable Cause:
Write back caching is being suspended. This could be due to (1) a battery charging after a power cycle, (2) a battery failure/discharge, (3) a UPS two-minute warning, or (4) a controller not being able to mirror the cached data.
Action To Take:
If you power cycled the RAID Module, wait approximately 12 to 15 minutes. The caching should be enabled again. Also, check the message log for additional messages concerning batteries, UPS, or AC Power. Also, make sure that both controllers are operational.
Hardware Message
Date: 08/02/2004 Time: 11:11:09
RAID Module: fsserver1_001
Controller: c3t5d0
Sense Key: 06
ASC/ASCQ Code: 3FD8
Affected Component: -
Affected Tray: -
Affected Logical Unit: 0
____________________________________________________________________
Probable Cause:
The controller has failed the battery because the battery has reached its expiration date.
Action To Take:
Please use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem.
************************
**执行rm6**************
************Recovery***
Failed Battery
Detailed Status
Host: server1.com
Module: fsserver1_001
Affected Tray: Controller Tray
Affected Components: Failed Battery
Controller A: 1T04359410 ( c3t5d0 )
Probable Cause
The batteries in the battery canister have failed or reached their expiration date.
CAUTION
o Do not perform these recovery steps if you have just turned on the RAID Module or replaced a controller. During these two
situations, the battery's self-test diagnostics takes approximately 12 to 15 minutes to complete (dependent on the controller
type and whether the batteries were discharged). Until the diagnostic test is completed, you may see Battery Alert or Failure
indications in the Recovery Guru for batteries that are operational and fully charged.
o On some models, the battery canister can weigh up to 24 pounds (10.86 kilograms). Use both hands to remove and replace the
canister.
Important
o The battery and its replacement procedure vary depending on the type of RAID Module you have. The following steps provide
common procedures you will need to perform for a battery replacement. Consult the appropriate hardware manual if you need
details on locating and accessing the battery.
o Each controller in a dual controller module has its own view of the battery's expiration date and current time of day.
Under normal circumstances these views should be consistent and you should observe two battery entries in the Recovery Guru
Summary Information Screen, one for each controller.
Recovery Steps
1. Stop all I/O activity to the controller and turn off the power to the RAID Module.
2. Remove the battery canister and replace it with a new one.
3. Record today's date (installation) and the new replacement date on the label. The replacement date is 2 years from the
installation date.
4. Turn on the power to the RAID Module. Use the raidutil command line utility as follows to reset the battery age for EACH
controller (device) in the RAID Module: raidutil -c <device name>; -R
If you need information on the device name, select Module Profile and look at the Summary Information screen.
5. Wait 15 minutes and re-run the Recovery Guru to ensure that the failure has been fixed. If a battery alert or failure is
reported again, you probably did not reset the battery age on EACH controller.
Additional Notes
Some older RAID Modules may have separate batteries mounted on each controller. In this case, a battery failure entry refers
to the battery associated with the controller reporting the failure.
Dead LUN - Awaiting Format
Detailed Status
Host: server1.com
Module: fsserver1_001
Affected Tray: -
Affected Components: Dead LUN - Awaiting Format
Controller A: 1T04359410 ( c3t5d0 )
Drive(s): [1,1], [1,2]
Affected LUNs: 0
LUN Status: Dead
RAID Level: 5
Probable Cause
This condition is caused by either (1) unformatted LUNs containing drives with
or (2) failed or unresponsive drives that were caused by a channel failure.
Important
Fix any channel failures reported in the Summary Information screen of the Reco
data from back up.
Recovery Steps
1. Format all LUNs in this drive group:
o In the Recovery Application, make sure the affected RAID Module is selected.
o Select Options >;>; Manual Recovery >;>; Logical Units from the top menu bar. Hig
ormatting, then Optimal.
2. Re-run the Recovery Guru to ensure the the failure has been fixed.
3. Add the LUN(s) back to the operating system (you may need to reboot the syst
NOTE: Do NOT start I/O to these LUNs until restoring from back up.
4. Restore the data for these LUNs from back up.
Additional Notes
o If the Format attempt fails and this drive group contains multiple LUNs, try
a. Highlight the Replaced drives and select Fail. Wait for the drives to transi
b. Highlight these drives again and select Revive.
c. Format these LUNs.
o If you attempt to Format the LUN(s) before the replaced drives are ready (comare ready (fault light Off) and try to Format
again. |
|
免费注册
发表于 2004-08-03 11:05