Waiting for file system error (compaq alpha server tru 64 bit)

[Zishan]

Dear all,

I am using tru 64 bit on compaq alpha server.I have four hard drives 72 GB each in my machine. My problem is when server starts it throws errors in event viewer that "waiting for file system /u01/oracle/db_1 ". Out of four one hard drive shows the red light which is hard drive # 4, the rest three are with green light.
Although I dont need data of 4th hard drive. Kinldy guide me how could I able remove this error and reinstall the oracle database for testing environment.
For more information the 4th hard drive contain /u01,u02,u03,u04,u05 drives which all related to database files.So is there any way to delete and recreate these logical drives ?
Any help would be appreciate.
Regards,

[Rob Leadbeater]

Hi,

To stop the system automatically trying to mount the broken file systems, then you need to remove, or comment them out, from /etc/fstab.

To delete and recreate the file systems, you probably want to be using rmfdmn and mkfdmn.

Post the output of /etc/fstab and "ls -lR /etc/fdmns" That will help us to help you.

Cheers,

Rob

[Zishan]

Hello,
below is the output of commands....

root@UNIXSVR/>cat fstab
root_domain#root / advfs rw 0 1
/proc /proc procfs rw 0 0
usr_domain#usr /usr advfs rw 0 2
usr_domain#var /var advfs rw 0 2
oracle_domain#orasw /u01 advfs rw 0 2
data1_domain#data1 /u02 advfs rw 0 2
data2_domain#data2 /u03 advfs rw 0 2
data3_domain#data3 /u04 advfs rw 0 2
backup_domain#dumps /u05 advfs rw 0 2
ora10g_domain#ora10g /u06 advfs rw 0 2
=======================
root@UNIXSVR/> ls â ir /etc/fdmns
1665 usr_domain 1892 data_domain 1660 .advfslock_fdmns
1663 root_domain 1901 backup_domain 1899 .advfslock_data3_domain
1889 oracle_domain 1662 .advfslock_usr_domain 1896 .advfslock_data2_domain
7023 ora10g_domain1661 .advfslock_root_domain1893 .advfslock_data1_domain
1898 data3_domain 1888 .advfslock_oracle_domain1902 .advfslock_backup_domain
1895 data2_domain 6859 .advfslock_oracle_domain

waiting for ur guidance. Also tell me that how could I able to comment in fstab file.
Regards,

[Steven Schweda]

> [...] Also tell me that how could I able
> to comment in fstab file.

man fstab

http://h30097.www3.hp.com/docs/pub_page/doc_list.html

http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/MAN/MAN4/0134____.HTM

[...]
The syntax of a line in the /etc/fstab file is as follows. Note that lines
beginning with a hash (#) sign are ignored. Blank lines are also ignored.
[...]

[Venkatesh BL]

> waiting for file system /u01/oracle/db_1

The closest mount point is 'oracle_domain#orasw /u01 advfs rw 0 2'

So, just precede this line with '#' in the fstab file and try rebooting the machine again.

[Zishan]

Hello,

Thanks for your reply. I already remove this line from fstab and reboot the machine but the error is still showing.

Regards,
Zishan

[Venkatesh BL]

I think it is emitted by one of your user/application startup scripts. Check out the rc3.d directory and see what needs to be tweaked.

[Zishan]

Hello,
Thanks for reply,infact I am new on Tru 64 bit would you like to explain where rc3.d is located ? I am login through root user.

Regards,

[Venkatesh BL]

The startup scripts for Run-level 3 (multiuser mode) are placed in /sbin/rc.d/ directory. A simple check would be go to this directory and do a 'grep' for the "waiting for" pattern. This would give a clue.

[Zishan]

Hello,
I found rc3.d directory in sbin.
what it means
> do a 'grep' for the "waiting for" pattern

Could you able to tell me the exact command ?

regards,

[Venkatesh BL]

# cd /sbin/rc3.d
# grep "waiting for file system" *

[Zishan]

I issued the command but there is no output for this command:

#grep "waiting for filesystem"*

[Venkatesh BL]

There is a 'space' between the double-quote and asterisk '*'... did you try it out correctly?

If still don't get any output...then, it could be that the startup script is calling some other command and the command is giving out the error.

Another possibility is that this is not part of the start up script and a background application daemon is giving out this error.