Sponsored Content
Top Forums UNIX for Dummies Questions & Answers I got a corrupt /etc/inittab file....what next? Post 28999 by Perderabo on Friday 27th of September 2002 08:49:18 AM
Old 09-27-2002
I'm not familiar with the Netra. But I found this on Sun's web site...
Quote:
The Netra[TM] X1 server comes preinstalled with Solaris[TM] 8 Update 2 (10/00), including LOM (Lights out Management)software and all the patches it needs to function correctly. Because the Netra X1 server does not contain a CD-ROM drive and the Solaris installation media is not bootable on this system, if you need to reinstall the Solaris 8 operating environment, you must do so from a network install server. Additionally, the Netra X1 Drivers must be downloaded from Sun and added to the installation image.
This means that if you can't get that thing to boot, you are going to need a network install server. And really, you are going to need a Sun/Solaris guru to go with it. I guess that I might call my local Sun office and ask them to handle this.

Before that, I would be sure that I really can't get into single user mode. Can you get an "ok" prompt? What are you doing to get into single user mode? "boot -s"? If that doesn't work you may need to use the above procedure to reinstall.

I found one Sun Doc that says "boot -s" from a cdrom is way out of a corrupt /etc/default/init so it may be impossible to get to single user mode with a corrupt /etc/inittab as well.

If you do get yourself out of this fix, please post back and tell us what it took. Good luck.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

inittab solaris

Hi! Is it possible to add more ttys in Solaris, like with inittab in Linux? I want to switch between the ttys with Alt F1+F2+F3 .... like Linux does. How can i do this? (1 Reply)
Discussion started by: donald1111
1 Replies

2. HP-UX

Corrupt Member File

I have been fine adding/removing printers up until this week. Now when I go to add a new remote printer I get "corrupted member file". I go to /etc/lp/member and the byte count on the new printer name is 0. I VI the file and put /dev/null in to make it the correct size and it all looks fine and... (2 Replies)
Discussion started by: astout
2 Replies

3. UNIX for Dummies Questions & Answers

find a corrupt tar file

Hey there I am just looking for a way to find a corrupt tar file. I want to write a script to help sift through the 1000's of tar files we go through daily and move any corrupt ones to a different directory structure. Is there an easy way to do this. (4 Replies)
Discussion started by: car2nst2006
4 Replies

4. AIX

GPFS file system corrupt issue

Hi Administrators, I have one issue related to GPFS filesystem. We have bad entries in this file system, which reflects error like ls: 0653-341 The file <filename> does not exist. when we give "ls -ltr" on this directory. So we taken the FS filesystem offline and followed the below steps. ... (6 Replies)
Discussion started by: gauravgarg
6 Replies

5. UNIX for Dummies Questions & Answers

Zipped tar file is corrupt

Hello, I am currently dumping 30-40 reports on a Unix folder located here /home/apps/reports/prode/excel I use K-shell to do this task. In that, I use the gzip command to compress these files. I want to be able to use a tar command to first load the entire directory into one file then gzip that... (2 Replies)
Discussion started by: Pramodini Rode
2 Replies

6. Solaris

Recovering from corrupt /etc/system file

Hi I would like to know one thing while recovering from corrupt /etc/system file. For that we have to do at ok> boot -a when system ask for system file we give /dev/null. Could any one tell me what /dev/null value will do in this case. Regards (1 Reply)
Discussion started by: sb200
1 Replies

7. UNIX for Advanced & Expert Users

Linux on vmware won't boot due to corrupt library file!

We have an issue here: The libc.so.6 file (link) is corrupted and it causes the system unbootable. It even doesn't boot to single user mode. How can we boot the system to fix the library file? Or is there any other solutions for this issue? Here are some boot messages:... (6 Replies)
Discussion started by: aixlover
6 Replies

8. UNIX for Dummies Questions & Answers

What breaks inittab

Today there was a situation where processes running from inittab was broken. Can someone help me understand, how to find out, who might have stopped those processes? Or how does it get broken? G (2 Replies)
Discussion started by: ggayathri
2 Replies

9. Solaris

UNIX : how can I recover a corrupt tar file from a tape?

I've a tape contains a corrupt tar file. I'm using Unix SunOS 5.5.1. So when I run this command : dd if=/dev/rmt/0 of=/tmp/outputfile.tar I get this error message : warning /pci@1f, 0/pci@1/pci@1/sunw, isptwo@4/st@4,0 (sty): Error for command : read Error Level: Fatal Requested... (2 Replies)
Discussion started by: akaderb
2 Replies
patchsvr(1M)						  System Administration Commands					      patchsvr(1M)

NAME
patchsvr - set up a Sun Update Connection Proxy SYNOPSIS
/usr/sbin/patchsvr setup [-c cache-location] [-d] [-h] [-l] [-p update-source-url] [-s pw-file-location] [-u user-name] [-x web-proxy- host:port] /usr/sbin/patchsvr start /usr/sbin/patchsvr stop /usr/sbin/patchsvr enable /usr/sbin/patchsvr disable DESCRIPTION
The patchsvr command enables you to set up a Sun Update Connection Proxy on your intranet. The setup subcommand configures the Sun Update Connection Proxy. The start and stop subcommands start and stop the Sun Update Connection Proxy. Finally, the enable and disable subcom- mands permit you to start up and prevent startup of the Sun Update Connection Proxy at boot time. The Sun Update Connection Proxy was previously called local patch server. Note - The Sun Update Connection Proxy supports client systems that use the Sun Update Connection, System Edition software and the Sun Patch Manager 2.0 software. A Sun Update Connection client system is not compatible with the older local patch server feature asso- ciated with the Sun Patch Manager 2.0 software. Configuring Your Sun Update Connection Proxy By default, Update Manager expects that your local systems are connected, via the Internet, to the Sun update server to be analyzed and to receive updates. By using a Sun Update Connection Proxy instead, you can minimize the Internet traffic and serve your local systems from a update server on your intranet. The system you choose to act as the Sun Update Connection Proxy must be running at least the Developer Solaris Software Group of the Solaris 10 Operating System. You must also install the Sun Update Manager 1.0 software and the Sun Update Connection Proxy software. The use of a Sun Update Connection Proxy addresses security concerns and reduces the amount Internet traffic between the Sun update server and your client systems. For instance, instead of having to download updates and metadata from the Sun update server to each of your systems, the data is downloaded to the Sun Update Connection Proxy the first time that a client system requests an update. After the update data is stored on your Sun Update Connection Proxy, the transfer of update data to your system for analysis is done over your intranet instead of over the Internet. You can configure a chain of update servers on your intranet. The last link in the chain of local servers can point to the Sun update server or to a local collection of updates. By using this chain of servers, an update download request from your system to its primary update server can be forwarded to other servers in the chain in an attempt to fulfill the request. So, if your system's primary server can- not locate an update, the server makes the same request of the next server in the chain to see if the update is stored there. If the update is found, it is downloaded to the system. If the update is not found, the request continues along the chain until the update is found or the terminal point in the chain is reached. Each server in the chain stores the updates found on another server in the chain based on the download request. So, an update that is not initially found on your local server will be downloaded to your local server and stored before being downloaded to the client system. Your Sun Update Connection Proxy must specify the source of updates to use. By default, the server obtains updates from the Sun update server, but it can also obtain updates from another update server in the chain or from a collection of updates on your system. You must specify the URL that points to the collection of updates. By default, the Sun update server is the source of updates. The URL is: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. This URL must point to another server in the chain or to a collection of updates on the local system. This URL cannot be null. Starting and Stopping Your Sun Update Connection Proxy The patchsvr start command starts the Sun Update Connection Proxy. You can also enable the boot-time startup of the Sun Update Connection Proxy by running patchsvr enable. The patchsvr stop command stops the Sun Update Connection Proxy. You can also disable the boot-time startup of the Sun Update Connection Proxy by running patchsvr disable. Before you use your Sun Update Connection Proxy for the first time, you must run the patchsvr start command. Use these commands when you want to change the configuration of your Sun Update Connection Proxy. Before you use the patchsvr setup command to change the configuration parameter values, you must stop your Sun Update Connection Proxy. Then, you can update the configuration val- ues. Finally, you must restart the Sun Update Connection Proxy. OPTIONS
The following options are supported for the patchsvr setup command: -c cache-location Specifies the location of the server's cache, also known as the update repository. This is the directory in which downloaded updates are stored on the Sun Update Connection Proxy. You must specify a full path to the cache loca- tion. By default, the cache location is file:/var/sadm/spool/patchsvr. Ensure that this update repository has 2 Gbytes of free disk space available to store downloaded updates. -d Resets the Sun Update Connection Proxy configuration settings to the default values. -h Displays information about the command-line options. -l Lists the configuration settings for the update server. -p update-source-url Specifies the URL that points to the collection of updates. By default, the URL points to the Sun update server: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. -s pw-file-location Specifies the path of the proxy password file in which you have stored your proxy password. You must put the password in a file rather than specifying it on the command line because command-line information is visible via the ps command. -u user-name Specifies the user name required for web proxy authentication. -x web-proxy-host:port Specifies the local web proxy. If the Sun Update Connection Proxy is behind a firewall, use this option to specify the web proxy that accesses the Internet. Get the name of the web proxy, web-proxy-host, and its port, port, from your system administrator or network administrator. The default port value is 8080. Do not use this option if you are accessing update data from a collection of updates on the Sun Update Connection Proxy. EXAMPLES
Example 1: Changing the Cache Location # patchsvr setup -c /var/update/cache Example 2: Specifying the Sun Update Server as the Source of Updates # patchsvr setup -p https://getupdates.sun.com/solaris/ The Sun update server is the default source of updates. Example 3: Specifying a Sun Update Connection Proxy as the Source of Updates # patchsvr setup -p http://updatesvr1:3816/solaris/ Specifies the system called updatesvr1, a Sun Update Connection Proxy, as the source of updates. Example 4: Specifying a CD as the Source of Updates # patchsvr setup -p file:/cdrom/cdrom0 Specifies the CD mounted from the first CD-ROM drive of the local system as the update source. Example 5: Specifying a Web Proxy # patchsvr setup -x webproxy:8080 Specifies the host name, webproxy, and port, 8080, of the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Example 6: Specifying a User Name and Password for Web Proxy Authentication # (umask 77 ; vi /tmp/password) # patchsvr setup -u terry -s /tmp/password # rm /tmp/password While in a subshell, you create a temporary file that is not readable by others and put the password in that file. Next, you specify the user name, terry, and location of the password file, /tmp/password, used to authenticate the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Then, you delete the temporary file now that the web proxy authentication is specified. Example 7: Resetting the Configuration Settings to the Default Values # patchsvr setup -d Example 8: Listing the Configuration Settings for Your Sun Update Connection Proxy # patchsvr setup -l Patch source URL: https://getupdates.sun.com/solaris/ Cache location: /var/sadm/spool/patchsvr Web proxy host name: mars Web proxy port number: 8080 Shows the configuration settings, which include information about the source of updates, the location of the cache directory, and, if needed, a web proxy and port. Example 9: Starting the Sun Update Connection Proxy # patchsvr start Example 10: Stopping the Sun Update Connection Proxy # patchsvr stop Stops your Sun Update Connection Proxy. While the update server is stopped, you can change the configuration settings for your Sun Update Connection Proxy, then restart it. Example 11: Enabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr enable Example 12: Disabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr disable ATTRIBUTES
See the attributes(5) man page for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWpsvru | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
smpatch(1M), attributes(5) Sun Update Manager 1.0 Administration Guide SunOS 5.10 12 May 2005 patchsvr(1M)
All times are GMT -4. The time now is 06:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy