GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
did the biannual windows reinstall and lost bootmanager GRUB of course. Upon doing grub-install /dev/sdb1 (wrong drive, it seems :S) I broke my NTFS drive (I have several drives, one for files one for os, and i broke the file one). Now it is unreadable both by LINUX and Windows.
Anyone have any ideas? I've tried using the supergrub tool to restore, but I don't really know how it works. Is there any way to undo this damage? I realize formatting it is an option and then recovering all files, but I don't trust that it will work.
This overwrites the boot-sector record of the partition. If this was NTFS - erk !!!
Try fixboot from recovery console from the Windoze CD. Might work, might not.
Grub can overwrite several sectors, and fixboot doesn't always repair them all.
Else you're probably up for a re-install - of at least the system; DLLs, exe's ... that sort of thing.
how does messing with that make the rest of the disk un-readable ?
if anything it should be able to be used for storage but not booting.
what am i missing ?
The MBR is the first 512 bytes of the drive--AKA sector #0
The first 512 bytes of a partition is sometime called the boot sector.
Regardless of what boot code is in the MBR, windows also has boot code in the boot sector of its partition. So putting GRUB there stops Windows from booting.
Typically, the first partition does not start until sector 63. Sectors 1-62 can contain boot code but are often just empty.
I don't know much about grub. But I can tell you something that might help you get your files back.
Look up "photorec". This is a useful tool indeed. You may be able to recover your data.
The MBR is the first 512 bytes of the drive--AKA sector #0
The first 512 bytes of a partition is sometime called the boot sector.
Regardless of what boot code is in the MBR, windows also has boot code in the boot sector of its partition. So putting GRUB there stops Windows from booting.
Typically, the first partition does not start until sector 63. Sectors 1-62 can contain boot code but are often just empty.
thanks for the explanation, but i am still lost on how hacking the mbr/ boot sectors can brick a hard drive. i know he can no longer boot into windows but how does that make the partitions un-mountable in linux ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.