0

This is almost definitely a duplicate: Link

I have grub with dual boot os: windows 7 and ubuntu 14.01. I had accidentally dropped a small object on my laptop and it hit with a thud, but no major damage, and a few seconds later closed an application while using windows 7, then windows explorer crashed, with my desktop bg only showing for a while, so I restarted. Upon restart, I got the error:attempt to read or write outside of disk 'hd0' error.

I found the above question and did the following:

grub rescue> ls
(hd0) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)

On trying to ls inside all, I got

(hd0,msdos*): Filesystem is unknown.

Except for (hd0,msdos6) which gave Filesystem ext2. I assumed that this is where the linux partition is.

Following the answer in the above link, I did:

grub rescue > ls (hd0,msdos6)/
grub rescue > set root=(hd0,msdos6)
grub rescue > set prefix=(hd0,msdos6)/boot/grub
grub rescue > insmod normal

After this, it again displayed the error message instead of bringing up the boot menu.

grub rescue > normal

This was an unknown command as the boot menu failed to open. Thus, back to square one.

However, I have not yet tried using Boot-Repair, and I don't know if the commands of changing root and prefix will have made the issue worse.

Looking at the other answers, it seems to me that the only solution to this is creating another tiny partition in the beginning which is ext4, and that that should fix it.

However, I don't have my pen drive which I used for installing Ubuntu, and reinstalling them and using Rufus etc. will take time. The same applies for boot-repair. I can reinstall them in a different pen drive, but have a horrendous internet speed, so they will take time.

What solution should I use? Could the dropping of a small object have caused this? Is Windows broken because I didn't find any partitions with ntfs file systems?

  • I wouldn't do any repair, or anything that wrote to your disk/hdd until you've read the SMART data for your disk to see if their are problems (with the drive). The SMART (self monitoring analysis & reporting tech) is data stored in the circuits of the drive itself and won't impact the disk surface as much as actual reads, or esp. writes would. If the disk is OK, then you can look at data recovery, or just fixing it. I'd read/check your drive smart data from a live usb/dvd.... – guiverc Dec 5 '17 at 13:01
  • @guiverc I assume I do that using a boot loader of ubuntu? – Aryan poonacha Dec 5 '17 at 13:09
  • I generally use a knoppix (usb) thumb drive I carry with me; but use Ubuntu install media heaps too (ie. any live media). i was suggesting booting from a non-hdd installed OS as if was my system I'd check the hardware to check nothing is detected as wrong because of the dropped object, crash & unsual boot behavior. I avoid using the suspect-disk until I've worked out its state (reading smart data doesn't use actual heads/platters.. if its dying each use brings death closer so I save its remaining use for getting data off.... note: I regularly repair, so I see what i regularly deal with) – guiverc Dec 5 '17 at 21:45

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.