by Derek Wa » Mon, 06 Mar 1995 11:20:23
e2fsck gives me "bad magic number in super-block" and doesn't
offer to fix the partition. Does anyone have any ideas on what this
means and how I could fix it. I desperately need to get at this partition.
Thanks for any help,
Derek
--
Computer Science IV Co-Op U of Manitoba, Winnipeg, Canada
by Sindre R|dseth Hans » Sat, 11 Mar 1995 20:56:01
In article 93934, Derek Ward writes:
|>
|>
|> e2fsck gives me "bad magic number in super-block" and doesn't
|>offer to fix the partition. Does anyone have any ideas on what this
|>means and how I could fix it. I desperately need to get at this partition.
|>
|>Thanks for any help,
|>Derek
|>
|>
|>--
|>Computer Science IV Co-Op U of Manitoba, Winnipeg, Canada
|>
Try an alternative superblock, e2fsck -b 8193 /dev/xxx, where
(8192*n)+1, n is an integer, gives the alternative ones.
Make user you have the latest version of e2fsck (can be found at
tsx-11.mit.edu).
Sindre
1. Help: "cg 0: bad magic number" when newfs ?
Because of electric power stop. One of our Sun sparc1 disk file system
was damaged with "read error". We try to use "newfs" command to rebuilde
the file system. But seems not work. So we use the "format" to reformat the
disk, then use "newfs" again to build filesystem. The format processes fine.
But when we use "newfs" , the message "cg 0: bad magic number" happened.
We've tried to analyze, extract manufacturer's defects list, label again
and again... . The ghost of "bad magic number" still follows us.
If someone so kind to give us any advice.
Thanks!!
<phys1:/>% newfs sd1c
/dev/rsd1c: 204540 sectors in 974 cylinders of 6 tracks, 35 sectors
104.7MB in 61 cyl groups (16 c/g, 1.72MB/g, 768 i/g)
super-block backups (for fsck -b #) at:
32, 3440, 6848, 10256, 13664, 17072, 20480, 23888, 26912,
30320, 33728, 37136, 40544, 43952, 47360, 50768, 53792, 57200,
60608, 64016, 67424, 70832, 74240, 77648, 80672, 84080, 87488,
90896, 94304, 97712, 101120, 104528, 107552, 110960, 114368, 117776,
121184, 124592, 128000, 131408, 134432, 137840, 141248, 144656, 148064,
151472, 154880, 158288, 161312, 164720, 168128, 171536, 174944, 178352,
181760, 185168, 188192, 191600, 195008, 198416, 201824,
cg 0: bad magic number
cg 0: bad magic number
^^^^^^^^^^^^^^^^^^^^^^
<phys1:/>% fsck /dev/sd1c
** /dev/sd1c
CANNOT READ: BLK 16
CONTINUE? y
THE FOLLOWING SECTORS COULD NOT BE READ: 16, 17, 18, 19, 20, 21, 22, 23, 24,
25, 26, 27, 28, 29, 30, 31,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3. AMD 5x86 = "Bad Magic Number" !?!
4. DNS problem, hostname gets screwed up
5. functioning file system with "bad super block: magic number wrong"?
6. Help. Whole machine crashes running TRN
7. "Bad magic number in disk label"...what the....
8. xterm and rlogin: closed connection.
10. anybody know what "bad magic number" means?
11. SCO UNIX: "Out of sync; bad magic number/header"
12. Cant get rid of "bad magic numbers" setting up new disk
13. syslog() "returns" "bad file number"