CaptainSpalding Posted January 20, 2012 Share Posted January 20, 2012 Hi, A while ago my server did a scheduled parity check and I noticed one drive got 450 read errors and the next time I refreshed the parity check had stopped and the dot on the drive was red. So I thought that was an old drive and bought a replacement, installed it and started data-rebuild, but now I'm getting errors on other drives. Should I cancel the data-rebuild and do something before it finishes? I'm on 4.7. Link to comment
lionelhutz Posted January 20, 2012 Share Posted January 20, 2012 Anything common between those 4 drives, such as the same backplane or the same SATA card?? I'd be tempted to let it finish though I have doubts the rebuilt data will be much use. Peter Link to comment
CaptainSpalding Posted January 20, 2012 Author Share Posted January 20, 2012 They are not all connected to the same controller. Now I cannot even get there through telnet or http? Could or should I boot it and check the wires? Link to comment
CaptainSpalding Posted January 20, 2012 Author Share Posted January 20, 2012 I booted and noticed that one of the sas cables was poorly connected, so now trying the parity check again. Link to comment
lionelhutz Posted January 20, 2012 Share Posted January 20, 2012 I hope you mean the disk rebuild started again. Peter Link to comment
CaptainSpalding Posted January 21, 2012 Author Share Posted January 21, 2012 Yes, and this time it looks fine! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.