booting without NFS

[Kay Liesenfeld]

There's an invalid entry in /etc/fstab for a NFS-filesystem.

While booting, HP-UX searches this non-existing NFS-server. It's searching for a while and it doesn't seem to stop any more...

How can I kill the invalid entry in /etc/fstab? I booted in single user mode but then I have no chance to edit the file.

I can't mount any other filesystem (e.g. /usr), because it's dirty and fsck terminates with an error (wrong filesystem -> it's Veritas vxfs).

Any ideas?

Thanks in advance!

[RAC_1]

Do you have a ignite recovery tape? Boot from it and restore OS. You may get it.

OR
boot to hpux -lm(;0)/stand/vmunix

then do fsck

Regards,

[Kay Liesenfeld]

Thanks for the fast reply.

I can't run fsck, because it creates an error like "wrong file system" or something like that. It doesn't seem to work with Veritas vxfs.

Unsuddenly no tape available... :-(

Is there no possibility to boot without starting NFS at all?

[U.SivaKumar_2]

Hi,
try running fsck the /usr logical volume and mounting the filesystem.Now edit
the /etc/fstab. IF NOT

In single user mode edit /etc/inittab file
and change initdefault runlevel in the first line of the file to
init:2:initdefault:

reboot the system , since the system does not touch runlevel 3 nfs server will not run . Now run fsck on /usr raw logical volume and mount it and edit the /etc/fstab

regards,
U.SivaKumar

[U.SivaKumar_2]

Hi,
Sorry forgot about /usr problem. again there is a way
From single user mode give
#init 2
#/sbin/init.d/net start
From another Hp-UX server
ftp "ip of problematic server"
login and put /usr/bin/vi to problematic server
ftpd will work because it is in /usr/lbin/ftpd
Now back to problematic server
#vi /etc/fstab

regards,
U.SivaKumar

[U.SivaKumar_2 · Accepted solution]

sorry again in a rush.
use have to use recovery CD in hp-ux 10.20
to get out of this.

regards,
U.SivaKumar

[Kay Liesenfeld]

I just tried this ftp-thing, because it seemed to be the most quickest one. As I tried, the box continued booting -- after more than 1 hour! ;-)

Many thanks for your hints, I'll save them for later tests.

Have a nice weekend!

[T G Manikandan]

Hello,

1.Boot through your core OS cdrom
boot from your CD do not interact with ISL.

2.From the options listed

go to
Exit to recovery shell.
use x to exit into the shell.
3.run chroot_lvmdisk
Enter the exact hardware path of the root file system residing disk.
4.Now enter
cd ROOT; chroot /ROOT /sbin/sh
at the prompt.

5. vgchange -a y /dev/vg00.
now your /usr file system will be mounted.

Now you can edit your /etc/fstab and change the required entry.

just reboot.

Thanks

[RAC_1]

Boot into single user mode

execute following echo " cat - << EOF|ed -s file1
1,$s/abc/#abc/
w file1
q
EOF" >> test.sh

this will create test.sh file, then chmod 700 test.sh

then ./test.sh

In above echo command abc should exactly be your nfs mount point. This just puts the #for nfs mount point.

Then boot, hope it works and you boot.

[John Carr_2]

Hi

in single user mode

cp /etc/fstab /etc/fstab.saved
cat /etc/fstab | grep -v NFS-server > /etc/fstab.new
cp /etc/fstab.new /etc/fstab

reboot -n

cheers
John.

[Tim D Fulford]

My thoughts are off the train of thought here but...

boot to single user mode
ISL> hpux -is

when it cones up, mount the good stuff in vg00, really only need /var & /
# vgchange -a y vg00
# mount /dev/vg00/lvol8 /var

# vi /etc/rc.config.d/nfsconf
edit it so NFS does not come up

# vi /etc/fstab

# init 3

No recovery CD...

[Pete Randall]

Kay,

It sounds like single user mode would work for you if only you could get /usr mounted. How are you trying to run your fsck? Are you specifying the FSType? From the man page for fsck:
-F FStype Specify the file system type on which to operate
(see fstyp(1M) and fs_wrapper(5)). If this option
is not included on the command line, then the file
system type is determined from the file /etc/fstab
by matching special with an entry in that file.
If there is no entry in /etc/fstab, then the file
system type is determined from the file
/etc/default/fs.

This might account for your wrong filesystem error.

HTH,
Pete

[Donald Kok]

At the moment I have the same problem: system is not starting because another (NFS)server is not available.

I just did a ctrl-c during the nfs-client subsystem. Then I could edit /etc/fstab, where I commented out the NFS-mount.

The server started perfectedly.