Results 1 to 2 of 2

Thread: Deleted Kali Linux partition - can't boot into windows 10 now (grub)

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    2016-Sep
    Posts
    1

    Deleted Kali Linux partition - can't boot into windows 10 now (grub)

    I installed Kali Linux on D:\ drive (i think? most likely). I wanted to remove it. To remove it I just deleted the disk / partition using Disk Utility on windows (stupid, I know). Next restart I get "error: no such device eb54...790e. Entering rescue mode

    grub rescue>

    I tried the one where you set boot=(hd0, msdos6) then set prefix=(hd0, msdos6)/boot/grub then insmod normal but at insmod normal I get error no such partition. I then tried to do ls (hd0, msdos6)/boot but that alos didn't work "file system not found" or something like that.

    I'm thinking of booting from usb and installing kali linux again. would that fix it? Would prefer a quicker fix though.

    Cheers

  2. #2
    See http://superuser.com/questions/94921...r-from-windows which gives a really good answer on how to repair your MBR (Master Boot Record) that was destroyed when you removed the source-partition containing the remainder of Grub's components that allow it to boot correctly.

    Recommendation: First, document the answers from the article I've linked to, into a local file that you can pull up while you work on the system needing repair (or, alternatively, print it out if you only have the 1 machine). Second, download the 'Gparted-Live' ISO, and follow the instructions available online (Google search it) to create a bootable USB drive from the Gparted ISO. Third, after applying the MBR repair, boot up Gparted-Live and use it to make any resizing corrections to your partitions (if you would like to reclaim the space that was lost to installing Kali).

    Finally... don't feel bad about this... just about everyone that's new-to-Linux makes this mistake at least once. Back when I started working with Linux back in 1997, Gparted didn't exist yet (or at least, I wasn't aware of it yet), so back then a mistake like this would have resulted in a complete loss of all data on the drive because it would have required a low-level-format to recover the drive to a usable state. Nowadays though, it's trivial to recover from this. Anyway, best of luck.

Similar Threads

  1. Replies: 1
    Last Post: 2022-08-24, 19:53

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •