Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I am having problems trying to mount a filesystem where I get the following messege:
# mount /dev/vx/dsk/rootdg/vol01 /data/u01
mount: /dev/vx/dsk/rootdg/vol01 is not this fstype.
when I run fsck I get:
** /dev/vx/dsk/rootdg/vol01
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
eg. fsck [-F ufs] -o b=# [special ...]
where # is the alternate super block. SEE fsck_ufs(1M).Any ideas how to run fsck to fix the filesystem
Thanks in Advance

First, is /dev/vx/dsk/rootdg/vol01 ufs, vxfs or some other FS? If it is ufs, then you need to figure out what controller/target/disk/slice the filesystem is. Try running "vxdisk list" (as root) to get the c#t#d#s# for the disk. Then run fsck as indicated:
fsck -F ufs /dev/rdsk/c#t#d#s#If it comes back with the "alternate super-block" error, run "newfs -Nv /dev/rdsk/c#t#d#s#". This will generate a list of alternate superblocks. Then run:
fsck -F ufs -o b= /dev/rdsk/c#t#d#s#

It seems that the error messages is indicating a wrong filesystem being specified.
Check your /etc/default/fs to see which
the default filesytem.
try mounting it as a veritas filesystem .
mount -F vxfs /dev/vx/dsk/rootdg/vol01 /data/U01 .Let us know the outcome
iosakwe

Thanks Guys you feed back was usefull, but
I have tried the newfs and fsck as mentioned by Erulia, but what I discovered is that the filesystem was corrupt because one of the disks failed, hence I had to clean and enable to striped plex used by that file system then used "newfs" to rebuild the file system and recovered the data from tapes.The file system is mounted ok now
Once again thank you guys for the info

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |