On 19/12/18 08:13, Alexis BRENON wrote: >> OMG - I was just looking for your version of mdadm, and I noticed - >> > Seagate Baracudas! Can you let us know (a) what version of mdadm, and >> > (b) have you fixed the timeout problem! If you haven't done (b) then >> > that's probably your problem! >> > > I do not have access to my computer right now but if I remember well, > my system is a Debian stretch and I upgraded it recently. So mdadm > should be in version 3.4-4. I will confirm that as soon as possible. Okay. So do as the wiki says and upgrade. 3.4 has a bunch of known bugs, although they're probably not responsible this. > > I "fixed" the timeout problem yesterday, while reading the wiki saying > "If you didn't fix timeout, do it right now!" ^^ My 3 SG Baracudas > reported a disabled SCT Error Recovery, and my WesternDigital reports > an unsupported command. > I used the script provided in the wiki to set the timeout to 7s on the > Baracudas and to 180ms for my WD but the latter is not preserve > accross reboot as reported in smartctl sum-up (see below). > Okay, the Barracudas don't support ERC - I think you can't enable it, so setting it 7s probably did nothing. Set the kernel timeout to 180 for the Barracudas also. Cheers, Wol
