filesystem corruption with bad super block....
From: barry deevey (barry.deevey_at_enmo.co.uk)
Date: 02/27/04
- Previous message: nicholas: "No space left on device (more info)"
- Next in thread: barry deevey: "UPDATE: filesystem corruption with bad super block"
- Reply: barry deevey: "UPDATE: filesystem corruption with bad super block"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: <sunmanagers@sunmanagers.org> Date: Fri, 27 Feb 2004 18:09:47 -0000
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
- Previous message: nicholas: "No space left on device (more info)"
- Next in thread: barry deevey: "UPDATE: filesystem corruption with bad super block"
- Reply: barry deevey: "UPDATE: filesystem corruption with bad super block"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
