> This is a problem. What do you get for > > cat /sys/block/sdc/device/timeout [root@lamachine ~]# cat /sys/block/sdc/device/timeout 30 [root@lamachine ~]# cat /sys/block/sdd/device/timeout 30 [root@lamachine ~]# cat /sys/block/sde/device/timeout 30 [root@lamachine ~]# > Anyone specifically familiar with WDC Greens, and if the lack of SCT > ERC can be worked around in the usual way by increasing the SCSI > command timer value? Or is there also something else? I vaguely recall > something about drive spin down that can also cause issues, does that > need mitigation? If no one chimes in, this information is in the > archives, just search for 'WDC green' and you'll get an shittonne of > results. In another thread I found Phil Turmel recommending to change the timeout value like this: for x in /sys/block/*/device/timeout ; do echo 180 > $x ; done Is that what you guys are talking about when mentioning the SCT/ERC issues? > OK so the next thing I want to see is why you're getting these > messages from parted when you check sdc and sde for partition maps. At > the time you do this, what do you see in kernel messages? Maybe best > to just stick the entire dmesg for the current boot up somewhere like > fpaste.org or equivalent. https://paste.fedoraproject.org/427719/37952531/ -- 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
