Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #209960 > unrolled thread

Boot Problem

Back to article view | Back to linux.debian.user

Contents

  Boot Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-06-16 16:00 +0200
    Re: Boot Problem songbird <songbird@anthive.com> - 2019-06-17 01:30 +0200
    Re: Boot Problem David Christensen <dpchrist@holgerdanske.com> - 2019-06-17 05:00 +0200
    Re: Boot Problem Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-17 20:30 +0200

#209960 — Boot Problem

I have just installed a new SSD in my 64 bit Stretch platform.

When I boot the machine I get the following error:

error: file '/boot/grub/i386-pc/normalmod' not found
Entering rescue mode .. . .
grub rescue>_

Pressing Contro-Alt-Delete reboots the system.  Pressing Delete , or 
F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode 
(actually, F-8 opens the boot selection).

Clicking  on P0 boots the machine normally.

Here are the drives:

blkid
/dev/sda1: UUID="b780b7fb-05a5-4996-8ad5-cd2a578bb4f2" TYPE="ext4" 
PARTUUID="a14552f2-01"
/dev/sda5: UUID="2e6c48ee-b1b5-441e-ae90-549f5e3b6134" TYPE="swap" 
PARTUUID="a14552f2-05"
/dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" 
PARTUUID="eb2be395-01"
/dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" 
PARTUUID="0bc7db76-01"
/dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" 
PARTUUID="0bc7db76-05"
/dev/sdd1: UUID="51941391-3c92-4370-a330-270d2c4d7003" TYPE="ext4" 
PARTUUID="7809855e-01"

Sda1 is the Stretch OS (P0), sdd1 is the new drive. I had no problems 
installing the new drive, nor making it known to Stretch. My intention 
is to install Buster on sdd1, while maintaining Stretch on sda1 for a 
hopefully short period of time.  I should note that I have added the 
i386 applications to /etc/apt/sources.list as a number of my 
applications require i386 libraries.

I have absolutely no idea as to why the new boot error, nor the solution:

     1. What might be the source of the error?
     2. More importantly, what is the solution, would running 
update-grub solve the problem?

Comments will be appreciated.

Thanks in advance.

-- 
Stephen P. Molnar, Ph.D.          Life is a fuzzy set
www.molecular-modeling.net        Stochastic and multivariate
(614)312-7528(c)
Skype:  smolnar1

[toc] | [next] | [standalone]

#209969

Stephen P. Molnar wrote:

> I have just installed a new SSD in my 64 bit Stretch platform.

  what do you mean by "installed"?  there is a lot
of difference between plugging it in vs. plugging 
it in and putting something on it.

  what did you do?

  give details.  we don't know what you did nor can
we read your mind.


> When I boot the machine I get the following error:
>
> error: file '/boot/grub/i386-pc/normalmod' not found
> Entering rescue mode .. . .
> grub rescue>_
>
> Pressing Contro-Alt-Delete reboots the system.  Pressing Delete , or 
> F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode 
> (actually, F-8 opens the boot selection).
>
> Clicking  on P0 boots the machine normally.

  so you can boot the system into Stretch ok.


> Here are the drives:
>
> blkid
> /dev/sda1: UUID="b780b7fb-05a5-4996-8ad5-cd2a578bb4f2" TYPE="ext4" 
> PARTUUID="a14552f2-01"
> /dev/sda5: UUID="2e6c48ee-b1b5-441e-ae90-549f5e3b6134" TYPE="swap" 
> PARTUUID="a14552f2-05"
> /dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" 
> PARTUUID="eb2be395-01"
> /dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" 
> PARTUUID="0bc7db76-01"
> /dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" 
> PARTUUID="0bc7db76-05"
> /dev/sdd1: UUID="51941391-3c92-4370-a330-270d2c4d7003" TYPE="ext4" 
> PARTUUID="7809855e-01"
>
> Sda1 is the Stretch OS (P0), sdd1 is the new drive. I had no problems 
> installing the new drive, nor making it known to Stretch.

> My intention 
> is to install Buster on sdd1, while maintaining Stretch on sda1 for a 
> hopefully short period of time.  I should note that I have added the 
> i386 applications to /etc/apt/sources.list as a number of my 
> applications require i386 libraries.

  i have no idea how to run a mixed system like that
so you are out of my range of experience there.

  i just use the amd64 debs.

  if it was running ok before i see no reason why you'd
add that now?


> I have absolutely no idea as to why the new boot error, nor the solution:
>
>      1. What might be the source of the error?
>      2. More importantly, what is the solution, would running 
> update-grub solve the problem?
>
> Comments will be appreciated.

  since we don't know what you've done i don't know
for sure what has changed.  running update-grub may
make no change at all.

  the more you can say what you did the better 
context we have for replying.


  songbird

[toc] | [prev] | [next] | [standalone]

#209974

On 6/16/19 6:53 AM, Stephen P. Molnar wrote:
> I have just installed a new SSD in my 64 bit Stretch platform.
> 
> When I boot the machine I get the following error:
> 
> error: file '/boot/grub/i386-pc/normalmod' not found
> Entering rescue mode .. . .
> grub rescue>_
> 
> Pressing Contro-Alt-Delete reboots the system.  Pressing Delete , or 
> F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode 
> (actually, F-8 opens the boot selection).
> 
> Clicking  on P0 boots the machine normally.
> 
> Here are the drives:
> 
> blkid
> /dev/sda1: UUID="b780b7fb-05a5-4996-8ad5-cd2a578bb4f2" TYPE="ext4" 
> PARTUUID="a14552f2-01"
> /dev/sda5: UUID="2e6c48ee-b1b5-441e-ae90-549f5e3b6134" TYPE="swap" 
> PARTUUID="a14552f2-05"
> /dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" 
> PARTUUID="eb2be395-01"
> /dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" 
> PARTUUID="0bc7db76-01"
> /dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" 
> PARTUUID="0bc7db76-05"
> /dev/sdd1: UUID="51941391-3c92-4370-a330-270d2c4d7003" TYPE="ext4" 
> PARTUUID="7809855e-01"
> 
> Sda1 is the Stretch OS (P0), sdd1 is the new drive. I had no problems 
> installing the new drive, nor making it known to Stretch. My intention 
> is to install Buster on sdd1, while maintaining Stretch on sda1 for a 
> hopefully short period of time.  I should note that I have added the 
> i386 applications to /etc/apt/sources.list as a number of my 
> applications require i386 libraries.
> 
> I have absolutely no idea as to why the new boot error, nor the solution:
> 
>      1. What might be the source of the error?
>      2. More importantly, what is the solution, would running 
> update-grub solve the problem?
> 
> Comments will be appreciated.
> 
> Thanks in advance.
> 

Did you read my reply to your previous post?

https://lists.debian.org/debian-user/2019/06/msg00335.html


David

[toc] | [prev] | [next] | [standalone]

#209996

Le 16/06/2019 à 15:53, Stephen P. Molnar a écrit :
> I have just installed a new SSD in my 64 bit Stretch platform.
> 
> When I boot the machine I get the following error:
> 
> error: file '/boot/grub/i386-pc/normalmod' not found
> Entering rescue mode .. . .
> grub rescue>_
> 
> Pressing Contro-Alt-Delete reboots the system.  Pressing Delete , or 
> F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode 
> (actually, F-8 opens the boot selection).
> 
> Clicking  on P0 boots the machine normally.
(...)
> Sda1 is the Stretch OS (P0), sdd1 is the new drive.
(...)
>      1. What might be the source of the error?

My first guess, like bw, would be that adding the new SSD has somhow 
changed the BIOS/UEFI boot order and now it defaults to boot another 
disk which contains an incomplete GRUB (maybe a remain of a deleted 
installation).

At the grub rescue prompt, you could type the commands "ls" and "set" 
and report the returns (not all variables, only "cmdline" and "prefix" 
are interesting).
You could also run bootinfoscript from the boot-info-script package and 
post the initial part of the report (before the contents of grub.cfg).

>      2. More importantly, what is the solution, would running 
> update-grub solve the problem?

No. A missing or corrupted grub.cfg does not cause this kind of error. 
The error means that the GRUB core image successfully loaded but failed 
to find the contents of /boot/grub where it expected it.

The best solution is to fix the boot order in the BIOS/UEFI settings. A 
workaround when the former is not applicable is to run grub-install to 
install a copy of GRUB on the actual boot drive.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web