HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- File type conflicts when upgrading to 5.1B from 5....
Operating System - Tru64 Unix
1830015
Members
2088
Online
109998
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
10-21-2004 10:04 PM
10-21-2004 10:04 PM
File type conflicts when upgrading to 5.1B from 5.1A of Tru64 Unix
In analysis phase of update
installation file type conflict
appears which causes the exit
from the installation.
The problem is with /usr/sys/streamsm
which must be a directory.
It is defined as symbolic link
streamsm@ -> ../usr/sys/streamsm,
and there is no file or directory
in that path.
What to do to be able to continue with
the installation, is that directory
necessary for installation, if I removed
that link, would it work, or must
such a directory exist for upgrading OS?
Thanks for advise,
A.
installation file type conflict
appears which causes the exit
from the installation.
The problem is with /usr/sys/streamsm
which must be a directory.
It is defined as symbolic link
streamsm@ -> ../usr/sys/streamsm,
and there is no file or directory
in that path.
What to do to be able to continue with
the installation, is that directory
necessary for installation, if I removed
that link, would it work, or must
such a directory exist for upgrading OS?
Thanks for advise,
A.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2004 12:12 AM
10-22-2004 12:12 AM
Re: File type conflicts when upgrading to 5.1B from 5.1A of Tru64 Unix
On our cluster /sys and /usr/sys look like this:
# ls -ald /sys/*
drwxr-xr-x 2 root system 24576 Aug 11 19:47 /sys/BINARY
lrwxrwxrwx 1 root system 17 Jan 14 2003 /sys/HOSTNAME -> ../usr/sys/HOSTNAME
lrwxr-xr-x 1 root system 15 Jan 12 2003 /sys/arch -> ../usr/sys/arch
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/bin -> ../usr/sys/bin
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/bsd -> ../usr/sys/bsd
lrwxr-xr-x 1 root system 15 Jan 12 2003 /sys/conf -> ../usr/sys/conf
lrwxr-xr-x 1 root system 15 Jan 12 2003 /sys/data -> ../usr/sys/data
lrwxr-xr-x 1 root system 18 Jan 12 2003 /sys/include -> ../usr/sys/include
lrwxr-xr-x 1 root system 13 Jan 12 2003 /sys/io -> ../usr/sys/io
lrwxr-xr-x 1 root system 15 Jan 12 2003 /sys/kern -> ../usr/sys/kern
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/net -> ../usr/sys/net
lrwxr-xr-x 1 root system 18 Jan 12 2003 /sys/streams -> ../usr/sys/streams
lrwxr-xr-x 1 root system 19 Jan 12 2003 /sys/streamsm -> ../usr/sys/streamsm
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/ufs -> ../usr/sys/ufs
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/vfs -> ../usr/sys/vfs
# ls -ald /usr/sys/*
drwxr-xr-x 2 bin bin 24576 Jul 6 19:21 /usr/sys/BINARY
drwxr-xr-x 2 root system 16384 Jul 14 21:23 /usr/sys/HOSTNAME
drwxr-xr-x 3 root system 8192 Jul 6 11:41 /usr/sys/arch
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/bin
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/bsd
drwxr-xr-x 4 root system 8192 Jul 6 19:21 /usr/sys/conf
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/data
drwxr-xr-x 2 root system 8192 Jan 12 2003 /usr/sys/hardware
drwxr-xr-x 37 root system 8192 Jul 6 19:21 /usr/sys/include
drwxr-xr-x 5 root system 8192 Jul 6 11:41 /usr/sys/io
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/kern
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/net
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/streams
drwxr-xr-x 2 bin bin 8192 Jul 6 11:41 /usr/sys/streamsm
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/ufs
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/vfs
Probably on your config someone accidently deleted the streamsm directory and made a mistake with the ln command when recreating it.
Since the direcory streamsm seems to be empty in most cases:
ls -al /usr/sys/streamsm
total 16
drwxr-xr-x 2 bin bin 8192 Jul 6 11:41 .
drwxr-xr-x 20 root system 8192 Oct 22 14:04 ..
To solve:
# cd /usr/sys
# rm streamsm
# mkdir streamsm ; chown bin:bin streamsm ; chmod 755 streamsm
# cd /sys
# ln -s ../usr/sys/streamsm
-j-
._.
_JB_
# ls -ald /sys/*
drwxr-xr-x 2 root system 24576 Aug 11 19:47 /sys/BINARY
lrwxrwxrwx 1 root system 17 Jan 14 2003 /sys/HOSTNAME -> ../usr/sys/HOSTNAME
lrwxr-xr-x 1 root system 15 Jan 12 2003 /sys/arch -> ../usr/sys/arch
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/bin -> ../usr/sys/bin
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/bsd -> ../usr/sys/bsd
lrwxr-xr-x 1 root system 15 Jan 12 2003 /sys/conf -> ../usr/sys/conf
lrwxr-xr-x 1 root system 15 Jan 12 2003 /sys/data -> ../usr/sys/data
lrwxr-xr-x 1 root system 18 Jan 12 2003 /sys/include -> ../usr/sys/include
lrwxr-xr-x 1 root system 13 Jan 12 2003 /sys/io -> ../usr/sys/io
lrwxr-xr-x 1 root system 15 Jan 12 2003 /sys/kern -> ../usr/sys/kern
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/net -> ../usr/sys/net
lrwxr-xr-x 1 root system 18 Jan 12 2003 /sys/streams -> ../usr/sys/streams
lrwxr-xr-x 1 root system 19 Jan 12 2003 /sys/streamsm -> ../usr/sys/streamsm
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/ufs -> ../usr/sys/ufs
lrwxr-xr-x 1 root system 14 Jan 12 2003 /sys/vfs -> ../usr/sys/vfs
# ls -ald /usr/sys/*
drwxr-xr-x 2 bin bin 24576 Jul 6 19:21 /usr/sys/BINARY
drwxr-xr-x 2 root system 16384 Jul 14 21:23 /usr/sys/HOSTNAME
drwxr-xr-x 3 root system 8192 Jul 6 11:41 /usr/sys/arch
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/bin
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/bsd
drwxr-xr-x 4 root system 8192 Jul 6 19:21 /usr/sys/conf
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/data
drwxr-xr-x 2 root system 8192 Jan 12 2003 /usr/sys/hardware
drwxr-xr-x 37 root system 8192 Jul 6 19:21 /usr/sys/include
drwxr-xr-x 5 root system 8192 Jul 6 11:41 /usr/sys/io
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/kern
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/net
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/streams
drwxr-xr-x 2 bin bin 8192 Jul 6 11:41 /usr/sys/streamsm
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/ufs
drwxr-xr-x 2 root system 8192 Jul 6 19:21 /usr/sys/vfs
Probably on your config someone accidently deleted the streamsm directory and made a mistake with the ln command when recreating it.
Since the direcory streamsm seems to be empty in most cases:
ls -al /usr/sys/streamsm
total 16
drwxr-xr-x 2 bin bin 8192 Jul 6 11:41 .
drwxr-xr-x 20 root system 8192 Oct 22 14:04 ..
To solve:
# cd /usr/sys
# rm streamsm
# mkdir streamsm ; chown bin:bin streamsm ; chmod 755 streamsm
# cd /sys
# ln -s ../usr/sys/streamsm
-j-
._.
_JB_
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP