since hde1 is the active drive, it extends logically that hdg is the failed drive. As for whether it's actually failed -- I ran into this once, where the drives got themselves out of sync. Have you tried running
mdadm /dev/md0 -a /dev/hdg1 And if that fails, mdadm -C /dev/md0 If you're certain one of the drives has failed, it certainly looks like hdg is the one that needs replacing. On Tue, Mar 10, 2009 at 6:26 AM, Nelson Serafica <[email protected]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm new to this raid via software. I just need to do fsck manually to > /dev/md0 because it encountered an I/O error. After doing fsck, I need to > discover which hard drive cause the error. Since the affected partition is > raid1 (/dev/md0), I need to know which one of them is the I need to replace > to. I tried to check via mdadm. See below: > > [r...@core home]# mdadm --detail /dev/md0 > /dev/md0: > Version : 00.90.01 > Creation Time : Sun Jul 17 21:00:18 2005 > Raid Level : raid1 > Array Size : 195358336 (186.31 GiB 200.05 GB) > Device Size : 195358336 (186.31 GiB 200.05 GB) > Raid Devices : 2 > Total Devices : 1 > Preferred Minor : 0 > Persistence : Superblock is persistent > > Update Time : Tue Mar 10 18:19:00 2009 > State : dirty, no-errors > Active Devices : 1 > Working Devices : 1 > Failed Devices : 0 > Spare Devices : 0 > > > Number Major Minor RaidDevice State > 0 33 1 0 active sync /dev/hde1 > 1 0 0 -1 removed > UUID : f613b3d3:fd0e6a89:623827b0:40f4ed2e > Events : 0.84876630 > > > When I do fdisk -l, here is the result: > > [r...@core home]# fdisk -l > > Disk /dev/hde: 200.0 GB, 200049647616 bytes > 255 heads, 63 sectors/track, 24321 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/hde1 * 1 24321 195358401 fd Linux raid autodetect > > Disk /dev/hdg: 200.0 GB, 200049647616 bytes > 255 heads, 63 sectors/track, 24321 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/hdg1 * 1 24321 195358401 fd Linux raid autodetect > > Disk /dev/hda: 80.0 GB, 80026361856 bytes > 16 heads, 63 sectors/track, 155061 cylinders > Units = cylinders of 1008 * 512 = 516096 bytes > > Device Boot Start End Blocks Id System > /dev/hda1 * 1 20317 10239736+ 83 Linux > /dev/hda2 20318 40634 10239768 83 Linux > /dev/hda3 40635 44795 2097144 82 Linux swap > /dev/hda4 44796 155061 55574064 f W95 Ext'd (LBA) > /dev/hda5 44796 155061 55574032+ 83 Linux > > However, when I do mdadm /dev/md0 --fail /dev/hdg1, it says "mdadm: set > device faulty failed for /dev/hdg1: No such device". > > I believe I need to replace the sata disk but I do not know which one of > them. Also, I have a feeling that the software raid1 is now properly set > though I'm new to this software raid thing. > > Could anyone give an insight? My suspect is that /dev/hdg1 was not > replicating the /dev/hde1 but I cannot mount it since the system is Linux raid > autodetect. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkm2QEwACgkQUZICHAVQ58qlrgCfan+TbyTzjn92pdmpC6RBt8yf > OIUAoJGUi4YwuBwpxwVI3hHhMEjV1ofw > =IPHs > -----END PGP SIGNATURE----- > > > -- Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
