- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- getting an err when running script
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-18-2009 04:09 AM
тАО06-18-2009 04:09 AM
getting an err when running script
I am getting below error when running a script. My server is DS10 running tru64 5.1B OS.
/dev/rrz1c: character special (8/1026) EIDE #0 "WD400BB-60DGA0" disk #8 (SCSI ID #1) (SCSI LUN #0) errors = 0/2162
This disk was newly replaced because of restarting issue in the server.It was ok after replace this disk. But we are still getting this error.
Please anybody advice me.
Regards
Nirukshitha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2009 07:07 AM
тАО06-18-2009 07:07 AM
Re: getting an err when running script
> I am getting below error when running a script.
Sharing the script with us would be a good start...
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2009 10:51 PM
тАО06-18-2009 10:51 PM
Re: getting an err when running script
For Tru64 V5.x you should use the notation /dev/disk/dsk1c
maybe the "/dev/rz1c" special file does not map any more to the replaced disk?
In Tru64 4.x the devicename only depends on the bus/target/lun so rz1 remains rz1 after replacement.
wIn Tru64 %.x when replacing a disk the disk initially gets a new devicename
e.g you got dsk1, dsk2, dsk, dsk4 and replace dsk2, then the OS calls it dsk5.
and you must give some extra commands to put in the "original" place
"dsfmgr -e dsk5 dsk2".
try "hwmrg -view devices" to get the current mapping
Pieter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2009 03:01 AM
тАО06-19-2009 03:01 AM
Re: getting an err when running script
Please find the attached command output.According to this, disk notation is correct.Anyway I already replaced this same disk due to server rebooting when some application is started up. Then we replaced the disk and did the same as you mentioned in your mail.But, we are getting disk error when running health check script.
Regards
Nirukshitha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2009 03:34 AM
тАО06-19-2009 03:34 AM
Re: getting an err when running script
is it a custom health-check?
yes we are looking at the same disk /dev/rz1 is pointing to (SCSI ID #1) (SCSI LUN #0) .
# hwmgr -v d
46: /dev/disk/dsk0c Maxtor 6E040L0 bus-0-targ-0-lun-0
47: /dev/disk/dsk1c WDC WD400BB-60DGA0 bus-0-targ-1-lun-0
#
# hwmgr -show scsi
46: 0 STATION_A disk none 2 1 dsk0 [0/0/0]
47: 1 STATION_A disk none 2 1 dsk1 [0/1/0]
seems to me these are IDE disks? and not "real" SCSI disks
at this moment the dik dsk1 is not mounted!
all volumes mounted are on dsk0 or on a remote host (nfm).
maybe the script fails because no disklabel (partitiontable) is present on this disk ?
try "disklabel -r dsk1"
if this returns "no disklabel" do "disklabel -rw dsk1"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2009 03:58 AM
тАО06-19-2009 03:58 AM
Re: getting an err when running script
This is health checking script. Also we had received some SCSI CAM events in the binary error log. Can this be a hard disk issue?
Regards
Nirukshitha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2009 04:58 AM
тАО06-19-2009 04:58 AM
Re: getting an err when running script
what command do you issue, where is the script located, (maybe post the content of the script) and at what step comes the error?
If you mean the sys_check script, this gives an error on the CD-rom drive when no CD is present/mounted; this also logs CAM/SCSI errors that may be ignored.
it may also occur when a disk has no label.
did you check the disklabel on the new disk as i suggested?
did you view the information in the page that sys_check generates?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2009 10:31 AM
тАО06-19-2009 10:31 AM
Re: getting an err when running script
> This is health checking script
Nobody is going to be able to help you, if you cannot show us the contents of the script !
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2009 08:22 PM
тАО06-21-2009 08:22 PM
Re: getting an err when running script
This is not a our own script. This is one of the customer implemented.So they don't like to share with us. Anyway I will check with them possibility of getting this.
BTW, when we run the disklable command on the same disk, it shows bad sector status. So it can be the issue for this.
Regards
Nirukshitha