UPDATE: filesystem corruption with bad super block
2007-12-25 2:56:00
most are pointing me to run newfs -N
I should have mentioned that I've already done this and it only returned an
alternate super block of 32 - which I've already tried.....
I don't think theres anything else I can do....
Thanks again,
Barry
-----Original Message-----
From: codeprof-bounces at codeprof.com
[mailto:codeprof-bounces at codeprof.com]On Behalf Of barry deevey
Sent: 27 February 2004 18:10
To: codeprof at codeprof.com
Subject: filesystem corruption with bad super block....
All,
When I try fsck on a filesystem I get the below:
# fsck /dev/rdsk/c1t1d0s7
** /dev/rdsk/c1t1d0s7
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).
I then tried to use the alternate super block:
# fsck -F ufs -o b=32,f /dev/rdsk/c1t1d0s7
Alternate super block location: 32.
** /dev/rdsk/c1t1d0s7
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 at all to get fsck to recognise this filesystem would be greatly
appreciated.
Cheers
Barry.
_______________________________________________
codeprof mailing list
codeprof at codeprof.com
http://www.codeprof.com/execute/ask/?codeinfoid=29002
Comments
Got something to say?
You must be logged in to post a comment.
