Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

GRUB Boot Error [Solved]

Post Reply
User avatar
NevilsStation
Forum Regular
Forum Regular
Posts: 376
Joined: Sun Feb 26, 2017 3:09 pm

GRUB Boot Error [Solved]

#1

Post by NevilsStation » Tue Jul 23, 2019 7:21 pm

I was powering on my laptop (ThinkPad W520)

These are the lines displayed:
Loading Linux 4.19.0.1-amd64 ...
Loading initial ramdisk ...
error: attempt to read or write outside of disk 'hd0'.
Press any key to continue ...
It then throws a bunch of text that concludes with a kernel panic error.

timkb4cq had me run GRUB Repair, then Reinstall GRUB bootloader to MBR.

When I restart the problem returns.

Anyone seen this before & have ideas to solve it, please?
Last edited by NevilsStation on Tue Aug 06, 2019 7:21 am, edited 1 time in total.
Custom-built PC w/i7 CPU running MX-16.

User avatar
fehlix
Developer
Posts: 4922
Joined: Wed Apr 11, 2018 5:09 pm

Re: GRUB Boot Error

#2

Post by fehlix » Tue Jul 23, 2019 8:01 pm

NevilsStation wrote:
Tue Jul 23, 2019 7:21 pm
I was powering on my laptop (ThinkPad W520)
Some more details please. Please post this info:
Quick System info found in the menu.
And output of terminal commands:

Code: Select all

sudo parted --list

Code: Select all

sudo lsblk -f
Is that a fresh install?
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
NevilsStation
Forum Regular
Forum Regular
Posts: 376
Joined: Sun Feb 26, 2017 3:09 pm

Re: GRUB Boot Error

#3

Post by NevilsStation » Tue Jul 23, 2019 8:17 pm

fehlix wrote:
Tue Jul 23, 2019 8:01 pm
Is that a fresh install?
:puppy:
It was a clean install with fldigi, flrig (installed from Test Repo), then upgraded from 18.1 to 18.3, then fldigi, flrig, and a few others in that suite upgraded and added after timkb4cq updated and added them to the Test Repo.

I'll post the terminal command results separately.
Last edited by NevilsStation on Tue Jul 23, 2019 9:25 pm, edited 1 time in total.
Custom-built PC w/i7 CPU running MX-16.

User avatar
NevilsStation
Forum Regular
Forum Regular
Posts: 376
Joined: Sun Feb 26, 2017 3:09 pm

Re: GRUB Boot Error

#4

Post by NevilsStation » Tue Jul 23, 2019 8:32 pm

Custom-built PC w/i7 CPU running MX-16.

User avatar
fehlix
Developer
Posts: 4922
Joined: Wed Apr 11, 2018 5:09 pm

Re: GRUB Boot Error

#5

Post by fehlix » Tue Jul 23, 2019 10:13 pm

NevilsStation wrote:
Tue Jul 23, 2019 8:17 pm
I'll post the terminal command results separately.
Thanks, please post terminal command text-output as text - wrapped
within code-tags [code]text output goes here[/code].
Do re-post the text-output of these commands:

Code: Select all

sudo parted --list
and

Code: Select all

sudo lsblk -f
and

Code: Select all

sudo fdisk --list
Meanwhile you can download antiX19b2 ISO, which comes with "Boot Rescue Menu" to boot into a broken system.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
NevilsStation
Forum Regular
Forum Regular
Posts: 376
Joined: Sun Feb 26, 2017 3:09 pm

Re: GRUB Boot Error

#6

Post by NevilsStation » Wed Jul 24, 2019 10:46 pm

Code: Select all

demo@mx1:~
$ sudo parted --list
Model: ATA INTEL SSDSC2BW18 (scsi)
Disk /dev/sda: 180GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start  End    Size    Type     File system     Flags
 1      512B   178GB  178GB   primary  ext4            boot
 2      178GB  180GB  2147MB  primary  linux-swap(v1)

Model: ATA WDC WD10JPLX-00M (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1000GB  1000GB  primary  ext4

Model: SanDisk Ultra Fit (scsi)
Disk /dev/sdc: 15.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  15.3GB  15.3GB  primary  ext4         boot
 2      15.3GB  15.4GB  52.4MB  primary  fat16        esp

demo@mx1:~
$ sudo lsblk -f
NAME   FSTYPE   LABEL       UUID                                 MOUNTPOINT
loop0  squashfs                                                  /live/linux
sda                                                              
├─sda1 ext4     rootMX18.1  7b555be1-4b9a-4dc2-bc7f-beac19a2c130 
└─sda2 swap     MXswap      04e94f95-3ebe-4c4c-98d8-1777dfadd997 [SWAP]
sdb                                                              
└─sdb1 ext4     homeMX      d378684c-c7d9-4138-a1c7-772ad43bef6d /media/demo/homeMX
sdc                                                              
├─sdc1 ext4     MX-Live-usb 6e2e103b-630d-41f0-828b-5b5fafd9330e /live/boot-dev
└─sdc2 vfat     MX-uefi     7E95-0D93                            
demo@mx1:~
$ sudo fdisk --list
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00da09e4

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1        2048 1953523711 1953521664 931.5G 83 Linux


Disk /dev/sda: 167.7 GiB, 180045766656 bytes, 351651888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x706c23d7

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *            1 347391999 347391999 165.7G 83 Linux
/dev/sda2       347392000 351586303   4194304     2G 83 Linux


Disk /dev/sdc: 14.3 GiB, 15376000000 bytes, 30031250 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9bb2e386

Device     Boot    Start      End  Sectors  Size Id Type
/dev/sdc1  *        2048 29927423 29925376 14.3G 83 Linux
/dev/sdc2       29927424 30029823   102400   50M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 1.3 GiB, 1421348864 bytes, 2776072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
demo@mx1:~
$ 
Custom-built PC w/i7 CPU running MX-16.

User avatar
fehlix
Developer
Posts: 4922
Joined: Wed Apr 11, 2018 5:09 pm

Re: GRUB Boot Error

#7

Post by fehlix » Thu Jul 25, 2019 6:55 am

The SSD-disk /dev/sda does have one issue with the partition table layout regarding the beginning of the partition table.
The first root-partition /dev/sda1 starts at sectore no #1, just after first MBR sector of 512B, which is sector no #0.

Code: Select all

Number  Start  End    Size    Type     File system     Flags
 1      512B   178GB  178GB   primary  ext4            boot

├─sda1 ext4     rootMX18.1  7b555be1-4b9a-4dc2-bc7f-beac19a2c130 

Sector size (logical/physical): 512 bytes / 512 bytes
Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *            1 347391999 347391999 165.7G 83 Linux
Normally the first partition starts at sector 2048, which gives about 1MB post MBR gap. This post MBR gap is used by GRUB to provide a reliable bootloader.

Without such a post MBR gap, you have created a potential GRUB-boot time bomb,as Grub cannot embed its core.img into the post MBR gab and has to use unreliable blocklists.
GRUB will stop working properly as soon as the core.img get's realocated, or rewritten in to the place where BIOS function show their limits, which can happen any time e.g. after a automated filesystem check.

A simple proof that your installation is still working would be to boot into the installed MX Linux using "Boot Rescue Menu" this way:

Boot from antiX19b2 LiveISO. ( https://sourceforge.net/projects/antix- ... s/Testing/ )
Select the last point "Switch to Grub Menu" and select "Boot Rescue Menus".
Here you can either search for Grub loader (core.img) and also for Grub menu (grub.cfg)
Try both variants.
If MX Linux boots normally in either of both cases we can go from here to repair.
One way to "repair" would be a quick-fix by re-using the MBR of the 2nd hdd /dev/sdb, another would be to use timeshift and re-partition the ssd properly and restore with timeshift.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
NevilsStation
Forum Regular
Forum Regular
Posts: 376
Joined: Sun Feb 26, 2017 3:09 pm

Re: GRUB Boot Error

#8

Post by NevilsStation » Thu Jul 25, 2019 8:12 am

I can do the antix boot a little later.

If it matters - there's nothing on the SSD that I need to protect.

Thanks!
Custom-built PC w/i7 CPU running MX-16.

User avatar
NevilsStation
Forum Regular
Forum Regular
Posts: 376
Joined: Sun Feb 26, 2017 3:09 pm

Re: GRUB Boot Error

#9

Post by NevilsStation » Thu Jul 25, 2019 10:35 am

I'm getting this when I try to boot from the antix USB stick:

Code: Select all

Error mounting /dev/sdc1 at /media/dmc/antiX-Live-usb: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc1" "/media/dmc/antiX-Live-usb"' exited with non-zero exit status 32: mount: /media/dmc/antiX-Live-usb: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
Can anyone spot the cause, please?

(I'm fussing with my old diesel Suburban in-between fussing with this laptop ... sigh.)

Thanks!
Custom-built PC w/i7 CPU running MX-16.

User avatar
fehlix
Developer
Posts: 4922
Joined: Wed Apr 11, 2018 5:09 pm

Re: GRUB Boot Error

#10

Post by fehlix » Thu Jul 25, 2019 11:28 am

NevilsStation wrote:
Thu Jul 25, 2019 10:35 am
I'm getting this when I try to boot from the antix USB stick:

Code: Select all

Error mounting /dev/sdc1 at /media/dmc/antiX-Live-usb: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc1" "/media/dmc/antiX-Live-usb"' exited with non-zero exit status 32: mount: /media/dmc/antiX-Live-usb: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
Can anyone spot the cause, please?
Not sure on what stage you get this. If that's related to a "normal" boot into antiX LiveUSB, perapsto disable automount might help. But that's rahter a topic for the antiX thread viewtopic.php?f=40&t=51472
Can we focus first on going through "Boot Rescue Menu" and try to boot from sda into the installed MX Linux.
Thanks
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Post Reply

Return to “Software / Configuration”