Re: Is this Hard drive dead, Jim?
From: Pankajkumar Chauhan (no_spam_at_dev.null)
Date: 01/19/04
- Next message: Henrik Carlqvist: "Re: IDE communication ??"
- Previous message: darklight: "Re: experiences with mainboard GA-7N400?"
- In reply to: Pete: "Is this Hard drive dead, Jim?"
- Next in thread: Pete: "Re: Is this Hard drive dead, Jim?"
- Reply: Pete: "Re: Is this Hard drive dead, Jim?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 19 Jan 2004 14:30:47 -0500
mr_peter_stevenson@hotmail.com (Pete) writes:
> Hi All,
>
> OK ... I *think* I already know the answer to this one but since I
> don't have a backup of the data (no real loss) I'm hoping someone here
> can give a second opinion.
>
> Need some background info?... Well, IDE hard drive was sitting in a
> server and all was working fine, with automatic mounting to /export2
> on boot. Setup on second IDE channel as master drive, CD-RW as slave.
> Primary channel contains two more IDE drives (3.2gb and 13gb).
>
> One shutdown over the holiday period later and we've got problems
> getting the little sucker to play ball.
>
> So, can anybody help confirm that this is "an ex hard drive" that has
> gone to meet it's maker. Alternativly any tips for convincing it to do
> an Elvis and come back from the dead?
>
> I'm not holding my breath but would appreciate some advice.
>
> Thanks in advance,
>
> Pete
I can't offer any technical suggestions, but let me say that yours is
one of the very few posts very well organized, and the language is
hilarious too.
>
> **** STARTS ****
>
> [root@amd /root]# dmesg | more
>
> === snip [blah blah] ===
>
> hda: ST33221A, ATA DISK drive
> hdb: WDC WD136AA, ATA DISK drive
> hdc: Maxtor 4R060J0, ATA DISK drive
> hdd: HP CD-Writer+ 7200, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 6303024 sectors (3227 MB) w/128KiB Cache, CHS=781/128/63
> hdb: 26564832 sectors (13601 MB) w/2048KiB Cache, CHS=1653/255/63
> hdc: 120103200 sectors (61493 MB) w/2048KiB Cache, CHS=119150/16/63
> Partition check:
> hda: hda1 hda2
> hdb: hdb1
> hdc: hdc1
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
>
> === snip [blah blah]===
>
> [root@amd /root]# mount /dev/hdc1 /export2/
> /dev/hdc1: Input/output error
> mount: you must specify the filesystem type
>
> [root@amd /root]# mount -t ext2 /dev/hdc1 /export2/
> mount: wrong fs type, bad option, bad superblock on /dev/hdc1,
> or too many mounted file systems
>
> [root@amd /root]# df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda2 2.8G 1.8G 967M 65% /
> /dev/hdb1 12G 7.6G 4.3G 64% /export
>
> [root@amd /root]# fsck /dev/hdc
> Parallelizing fsck version 1.19 (13-Jul-2000)
> WARNING: bad format on line 8 of /etc/fstab
> e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> Couldn't find ext2 superblock, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open
> /dev/hdc
>
> 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>
>
> [root@amd /root]# e2fsck -b 8193 /dev/hdc [shot in the dark, I have no
> idea what this means]
> e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> e2fsck: Bad magic number in super-block while trying to open /dev/hdc
>
> 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>
>
> [root@amd /root]# e2fsck /dev/hdc1
> e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> e2fsck: Attempt to read block from filesystem resulted in short read
> while trying to open /dev/hdc1
> Could this be a zero-length partition?
>
> [root@amd /root]# fdisk /dev/hdc
>
> The number of cylinders for this disk is set to 119150.
> There is nothing wrong with that, but this is larger than 1024,
> and could in certain setups cause problems with:
> 1) software that runs at boot time (e.g., old versions of LILO)
> 2) booting and partitioning software from other OSs
> (e.g., DOS FDISK, OS/2 FDISK)
>
> Command (m for help): p
>
> Disk /dev/hdc: 16 heads, 63 sectors, 119150 cylinders
> Units = cylinders of 1008 * 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hdc1 1 119150 60051568+ 83 Linux
>
> Command (m for help): q!
>
> [root@amd /root]# dmesg | tail -30
>
> eth1: SiS 900 Internal MII PHY transceiver found at address 1.
> eth1: Using transceiver found at address 1 as default
> eth1: SiS 900 PCI Fast Ethernet at 0x6500, IRQ 11, 00:06:4f:03:26:16.
> eth1: Media Link Off
> klips_info:ipsec_init: KLIPS startup, FreeS/WAN IPSec version: 2.02
>
> hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=66,
> sector=0
> end_request: I/O error, dev 16:01 (hdc), sector 0
> hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=66,
> sector=2
> end_request: I/O error, dev 16:01 (hdc), sector 2
> FAT: bogus logical sector size 0
> VFS: Can't find a valid FAT filesystem on dev 16:01.
> hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=66,
> sector=2
> end_request: I/O error, dev 16:01 (hdc), sector 2
> EXT2-fs: unable to read superblock
> hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=66,
> sector=0
> end_request: I/O error, dev 16:01 (hdc), sector 0
> hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=66,
> sector=2
> end_request: I/O error, dev 16:01 (hdc), sector 2
> hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=66,
> sector=0
> end_request: I/O error, dev 16:01 (hdc), sector 0
> hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=66,
> sector=2
> end_request: I/O error, dev 16:01 (hdc), sector 2
>
>
> **** ENDs ****
--
- Pankaj
----------------------------------------------------------------------
One OS to rule them all, one OS to find them,
One OS to bring them all and in the darkness bind them,
In the Land of Redmond where the Shadows lie.
----------------------------------------------------------------------
- Next message: Henrik Carlqvist: "Re: IDE communication ??"
- Previous message: darklight: "Re: experiences with mainboard GA-7N400?"
- In reply to: Pete: "Is this Hard drive dead, Jim?"
- Next in thread: Pete: "Re: Is this Hard drive dead, Jim?"
- Reply: Pete: "Re: Is this Hard drive dead, Jim?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
