- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- hard disk
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 01:18 AM
тАО06-25-2009 01:18 AM
hard disk
We are using TRU64 Digital UNIX V4.0D (Rev. 878); system.
I have been seeing the below error since few days and suspect that one of the disk is going to get corrupt.
Here is the error,
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 290.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Jun 25 10:10:38 2009
OCCURRED ON SYSTEM bwgb550
SYSTEM ID x00070016
SYSTYPE x00000000
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000000
----- UNIT INFORMATION -----
CLASS x0000 DISK
SUBSYSTEM x0000 DISK
BUS # x0001
x0050 LUN x0
TARGET x2
********************************* ENTRY 2. *********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 289.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Jun 25 10:10:26 2009
OCCURRED ON SYSTEM bwgb550
SYSTEM ID x00070016
SYSTYPE x00000000
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000001
----- UNIT INFORMATION -----
CLASS x0000 DISK
SUBSYSTEM x0000 DISK
BUS # x0001
x0050 LUN x0
TARGET x2
**********************************************************************************
I am a newbie but I can see that the disk having bus 01, Target 2 & Lun 0 is the disk in question.
I also did this,
# scu show edt
CAM Equipment Device Table (EDT) Information:
Device: RRD46 Bus: 0, Target: 5, Lun: 0, Type: Read-Only Direct Access
Device: RZ1EF-AB Bus: 1, Target: 1, Lun: 0, Type: Direct Access
Device: RZ2EA-LA Bus: 1, Target: 2, Lun: 0, Type: Direct Access
Device: RZ1EF-AB Bus: 1, Target: 3, Lun: 0, Type: Direct Access
Device: RZ2DA-LA Bus: 1, Target: 4, Lun: 0, Type: Direct Access
Device: RZ1CB-CA Bus: 1, Target: 5, Lun: 0, Type: Direct Access
Device: RZ2EA-LA Bus: 2, Target: 1, Lun: 0, Type: Direct Access
Device: RZ2EA-LA Bus: 2, Target: 2, Lun: 0, Type: Direct Access
Device: BD0366774C Bus: 2, Target: 3, Lun: 0, Type: Direct Access
Device: BD0186349B Bus: 2, Target: 4, Lun: 0, Type: Direct Access
Device: RZ1CB-CA Bus: 2, Target: 5, Lun: 0, Type: Direct Access
Device: BB00911CA0 Bus: 3, Target: 0, Lun: 0, Type: Direct Access
Device: RZ29B Bus: 3, Target: 1, Lun: 0, Type: Direct Access
Device: RZ28M Bus: 3, Target: 2, Lun: 0, Type: Direct Access
Device: RZ1EF-AB Bus: 3, Target: 3, Lun: 0, Type: Direct Access
Device: RZ1EF-AB Bus: 3, Target: 4, Lun: 0, Type: Direct Access
Device: RZ1CB-CS Bus: 3, Target: 5, Lun: 0, Type: Direct Access
So it seems , the disk exists there. But now our question is which is this disk?
And which filesystem it is holding on? And how do we prevent any loss of data.
Kindly suggest.
Admin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 10:34 PM
тАО06-25-2009 10:34 PM
Re: hard disk
Is there a reason why i m not getting any reply to this? Just want to know if I have made any mistake in this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 11:18 PM
тАО06-25-2009 11:18 PM
Re: hard disk
when the guys in the forum help you out with a problem, you are supposed to rate their help using the points system.
hope that helps
regards
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 11:21 PM
тАО06-25-2009 11:21 PM
Re: hard disk
I certainly agree to this and always follow this too. I go grant the points at the time of closing the thread. And I stongly believe in points allocation. No doubt.
Why you pointed out this , please share.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 11:27 PM
тАО06-25-2009 11:27 PM
Re: hard disk
I pointed this out in case you were not aware, as sometimes things like that stop people being so willing to provide answers. It was just a friendly reminder aimed at helping you if you were not aware of the system, as I saw you are fairly new to the forum.
regards
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 11:29 PM
тАО06-25-2009 11:29 PM
Re: hard disk
Ohh then thanx for this. But I really felt I have missed someone in allotting the points.
Like said before I respect all the techies out here by all means.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2009 12:04 AM
тАО06-26-2009 12:04 AM
Re: hard disk
>>>
BUS # x0001
x0050 LUN x0
TARGET x2
<<<
matches
>>>
Device: RZ2EA-LA Bus: 1, Target: 2, Lun: 0, Type: Direct Access
<<<
try "file /dev/rrz*c"
to identify disknames to scsi-bus B/T/L.
try "mount" to see wich disk(partitions) are mounted.
if using advfs you don't see the disks here, only "filedomainnames#filesetname", if so do
cd /etc/fdmns
showfdmn *
to see what disk is mapped to a filedomain#fileset
Now the mapping to the B/T/L 1/2/0 should be clear.
If you don't have any douments describing your physical system you might try a backup to /dev/null to identify the physical shelf and position of this disk (by disk activity light).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2009 12:15 AM
тАО06-26-2009 12:15 AM
Re: hard disk
That is as far as I know, 8XBus(1) + Target(2)= rz10 ..right??
So i tried "file /dev/rrz*c"
/dev/rrz10c: character special (8/18434) SCSI #1 RZ2EA-LA disk #80 (SCSI ID #2) (SCSI LUN #0) errors = 204/74 offline
So it is /dev/rrz10c (Or is it /dev/rrz10 only?? Confused)
We are using advfs. So I tried,
showfdmn *
# showfdmn *
Id Date Created LogPgs Domain Name
3de633a5.000abc98 Thu Nov 28 16:17:57 2002 512 backup_domain
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 35565080 5917872 83% on 256 256 /dev/rz27c
2 35565080 4198800 88% on 256 256 /dev/rz28c
---------- ---------- ------
71130160 10116672 86%
showfdmn: unable to get info for domain 'data_domain'
showfdmn: error = E_BAD_MAGIC (-1167)
Id Date Created LogPgs Domain Name
36fbd363.000c048e Fri Mar 26 19:35:15 1999 512 home
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 16758080 2799568 83% on 128 128 /dev/vol/dokudg/vol_home
Id Date Created LogPgs Domain Name
39a15fe1.0002f7dd Mon Aug 21 18:59:13 2000 512 install_domain
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 8380080 45184 99% on 256 256 /dev/rz29c
Id Date Created LogPgs Domain Name
39957e3d.00003713 Sat Aug 12 18:41:33 2000 512 root_domain
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 2097152 1518464 28% on 256 256 /dev/rz24a
Id Date Created LogPgs Domain Name
36fbab0b.000d26ec Fri Mar 26 16:43:07 1999 512 source_domain
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 106692120 49445504 54% on 128 128 /dev/vol/sourcedg/vol_source
Id Date Created LogPgs Domain Name
39957e4a.000c8fe2 Sat Aug 12 18:41:46 2000 512 usr_domain
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 6291456 3645008 42% on 256 256 /dev/rz24g
Id Date Created LogPgs Domain Name
39957e5a.00002d4f Sat Aug 12 18:42:02 2000 512 util_domain
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 7285764 133744 98% on 256 256 /dev/rz24h
But can not see the disk rz10c. Why??
Is it something to do with LVM?? Then how to check in this case?.
Moreover , how do i check backup /dev/null to identify the disk.
Thanx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2009 12:54 AM
тАО06-26-2009 12:54 AM
Re: hard disk
=> rz10 is the disk.
rz10c is partition-c on this disk
/dev/rz10c is for the OS to do block-io on this disk
/dev/rrz10c is for the OS to do "raw" (or "character") io on this device.
showfdmn: unable to get info for domain 'data_domain'
showfdmn: error = E_BAD_MAGIC (-1167)
this could be the reason why you don't see rz10.
if so, the disk is not accessible anymore An advfs domain "panic" must have been logged in /var/adm/messages after wich the domain will be locked by the OS.
if using LSM you may try "volprint -Ath" or "volprint -Gts" to get LSM-info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2009 01:24 AM
тАО06-27-2009 01:24 AM
Re: hard disk
You might be able to get some more details as to what is going wrong by looking at the full error output.
# uerf -R -o full | more
That should show you whether the errors that you are seeing were correctable, although I'll guess probably not, and that the disk in question has died.
Cheers,
Rob