各位老大,磁盘组的问题,我该哪里下手查?救命啊~~~

tph

系统启动的时候:

vxvm:vxconfigd:warning:disk datadg01 in group dtadg:disk device not found !
vxvm:vxconfigd:warning:disk datadg02 in group dtadg:disk device not found !
vxvm:vxconfigd:warning:disk datadg03 in group dtadg:disk device not found !
vxvm:vxconfigd:warning:disk datadg06 in group dtadg:disk device not found !

在系统里面:
bash-2.03# vxdisk
vxvm:vxdisk: ERROR: Incorrect usage
vxvm:vxdisk: TO FIX:
    Usage: vxdisk [-f] keyword arg ...
vxvm:vxdisk: INFO: For detailed help use: vxdisk help
bash-2.03# vxdisk list
DEVICE       TYPE      DISK         GROUP        STATUS
c0t32d0s2    sliced    datadg05     datadg       online
c0t37d0s2    sliced    datadg04     datadg       online
c0t42d0s2    sliced    datadg07     datadg       online
c3t10d0s2    sliced    -            -            error
c3t11d0s2    sliced    disk15       rootdg       online
-            -         datadg01     datadg       failed was:c0t58d0s2
-            -         datadg02     datadg       failed was:c0t54d0s2
-            -         datadg03     datadg       failed was:c0t51d0s2
-            -         datadg06     datadg       failed was:c0t48d0s2

磁盘怎么丢了???我没有vxvm的管理经验,希望各位老大赐教!

lyh003473

vxdctl enable试一下

tph

楼上的老大,我按你的办法试了一下.发现还是没有解决问题.丢失的device还是找不到.我把我们的机器具体的信息说一下吧:服务器是 SUN 的 5500 ,磁盘柜配的是StoreEDGE A5200 ,磁盘柜的状态显示是OK.系统是 Solaris 8.出问题前我用vmsa  在察看磁盘组的状态,然后提示读盘错误...以前这个机器也出现过磁盘柜挂不进系统,一般都是出现了写错误,修复以后就可以挂接了.老大能否留个通讯方式:msn ,qq什么的,小弟想请教一二,另外我们的sun机器购买的服务过期了.sun估计不会派人来.数据库要恢复,急~~~

junglelion

找SUN买服务看来是来不及了, 一点建议:
1,#inito
2,ok setenv auto-boot? false
3,ok reset-all
4,probe-fcal-all       \看硬盘能否OK下找到
5,如果看不到A5200的硬盘,就是光纤通道上的一个部件坏了!/如果看到, 引导系统,仔细看看/var/adm/messages的出错信息!

tph

bash-2.03# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0t32d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>;
          /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a437,0
       1. c0t37d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>;
          /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a31b,0
       2. c0t42d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>;
          /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a98b,0
       3. c1t32d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>;
          /sbus@3,0/SUNW,socal@d,10000/sf@1,0/ssd@w2100002037e3a437,0
       4. c1t37d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>;
          /sbus@3,0/SUNW,socal@d,10000/sf@1,0/ssd@w2100002037e3a31b,0
       5. c1t42d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>;
          /sbus@3,0/SUNW,socal@d,10000/sf@1,0/ssd@w2100002037e3a98b,0
       6. c3t10d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>;
          /sbus@3,0/QLGC,isp@0,10000/sd@a,0
       7. c3t11d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>;
          /sbus@3,0/QLGC,isp@0,10000/sd@b,0


这个可以说明磁盘都可以看到吗?

tph

bash-2.03# luxadm probe
Found Enclosure(s):
SENA               Name:HNGD   Node WWN:50800200000e5318
  Logical Path:/dev/es/ses0
  Logical Path:/dev/es/ses2

这个好像是磁盘柜的.

tph

这是出故障的时候系统的提示信息...好像是光纤通道的问题...

Oct 11 11:08:12 hngd-db01 socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.5010] socal0: port 1: Fibre Channel is OFFLINE
Oct 11 11:08:12 hngd-db01 socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.5010] socal0: port 0: Fibre Channel is OFFLINE
Oct 11 11:08:12 hngd-db01 socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.6010] socal0: port 0: Fibre Channel Loop is ONLINE
Oct 11 11:08:12 hngd-db01 socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.6010] socal0: port 1: Fibre Channel Loop is ONLINE
Oct 11 11:08:12 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0 (sf1):
Oct 11 11:08:12 hngd-db01         target 0x3a al_pa 0x7a lun 0 offlined
Oct 11 11:08:12 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0 (sf1):
Oct 11 11:08:12 hngd-db01         target 0x33 al_pa 0x8f lun 0 offlined
Oct 11 11:08:12 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0 (sf1):
Oct 11 11:08:12 hngd-db01         target 0x3d al_pa 0x75 lun 0 offlined
Oct 11 11:08:12 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0 (sf1):
Oct 11 11:08:12 hngd-db01         target 0x2a al_pa 0xa5 lun 0 offlined
Oct 11 11:08:12 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0 (sf1):
Oct 11 11:08:12 hngd-db01         target 0x36 al_pa 0x82 lun 0 offlined
Oct 11 11:08:12 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0 (sf1):
Oct 11 11:08:12 hngd-db01         target 0x20 al_pa 0xb2 lun 0 offlined
Oct 11 11:08:12 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0 (sf1):
Oct 11 11:08:12 hngd-db01         target 0x25 al_pa 0xab lun 0 offlined
Oct 11 11:08:12 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0 (sf1):
Oct 11 11:08:12 hngd-db01         target 0x30 al_pa 0x98 lun 0 offlined
Oct 11 11:08:14 hngd-db01 socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.5010] socal0: port 0: Fibre Channel is OFFLINE
Oct 11 11:08:17 hngd-db01 scsi: [ID 799468 kern.info] ses32 at sf1: name w50800200000e5319,0, bus address 9e
Oct 11 11:08:17 hngd-db01 genunix: [ID 936769 kern.info] ses32 is /sbus@3,0/SUNW,socal@d,10000/sf@1,0/ses@w50800200000e5319,0
Oct 11 11:08:17 hngd-db01 genunix: [ID 408114 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@1,0/ses@w50800200000e5319,0 (ses32) online
Oct 11 11:08:18 hngd-db01 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Oct 11 11:08:18 hngd-db01 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Oct 11 11:08:26 hngd-db01 socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.5010] socal0: port 1: Fibre Channel is OFFLINE
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.warning] WARNING: /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         Offline Timeout
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x3a al_pa 0x7a lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x33 al_pa 0x8f lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x2d al_pa 0x9e lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x3d al_pa 0x75 lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x2a al_pa 0xa5 lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x36 al_pa 0x82 lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x20 al_pa 0xb2 lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x25 al_pa 0xab lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 243001 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0 (sf0):
Oct 11 11:09:00 hngd-db01         target 0x30 al_pa 0x98 lun 0 offlined
Oct 11 11:09:00 hngd-db01 scsi: [ID 107833 kern.warning] WARNING: /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a31b,0 (ssd12):
Oct 11 11:09:00 hngd-db01         ssdrestart transport failed (fffffffe)
Oct 11 11:09:00 hngd-db01 scsi: [ID 107833 kern.warning] WARNING: /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a437,0 (ssd11):
Oct 11 11:09:00 hngd-db01         ssdrestart transport failed (fffffffe)
Oct 11 11:09:00 hngd-db01 scsi: [ID 107833 kern.warning] WARNING: /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a98b,0 (ssd9):
Oct 11 11:09:00 hngd-db01         ssdrestart transport failed (fffffffe)
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x60 belonging to the dmpnode 229/0x38
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x28 belonging to the dmpnode 229/0x38
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 148046 kern.notice] NOTICE: vxvm:vxdmp: disabled dmpnode 229/0x38
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x58 belonging to the dmpnode 229/0x30
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x20 belonging to the dmpnode 229/0x30
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 148046 kern.notice] NOTICE: vxvm:vxdmp: disabled dmpnode 229/0x30
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x48 belonging to the dmpnode 229/0x20
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x10 belonging to the dmpnode 229/0x20
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 148046 kern.notice] NOTICE: vxvm:vxdmp: disabled dmpnode 229/0x20
Oct 11 11:09:00 hngd-db01 scsi: [ID 107833 kern.warning] WARNING: /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a65c,0 (ssd13):
Oct 11 11:09:00 hngd-db01         transport rejected (-2)
Oct 11 11:09:00 hngd-db01 scsi: [ID 107833 kern.warning] WARNING: /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a6ab,0 (ssd:
Oct 11 11:09:00 hngd-db01         transport rejected (-2)
Oct 11 11:09:00 hngd-db01 scsi: [ID 107833 kern.warning] WARNING: /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037e3a970,0 (ssd10):
Oct 11 11:09:00 hngd-db01         transport rejected (-2)
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x68 belonging to the dmpnode 229/0x40
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x30 belonging to the dmpnode 229/0x40
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 148046 kern.notice] NOTICE: vxvm:vxdmp: disabled dmpnode 229/0x40
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x40 belonging to the dmpnode 229/0x18
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x8 belonging to the dmpnode 229/0x18
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 148046 kern.notice] NOTICE: vxvm:vxdmp: disabled dmpnode 229/0x18
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x50 belonging to the dmpnode 229/0x28
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x18 belonging to the dmpnode 229/0x28
Oct 11 11:09:00 hngd-db01 vxdmp: [ID 148046 kern.notice] NOTICE: vxvm:vxdmp: disabled dmpnode 229/0x28
Oct 11 11:09:00 hngd-db01 vxio: [ID 834969 kern.warning] WARNING: vxvm:vxio: detaching RAID-5 db
Oct 11 11:09:00 hngd-db01 vxio: [ID 761242 kern.warning] WARNING: vxvm:vxio: Raid-5 db block 4046864:
Oct 11 11:09:00 hngd-db01         Uncorrectable read error on Subdisk datadg04-01 block 809360
Oct 11 11:09:00 hngd-db01 vxio: [ID 761242 kern.warning] WARNING: vxvm:vxio: Raid-5 db block 6002704:
Oct 11 11:09:00 hngd-db01         Uncorrectable write error on Subdisk datadg05-01 block 1200528
Oct 11 11:09:03 hngd-db01 socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.6010] socal0: port 1: Fibre Channel Loop is ONLINE
Oct 11 11:09:05 hngd-db01 socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.6010] socal0: port 0: Fibre Channel Loop is ONLINE
Oct 11 11:09:05 hngd-db01 scsi: [ID 799468 kern.info] ses34 at sf0: name w50800200000e531b,0, bus address 9e
Oct 11 11:09:05 hngd-db01 genunix: [ID 936769 kern.info] ses34 is /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ses@w50800200000e531b,0
Oct 11 11:09:05 hngd-db01 genunix: [ID 408114 kern.info] /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ses@w50800200000e531b,0 (ses34) online
Oct 11 11:30:39 hngd-db01 reboot: [ID 662345 auth.crit] rebooted by root
Oct 11 11:30:40 hngd-db01 /usr/dt/bin/ttsession[28401]: [ID 522926 daemon.error] 退出
Oct 11 11:30:40 hngd-db01 syslogd: going down on signal 15
Oct 11 11:30:46 hngd-db01 genunix: [ID 672855 kern.notice] syncing file systems...
Oct 11 11:30:46 hngd-db01 genunix: [ID 733762 kern.notice]  1
Oct 11 11:31:06 hngd-db01 last message repeated 19 times
Oct 11 11:31:07 hngd-db01 genunix: [ID 616637 kern.notice]  cannot sync -- giving up

greb

下载给系统检测软件检测一下,就知道了.应该不是硬件的问题

tph

在哪里可以下载?什么软件?楼上的老大推荐一下...

bear

如果你的系统中format看不到这些盘
c0t58d0s2 c0t54d0s2 c0t51d0s2 c0t48d0s2
说明你的阵列连接主机的光纤通道可能有问题了
但是你的这3个硬盘还能看到
c0t32d0s2     c0t37d0s2     c0t42d0s2
看控制器号是在一个阵列上，你描述的环境不是很清楚，是1台A5200带7个硬盘单光纤连接到主机的配置么？A5200有前后2面硬盘，出厂7个的话一般是一边3个另一边4个，如果是的话可能问题出在阵列中，有一侧的4个硬盘找不到了，怀疑是A5200内部的问题，因为你还有3个能用，如果光纤的问题7个都找不到了。