help please? corrupted hard disc - invalid super block.
Rob
robert at irrelevant.com
Mon Jun 28 02:04:18 PDT 2004
Hi!
I have a hard disc that I think must have been set up wrong initially...
It was however working fine, but at some point filled up to capacity,
wherapon the next reboot it failed to mount.
System is 4.8-RELEASE, Generic Kernel.
Currently the disc shows:
luggage# mount -r /dev/ad5s1e /mnt
mount: /dev/ad5s1e on /mnt: incorrect super block
luggage# disklabel -r ad5
# /dev/ad5c:
type: ESDI
disk: ad5s1
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 14593
sectors/unit: 234441585
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 234436482 0 unused 0 0 # (Cyl. 0 - 14592*)
e: 234436482 0 4.2BSD 16384 16384 300 # (Cyl. 0 - 14592*)
Warning, partition c doesn't cover the whole unit!
Warning, An incorrect partition c may cause problems for standard system
utilities
luggage# fsck /dev/ad5s1e
Can't open /dev/ad5s1e: Invalid argument
luggage# fsck -b 32 /dev/ad5s1e
Alternate super block location: 32
Can't open /dev/ad5s1e: Invalid argument
luggage# file -s /dev/ad5s1e
/dev/ad5s1e: can't read `/dev/ad5s1e' (Invalid argument).
At this point I am stuck ... most of the "Invalid Super Block" messages I
can find when searching relate to cd-roms.
If I could mount the disc even read-only, I could copy the data off.
Can anybody give me any clues on where to go from here?
Thanks in advance,
Rob
More information about the freebsd-questions
mailing list