From: John BOSSERT (jbossert@unifiedsignal.com)
Date: Tue Mar 16 2004 - 12:47:08 EST
Trying to convert a (12x) D1000 to an A1000 by replacing the controller
module.
Here's what I'm seeing:
# raidutil -c c3t5d0 -i
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
Vendor ID Symbios
ProductID StorEDGE A3000 <-- NOTE!!!
Product Revision 0301
Boot Level 03.01.02.33
Boot Level Date 06/16/99
Firmware Level 03.01.02.35
Firmware Date 08/12/99
raidutil succeeded!
I physically inspected the module and it is
a 375-0135 (A1000)
# healthck -a
Health Check Summary Information
rdc2_mb_002: Unable To Scan Module
healthck succeeded!
No drives can be seen:
# drivutil -i c3t5d0
Drive Information for rdc2_mb_002
Location Capacity Status Vendor Product Firmware
Serial
(MB) ID Version
Number
drivutil succeeded!
Trying to upload any firmware yields the following:
# fwutil sie3240c.dl c3t5d0
Invalid device name: c3t5d0.
fwutil failed!
# fwutil sie3240c.dl c3t5d0s0 <- A1000 NVSRAM
Invalid device name: c3t5d0s0.
fwutil failed!
I originally set this array up on a machine with a functional A1000
array (using the second port on a x6541a PCI card. Moved it to a second
machine with no existing array (but the same base Solaris9 w/ current
patches and Raid Manager 6.22.1). Same behavior.
All lights on the array/drives are green with the exception of the
battery check (battery compartment is empty for now.)
Anybody seen anything like this? What to do? What does "Unable To Scan
Module" indicate? I'm under the gun on this as I need to migrate data
to this array - thanks for any help!
I'll summarize to the list...
-- John BOSSERT _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:28:17 EDT