Hard drive failure

Manivasagam · 06-21-2012, 01:03 AM

Hi Experts,

In dell 2850 machine we have two HDDs, without RAID.

Each 300GB, In drive 0(sda) OS is installed(RHEL5), In other drive(sdb) /data is present. Yesterday due to some reason sdb became hanged, so i rebooted after that it is not detecting now.

Here is the var log messages :

Info fld=0x4f0016f
end_request: I/O error, dev sdb, sector 82837871
EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read inode block - inode=5178513, block=10354726
sd 0:0:1:0: SCSI error: return code = 0x08000002
sdb: Current: sense key: Medium Error
Add. Sense: Unrecovered read error

HDD is not seeming as a faulty one. There is no amber light.

Didier Spaier · 06-21-2012, 03:47 AM

Try to run e2fsck, if appropriate for the files system in sdb.

BTW you didn't tell which it is.

Manivasagam · 06-21-2012, 04:12 AM

Hi Spaier,
Thanks for your replay. sdb is not detecting, then how can we run e2fsck ?

whizje · 06-21-2012, 04:15 AM

Looks to me like a hardware failure. You could try to reinsert the disk. But I'm afraid it's dead.

onebuck · 06-21-2012, 08:22 AM

Hi,

Quote:

Originally Posted by Manivasagam

Hi Experts,

In dell 2850 machine we have two HDDs, without RAID.

Each 300GB, In drive 0(sda) OS is installed(RHEL5), In other drive(sdb) /data is present. Yesterday due to some reason sdb became hanged, so i rebooted after that it is not detecting now.

Here is the var log messages :

Info fld=0x4f0016f
end_request: I/O error, dev sdb, sector 82837871
EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read inode block - inode=5178513, block=10354726
sd 0:0:1:0: SCSI error: return code = 0x08000002
sdb: Current: sense key: Medium Error
Add. Sense: Unrecovered read error

HDD is not seeming as a faulty one. There is no amber light.

I suggest that you run diagnostics on the questionable drive. Most manufactures do provide utility sets that are used to diagnose and repair when possible. If possible get the drive manufacture's diagnostic set.

From Tools, Recovery, Diagnostic, Emergency in-case you do not have the manufactures diagnostic set;

Quote:

UBCD Ultimate Boot CD <- 'UBCD allows users to run floppy-based diagnostic tools from most CDROM drives on Intel-compatible machines, no operating system required. The cd includes many diagnostic utilities.'

SystemRescueCd <- 'is a Linux system on a bootable CD-ROM for repairing your system and recovering your data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the partitions of the hard disk. It contains a lot of system utilities (parted, partimage, fstools, ...) and basic tools (editors, midnight commander, network tools).' + 'Online-Manual

As too your query about 'e2fsck';

Quote:

excerpt from 'man e2fsck';
e2fsck - check a Linux ext2/ext3/ext4 file system

SYNOPSIS
e2fsck [ -pacnyrdfkvtDFV ] [ -b superblock ] [ -B blocksize ] [ -l|-L bad_blocks_file ] [ -C fd ] [ -j external-journal ] [ -E
extended_options ] device

DESCRIPTION
e2fsck is used to check the ext2/ext3/ext4 family of file systems. For ext3 and ext4 filesystems that use a journal, if the system has
been shut down uncleanly without any errors, normally, after replaying the committed transactions in the journal, the file system
should be marked as clean. Hence, for filesystems that use journalling, e2fsck will normally replay the journal and exit, unless its superblock indicates that further checking is required.

device is the device file where the filesystem is stored (e.g. /dev/hdc1).

Note that in general it is not safe to run e2fsck on mounted filesystems. The only exception is if the -n option is specified, and -c,
-l, or -L options are not specified. However, even if it is safe to do so, the results printed by e2fsck are not valid if the filesystem is mounted. If e2fsck asks whether or not you should check a filesystem which is mounted, the only correct answer is ``no''. Only experts who really know what they are doing should consider answering this question in any other way.

Please note the above underlined information.
HTH!

business_kid · 06-21-2012, 02:16 PM

Been here also.

If the drive is an unmitigated failure, it may be the control board and you may be able to swap it with one from another drive. One of the drive companies sorted me out that way & I lost nothing.