- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Corrupt /etc/sysconfigtab after volencap, volrecon...
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
тАО04-14-2006 10:06 PM
тАО04-14-2006 10:06 PM
We have a DS10 running 5.1B PK5 with dsk0 containing root_domain, swap, usr_domain, and one additional domain.
I used volencap, volreconfig, and volrootmir to mirror dsk0 onto a spare, previously unused, disk of the same type.
Everything went fine except that /etc/sysconfigtab got corrupted (probably during the volreconfig phase). The first part got replaced by
"Core
lsm:
lsm_rootdev_is_volume = 1
The machine seemed to work just fine even with the corrupted file but I copied in the missing stuff from a backup copy of the file just to be safe.
My question (finally): Are there any other modifications than the ones described above that must be done to /etc/sysconfigtab?
The enclosed file is /etc/sysconfig after adding the missing part.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-15-2006 02:41 PM
тАО04-15-2006 02:41 PM
SolutionOne thing: the stanza's you have for per:, aha_chim: and p3g: aren't settable kernel attributes. Those items should be in the PCI Options section above the kernel attributes section.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-18-2006 12:43 PM
тАО04-18-2006 12:43 PM
Re: Corrupt /etc/sysconfigtab after volencap, volreconfig
/etc/sysconfig corruption occures in many situations, So I would suggest to compare the new /etc/sysconfig with nbackup copy and make necessary changes for the differences.
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-18-2006 07:46 PM
тАО04-18-2006 07:46 PM
Re: Corrupt /etc/sysconfigtab after volencap, volreconfig
> So I would suggest to compare the new
> /etc/sysconfig with nbackup copy and
> make necessary changes for the differences.
That's what I did (see original post) but the problem is that I can't see if volencap/volreconfig had tried to change something in the missing part of the corrupt file, hence my question. Philip already answered, and I also found out that the best practice document "Using LSM to Create Mirrored Volumes for Boot
Disk Partitions" covers this kind of problem quite well. (Best practice documents are at
http://h30097.www3.hp.com/docs/best_practices/ )
Thanks anyway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-18-2006 07:50 PM
тАО04-18-2006 07:50 PM