On Wed 26 Aug 2015 at 01:55:15 -0700, Ldten K wrote:
> On Wed, 8/26/15, Pascal Hambourg wrote:
>
> // Didn't you install a more recent version of GRUB (possibly from a new
> // installation) at some time on that disk ?
>
> That could be it. The drive originally had a working wheezy installation
On Wed, 8/26/15, Pascal Hambourg wrote:
// Didn't you install a more recent version of GRUB (possibly from a new
// installation) at some time on that disk ?
That could be it. The drive originally had a working wheezy installation that
booted
properly and worked just fine. I then decided to upg
Ldten K a écrit :
> On Tue, 8/25/15, Pascal Hambourg wrote:
>
>> What does "ls (hd0,msdos1)/grub/" show ? Just a few files
>> and directories or plenty of *.mod files?
>
> I have the drive disconnected at the moment but, as far as I remember, "ls
> (hd0,msdos1)/grub/"
> shows all the files th
On Tue, 8/25/15, Pascal Hambourg wrote:
// What does "ls (hd0,msdos1)/grub/" show ? Just a few files
// and directories or plenty of *.mod files?
I have the drive disconnected at the moment but, as far as I remember, "ls
(hd0,msdos1)/grub/"
shows all the files that are normally expected to b
Ldten K a écrit :
>
> grub rescue> ls (hd0,msdos1)/
> config-3.2.0-4-amd64 grub initrd.img-3.2.0-4-amd64 lost+found
> System.map-3.2.0-4-amd64 vmlinuz-3.2.0-4-amd64
>
> grub rescue> set prefix=(hd0,msdos1)/grub
> grub rescue> insmod normal
> file '/grub/i386-pc/normal.mod not found
On Mon, 8/24/15, Brian wrote:
// If the device and path for prefix is correct you should see a grub
// directory in the output of
//
// ls ((hd0,msdos1)/
//
// Do you?
Yes.
grub rescue> ls (hd0,msdos1)/
config-3.2.0-4-amd64 grub initrd.img-3.2.0-4-amd64 lost+found
System.map-3.2.0-4-am
Ldten K a écrit :
>
> Am trying to restore my regular working HD from backup HD but booting
> from the restored HD results in "file '/grub/i386-pc/normal.mod' not
> found" error. This seems a bit odd since 1) my wheezy system is amd64
Indeed this seems odd, but not for that reason. "i386-pc" is j
On Sun 23 Aug 2015 at 20:14:32 -0700, Ldten K wrote:
> 2. In the grub rescue mode:
> grub rescue> set prefix=(hd0,msdos1)/grub
> grub rescue> insmod normal
> file '/grub/i386-pc/normal.mod not found
> grub rescue> insmod linux
> file '/grub/i386-pc/
Hi,
Am trying to restore my regular working HD from backup HD but booting from the
restored HD results in "file '/grub/i386-pc/normal.mod' not found" error. This
seems a bit odd since 1) my wheezy system is amd64 and 2) I can boot from my
backup HD just fine. My regular working and backup HDs h
On 05/21/2013 04:24 PM, Gary Roach wrote:
Hi
My wife let her Debian machine get over 450 packages behind before I
caught it. What a mess. The last problem is that when booting up the
Welcome to Grub notice appears and then:
error:file not found
Entering rescue mode
gru
On Thu, 23 May 2013 07:34:45 +0800, Gary Roach
wrote:
To all,
I reinstalled grub2 with "Aptitude reinstall grub2". The installation
seemed to work fine. I updated grub afterward.
Brian asked
grub-install /dev/sdX ?
So..
# grub-install --recheck /dev/sdX
# update-grub
--
To UNSUBS
On 05/22/2013 11:20 AM, Gary Roach wrote:
To all the questions.
I reinstalled grub2. The same problem persists.
I have run update-grub2 (a stub that runs grub-mkconfig for grub2)
several times with no improvement. i also ran grub-mkconfig directly.
Same results. See listing below.
I've had Wh
On Wed 22 May 2013 at 11:20:38 -0700, Gary Roach wrote:
> On 05/21/2013 04:24 PM, Gary Roach wrote:
>
> I reinstalled grub2. The same problem persists.
Does this refer to reinstalling the grub packages or to the command
grub-install /dev/sdX ?
--
To UNSUBSCRIBE, email to debian-user-requ.
On Wed, May 22, 2013 at 12:20 PM, Gary Roach wrote:
> On 05/21/2013 04:24 PM, Gary Roach wrote:
>
> Hi
>
> My wife let her Debian machine get over 450 packages behind before I caught
> it. What a mess. The last problem is that when booting up the Welcome to
> Grub notice appears and then:
>
On 05/21/2013 04:24 PM, Gary Roach wrote:
Hi
My wife let her Debian machine get over 450 packages behind before I
caught it. What a mess. The last problem is that when booting up the
Welcome to Grub notice appears and then:
error:file not found
Entering rescue mode
gru
Sorry, I cannot help with your original question, but this doesn't fit:
Gary Roach:
>
> My wife let her Debian machine get over 450 packages behind before I
> caught it. […] Oh yes, we are running Debian Wheezy (stable) and KDE
> desktop […]
Are you sure you are running wheezy? It has only been
On 05/21/2013 07:24 PM, Gary Roach wrote:
Hi
My wife let her Debian machine get over 450 packages behind before I
caught it. What a mess. The last problem is that when booting up the
Welcome to Grub notice appears and then:
error:file not found
Entering rescue mode
gru
On Tue, May 21, 2013 at 04:24:39PM -0700, Gary Roach wrote:
> Hi
>
> My wife let her Debian machine get over 450 packages behind before I
> caught it. What a mess. The last problem is that when booting up the
> Welcome to Grub notice appears and then:
> error:file not found
> Enter
Hi
My wife let her Debian machine get over 450 packages behind before I
caught it. What a mess. The last problem is that when booting up the
Welcome to Grub notice appears and then:
error:file not found
Entering rescue mode
grubrescue>
If I run "ls" I find that the roo
>> >>at the moment 'grub-pc' is broken in sid. When you have a separate /boot
>> >>partition, the package generates a wrong '/boot/grub/grub.cfg'. Look at
>> >>the BTS for bug #558042. There is also the workaround for the problem.
>> I ran across the same problem, but I am running mdraid RAID 1, w
On Tue, Dec 01, 2009 at 04:17:36PM -0600, Mark Allums wrote:
>
> >>at the moment 'grub-pc' is broken in sid. When you have a separate /boot
> >>partition, the package generates a wrong '/boot/grub/grub.cfg'. Look at
> >>the BTS for bug #558042. There is also the workaround for the problem.
> >>
>
at the moment 'grub-pc' is broken in sid. When you have a separate /boot
partition, the package generates a wrong '/boot/grub/grub.cfg'. Look at
the BTS for bug #558042. There is also the workaround for the problem.
Hth Michael
I ran across the same problem, but I am running mdraid RAID 1, w
Thanks guys.
After setting the boot disk to "hd(0,0)" (from "hd(0,1)") and removing the
"/boot" suffix by editing the grub entry from the boot menu I got finally in
and aptitude update then pulled in a working version of grub-pc.
Joh
Michael Wagner wrote:
> * Johannes Graumann 30.11.2009
>
Johannes Graumann wrote:
>> A recent update of both my home machines running sid pulled in an update of
>> grub2. Now both machines are stuck with the grub menu showing up fine, but
>> no matter which kernel I choose, I always end up with this error:
>> "error: you need to load the kernel first"
>
* Johannes Graumann 30.11.2009
> A recent update of both my home machines running sid pulled in an update of
> grub2. Now both machines are stuck with the grub menu showing up fine, but
> no matter which kernel I choose, I always end up with this error:
>
> "error: you need to load the kernel
Hello,
A recent update of both my home machines running sid pulled in an update of
grub2. Now both machines are stuck with the grub menu showing up fine, but
no matter which kernel I choose, I always end up with this error:
"error: you need to load the kernel first"
Does anyone here have an id
26 matches
Mail list logo
