Unable to boot to kernel higher then 3.13.0.29: attempt to read or write outside of disk 'hd0'

[Gilad Ravid]

Any kernel Ubuntu update installed after kernel 3.13.0.29 does not boot with the error message error: attempt to read or write outside of disk 'hd0'
when choosing the 3.13.0.29 kernel from the advanced option in GRUB menu there is no problem to boot.

Gilad
---
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gilad 2284 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=bc393e85-cca5-416c-9101-dab5139a92b2
InstallationDate: Installed on 2014-03-20 (150 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=c6f5efd3-0369-4d6e-a4d3-aa09265755f5 ro quiet splash
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-29-generic N/A
 linux-backports-modules-3.13.0-29-generic N/A
 linux-firmware 1.127.5
RfKill:

Tags: trusty
Uname: Linux 3.13.0-29-generic i686
UpgradeStatus: Upgraded to trusty on 2014-04-19 (120 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/05/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: G31M-S2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/05/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G31M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1357871/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1357871

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

apport information

[Gilad Ravid (gilad-m)]

pay attention that the problem is with booting to other kernel

[Andy Whitcroft (apw)]

The error message mentioned here is actually a grub2 by the looks of it, in particular the use of "hd0" to refer to a disk is not something the kernel refer to. Adding grub2 as an affected package.

This looks to be one of the checks in grub disk or "pc" partitioning handling:

  static grub_err_t
  grub_disk_adjust_range (grub_disk_t disk, grub_disk_addr_t *sector,
                          grub_off_t *offset, grub_size_t size)
  {
  [...]
        return grub_error (GRUB_ERR_OUT_OF_RANGE,
                           N_("attempt to read or write outside of partition"));

I have had trouble with very very large disks in the past affecting some installed kernels, this turned out to be due to them being placed very high on the drive. How big is the disk on which /boot is placed?

[Andy Whitcroft (apw)]

A quick poke about in your dmesg and it looks a lot like your root disk is on a drive over 2TB, which has more than 2^32 sectors on it.

[Andy Whitcroft (apw)]

To be clear, in our case the BIOS was not able to cope with doing initial loads from such high disk sector addresses, despite supporting capable interfaces.

[Andy Whitcroft (apw)]

It would be instructive to get the output of the command below:

    sudo filefrag -v /boot/vmlinuz-*

[Gilad Ravid (gilad-m)]

gilad@Gilad-Desktop:~$ sudo filefrag -v /boot/vmlinuz-*
[sudo] password for gilad:
Filesystem type is: ef53
File size of /boot/vmlinuz-3.11.0-19-generic is 5669328 (1385 blocks of 4096 bytes)
 ext: logical_offset: physical_offset: length: expected: flags:
   0: 0.. 1384: 32780288.. 32781672: 1385: eof
/boot/vmlinuz-3.11.0-19-generic: 1 extent found
File size of /boot/vmlinuz-3.13.0-24-generic is 5800496 (1417 blocks of 4096 bytes)
 ext: logical_offset: physical_offset: length: expected: flags:
   0: 0.. 1416: 48748544.. 48749960: 1417: eof
/boot/vmlinuz-3.13.0-24-generic: 1 extent found
File size of /boot/vmlinuz-3.13.0-27-generic is 5814832 (1420 blocks of 4096 bytes)
 ext: logical_offset: physical_offset: length: expected: flags:
   0: 0.. 1419: 347425792.. 347427211: 1420: eof
/boot/vmlinuz-3.13.0-27-generic: 1 extent found
File size of /boot/vmlinuz-3.13.0-29-generic is 5813456 (1420 blocks of 4096 bytes)
 ext: logical_offset: physical_offset: length: expected: flags:
   0: 0.. 1419: 49750016.. 49751435: 1420: eof
/boot/vmlinuz-3.13.0-29-generic: 1 extent found
File size of /boot/vmlinuz-3.13.0-30-generic is 5813328 (1420 blocks of 4096 bytes)
 ext: logical_offset: physical_offset: length: expected: flags:
   0: 0.. 1419: 54166528.. 54167947: 1420: eof
/boot/vmlinuz-3.13.0-30-generic: 1 extent found
File size of /boot/vmlinuz-3.13.0-32-generic is 5820336 (1421 blocks of 4096 bytes)
 ext: logical_offset: physical_offset: length: expected: flags:
   0: 0.. 1023: 367803392.. 367804415: 1024:
   1: 1024.. 1420: 367807488.. 367807884: 397: 367804416: eof
/boot/vmlinuz-3.13.0-32-generic: 2 extents found
File size of /boot/vmlinuz-3.13.0-33-generic is 5820336 (1421 blocks of 4096 bytes)
 ext: logical_offset: physical_offset: length: expected: flags:
   0: 0.. 1420: 371701760.. 371703180: 1421: eof
/boot/vmlinuz-3.13.0-33-generic: 1 extent found
File size of /boot/vmlinuz-3.13.0-34-generic is 5820592 (1422 blocks of 4096 bytes)
 ext: logical_offset: physical_offset: length: expected: flags:
   0: 0.. 1023: 32977920.. 32978943: 1024:
   1: 1024.. 1421: 32982016.. 32982413: 398: 32978944: eof
/boot/vmlinuz-3.13.0-34-generic: 2 extents found

[Gilad Ravid (gilad-m)]

if it is a case of large disk (the disk is 3T) how I can solve it?

[Phillip Susi (psusi)]

Can you run ls -l at the grub command line and post the output?

If you do have a broken bios, your manufacturer might have an update to fix it, otherwise the work around is to install with a /boot partition near the start of the disk.

[Gilad Ravid (gilad-m)]

I solved the problem by creating small boot partitaion in the begining of the disk

many mnay thnaks to all the ones that helped me

[Launchpad Janitor (janitor)]

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]