"Bad magic number"

[Tobias Speckbacher]

If this is happening running fsck I'd ditch it, looks to me like a bad
drive.

-T

-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Edwin Humphries
Sent: Friday, April 16, 2004 3:51 PM
To: redhat-list at redhat.com
Subject: RE: "Bad magic number"

Tobias,

Yes, thanks, that worked. But now I have lots of error messages of 
the format:
"dma=intr: status=0x51 { DriveReady SeekComplete Error }
dma_intr: error=0x40 { UnrecoverableError }, LBAsect=nnnnn, 
sector=xxxxx, end_request: I/O error, dev 04:41 (hdb), sector=xxxxx"

Does this really mean unrecoverable error, or is does it mean that 
the bad sector is being added to the bad sector file, and that the 
rest of the drive is OK?

On 16 Apr 2004 at 15:30, Tobias Speckbacher wrote:

> Try running fsck on the partition (ie. hdb1) instead on the device
> (hdb).
> 
> -T
> 
> -----Original Message-----
> From: redhat-list-bounces at redhat.com
> [mailto:redhat-list-bounces at redhat.com] On Behalf Of Edwin 
Humphries
> Sent: Friday, April 16, 2004 1:25 PM To: redhat-list at redhat.com
> Subject: "Bad magic number"
> 
> G'day all,
> 
> We're just fitting a second HDD into our new Fedora server, and 
> getting error messages I don't know how to deal with.
> 
> The drive is near new, but we're not entirely sure of its 
provenance,
> so we're being cautious. However, it fdsisked fine, and running 
mke2fs
> -j /dev/hdb1 ran OK with no error messages.
> 
> But because of our cautions, I tried to check the drive for errors
> before using it for any data: ran e2fsck -c /dev/hdb.
> 
> The result was an error messages as follows:
> |Couldn't find ext2 superblock, trying backup blocks ...
> |e2fsck: Bad magic number in super-block while trying to open 
> |/dev/hdb
> |
> |The superblock could not be read or does not describe a correct 
ext2
> |filesystem.  If the device is valid and it really contains an ext2
> |filesystem (and not swap or ufs or something else), then the
> |superblock is corrupt, and you might try running e2fsck with an
> |alternate superblock: e2fsck -b 8193 <device>  
> 
> Now I'm not sure what magic numbers or super-blocks are, and I have 
no
> idea how to fix this. Can anyone shed some light on this?
> 
> Edwin Humphries,
> Ironstone Technology Pty Ltd
> edwin at ironstone.com.au
> www.ironstone.com.au
> Phone: 02 4233 2285
> Fax: 02 4233 2299
> Mobile: 0419 233 051
> 
> 
> -- 
> redhat-list mailing list
> unsubscribe mailto:redhat-list-
request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list


Edwin Humphries,
Ironstone Technology Pty Ltd
edwin at ironstone.com.au
www.ironstone.com.au
Phone: 02 4233 2285
Fax: 02 4233 2299
Mobile: 0419 233 051


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list