On 15/10/2019 23:44, Curtis Vaughan wrote: >> >>>> >>>> Device info: >>>> ST1000DM003-9YN162, S/N:Z1D17B24, WWN:5-000c50-050e6c90f, FW:CC4C, >>>> 1.00 TB >>> Urkk >>> >>> Seagate Barracudas are NOT recommended. Can you do a "smartctl -x" and >>> see if SCT/ERC is supported? I haven't got a datasheet for the 1GB >>> version, but I've got the 3GB version and it doesn't support it. That >>> means you WILL suffer from the timeout problem ... >>> >>> (Not that that's your problem here, but there's no point tempting fate. >>> I know Seagate say "suitable for desktop raid", but the experts on this >>> list wouldn't agree ...) >> >> SCT supported, but SCT/ERC not. GREAT! Hm and the replacement is also >> a Seagate. > > My new drives are Seagate Ironwolf, which are supposedly fine. I still > haven't managed to boot the system - it's been sat for ages with an > assembly problem I haven't solved - I hope it's something as simple as > needs a bios update, but I can't do that ... >> However another of my servers also has Seagates like the one I'm >> buying and it >> that ERC is supported. So maybe I should buy one more such drive and >> also >> replace sdb? > > Depends. If you run the script on the timeout problem page it "fixes" > the problem. The only downside is that if you have a disk error, > you've just set your timeout to three minutes, so the system could > freeze for near enough that time. Not nice for the user, but at least > the system will be okay. A proper ERC drive can be set to return with > an error very quickly - the default is 7 secs. >> >> Here are the results of the command on the problem drive: >> >> smartctl -x /dev/sda | grep SCT >> SCT capabilities: (0x3085) SCT Status supported. >> 0xe0 GPL,SL R/W 1 SCT Command/Status >> 0xe1 GPL,SL R/W 1 SCT Data Transfer >> SCT Status Version: 3 >> SCT Version (vendor specific): 522 (0x020a) >> SCT Support Level: 1 >> SCT Data Table command not supported >> SCT Error Recovery Control command not supported >> > Typical Barracuda :-( > Switched out bad hard drive and added a brand new one. Now I thought I should just run: sudo mdadm --add /dev/md1 /dev/sda2 sudo mdadm --add /dev/md1 /dev/sda1 and the raid would be back up and running (RAID1, btw). But I think it won't add sda1 or sda2 cause they don't exist. So it seems I need to first partition the drive? But how do I partition EXACTLY like the other? Or is there another way?
