LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
LinkBack Search this Thread
Old 11-28-2006, 01:49 PM   #1
keysorsoze
Member
 
Registered: Apr 2004
Location: Queens, NY
Distribution: Red Hat, Solaris
Posts: 295

Rep: Reputation: 30
Hard Drive Failing?


Hi! I am receiving the following error messages when I perform a dmesg | less this is what I receive: Can someone tell me what I need to do to fix this? Can I replace the drive and if so is it /dev/hdg2 or a mix ? If I just replace this 160GB will everything return to normal? What about just running fsck on the drive?

Thanks.

Here is an output from my df -h to identify the drives I currently have.

Filesystem Size Used Avail Use% Mounted on
/dev/hda3 34G 5.2G 27G 17% /
/dev/hda1 99M 8.4M 86M 9% /boot
/dev/hdg2 146G 10G 129G 8% /bak
none 379M 0 379M 0% /dev/shm
/dev/md0 230G 90G 129G 41% /home


[root@mail back]# dmesg | less
ev hdg, sector 23538128
end_request: I/O error, dev hdg, sector 23538136
end_request: I/O error, dev hdg, sector 23538144
end_request: I/O error, dev hdg, sector 23538152
end_request: I/O error, dev hdg, sector 23538160
end_request: I/O error, dev hdg, sector 23538168
end_request: I/O error, dev hdg, sector 23538176
end_request: I/O error, dev hdg, sector 23538184
end_request: I/O error, dev hdg, sector 23538192
end_request: I/O error, dev hdg, sector 23538200
end_request: I/O error, dev hdg, sector 23538208
end_request: I/O error, dev hdg, sector 23538216
end_request: I/O error, dev hdg, sector 23538224
end_request: I/O error, dev hdg, sector 23538232
end_request: I/O error, dev hdg, sector 23538240
end_request: I/O error, dev hdg, sector 23538248
end_request: I/O error, dev hdg, sector 23538256
end_request: I/O error, dev hdg, sector 23538264
end_request: I/O error, dev hdg, sector 23538272
end_request: I/O error, dev hdg, sector 23538280
end_request: I/O error, dev hdg, sector 23538288
end_request: I/O error, dev hdg, sector 23538296
end_request: I/O error, dev hdg, sector 23538304
end_request: I/O error, dev hdg, sector 23538312
end_request: I/O error, dev hdg, sector 23538320
end_request: I/O error, dev hdg, sector 23538328
end_request: I/O error, dev hdg, sector 23538336
end_request: I/O error, dev hdg, sector 23538344
end_request: I/O error, dev hdg, sector 23538352
end_request: I/O error, dev hdg, sector 23538360
end_request: I/O error, dev hdg, sector 23538368
printk: 260 messages suppressed.
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): read_inode_bitmap: Cannot read inode bitmap - block_group = 0, inode_bitmap = 12
hde: status timeout: status=0x80 { Busy }

ide: failed opcode was: unknown
PDC202XX: Primary channel reset.
PDC202XX: Secondary channel reset.
hde: drive not ready for command
ide2: reset: master: error (0x00?)
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
d: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
end_request: I/O error, dev hde, sector 488391871
md: write_disk_sb failed for device hde1
md: errors occurred during superblock update, repeating
md: write_disk_sb failed for device hde1
md: excessive errors occurred during superblock update, exiting
end_request: I/O error, dev hde, sector 19399
raid1: Disk failure on hde1, disabling device.
Operation continuing on 1 devices
end_request: I/O error, dev hde, sector 19407
end_request: I/O error, dev hde, sector 369778711
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:1, o:0, dev:hde1
disk 1, wo:0, o:1, dev:hdf1
RAID1 conf printout:
--- wd:1 rd:2
disk 1, wo:0, o:1, dev:hdf1
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2056416
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): read_inode_bitmap: Cannot read inode bitmap - block_group = 0, inode_bitmap = 12
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2056416
end_request: I/O error, dev hdg, sector 2056320
EXT2-fs error (device hdg2): ext2_readdir: bad page in #2
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): ext2_readdir: bad page in #2
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): ext2_readdir: bad page in #2
end_request: I/O error, dev hdg, sector 2056424
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): ext2_get_inode: unable to read inode block - inode=2, block=13
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): ext2_readdir: bad page in #2
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): ext2_readdir: bad page in #2
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): ext2_readdir: bad page in #2
end_request: I/O error, dev hdg, sector 2060520
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): ext2_readdir: bad page in #2
end_request: I/O error, dev hdg, sector 2056424
end_request: I/O error, dev hdg, sector 2056320
Buffer I/O error on device hdg2, logical block 0
lost page write due to I/O error on hdg2
EXT2-fs error (device hdg2): ext2_get_inode: unable to read inode block - inode=2, block=13
 
Old 11-28-2006, 02:53 PM   #2
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 405

Rep: Reputation: 42
Doesn't look like /dev/hdg is a valid physical device. In fact it's possible but it doesn't make much sense to have a /dev/hda drive and a /dev/hdg drive. Looks like /dev/hdg is a typo to me. I can only guess, but I think you need to change that "/dev/hdg2" to "/dev/hda2".
 
Old 11-28-2006, 02:55 PM   #3
keysorsoze
Member
 
Registered: Apr 2004
Location: Queens, NY
Distribution: Red Hat, Solaris
Posts: 295

Original Poster
Rep: Reputation: 30
Would I edit this partition in the fstab? This is a Red Hat Enterprise Box.
 
Old 11-28-2006, 06:37 PM   #4
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 405

Rep: Reputation: 42
Yes. You should see a stanza in there that looks like:

/dev/hdg2 /bak reiserfs defaults 1 2
Just change "/dev/hdg2" to "/dev/hda2"

Note: You may have a different file system then Reiserfs or different options at the end. You probably won't need to mess with those. Try it and see where you're at.
 
Old 11-28-2006, 09:56 PM   #5
keysorsoze
Member
 
Registered: Apr 2004
Location: Queens, NY
Distribution: Red Hat, Solaris
Posts: 295

Original Poster
Rep: Reputation: 30
Meetscoot,

I think /dev/hdg2 is a real device. However after umounting it I can no longer re-mount it. I get the following. I changed it to hda2 as suggested but it is currently used by swap.


[root@mail ~]# mount /dev/hdg2
mount: wrong fs type, bad option, bad superblock on /dev/hdg2,
or too many mounted file systems

Here is a print out of my fstab.

[root@mail ~]# cat /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
/dev/hdg2 /backup/ ext2 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
/dev/md0 /home ext3 defaults 1 2
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/hda2 swap swap defaults 0 0

Can I mount the drive as something else? Such as /dev/hdb1 does it matter if its located on the second ide controller? How can you tell?

Thanks.
 
Old 11-29-2006, 07:15 AM   #6
nhydra
Member
 
Registered: May 2006
Distribution: Fedora Core, FreeSpire, PC-BSD, NetBSD
Posts: 96

Rep: Reputation: 15
Ohh i think this disk probably dies.
So, i suggest running this: http://smartmontools.sourceforge.net/

This is a hard drive SMART analyzing tool. If you use Fedora just install it with yum
yum install smartmontools

Then you just run it to check the SMART status:
smartctl -a /dev/your-device

Then run short and long selftests to examine the health of the device.
smartctl -t short /dev/your-device

Wait 5 mins and then run the long test.
smartctl -t long /dev/your-device

After long test running you have to wait about 30-60 mins for analyzing...

Then you will finaly know that your hard drive is dead or not.

Regards.
 
Old 11-29-2006, 08:59 AM   #7
hansalfredche
Member
 
Registered: Jun 2005
Posts: 445

Rep: Reputation: 31
Some inputs

As nhydra says, try running smartctl. If you are booting your machine frequently, also enable SMART in your BIOS. It should warn you if the drive is about to fail.

If your drive is attached to a PCI controller or you have 4 IDE connectors on your main board it is possible that your drive is /dev/hdg. Try to find out what your drive is called. If smartctl gives drive information if you tell it to print infos about /dev/hdg (not /dev/hdg2), then that drive exists.

In /etc/fstab you must say which partitions must be mounted, therefore /dev/hdg2.
/dev/hda2 is your swap partition, probably not what you are looking for!!! Do not mess around with /dev/hda2!

So install smartmontools with your favourite packet manager and try command:
smartctl --all /dev/hdg

Make sure you are using the correct file system. You must find out which one you use. If you have a tool like QtParted you could look what partitions are on it, what filesystems, what they are called etc. Watch out however as you very quickly can destroy the data on the drive if doing wrong things. Don't try to repartition/format!

PS: For Red Hat geeks: is it normal that /dev/hda1 and /dev/hdg1 is missing?

Last edited by hansalfredche; 11-29-2006 at 09:03 AM.
 
Old 12-01-2006, 11:41 PM   #8
keysorsoze
Member
 
Registered: Apr 2004
Location: Queens, NY
Distribution: Red Hat, Solaris
Posts: 295

Original Poster
Rep: Reputation: 30
Thanks for the responses guys, I'll give the tool provided a go. I'll post back with the results.
 
Old 12-02-2006, 12:03 AM   #9
keysorsoze
Member
 
Registered: Apr 2004
Location: Queens, NY
Distribution: Red Hat, Solaris
Posts: 295

Original Poster
Rep: Reputation: 30
[root@mail ******]# smartctl --all /dev/hdg
smartctl version 5.33 [i386-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number: [No Information Found]
Firmware Version: [No Information Found]
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 1
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sat Dec 2 00:57:52 2006 EST
SMART is only available in ATA Version 3 Revision 3 or greater.
We will try to proceed in spite of this.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
[root@mail *******]#

Hi! Guys I ran the smart utility on the disk, I don't think smart is enabled in the bios though because I didn't get anything off of the command. I believe /dev/hdg is a part of a raid1 array I can't get access to the drive until monday since this is a remote box so I'll have to see if smart is turned on bios.

One more thing can someone explain /dev/md0? Is this raid?

I ran fdisk -l and this is what I see.


[root@mail ******]# fdisk -l

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 395 3068415 82 Linux swap
/dev/hda3 396 4865 35905275 83 Linux

Disk /dev/hdf: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdf1 * 1 30401 244196001 fd Linux raid autodetect

Disk /dev/md0: 250.0 GB, 250056605696 bytes
2 heads, 4 sectors/track, 61048976 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md0 doesn't contain a valid partition table

------------------------------------------------------------------------

Can /dev/md0 be where /dev/hdg2 located?

Thanks

Last edited by keysorsoze; 12-02-2006 at 12:14 AM.
 
Old 12-02-2006, 01:29 AM   #10
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 405

Rep: Reputation: 42
Sorry, but indeed hda2 is your swap now that I've seen the fstab output. I feel like we're throwing rocks in the dark. /dev/md0 is raid.

Look man, you don't have an /dev/hdg drive! I should have asked you to do this before but I really thought things were a typo earlier. Let's straighten you out now. You have 2 physical hard disks, one referred to as /dev/hda and one referred to as /dev/hdf. /dev/hdf1 is actually /dev/md0. We're going to change that.

I'm going to assume that the 250GB drive (/dev/hdf) is supposed to back up the 160GB drive (/dev/hda). You need to use fdisk to change the file system type id from "fd" to "83" like your other Linux partitions on /dev/hda. Then run mkfs.ext3 or whatever to create a file system on /dev/hdf1. Then change your /etc/fstab accordingly (meaning /dev/hdg2 is going to become /dev/hdf1 in your fstab). Remember there is no /dev/hdg in your world, it's /dev/hdf ;-) Also remove the /dev/md0 reference in your fstab file. It will no longer be raid auto detected at boot time. This will take care of all those errors because fstab won't be asking the system to try and mount it at boot time when it doesn't exist. Also, your I/O request errors will go away because you're no longer trying to mount a physical device that does not exist.

I'm not going to say the others are outright wrong for checking that hard disk for functionality with a utility, but I will say that in my experience, that is with last half dozen or so hard disks I've worn out, that drives usually just die. Or they will only operate for a brief period at boot time or for a short time after. Then they quit. I don't see what new information these utilities glean. 2 things typically happen on a drive: the read/write head crashes or is unable to move effectively in which case you're dead right away or the bearings lose their lubrication and the drive sounds like it's grinding when it's spinning which results in a drive that will fail after running for a bit. You may be able to get data off these drives by normal means, especially by repeatedly trying. The grinding drive will be done soon so act reasonably fast to get your important data off.

As I say, I won't say the others are wrong, but usually a hard disk problems show themselves in really obvious ways so there is no question about it. Post back if you don't understand something or you're still having problems getting things configured. What you have is quite simple, it's just a matter of getting all the pieces put together properly.

Last edited by meetscott; 12-02-2006 at 01:32 AM.
 
Old 12-02-2006, 09:36 AM   #11
keysorsoze
Member
 
Registered: Apr 2004
Location: Queens, NY
Distribution: Red Hat, Solaris
Posts: 295

Original Poster
Rep: Reputation: 30
Thank's Meetscott

I'll give your suggestions a shot on Monday when I go physically look at the system.
 
Old 12-03-2006, 07:10 AM   #12
nhydra
Member
 
Registered: May 2006
Distribution: Fedora Core, FreeSpire, PC-BSD, NetBSD
Posts: 96

Rep: Reputation: 15
Hey, just try this.
smartctl -a /dev/hda
smartctl -a /dev/hdb
smartctl -a /dev/hdc
smartctl -a /dev/hdd
smartctl -a /dev/hdg
smartctl -a /dev/hdh

I don't understand where the problem is... Just run smarctl on the target drive.
If you don't know who the drive is just run all the above commands to all available drives...
These commands that match your drives will execute others will fail.
Post the results here. And you can enable the SMART via smactctl too.

Do that to enable the SMART:
smartctl --smart=on /dev/your-device

And then you can run all the test you want.
 
Old 12-03-2006, 01:40 PM   #13
keysorsoze
Member
 
Registered: Apr 2004
Location: Queens, NY
Distribution: Red Hat, Solaris
Posts: 295

Original Poster
Rep: Reputation: 30
Ok, I got smart to function on the drives by running the smartctl command on all drives. The ones that did not come up I did not list. Such as /dev/hdb /dev/hdc.
However /dev/hdg did not come up but I was able to umount it before so it is strange I can no longer remount it. Here is a cat of /proc/partitions. Does this mean that there was a drive there before? I could swear /dev/hdg existed and when I unmounted it it never was mountable again. It is a part of a raid controller. Sorry for all these questions its just I took over this system and there was no documentation on the install process and I have to figure out why there is an error since we used to back up to this drive and now its no longer readable.

[root@mail proc]# cat partitions
major minor #blocks name

3 0 156290904 hda
3 1 104391 hda1
3 2 3068415 hda2
3 3 35905275 hda3
33 0 244198584 hde
33 1 244196001 hde1
33 64 244198584 hdf
33 65 244196001 hdf1
34 0 156290904 hdg
34 1 1028159 hdg1
34 2 155260192 hdg2
9 0 244195904 md0

Also what does Disk /dev/md0 doesn't contain a valid partition table mean?

[root@mail ~]# smartctl --smart=on /dev/hda
smartctl version 5.33 [i386-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
--------------------------------------------------------------------------------
[root@mail ~]# smartctl --smart=on /dev/hdf
smartctl version 5.33 [i386-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
--------------------------------------------------------------------------------
[root@mail ~]# smartctl --smart=on /dev/hdg
smartctl version 5.33 [i386-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
---------------------------------------------------------------------------------
[root@mail proc]# smartctl --smart=on /dev/hde
smartctl version 5.33 [i386-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
--------------------------------------------------------------------------------
[root@mail proc]# smartctl --smart=on /dev/md0
smartctl version 5.33 [i386-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Smartctl: please specify device type with the -d option.

Use smartctl -h to get a usage summary

From what I think is the issue /dev/md0 is some type of RAID and /dev/hde a and /dev/hdg are now no longer mountable or died? They clearly show up in the /proc/partitions and I cannot run any tools on them.

Last edited by keysorsoze; 12-03-2006 at 01:47 PM.
 
Old 12-03-2006, 08:04 PM   #14
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 405

Rep: Reputation: 42
The reason you can't mount _anything_ except /dev/hda and /dev/hdf is because those are the only drives you have! See my previous post and follow what I said. You gleaned no new or useful information from that exercise with smartctl. /dev/md0 is a virtual drive, not a physical device. Who cares whether it has a valid partition table or not. Even if you were using raid, it doesn't have to have a valid partition table. It is merely a virtual mapping for *real* devices and typically more than one device at a time is mapped to md0, md1, etc. Your original setup had one drive mapped to md0, which really doesn't make any sense because it's just more overhead to maintain raid if you're not actually going to use it to map more than one physical drive to a raid drive.

Please follow my previous post (that is if the assumptions I made were correct and if they're not, the concept is the same). It is a *very* slim possibility that you have bad hard disk here. All of those errors you had a boot time are easily solvable. Just follow what I said and post back if you're having trouble with understanding any of it.
 
Old 12-03-2006, 08:31 PM   #15
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 405

Rep: Reputation: 42
Quote:
Originally Posted by nhydra
Ohh i think this disk probably dies.
So, i suggest running this: http://smartmontools.sourceforge.net/

This is a hard drive SMART analyzing tool. If you use Fedora just install it with yum
yum install smartmontools

Then you just run it to check the SMART status:
smartctl -a /dev/your-device

Then run short and long selftests to examine the health of the device.
smartctl -t short /dev/your-device

Wait 5 mins and then run the long test.
smartctl -t long /dev/your-device

After long test running you have to wait about 30-60 mins for analyzing...

Then you will finaly know that your hard drive is dead or not.

Regards.
I want to know what evidence, from these posts, leads you to believe there is a bad hard disk drive involved here? I see no basis for this assumption. I see nothing but evidence of a bad configuration. The configuration in fstab is hosed up and pointing to a non-existent device. I see the partition type is messed up in the partitioning tables for one of the drives. I see raid being autodected at boot time because the partition table type is wrong for /dev/hdf1 which keysorsoze seems to imply he has no intention of using raid. I see that /dev/md0 needs to be removed from fstab and same with any reference to hdg which doesn't exist. Consequently the system is trying to do all this stuff at boot time based on *bad* information it's reading in the configuration files. I don't see there is *any* evidence for a bad disk.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Does this mean a physically failing hard drive? whysyn Linux - Hardware 9 07-20-2006 07:27 PM
my hard drive or my optical drive is failing fatblueduck Linux - Hardware 7 01-28-2006 08:30 PM
hard drive failing, how can I create an image of my drive? oily_rags Suse/Novell 6 07-07-2005 02:19 PM
Is my hard drive failing? HGeneAnthony General 1 11-23-2004 01:37 AM
Failing hard drive--need to copy Phathead Linux - Hardware 2 03-10-2004 12:59 PM


All times are GMT -5. The time now is 09:35 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration