Not working after reboot
#1
I was running hashcat using command
"hashcat -m 2500 /root/file.hccapx /root/rockyou.txt"

and it was running properly when suddenly there was a powercut and now after the power came back i tried running the same

but now it gives me an error "Cannot read /root/.hashcat/sessions/hashcat.pid". i tried changing the hccapx file's name but still the same error. Kindly guide me to the solution.
Thanks
Reply
#2
you shouldn't run hashcat (or almost any software) as root. Sounds like your file system got damaged, time for a fsck
Reply
#3
(06-10-2018, 11:49 AM)undeath Wrote: you shouldn't run hashcat (or almost any software) as root. Sounds like your file system got damaged, time for a fsck

I am new to linux and so i didn't know the use of fsck command. so i checked on internet about its use and it says there to use it on unmounted partition. I am using The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) linux in dual boot with windows 10, can you tell me how to perform the steps to this command in order to not damage my data while doing so. I used the command "sudo fdisk -l"
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 1944CA1D-BEC1-4BB5-BE09-9B95435D98AE

Device          Start        End   Sectors   Size Type
/dev/sda1        2048     923647    921600   450M Windows recovery environment
/dev/sda2      923648    1126399    202752    99M EFI System
/dev/sda3     1126400    1159167     32768    16M Microsoft reserved
/dev/sda4     1159168  817444121 816284954 389.2G Microsoft basic data
/dev/sda5   817444864  819197951   1753088   856M Windows recovery environment
/dev/sda6   819200000 1372157951 552957952 263.7G Microsoft basic data
/dev/sda7  1372160000 1797947391 425787392   203G Microsoft basic data
/dev/sda8  1797947392 1920043007 122095616  58.2G Linux filesystem
/dev/sda9  1920043008 1953523711  33480704    16G Linux swap

and it shows me this list, can you please list the commands to input now to unmount the partition that is damaged and use fsck command on that.
Thanks
Reply
#4
Your file system is not the problem. Just delete the hashcat.pid file and it will work again.
Reply
#5
(06-11-2018, 07:14 AM)GOD Wrote: Your file system is not the problem. Just delete the hashcat.pid file and it will work again.

Yayy, this solved my problem. Thanks mate. Kudos to you. Smile (I was in the grub menu making my system read only to use fsck when I received your answer). You saved me from a lot of hassle.
Reply