- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- File systems not mounting
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
Forums
Discussions
Discussions
Forums
Discussions
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
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-04-2002 12:39 PM
04-04-2002 12:39 PM
#mountall
mountall: /dev/vg03/lvol3 has to be fsck'd
mountall: diagnotics from fsck
vxfs fsck: sanity check failed: Cannot open /dev/vg03/lvol3: No such device or address
mountall: cannot fsck /dev/vg03/lvol3
mountall: diagnotics from fsck
cannnot open devise /dev/vg03/lvol3
file system check failure, aborting...
mountall: /dev/vg03/lvol3 faild in fsck
mountall: /dev/vg03/lvol3/lvol3 cannot be mounted
mountall: /dev/vg03/lvol2 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: sanity check faild: Cannot open /dev/vg03/lvol2/: No such device or address
mountall: cannot fsck /dev/vg03/lvol2
mountall: diagnotics from fsck
cannot open device /dev/vg03/lvol2
file system check failure, aborting...
mountall: /dev/vg03/lvol2/ failed in fsck
mountall: /dev/vg03/lvol2/ cannot be mounted
mountall: /dev/vg02/lvol1/ has to be fsck'd
mountall: diagnotics from fsck
vxfs fsck: sanity check faild: Cannot open /dev/vg03/lvol1/: No such device or address
mountall: cannot fsck /dev/vg03/lvol1
mountall: diagnotics from fsck
cannot open device /dev/vg03/lvol1
file system check failure, aborting...
mountall: /dev/vg03/lvol1/ failed in fsck
mountall: /dev/vg03/lvol1/ cannot be mounted
mountall: /dev/vg02/lvol3/ has to be fsck'd
mountall: diagnotics from fsck
vxfs fsck: sanity check faild: Cannot open /dev/vg02/lvol3/: No such device or address
mountall: cannot fsck /dev/vg02/lvol3
mountall: diagnotics from fsck
cannot open device /dev/vg02/lvol3
file system check failure, aborting...
mountall: /dev/vg02/lvol3/ failed in fsck
mountall: /dev/vg02/lvol3/ cannot be mounted
mountall: /dev/vg02/lvol2/ has to be fsck'd
mountall: diagnotics from fsck
vxfs fsck: sanity check faild: Cannot open /dev/vg02/lvol2/: No such device or address
mountall: cannot fsck /dev/vg02/lvol2
mountall: diagnotics from fsck
cannot open device /dev/vg02/lvol2
file system check failure, aborting...
mountall: /dev/vg02/lvol2/ failed in fsck
mountall: /dev/vg02/lvol2/ cannot be mounted
mountall: /dev/vg02/lvol1/ has to be fsck'd
mountall: diagnotics from fsck
vxfs fsck: sanity check faild: Cannot open /dev/vg02/lvol1/: No such device or address
mountall: cannot fsck /dev/vg02/lvol1
mountall: diagnotics from fsck
cannot open device /dev/vg02/lvol1
file system check failure, aborting...
mountall: /dev/vg02/lvol1/ failed in fsck
mountall: /dev/vg02/lvol1/ cannot be mounted
mountall: /dev/vg01/lvol1/ has to be fsck'd
mountall: diagnotics from fsck
vxfs fsck: sanity check faild: Cannot open /dev/vg02/lvol1/: No such device or address
mountall: cannot fsck /dev/vg02/lvol1
mountall: diagnotics from fsck
cannot open device /dev/vg02/lvol1
file system check failure, aborting...
mountall: /dev/vg02/lvol1/ failed in fsck
mountall: /dev/vg02/lvol1/ cannot be mounted
mountall: /dev/vg01/lvol1/ has to be fsck'd
mountall: diagnotics from fsck
vxfs fsck: sanity check faild: Cannot open /dev/vg02/lvol1/: No such device or address
mountall: cannot fsck /dev/vg02/lvol1
mountall: diagnotics from fsck
cannot open device /dev/vg02/lvol1
file system check failure, aborting...
mountall: /dev/vg02/lvol1/ failed in fsck
mountall: /dev/vg02/lvol1/ cannot be mounted
mountall: /dev/vg01/lvol1/ has to be fsck'd
mountall: diagnotics from fsck
vxfs fsck: sanity check faild: Cannot open /dev/vg01/lvol1/: No such device or address
mountall: cannot fsck /dev/vg01/lvol1
mountall: diagnotics from fsck
cannot open device /dev/vg01/lvol1
file system check failure, aborting...
mountall: /dev/vg01/lvol1/ failed in fsck
mountall: /dev/vg01/lvol1/ cannot be mounted
():
All your help is highly appreciated.
Regds
Ramesh
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2002 12:44 PM
04-04-2002 12:44 PM
Re: File systems not mounting
It look like there are some problems with your file systems. Did you shutdown the system properly ?
Now, you can do 'fsck' on all these filesystems inorder to get rid of these errors:
# fsck
Once fscked, then activate each VG (because you are in single user mode) and give mount -a command. That may solve your problem.
HTH,
Shiju
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2002 12:46 PM
04-04-2002 12:46 PM
Re: File systems not mounting
Do the vg02 & vg03 dirs exist under /dev?
Do they contain the group & lvol files?
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2002 12:46 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2002 12:47 PM
04-04-2002 12:47 PM
Re: File systems not mounting
It looks as if none of the volume groups are activated except may be vg00 , was there are ny error messages in teh startup , do a fsck on /dev/vg00/rlvol* and mount all the partions in vg00 first . Then manually try to doa vgdisplay on each volume groups to get moer inforamtion . Most like it is either to do with the disks detection external ones , or the env of root ( default shell of root should not be ksh ) is not proper as it is not bringing up the system properly.
Manoj Srivastava
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2002 12:48 PM
04-04-2002 12:48 PM
Re: File systems not mounting
#fsck
After that run
#vgchange -a y
#mount -a
Sandip
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2002 12:58 PM
04-04-2002 12:58 PM
Re: File systems not mounting
#fsck -y
#vgchange -a y /dev/vg01
#vgchange -a y /dev/vg02
"
"
and so on for all vgs.
Then
#mount -a
I think you are then fine.
-pap