cannot execute lvol's

[sagi_1]

Hi,
I am getting the below errors when trying to boot the server:


/sbin/rc[75]: /dev/vg00/lvol8: cannot execute
/sbin/rc[75]: /dev/vg00/lvol10: cannot execute
/sbin/rc[75]: /dev/vg00/lvol9: cannot execute
/sbin/rc[75]: /dev/vg00/lvol7: cannot execute
/sbin/rc[75]: /dev/vg00/lvol6: cannot execute
/sbin/rc[75]: /dev/vg00/lvol5: cannot execute
/sbin/rc[75]: /dev/vg00/lvol4: cannot execute

But if i boot into single user mode, i am able to mount these lv's. Please suggest.
Thanks,
sagar.

[Raj D.]

>I am getting the below errors when trying to boot the server:

- Seems to be there is some corruption , and the last shutdown was not proper.
- What happened before you got this message. Was it an unexpected shutdown.
- Can you mount all these lvs in single user mode. If yes, after mount , use # vgchange -a y vg00 , then init 3 ( for multiuser mode).

- else , go with fsck: Seems lvol3 is good, that is root.
- run in single user mode, run fsck to all the lvs [ 4,5,6,7,8,9,10 ] and shutdown and try again the boot process.



Hth,
Raj.

[Dennis Handly]

What's on line 75 of /sbin/rc?
This is likely rc.config(4) which sources all files in /etc/rc.config.d/. And you have left a junk file there, which contains a list of your LVs.

[Bill Hassell · Accepted solution]

> in /etc/rc.config.d/. And you have left a junk file there, which contains a list of your LVs.

The rule is: Never create temporary files or other junk in the directory:/etc/rc.config.d If you must keep an old copy of a file, create a directory such as /etc/rc.config.d/old and put old copies of files there. You may have cd'ed into/etc/rc.config.d, then performed some sort of lvol listing and stored the result. This is another reason NOT to cd into a drirectory, especially a system directory, and run various commands.

To find the bad file(s), use this command:

ls -lrt /etc/rc.config.d

The files at the end of this list are new and most likely junk that does not belong in /etc/rc.config.d

> in /etc/rc.config.d/. And you have left a junk file there, which contains a list of your LVs.

That's because the files in /etc/rc.config.d are not executed (sourced) for single user mode.

[James R. Ferguson]

Hi Sagar:

One approach to finding problems like this is to do::

# sh -vx /etc/rc.config 2>&1|more

The sourcing of the '/etc/rc.config.d' directory's files will stops at the first culprit, enabling you to isolate the problem.

With regard to how the '/etc/rc.config.d' directory is processed, it is true that any file therein is a candidate for processing with the *exception* that you *can* have backup copies of files that are *not* processed.

When '/sbin/rc' runs, the '/etc/rc.config.d' directory is examined by the script '/etc/rc.config'. This script skips any file whose basename contains an "extension" that begins with the characters [.,~#].

Thus, it is permissible to have 'netconf' and 'netconf.old'. The '.old' backup will *not* be processed.

If, however, you had kept an old version of your 'netconf' file named as, 'oldnetconf', then *both* 'netconf' and 'oldnetconf' would be sourced. Since the letter "o" follows "n", the result would be undesirable insofar as the last variable declarations seen would be from the wrong file.

However, caveat emptor!

Regards!

...JRF...

[sagi_1]

netconf file was empty. the cause is unknown.
Recreated the file and made teh required entries.