ntang (ntang) wrote,
ntang
ntang

Bloody hell

I'm still not entirely awake, so this may not make sense, but anyone who's a.) more awake and b.) more knowledgeable w/ disks in linux may be able to help.

Long and short: one of the disks in one of my servers appears to have gone bad.

sting root # fsck /dev/hdb1
fsck 1.35 (28-Feb-2004)
e2fsck 1.35 (28-Feb-2004)
fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open /dev/hdb1
Could this be a zero-length partition?

I tried mke2fs -n on the disk to print up the alternate superblocks, and I tried the first several and last several alternate superblocks, ala:

sting root # fsck -b 32768 /dev/hdb1
fsck 1.35 (28-Feb-2004)
e2fsck 1.35 (28-Feb-2004)
fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open /dev/hdb1
Could this be a zero-length partition?

and

sting root # fsck -b 23887872 /dev/hdb1
fsck 1.35 (28-Feb-2004)
e2fsck 1.35 (28-Feb-2004)
fsck.ext3: Invalid argument while trying to open /dev/hdb1

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

Which, as you can see, didn't help much. What disturbs me are the different error messages, but I'm too tired to fully process that.

If at all possible I'd like to recover the data off the disk; I've got other places I can put it, but at this point I can't even get it to be recognized.

sting root # cfdisk -P s /dev/hdb1
FATAL ERROR: Cannot read disk drive

I'm wondering if either the disk is literally fried, or maybe there's a cable loose or something... sigh. I'm too tired to think right now, so I'm going back to bed. If anyone has any bright ideas, feel free to spew 'em, but I'm having trouble keeping my eyes open. (I hadn't intended to wake up; I hadn't intended to go looking at the machine; I hadn't intended on trying to debug the problem. It all just sort of happened. But I go back to bed now, wake up later, take a look later once I'm awake.)

(Oh, and I shutdown the computer. I figure if there's something wrong, better to kill power to it; although I suppose technically I know that when debugging you ought to change as little as possible until you've done some diagnosis, but f' it.)
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 5 comments