OP, tks but I did not get chance. I ended up with a grub error 17, so i hooked into another good hd and saw your post. In the past we tried and tried, but I think it would just be easier to reload the / and not the home and hope that gets it going. But the issue doing all this my be in the /home also. But I had a good teacher like you work with me on this last year. C ya tomorrow. Farmers Bed Time
Ps. KTorrent on this hd works just fine too. So it was not a K Torrent bug.
The grub error 17 pretty much confirms the corruption on that partition. Before doing a reinstall, try the fsck command previously posted. The partition needs to be unmounted for fsck to work, so that's not a problem. Once the fsck is done, grub should be able to again mount the partition, unless the hard drive itself is in the process of dying.
There are many ways to get a filesystem corruption, but the most common is an improper shutdown of the running system, with some files still being written to. Almost every time the filesystem can be made whole by running the fsck
command with the -f
argument. This forces an inode by inode check of the entire partition space and asks for permission to do those steps it normally won't do without that permission. For each question asked, just press the Enter
key to accept the default choice. I've done this many times, and have never seen the default choice be wrong.