I'm trying to get to my admin password on my computer(Acer Nitro 5, running windows10) using a kali live usb. I already burned kali to the usb, and have booted to the kali interface, but then I can't find the disk to mount. sudo fdisk -l shows me three disks/partitions, but only one is Hidden HPFS/ntfs(the other2 are FAT and Linux) and that one just gives

Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.

How do I find the windows disk to mount? Going to /proc/partitions just shows

major  minor  #blocks  name
8        0     30274560 sda
8        1      3273568 sda1
8        2          736 sda2
8        3      6836224 sda3
7        0      2999252 loop0

There's nothing in /media either that doesn't lead back to the thumbdrive either, and fuser shows nothing for any drive

  • The error message suggests that something is already accessing the NTFS partition. Are you sure the disk is not already automatically mounted for you by the desktop environment? It might get mounted at somewhere under /media.
    – telcoM
    Oct 17, 2019 at 6:39
  • ls /media is empty. is there a command to show potentially hidden files?
    – Bim Detik
    Oct 17, 2019 at 6:48
  • Look into /proc/mounts to see a list of all the mounted filesystems and their mount point locations. Or run fuser /dev/<your NTFS partition device> to see if some process is accessing the partition.
    – telcoM
    Oct 17, 2019 at 7:12
  • a closer look at fdisk's output shows me that sda1 has the boot option checked, for some reason. It has an entry in /proc/mounts and nothing in fuser/dev/sda1
    – Bim Detik
    Oct 18, 2019 at 4:22
  • I thunk sda1 is the thumbdrive itself. when I went to /proc/mounts its entry was /run/live/medium and when I went there I found some files on the thumbdrrive before I burned it. could not completely wiping my drive have caused the issue?
    – Bim Detik
    Oct 18, 2019 at 4:55

1 Answer 1


Fixed! I went to the bios system and switched the SATA controller to Ahci. When I ran fdisk -l it showed me new drives like /dev/nvme0n1. I needed to switch it back to its original setting when moving from kali to windows 10, but besides that it looks ok so far

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .