Server keeps shutting down ! (FC3)

Lonni J Friedman netllama at gmail.com
Tue Dec 5 00:28:50 UTC 2006


On 12/4/06, Kim Lux <lux at diesel-research.com> wrote:
> This is what I get from the drive when its mounted via the USB drive
> caddy on another machine:
>
> #/sbin/fsck /dev/sda
> fsck 1.39 (29-May-2006)
> e2fsck 1.39 (29-May-2006)
> Couldn't find ext2 superblock, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
>
> 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>
>
> # /sbin/fsck /dev/sda1
> fsck 1.39 (29-May-2006)
> e2fsck 1.39 (29-May-2006)
> /boot: clean, 67/26104 files, 34101/104388 blocks
>
> ]# /sbin/fsck /dev/sda3
> fsck 1.39 (29-May-2006)
> e2fsck 1.39 (29-May-2006)
> /: clean, 506434/24821760 files, 41973788/49634825 blocks
>
> The first error message is exactly the same as what happens on the
> server.  Why does fsck /dev/sda fail, but fsck /dev/sda1 and
> fsck /dev/sda3 work ?

Because you fsck a filesystem, not a block device.

>
> Does this drive problem have something to do with the server shutting
> down ?

I don't see any connection between user error & hardware failure.


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                                    netllama at gmail.com
LlamaLand                       http://netllama.linux-sxs.org




More information about the fedora-list mailing list