Hello,
I replaced the failed disk. The configuration is /dev/hde, /dev/hdf
(replaced), on IDE channel 0, /dev/hdg, /dev/hdh on IDE channel 1, on a
single PCI controller card. The issue here is that hde in now also not
accessible after the failure of hdf. I cannot see the jumper configs as
the server is at home, and I am at work. The general thinking was that
the hde superblock got hosed with the loss of hdf.
My initial post only did discuss the disk ordering and device names. As
I had replaced the disk which had failed (in a previously fully
functioning array), with a new disk with exactly the same configuration
(jumpers, cable locations, etc), and each of the disks could be
accessed, my thinking was that there would not be a hardware problem to
sort through. Is this logic flawed?
Thanks again,
Nate
Maurice Hilarius wrote:
Nate Byrnes wrote:
Hi All,
I'm not sure that is entirely the case. From a hardware
perspective, I can access all the disks from the OS, via fdisk and dd.
It is really just mdadm that is failing. Would I still need to work
the jumper issue?
Thanks,
Nate
IF the disks are as we suspect (master and slave relationships) and IF
you now have either a failed or a removed drive, then you MUST correct
the jumpering.
Sure, you can often see a disk that is misconfigured.
It is almost certain, however, that when you write to it you will simply
cause corruption on it.
Of course, so far this is all speculation, as you have not actually said
what the disks, controller interfaces, and jumpering and so forth are at.
I was merely speculating, based on what you have said.
No amount of software magic will "cure" a hardware problem..
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
