- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: tru64 unix v5.1B installation
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
тАО08-14-2003 11:54 PM
тАО08-14-2003 11:54 PM
tru64 unix v5.1B installation
i facing problem with installation on DS10 while installing i selected default or customised layout,then it copies whole 150 subsets after that it reboots with boot disk dsk0 and goes into single usr mode by giving
following error
bcheckrc:device naming failed boot configure or verify , please correct problem and continu or reboot..........
After that i checked disk partions booting through cd . a,b,g are o.k. but h partion is unused not showing advfs. and while installing
it is not giving option for choosing file system type.
pls suggest solution for installation
sunil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2003 04:54 AM
тАО08-15-2003 04:54 AM
Re: tru64 unix v5.1B installation
get the system up?
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2003 09:29 PM
тАО08-15-2003 09:29 PM
Re: tru64 unix v5.1B installation
whe i tried df -k command it shows only
rootdevice not any other domain or file systm mounted.
i tried init 2 and init 3 also , system get hang.
Another que ---- suppose i have one domain.i created two filesets in that doamin. in df output it shows available size for both file sets same as the domain size. how it manages
available & used size for both filesets in single domain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2003 05:51 PM
тАО08-17-2003 05:51 PM
Re: tru64 unix v5.1B installation
I'd recommend a simple re-install, using a terminal emulator with a long history to be able to verify any and all step.
If you want to go on with the current install, then in order to 'do' something you will probably need to execute: /sbin/mountroot
During a recent installation I managed to create an unacceptable /tmp. The first error showed up during LSM start, and I did happen to notice it during the boot as it went. Other errors accumulated rapidly after that. Anyway, after mountroot I could re-create /tmp and hit init 3 (actually used ^D). You'll probably need to analyze /etc/fstab, grep etc/sysconfigtab for swap, hwmgr -show scsi, disklabel, ls /dev/*dsk, and stuff like that verify your setup.
As for the other question, AdvFS Fsets are just a creature feature allowing you to group files under a specific mountpoint for dump & restore. The real allocation happens against to domain which they all share. So while more than one fset might show available space, you can only spend it once, for a single fset and it will be deducted everywhere.
Good luck,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2003 07:10 PM
тАО08-17-2003 07:10 PM
Re: tru64 unix v5.1B installation
There was something buried in the release notes which stated that I had to upgrade the LVM filesystem layout before commencing the 5.1 upgrade, otherwise the filesystems would be unusable (if this sounds like it could be helpful let me know and I'll dig up more info).
What is the filesystem layout of your root volumes? It sounds like this is a new install rather than an upgrade - your boot volume is Advfs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2003 11:05 PM
тАО08-17-2003 11:05 PM
Re: tru64 unix v5.1B installation
error #5, then device checks then device nodes, erro:wrong ldev major#(82,0):/dev/kevm:84
error:wrong ldev major,#82,2:/dev/kevm.pterm:84
errors 2, bcheckrc:device naming failed to boot configure or verify
such problems starts if the /dev/ directory is corrupted or files are missing. Please try:
>>> boot -fl s
# mount -u /
# dn_setup -sanity_check
please post output of console or commands for further investigation. Be sure you have set the boot_device to "" prior to installing the system!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2003 12:41 AM
тАО08-18-2003 12:41 AM
Re: tru64 unix v5.1B installation
I had a more/less similar problem and got rid of it by resetting the console-parameter BOOTDEF_DEV
>>> set bootdef_dev " "
The installation-procedure checks this variable and will try to fetch old HW-info from the disk defined by this parameter.
This "feature" is mentioned somewhere in the installation guide.
So, if you want a real "from scratch" installation --> reset bootdef_dev
Hope it helps
Joris