On Saturday, 15 June 2019 15:03:01 BST Ralph Corderoy wrote: > > I came across a bug posted about three years ago about smartctl > > throwing up false read errors > > Do you mean badblocks?
This was the bug report that I found: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1612220[1] As I said, it's old now > It depends how scattered through the disk they are. But really, push > the problem down to the drive. Allow it to reallocate those sectors it > knows are duff but writing to them; easy if the drive's contents are > worthless by employing badblocks' destructive write test. They were fairly close to the beginning. After logging these badblocks reported nothing until I gae up about 6 hours later. > > I presume it would try to mirror the whole thing, since that is what > > is would expect to do. > > But this is a ‘new’ drive being added to the existing one to make an > array so it will be the destination of the mirroring and have lots > written to it? It's only the reading of it, e.g. a regular ‘scrub’ that > will show problems. The 'old' drive will have nothing on it, so we could put this one in first and then add the other. Having said that, I'd like to start with a known good disc if possible. We aren't storing the combinations of the vaults in the Bank of England, but it would still be a pain to lose historical data. -- Terry Coles -------- [1] https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1612220 -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
