K Torrent?

[david1958]

Is anyone having trouble with KTorrent in the full Monty Version. Mine worked just fine until last night and it will not seed, and it will not upload or download and If I can get it open either on page1 or thru the internet link and it will just either not open or freeze  up once it does. Anyone got any suggestions, I have view a few past issues with KTorrent and I still find no results.
best regards,
david

[Old-Polack]

Is anyone having trouble with KTorrent in the full Monty Version. Mine worked just fine until last night and it will not seed, and it will not upload or download and If I can get it open either on page1 or thru the internet link and it will just either not open or freeze  up once it does. Anyone got any suggestions, I have view a few past issues with KTorrent and I still find no results.
best regards,
david

I use Ktorrent every day seeding our ISO images. From your description, it's not clear to me what the problem actually is, except that it isn't working. Have you tried running a filesystem check on your installed / partition? Possibly some corruption of files associated with the application is causing your problem. Running a fsck -f  /dev/sdxn command from a root terminal on the liveCD would at least eliminate that as a possibility, if it doesn't actually correct the problem.

Replace the x in the command given, with the actual drive letter designation and the n with the proper partition number.

[david1958]

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
David 

Ps. KTorrent on this hd works just fine too. So it was not a K Torrent bug.

[Old-Polack]

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
David 

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.

[david1958]

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.

OP, tks but it would not work. It found a inode error but for some reason it would not repair. As for shutdown issue, That might have been a issue, but I truthfully do not think that was the reason. I wish I could have posted results from the / terminal but I got the grub error after I tried fsck -f/dev/sda/6 so it could not reboot. I believe the hd is good though.

but mabe for me and other users a  "battery backup" for the tower would be worthwhile in case of a Power Failure and the adbrupt shutdown for that would give you an chance to make a clean shutdown.

tks again for the help OP. And glad to see you again
david1958

[Old-Polack]

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.

OP, tks but it would not work. It found a inode error but for some reason it would not repair. As for shutdown issue, That might have been a issue, but I truthfully do not think that was the reason. I wish I could have posted results from the / terminal but I got the grub error after I tried fsck -f/dev/sda/6 so it could not reboot. I believe the hd is good though.

but mabe for me and other users a  "battery backup" for the tower would be worthwhile in case of a Power Failure and the adbrupt shutdown for that would give you an chance to make a clean shutdown.

tks again for the help OP. And glad to see you again
david1958

I hate to keep pushing this, but it's very very rare that fsck -f can't repair a filesystem problem. Stating that "it did not work" without posting the actual error message, leaves us with nothing to work with. Seeing the actual error message may give those of us with more advanced knowledge a clue as to how to force the issue, and achieve a satisfactory repair. If the error involves a bad superblock, there are multiple backup superblocks that can be used instead. How many backup superblocks are present depends on the total size of the partition, but they are in known locations, and if even one is intact, that is enough to repair the whole filesystem and recreate all of the backup superblocks. Without the actual error message, that's just a likely guess, not anything that you can follow through on.

I just hate giving up on a filesystem repair before knowing that all possibilities for a repair have been truly exhausted.   

[Just17]

I got the grub error after I tried fsck -f/dev/sda/6 so it could not reboot

was that really the command you tried?

[david1958]

I got the grub error after I tried fsck -f/dev/sda/6 so it could not reboot

was that really the command you tried?

Just17 yes that was the command I used. The system started to run sluggish the day before. I downloaded a "family movie? thru KTorrent and I feel it was a corrupt torrent file that started all this. I am not a rocket scientist on linux since you have seen and helped me in the past.  On that command, I did have a inode error come up thru the terminal, then the system wigged out on me and rebooted. I wanted to post the term script in a quote to OP, but I lost everything. But I could have caused it all because of a bad shutdown. We had a power failure here on Wed when I was out so the system shut down. I was able to get it restarted but that is when I started to have problems and I have learned from the past to go backwards and remember what you had done just before the flaw in the system.
david

[DeBaas]

fsck -f/dev/sda/6

Its like speaking after drinking to much
Next try:

Code: [Select]

fsck -f /dev/sda6there should be a space after -f and no slash between sda and 6

[david1958]

Ok, i guess i did make a misake: yes i put

fsck -f/dev/sda/6

and it should have been

fsck -f /dev/sda6

  so we learn by our own mistakes or someone directs you that has more experiene in linux. And as for the post of

How did this corrupt the system

  If that is the way it was understood, I am sorry that script right or wrong did not do  the corruption on the system. As I stated I feel I got a bad torrent for a movie from a site and I feel that is what started causing the issues I had going. Sorry for the confusion on this to the experienced and to the layman users on the forum
david

[david1958]

I just want to say that I did get this issue on this hd that I thought was bad thru the

Code: [Select]

fsck -f /dev/sda6 and I did get my issue fixed. I had to use the live disk and go thru the term as explained but with he help of O.P., Debass and Just 17 they straightned me out on my confussion. But if i would have reread O.P's post again as I just looked back he told my bonehead to use the live disk to do this. Thank you guys for your ongoing support to help a ole farmer out.

david the bonehead!