From: barry deevey (barry.deevey@enmo.co.uk)
Date: Fri Feb 27 2004 - 15:35:59 EST
Thanks all for the responses so far...
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: sunmanagers-bounces@sunmanagers.org
[mailto:sunmanagers-bounces@sunmanagers.org]On Behalf Of barry deevey
Sent: 27 February 2004 18:10
To: sunmanagers@sunmanagers.org
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.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:28:09 EDT