Re: Signs of hard drive failure?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Today Bob Weber wrote, in part:
> I would first check if the raid was working. Use "cat
> /proc/mdstat". You will see something like this for each raid drive
> configured:
>
> md0 : active raid1 sdb1[3] sda1[2] 28754230 blocks super 1.2 [2/2]
> [UU]
>
> Make sure that both U's are there. If not be careful because the
> raid is operating on one disk. Before you reboot copy all the
> important data from that raid drive.
I had tried that, and both U's were there.
> Next use smartctl to do a long self test. Use "smartctl -t long
> /dev/sda". You can still use the machine but it will slow the
> test down. The tests take a long time and smartctl will estimate
> how long. Then do the second drive "smartctl -t long /dev/sdb".
I will do these tonight while I watch the results of the Canadian
election.
> If these pass then you could try booting with a system rescue CD.
> First check what drive names it has used by running "ls /dev/md*".
> You will see something like /dev/md0 or /dev/md123. Now check the
> filesystem on the raid drive with "fsck -f /dev/mdx" replacing x
> with what you found in the previous command.
To be kept in reserve; I have used Knoppix before.
> That should keep you bust for a while.
Indeed. The other three responders also found problems with my
scripts; so I will have to look into those as well.
> Let the list know what you found.
Of course.
Regards, Ken
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQR9YFyM2lJAhDprmoOU2UnM6QmZNwUCXa44BAAKCRCU2UnM6QmZ
N/OGAJ9n/eEBs3TjdrBz7x5VRr4qJ4jilgCeKnzk4FHtXNkFdM/x2tajyXOh3WI=
=Q0kb
-----END PGP SIGNATURE-----
Reply to: