| 1 |
> Ok, maybe stupid questions time. |
| 2 |
> |
| 3 |
> /dev/hdj1 does exist, right? |
| 4 |
|
| 5 |
yes |
| 6 |
|
| 7 |
> Is this the same drive that was once part of the array? |
| 8 |
|
| 9 |
It is existing. But possible it may have legitamatly failed. Here is a log generated today when I |
| 10 |
tried to add it back into the array. |
| 11 |
Sep 2 09:11:02 [kernel] end_request: I/O error, dev hdj, sector 586099263 |
| 12 |
Sep 2 09:11:02 [kernel] Buffer I/O error on device hdj1, logical block 146524800 |
| 13 |
... |
| 14 |
Sep 2 09:11:02 [kernel] lost page write due to I/O error on hdj1 |
| 15 |
Sep 2 09:11:02 [kernel] end_request: I/O error, dev hdj, sector 586099263 |
| 16 |
Sep 2 09:11:02 [kernel] md: disabled device hdj1, could not read superblock. |
| 17 |
Sep 2 09:11:02 [kernel] md: hdj1 has invalid sb, not importing! |
| 18 |
Sep 2 09:11:02 [kernel] md: md_import_device returned -22 |
| 19 |
|
| 20 |
|
| 21 |
> If the same drive, does it work if you do "mdadm --zero-superblock |
| 22 |
> /dev/hdj1" first? |
| 23 |
|
| 24 |
~ # mdadm --zero-superblock /dev/hdj1 |
| 25 |
mdadm: Unrecognised md component device - /dev/hdj1 |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
> What does "mdadm --examine /dev/hdj1" report? How about for /dev/hdg1? |
| 30 |
|
| 31 |
|
| 32 |
~ # mdadm --zero-superblock /dev/hdj1 |
| 33 |
mdadm: Unrecognised md component device - /dev/hdj1 |
| 34 |
|
| 35 |
~ # mdadm --examine /dev/hdj1 |
| 36 |
mdadm: No md superblock detected on /dev/hdj1. |
| 37 |
db_server01 ~ # mdadm --examine /dev/hdg1 |
| 38 |
/dev/hdg1: |
| 39 |
Magic : a92b4efc |
| 40 |
Version : 00.90.03 |
| 41 |
UUID : d77079f9:c084dedf:ba141e09:96726a79 |
| 42 |
Creation Time : Tue May 30 19:48:40 2006 |
| 43 |
Raid Level : raid1 |
| 44 |
Device Size : 293049600 (279.47 GiB 300.08 GB) |
| 45 |
Array Size : 293049600 (279.47 GiB 300.08 GB) |
| 46 |
Raid Devices : 2 |
| 47 |
Total Devices : 1 |
| 48 |
Preferred Minor : 4 |
| 49 |
|
| 50 |
Update Time : Fri Sep 1 20:52:33 2006 |
| 51 |
State : clean |
| 52 |
Active Devices : 1 |
| 53 |
Working Devices : 1 |
| 54 |
Failed Devices : 0 |
| 55 |
Spare Devices : 0 |
| 56 |
Checksum : 2cbf93d9 - correct |
| 57 |
Events : 0.1402072 |
| 58 |
|
| 59 |
|
| 60 |
Number Major Minor RaidDevice State |
| 61 |
this 1 34 1 1 active sync /dev/hdg1 |
| 62 |
|
| 63 |
0 0 0 0 0 removed |
| 64 |
1 1 34 1 1 active sync /dev/hdg1 |
| 65 |
|
| 66 |
Does all of this suggest a complete and total drive failure? :-) I orginally built this md4 array |
| 67 |
as a Raid 5 from three of the cheepest drives that I could find (Maxtors). Then a couple of |
| 68 |
months later, one drive died. So I converted the remaining to into a raid 1. Now this one seems |
| 69 |
to have died. I guess I am learning my leason about buying cheep hardware. Fortunately I have a |
| 70 |
back-up of everything on this array. |
| 71 |
|
| 72 |
|
| 73 |
Regards, |
| 74 |
|
| 75 |
Richard Broersma Jr. |
| 76 |
-- |
| 77 |
gentoo-user@g.o mailing list |
Archives