Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Heads and Sectors Restored Error


  • Please log in to reply
3 replies to this topic

#1 kzVlad

kzVlad

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 06 February 2016 - 12:23 AM

Hi everyone,

I just installed Ubuntu Mate dual boot with Windows 10. I only have 1 drive (an SSD) and here is my partition layout:

Type: MBR

Primary Partition 1: NTFS (Bootable) [created by windows]

Primary Partition 2: NTFS [Windows 10]

Primary Partition 3: Ext4 [Contains GRUB bootloader]

Primary Partition 4: SWAP

 

I use Windows bootloader as default, and it then chainloads GRUB which is located on the Ext4 partition.

Everything seems to be working OK, but I noticed this screen [see attached pic] before GRUB loads and thought it was odd.

Does anyone know why this happens? Is this normal?

 

Not sure how to attach pic, so here is the text from the screen:

"!! number of heads for drive 80 restored from 255 to 222."

"!! sectors-per-track for drive 80 restored from 63 to 30."

"(hd0,2)" .....bla bla...


Edited by kzVlad, 06 February 2016 - 12:23 AM.


BC AdBot (Login to Remove)

 


#2 Platypus

Platypus

  • Global Moderator
  • 15,768 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:07:52 AM

Posted 06 February 2016 - 02:28 AM

If everything operates correctly, I suspect it isn't a problem, but others who have more to do with Linux than I do may know more.

 

The issue is spoken about on forums with people dual booting, but with few clear responses that I can find. There's even a comment here that it is normal:

 

https://translate.google.com.au/translate?hl=en&sl=zh-CN&u=http://bbs.wuyou.net/forum.php%3Fmod%3Dviewthread%26tid%3D273911&prev=search

 

It seems to me that it's related to CHS translation, which in modern systems should only be required for drive access for loading boot code. So as long as the boot code is loaded correctly (i.e. each OS starts properly) it is probably simply an operational quirk. I think it is likely to be due to the way the legacy BIOS on your particular mainboard implements CHS translation for the access routines used by the bootloader, and this is handled differently by the Windows loader and GRUB. As long as each loader can locate the boot code and run it, it's OK.


Edited by Platypus, 06 February 2016 - 02:30 AM.

Top 5 things that never get done:

1.

#3 kzVlad

kzVlad
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 15 February 2016 - 04:40 PM

Thanks Platypus.

 

I've reinstalled with a different distribution (debian Jessie) and loaded GRUB into the MBR.

Now everything seems normal. 

I'm thinking the problem might have been because GRUB was loaded on my 3rd Partition.



#4 Platypus

Platypus

  • Global Moderator
  • 15,768 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:07:52 AM

Posted 16 February 2016 - 06:19 PM

That seems like a good result. Thanks for getting back to us.


Top 5 things that never get done:

1.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users