Skip to contentSkip to conversation

strangre drive behaviour.

DISCUSSION Max Waterman 3 participants 4 messages Mar 6, 2005 – Mar 7, 2005 MD RAID

lore
Share & tools
lore
#0 lore raw

I've been reconfiguring my raid drives.

I used to have it this way...

4 Parallel IDE i/f's
each i/f's master was a WD800 in a RAID5
each i/f's slave was a WD2000 in a RAID5

I am removing the WD800 array and moving the WD2000 array to masters; so there are no slaves.

However, in the process, one of my WD2000's seems to be having problems.

It seems to work as a slave device, but not as a master. I have tried many combinations of interfaces/cables/power/etc.

I can even put it on an i/f on it's own as a slave device, and it seems to work (the device name changes to show that it is actually the 2nd device on the channel - ie when testing it on the motherboard, it shows up as hdd, not hdc).

I am not sure what to do.

Can I just make it a slave device? How will that effect performance?

Any ideas?

Max.

#1 lore raw

hi max

Quoted 2 lines · Max Waterman

It seems to work as a slave device, but not as a master. I have tried many combinations of interfaces/cables/power/etc.

just to check basic things: what are your drives' jumper settings? if all your drives are set to "cable select", and the "strange" drive explicitely to "slave", then this could explain the behavior. see [1] for jumper settings on the WD series.

Quoted 1 line

Can I just make it a slave device? How will that effect performance?

AFAIK there should be only a problem if you have two drives on the same bus - they block each other. so it should be fine if you just leave it that way...

though somebody might have a better explanation for the phenomenon...

regards
nicola

[1]:
http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=84&p_created=1005005461

#2 lore raw

Re: strange drive behaviour.

Quoted 11 lines · Nicola Fankhauser

hi max

Quoted 1 line · Max Waterman

It seems to work as a slave device, but not as a master. I have tried many combinations of interfaces/cables/power/etc.

just to check basic things: what are your drives' jumper settings? if all your drives are set to "cable select", and the "strange" drive explicitely to "slave", then this could explain the behavior. see [1] for jumper settings on the WD series.

Unfortunately, all the WD drives are identical and so it's 'impossible' to get (just one) wrong; and they're clearly labeled with the jumper positions. However, the page at the URL below does show another position which isn't on marked on the drive - [4-6] - which is another master position. Unfortunately, it didn't make any difference.

The page at the URL below does explain which of the plugs on an EIDE cable is master (the black plug on the end) and which is slave (the grey plug in the 'middle'), so I was able to try setting it to 'cable select' - [1-2] - and try as master and then as slave. Unfortunately, it shows the same behaviour - system locks on the initial motherboard flash screen (with the fault LED lit) when it is master, and seems to work 'OK' when set as slave (even though there is no master device[?]).

Quoted 8 lines
Quoted 3 lines

Can I just make it a slave device? How will that effect performance?

AFAIK there should be only a problem if you have two drives on the same bus - they block each other. so it should be fine if you just leave it that way...

Hrm. I would be worried about it failing, so I am looking to avoid it in that situation in the long term. Since the drives were RAID5, all my data is still there (right?), but it'll run degraded (or something) when it powers up.

Fortunately, I have 4 other WD2000 drives, but they're SATA. I don't think that makes (much) difference; so, I guess I should be able to use one of those fairly easily.

What would be the best procedure?

I'm guessing one of these :

1) put the dodgy drive as a slave (with a CDROM as master), and one of the SATA drives off the motherboard; use some disk duplicator utility to duplicate the contents of the dodgy drive to the SATA drive. Then edit the mdadm.conf file to use the SATA drive instead of the dodgy one. RMA the dodgy drive.

2) add the SATA drive as a 'spare' and let the md stuff sort itself out.

Any recommendations?

Max.

Quoted 13 lines

though somebody might have a better explanation for the phenomenon...

regards
nicola

[1]:
http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=84&p_created=1005005461

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
In reply to Max Waterman
Quoted 1 line · Max Waterman

Can I just make it a slave device? How will that effect performance?

AFAIR (CMIIW):
- The standards does not allow a slave without a master.
- The master has a role to play in that it does coordination of some sort (commands perhaps?) between the slave drive and the controller.

But on the other hand, I've seen ATAPI cdrom drives working in "slave only" configurations for years. Hm.

It shouldn't cause performance degradation, but it's a kinky setup which you should probably trust a bit less than a master-only setup.

If it's not the CABLE SELECT thing, it could be that the firmware on the drive acting up is different from f/w on the other drives. Check versions?