RAID5 problems on solaris


 
Thread Tools Search this Thread
Operating Systems Solaris RAID5 problems on solaris
# 1  
Old 01-11-2008
RAID5 problems on solaris

I have one volume raid5 with 3 slice one of them is maintenance state. I replace this slice and resync the volume. when I try to mount the file system another slice goes to last erred. Again resync and the state goes to OK but the slice in mantenance persist. I try to enabled this but persist in manitenance state.

What can I do , I have a lot of critical data here without backup of this


Thanks

Daniel
# 2  
Old 01-11-2008
you have critical data but no backup??? Did you confirm if you have a failed disk?

what is the output of

Code:
/usr/sbin/metastat -i
iostat -En
dmesg

# 3  
Old 01-13-2008
Solaris RAID 5 problems

Hi Frank Rizo, thanks for your atention. Yes I have critical date without backup.... below iI post the results of commands that you suggest.

I apreciate your advice...

Thanks, Daniel

metastat -i

d0: RAID
State: Needs Maintenance
Invoke: metareplace d0 c2t22E4000A33007FA1d0s2 <new device>
Interlace: 32 blocks
Size: 976607415 blocks (465 GB)
Original device:
Size: 976622784 blocks (465 GB)
Device Start Block Dbase State Reloc Hot Spare
c2t22E4000A33007F99d0s2 16395 No Okay Yes
c2t22E4000A33007FA1d0s2 16395 No Maintenance Yes
c2t22E4000A33007F9Bd0s2 16395 Yes Okay Yes

Device Relocation Information:
Device Reloc Device ID
c2t22E4000A33007F9Dd0 Yes id1,sd@n22e4000a33007f9d
c2t22E4000A33007F9Ed0 Yes id1,sd@n22e4000a33007f9e
c2t22E4000A33007F9Fd0 Yes id1,sd@n22e4000a33007f9f
c2t22E4000A33007F99d0 Yes id1,sd@n22e4000a33007f99

-----------------------
bash-3.00# iostat -En


c0t0d0 Soft Errors: 11 Hard Errors: 1 Transport Errors: 0
Vendor: TEAC Product: CD-224E Revision: 1.9A Serial No:
Size: 0.27GB <266313728 bytes>
Media Error: 0 Device Not Ready: 1 No Device: 0 Recoverable: 0
Illegal Request: 11 Predictive Failure Analysis: 0
c2t22E4000A33007F9Dd0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMUW
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST373307LC Revision: 0007 Serial No:
Size: 73.41GB <73407868416 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c2t22E4000A33007F9Fd0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMM7
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c2t22E4000A33007F9Ed0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMJD
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c2t22E4000A33007FA0d0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMJD
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c2t22E4000A33007FA1d0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEML5
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c2t22E4000A33007FA3d0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMTE
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c2t22E4000A33007FA2d0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMSX
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c2t22E4000A33007F99d0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMH3
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c2t22E4000A33007FA4d0 Soft Errors: 4 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMGZ
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 4 Predictive Failure Analysis: 0
c2t22E4000A33007F9Ad0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMM7
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
c2t22E4000A33007F9Bd0 Soft Errors: 2 Hard Errors: 36 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMJD
Size: 250.05GB <250050772480 bytes>
Media Error: 36 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
c2t22E4000A33007F9Cd0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HDS7225SASUN250G Revision: A6DA Serial No: VN6J7HCFEMUG
Size: 250.05GB <250050772480 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0

======================================

bash-3.00# dmesg

Sun Jan 13 21:10:07 VET 2008
Jan 10 19:27:50 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 19:27:50 perol Error for Command: read(10) Error Level: Retryable
Jan 10 19:27:50 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 10 19:27:50 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 19:27:50 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 19:27:50 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 19:27:56 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 19:27:56 perol Error for Command: read(10) Error Level: Retryable
Jan 10 19:27:56 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 10 19:27:56 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 19:27:56 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 19:27:56 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 19:28:02 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 19:28:02 perol Error for Command: read(10) Error Level: Retryable
Jan 10 19:28:02 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 10 19:28:02 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 19:28:02 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 19:28:02 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 19:28:08 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 19:28:08 perol Error for Command: read(10) Error Level: Fatal
Jan 10 19:28:08 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 10 19:28:08 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 19:28:08 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 19:28:08 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 19:28:08 perol md_raid: [ID 112651 kern.warning] WARNING: md d0: read error on /dev/dsk/c2t22E4000A33007F9Bd0s2
Jan 10 19:28:13 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 19:28:13 perol Error for Command: read(10) Error Level: Fatal
Jan 10 19:28:13 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 10 19:28:13 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 19:28:13 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 19:28:13 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 19:28:13 perol md_raid: [ID 112651 kern.warning] WARNING: md d0: read error on /dev/dsk/c2t22E4000A33007F9Bd0s2
Jan 10 19:28:13 perol ufs: [ID 702911 kern.warning] WARNING: Error reading ufs log
Jan 10 19:28:13 perol ufs: [ID 127457 kern.warning] WARNING: ufs log for /ula1 changed state to Error
Jan 10 19:28:13 perol ufs: [ID 616219 kern.warning] WARNING: Please umount(1M) /ula1 and run fsck(1M)
Jan 10 19:29:10 perol ufs: [ID 702911 kern.warning] WARNING: Error writing ufs log state
Jan 10 19:29:10 perol ufs: [ID 127457 kern.warning] WARNING: ufs log for /tmp/.rlg.otaqSb/.rlg.otaqSb changed state to Error
Jan 10 19:29:10 perol ufs: [ID 616219 kern.warning] WARNING: Please umount(1M) /tmp/.rlg.otaqSb/.rlg.otaqSb and run fsck(1M)
Jan 10 20:23:27 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 20:23:27 perol Error for Command: read(10) Error Level: Retryable
Jan 10 20:23:27 perol scsi: [ID 107833 kern.notice] Requested Block: 30731 Error Block: 31502
Jan 10 20:23:27 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 20:23:27 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 20:23:27 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 20:23:33 perol scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1
Jan 10 20:23:33 perol scsi: [ID 243001 kern.warning] WARNING: /pci@0,0/pci1022,7450@b/pci1077,106@1/fp@0,0 (fcp0):
Jan 10 20:23:33 perol FCP: WWN 0x0a00e5229b7f0033 reset successfully
Jan 10 20:23:33 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 20:23:33 perol Error for Command: read(10) Error Level: Retryable
Jan 10 20:23:33 perol scsi: [ID 107833 kern.notice] Requested Block: 30731 Error Block: 31502
Jan 10 20:23:33 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 20:23:33 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 20:23:33 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 20:23:39 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 20:23:39 perol Error for Command: read(10) Error Level: Retryable
Jan 10 20:23:39 perol scsi: [ID 107833 kern.notice] Requested Block: 30731 Error Block: 31502
Jan 10 20:23:39 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 20:23:39 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 20:23:39 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 20:23:45 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 10 20:23:45 perol Error for Command: read(10) Error Level: Fatal
Jan 10 20:23:45 perol scsi: [ID 107833 kern.notice] Requested Block: 30731 Error Block: 31502
Jan 10 20:23:45 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 10 20:23:45 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 10 20:23:45 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 10 20:30:15 perol pseudo: [ID 129642 kern.info] pseudo-device: pseudo1
Jan 10 20:30:15 perol genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex@1
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: llc10
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: profile0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Jan 10 20:30:18 perol ipf: [ID 774698 kern.info] IP Filter: v4.0.2, running.
Jan 10 20:30:18 perol pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0
Jan 10 20:30:18 perol genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap@0
Jan 10 20:30:19 perol pseudo: [ID 129642 kern.info] pseudo-device: bmc0
Jan 10 20:30:19 perol genunix: [ID 936769 kern.info] bmc0 is /pseudo/bmc@0
Jan 10 21:08:41 perol su: [ID 810491 auth.crit] 'su root' failed for dcobos on /dev/pts/4
Jan 11 08:13:23 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 08:13:23 perol Error for Command: read(10) Error Level: Retryable
Jan 11 08:13:23 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 11 08:13:23 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 08:13:23 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 08:13:23 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 08:13:28 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 08:13:28 perol Error for Command: read(10) Error Level: Retryable
Jan 11 08:13:28 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 11 08:13:28 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 08:13:28 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 08:13:28 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 08:13:34 perol scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1
Jan 11 08:13:34 perol scsi: [ID 243001 kern.warning] WARNING: /pci@0,0/pci1022,7450@b/pci1077,106@1/fp@0,0 (fcp0):
Jan 11 08:13:34 perol FCP: WWN 0x0a00e5229b7f0033 reset successfully
Jan 11 08:13:34 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 08:13:34 perol Error for Command: read(10) Error Level: Retryable
Jan 11 08:13:34 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 11 08:13:34 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 08:13:34 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 08:13:34 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 08:13:40 perol scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1
Jan 11 08:13:40 perol scsi: [ID 243001 kern.warning] WARNING: /pci@0,0/pci1022,7450@b/pci1077,106@1/fp@0,0 (fcp0):
Jan 11 08:13:40 perol FCP: WWN 0x0a00e5229b7f0033 reset successfully
Jan 11 08:13:40 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 08:13:40 perol Error for Command: read(10) Error Level: Retryable
Jan 11 08:13:40 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 11 08:13:40 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 08:13:40 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 08:13:40 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 08:13:47 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 08:13:47 perol Error for Command: read(10) Error Level: Retryable
Jan 11 08:13:47 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 11 08:13:47 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 08:13:47 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 08:13:47 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 08:13:52 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 08:13:52 perol Error for Command: read(10) Error Level: Fatal
Jan 11 08:13:52 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 11 08:13:52 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 08:13:52 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 08:13:52 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 08:13:52 perol md_raid: [ID 112651 kern.warning] WARNING: md d0: read error on /dev/dsk/c2t22E4000A33007F9Bd0s2
Jan 11 08:13:58 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 08:13:58 perol Error for Command: read(10) Error Level: Retryable
Jan 11 08:13:58 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 11 08:13:58 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 08:13:58 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 08:13:58 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 08:14:03 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 08:14:03 perol Error for Command: read(10) Error Level: Fatal
Jan 11 08:14:03 perol scsi: [ID 107833 kern.notice] Requested Block: 31499 Error Block: 31502
Jan 11 08:14:03 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 08:14:03 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 08:14:03 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 08:14:03 perol md_raid: [ID 112651 kern.warning] WARNING: md d0: read error on /dev/dsk/c2t22E4000A33007F9Bd0s2
Jan 11 08:14:03 perol ufs: [ID 702911 kern.warning] WARNING: Error reading ufs log
Jan 11 08:14:03 perol ufs: [ID 127457 kern.warning] WARNING: ufs log for /ula1 changed state to Error
Jan 11 08:14:03 perol ufs: [ID 616219 kern.warning] WARNING: Please umount(1M) /ula1 and run fsck(1M)
Jan 11 08:14:03 perol ufs: [ID 699159 kern.warning] WARNING: Error accessing ufs log for /ula1; Please run fsck(1M)
Jan 11 17:13:06 perol pseudo: [ID 129642 kern.info] pseudo-device: dtrace0
Jan 11 17:13:06 perol genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace@0
Jan 11 17:16:29 perol pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x1 intin 0x4 is bound to cpu 0
Jan 11 17:16:29 perol last message repeated 1 time
Jan 11 17:16:29 perol isa: [ID 202937 kern.info] ISA-device: asy0
Jan 11 17:16:29 perol genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
Jan 11 17:16:29 perol pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Jan 11 17:16:29 perol genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Jan 11 17:16:29 perol pseudo: [ID 129642 kern.info] pseudo-device: pm0
Jan 11 17:16:29 perol genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Jan 11 17:16:32 perol pcplusmp: [ID 398438 kern.info] pcplusmp: pci14e4,1648.17c2.10 (bge) instance #1 vector 0x1a ioapic 0x2 intin 0x2 is bound to cpu 0
Jan 11 17:16:32 perol gld: [ID 944156 kern.info] bge1: BCM579x driver v0.44: type "ether" mac address 00000000000000
Jan 11 17:16:32 perol pci_pci: [ID 370704 kern.info] PCI-device: pci17c2,10@2,1, bge1
Jan 11 17:16:32 perol genunix: [ID 936769 kern.info] bge1 is /pci@0,0/pci1022,7450@a/pci17c2,10@2,1
Jan 11 18:08:04 perol /usr/dt/bin/ttsession[750]: [ID 862433 daemon.error] child (1482) exited due to signal 1
Jan 11 18:32:13 perol WBEM_Logging_Service[782]: [ID 411547 daemon.notice] A secure session was timeout and closed for user "root" from host "perol" with session identifier 1199992551489.
Jan 11 18:45:17 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 18:45:17 perol Error for Command: read(10) Error Level: Retryable
Jan 11 18:45:17 perol scsi: [ID 107833 kern.notice] Requested Block: 30731 Error Block: 31502
Jan 11 18:45:17 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 18:45:17 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 18:45:17 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 18:45:23 perol scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1
Jan 11 18:45:23 perol scsi: [ID 243001 kern.warning] WARNING: /pci@0,0/pci1022,7450@b/pci1077,106@1/fp@0,0 (fcp0):
Jan 11 18:45:23 perol FCP: WWN 0x0a00e5229b7f0033 reset successfully
Jan 11 18:45:23 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 18:45:23 perol Error for Command: read(10) Error Level: Retryable
Jan 11 18:45:23 perol scsi: [ID 107833 kern.notice] Requested Block: 30731 Error Block: 31502
Jan 11 18:45:23 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 18:45:23 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 18:45:23 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 18:45:30 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 18:45:30 perol Error for Command: read(10) Error Level: Retryable
Jan 11 18:45:30 perol scsi: [ID 107833 kern.notice] Requested Block: 30731 Error Block: 31502
Jan 11 18:45:30 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 18:45:30 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 18:45:30 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
Jan 11 18:45:36 perol scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g22e4000a33007f9b (sd12):
Jan 11 18:45:36 perol Error for Command: read(10) Error Level: Fatal
Jan 11 18:45:36 perol scsi: [ID 107833 kern.notice] Requested Block: 30731 Error Block: 31502
Jan 11 18:45:36 perol scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: VN6J7HCFEMJD
Jan 11 18:45:36 perol scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jan 11 18:45:36 perol scsi: [ID 107833 kern.notice] ASC: 0x11 (read retries exhausted), ASCQ: 0x1, FRU: 0x1
bash-3.00#
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Install RHEL6 on x3650M4 with RAID5

Hi All, I have a new x3650 M4 server with hardware RAID 5 configured 4 x 300 GB (HDD). The Raid controller is ServeRAID M5110e. Im getting "device not found" error during hardisk detection of RHEL6 install using DVD. Some pages over the net pointed to using ServerGuide media for... (1 Reply)
Discussion started by: Solaris_Begin
1 Replies

2. Hardware

RAID5 + STRIPED LUNs

Hello Experts, I have few doubts on RAID 5 with LUNs carved as STRIPE and CONCAT RAID 5 = STRIPE + Parity mirroring I would like to know if the LUNs carved are CONCATE from RAID 5 disk array. Are the I/Os are spread accross the disks within the RAID 5 Array? And if I do carve STRIPED... (1 Reply)
Discussion started by: sybadm
1 Replies

3. SuSE

Raid5

Hi all, I am currently using opensuse 12.1, We have Raid 5 array of 8 disks. A friend of mine accidently removed a drive & place it back and also added a new disk to it(making it 9 disks). now the output of mdadm --detail is as shown below si64:/dev # mdadm --detail /dev/md3 /dev/md3:... (1 Reply)
Discussion started by: patilrajashekar
1 Replies

4. UNIX for Advanced & Expert Users

RAID5 multi disk failure

Hi there, Don't know if my title is relevant but I'm dealing with dangerous materials that I don't really know and I'm very afraid to mess anything up. I have a Debian 5.0.4 server with 4 x 1TB hard drives. I have the following mdstat Personalities : md1 : active raid1 sda1 sdd1... (3 Replies)
Discussion started by: chebarbudo
3 Replies

5. Red Hat

Is overlapping two RAID5 arrays on same drives a bad idea ??

is placing two RAID5 arrays on disk as shown below Is advisable? Will this create performance problems? sda-(500GB) sdb-(1TB) sdc-(1TB) sdd-(1TB) (250MB)----------(250MB) ---------unused------------unused------->(/dev/md0) RAID1 ... (6 Replies)
Discussion started by: Saed
6 Replies

6. Filesystems, Disks and Memory

Problem booting a linux (RAID5)

Hello, we have a problem with our system, a machine with a RAID5: - We can boot the system from CD only, if we try to boot from hard-disk the GRUB seems to be "freezed". What is the difference, why we can boot from CD if something is wrong? - Allways we retreive an error like: "raid array is... (6 Replies)
Discussion started by: aristegui
6 Replies

7. AIX

how to mirror raid5

Hi, I have an ssa filesystem to move to san. We don't want any downtime. I heard that you can do a mirroring of existing file system on the san. The file system is a type of either raid 0, raid 1, or raid 5. Anyone know how to do this? Thanks in advance, itik (4 Replies)
Discussion started by: itik
4 Replies

8. AIX

Software-based RAID5 on Aix

Hello All. Is it possible? (5 Replies)
Discussion started by: sapbcer
5 Replies

9. AIX

Can not increase capacity of the vg using raid5 with ssa disks

hi all, i have an p620 server. it has 2 scsi 18gb disks for aix4.3 OS and 3 ssa disks for database and an serialRAID adapter. 3 ssa disks configured raid level 5. to increase capacity of the datavg, i buy 2 ssa 18gb disks. but i can not add them to the existing datavg. i did the following... (1 Reply)
Discussion started by: tinhlx
1 Replies

10. SCO

Raid5 Failure

Forgive me, I do not know much about RAID so I'm going to be as detailed as possible. This morning, our server's alarm was going. I found that one of our drives have failed. (we have 3) It is an Adaptec ATA RAID 2400A controller I'm purchasing a new SCSI drive today. My questions: ... (2 Replies)
Discussion started by: gseyforth
2 Replies
Login or Register to Ask a Question