Hello everyone,
I partly solved my problem and I would like to share my solution:
Until now, I thought that the EFI removable media path (\EFI\BOOT\BOOTX64.EFI)
is really a fallback location, i.e. a location for putting the boot loader that
just always works. Therefore I thought that I could fo
w that it works in principle. But now I want to
do it using command line utilities like debootstrap and grub-install."
But:
"the problem is that the ESC boot menu doesn't show an entry for
(the model name of) /dev/sda, so I can't boot into it."
My first question wo
On 26/04/2023 22:57, Valentin Caracalla wrote:
the issue with the BIOS boot interface (see my original posting) is still
unsolved
I had impression that there was no issue with booting in BIOS (legacy,
compatibility, CSM) mode, of course when it is chosen in firmware/BIOS
setup (requires disa
you just read this one post:
Hello everyone,
I want to install Debian on my Asus UX31A using command line utilities like
debootstrap and grub-install.
I want to install it to the internal drive /dev/sda, and I want to do so by
executing commands on an installer system, which is a system already
David Wright (12023-04-25):
> Don't knock it! The Human Era is much easier for us to parse than
;-)
> the French Republican calendar (pre 2018).
I had not realized I had fans devoted to the point of tracking the eras
of my mail attribution. ;-)²
Regards,
--
Nicolas George
signature.asc
De
Greg Wooledge (12023-04-25):
> find /mnt/boot/efi -exec ls -dl {} +
zsh
ls -dl /mnt/boot/efi/**/*
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
On Wed 26 Apr 2023 at 09:14:25 (+0700), Max Nikulin wrote:
> On 26/04/2023 00:42, Nicolas George wrote:
> > Steve McIntyre (12023-04-25):
[ … ]
> P.S. Nicolas, it seems your mailer has issues with parsing or
> formatting timestamps.
Don't knock it! The Human Era is much easier for us to parse th
On Wed, Apr 26, 2023 at 09:34:11AM +0700, Max Nikulin wrote:
> On 26/04/2023 05:02, Valentin Caracalla wrote:
> >
> > user@host:~$ ls -dl $(find /mnt/boot/efi)
>
> find /mnt/boot/efi -print0 | xargs -0 ls -dl --
>
> should be more resistant to peculiar file names, but it does not matter in
> thi
On 26/04/2023 05:02, Valentin Caracalla wrote:
user@host:~$ ls -dl $(find /mnt/boot/efi)
find /mnt/boot/efi -print0 | xargs -0 ls -dl --
should be more resistant to peculiar file names, but it does not matter
in this case.
...
-rwxr-xr-x 1 root root 126 Apr 25 13:59 /mnt/boot/efi/EFI/
On 26/04/2023 00:42, Nicolas George wrote:
Steve McIntyre (12023-04-25):
If you do not intend to install a Microsoft bootloader or anything
besides GRUB, 16 megaoctets is plenty enough, probably can work with
less.
Please STOP giving this advice to people!
That was not advice, that was inform
Valentin Caracalla (12023-04-26):
> EFI variables are not supported on this system.
To install GRUB in UEFI, you need to have booted the kernel in UEFI.
Try to find a live image that does, and you can reinstall GRUB from
there.
Regards,
--
Nicolas George
signature.asc
Description: PGP sign
Here's the output you requested:
user@host:~$ ls -dl $(find /mnt/boot/efi)
drwxr-xr-x 3 root root 32768 Jan 1 1970 /mnt/boot/efi
drwxr-xr-x 3 root root 32768 Apr 25 13:59 /mnt/boot/efi/EFI
drwxr-xr-x 2 root root 32768 Apr 25 13:59 /mnt/boot/efi/EFI/debian
-rwxr-xr-x 1 root root 108
Steve McIntyre (12023-04-25):
> >If you do not intend to install a Microsoft bootloader or anything
> >besides GRUB, 16 megaoctets is plenty enough, probably can work with
> >less.
> Please STOP giving this advice to people!
That was not advice, that was information. Make your own advice with it.
Nicolas George wrote:
>Max Nikulin (12023-04-25):
>> 0.5GB is usually enough, e.g. 550MiB recommended by
>> https://www.rodsbooks.com/gdisk/advice.html#esp_sizing)
>
>If you do not intend to install a Microsoft bootloader or anything
>besides GRUB, 16 megaoctets is plenty enough, probably can work
Max Nikulin (12023-04-25):
> 0.5GB is usually enough, e.g. 550MiB recommended by
> https://www.rodsbooks.com/gdisk/advice.html#esp_sizing)
If you do not intend to install a Microsoft bootloader or anything
besides GRUB, 16 megaoctets is plenty enough, probably can work with
less.
Regards,
--
On 25/04/2023 21:40, Valentin Caracalla wrote:
I checked my partition table using "sudo parted /dev/sda print"
Number Start End Size File system Name Flags
1 1049kB 128GB 128GB fat32 init boot, esp
2 128GB 256GB 128GB ext4 root
Please, show
vorubergeh...@tutanota.com wrote:
>By the way:
>
>The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the
>following will not show a GRUB command line:
>
>sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
>
>The same thing works for the BIOS boot interface, however (as in my
Valentin Caracalla (12023-04-25):
> The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the
> following will not show a GRUB command line:
>
> sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
Oh, I must check if the KVM virtual machine booting on UEFI I have been
toying w
By the way:
The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the
following will not show a GRUB command line:
sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
The same thing works for the BIOS boot interface, however (as in my original
recipe).
I apologize for the formatting in my last post, I don't know what happened. And
many thanks for your help!
I checked my partition table using "sudo parted /dev/sda print" and it didn't
show any flags for partition 1 (the "init" partition). Therefore I manually set
the flags using "sudo parted /
Valentin Caracalla writes:
> But this doesn't work either. Same problem here. However I can make
> such an EFI installation using official installation media on the same
> machine and that does work.
That recipe (and the whole post) was hard to read but don't you need
some flags for the ESP part
do mount --bind /proc /mnt/proc sudo mount
--bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind
/run /mnt/run sudo chroot /mnt apt install grub-efi sudo chroot /mnt
grub-install /dev/sda sudo umount /mnt/run sudo umount /mnt/dev/pts sudo umount
/mnt/dev sudo umount /mnt/
There are a few things I forgot to say:
The recipe I posted earlier is executed on a system installed on the external
drive /dev/sdb, which I call the installer system. It is also a Debian system,
with the recipe's dependencies installed. To reproduce the issue (if you want),
I suggest using a
Valentin Caracalla writes:
> Previously, I've successfully installaed Debian using official
> installation media on this machine (also using BIOS boot interface),
> so I know that it works in principle.
I can't see anything wrong with the script. Did that installation use
GPT and a BIOS Boot Par
Hello everyone,
I'm trying to install Debian on my Asus UX31A using command line utilities like
debootstrap and grub-install. However, the installed system is not bootable.
The problem is that the internal drive (which I install the system to) doesn't
show up in the boot menu (whi
Thanks a lot, this is very useful!
- vinceh121
On 9/18/22 13:42, Steve McIntyre wrote:
On Sat, Sep 17, 2022 at 03:07:29AM +0200, vinceh121 wrote:
Thanks, this works!
Is there a way to set this option during installation on a netinst image?
Yes! You can switch to expert mode for installatio
On Sat, Sep 17, 2022 at 03:07:29AM +0200, vinceh121 wrote:
>Thanks, this works!
>
>Is there a way to set this option during installation on a netinst image?
Yes! You can switch to expert mode for installation and then
grub-efi-$ARCH will ask you these questions. Or you can add these
options using
distro on.
However, many distros installs are broken by grub-install either safely
failing, or making the kernel hang while trying to write NVRAM boot
options. I've confirmed this on Debian Buster and Bullseye.
This causes the netinst images to give us a mostly working installation,
except
vinceh121 wrote:
>
>Southern French government is handing out laptops (HP ProBook x360 G1
>EE) to students, whom a lot of want to install a Linux distro on.
>
>However, many distros installs are broken by grub-install either safely
>failing, or making the kernel hang while try
Am 16.09.2022 um 20:19 schrieb vinceh121:
> Is there a way to mitigate this problem?
Apart from the plan, you seem to be favoring, i would like to introduce
another option to you:
(BTW: I used it myself, and still do, while i was learning to
reconfigure to UEFI-Booting)
There is a sort of boot
wrote:
Now I'm in my "full" Debian system. Next:
# grub-install /dev/sda2
# apt install [linux kernel]
# update-grub
Error: Cannot find GRUB drive for /dev/sda2
Unless you have a good reason to do otherwise grub is installed in the
MBR of the drive, so you probably want '
On Mi, 15 sep 21, 05:49:01, Musbur wrote:
>
> Now I'm in my "full" Debian system. Next:
> # grub-install /dev/sda2
> # apt install [linux kernel]
> # update-grub
> Error: Cannot find GRUB drive for /dev/sda2
Unless you have a good reason to do otherwise grub is i
/etc/resolv.conf /mnt/etc/resolv.conf
4) # chroot /mnt
5) mount /dev/sda2 /boot
Now I'm in my "full" Debian system. Next:
# grub-install /dev/sda2
# apt install [linux kernel]
# update-grub
Error: Cannot find GRUB drive for /dev/sda2
I tried both the grub-pc as well as the grub-e
On Tue, Sep 24, 2019 at 02:06:15PM +0200, Mattia wrote:
> Hello,
>
> toady I encountered this error while upgrading to buster:
Nevermind, I just found this workaround[¹]:
cd /boot/efi/EFI
mv debian debian-old
apt install -f
mv debian-old debian
update-grub2
Hope this helps other people.
[¹] h
, 0 B of additional disk space will be used.
Setting up shim-signed-common (1.33+15+1533136590.3beb971-7) ...
Installing for x86_64-efi platform.
grub-install: warning: efivarfs_get_variable:
open(/sys/firmware/efi/efivars/blk0-47c7b225-c42a-11d2-8e57-00a0c969723b):
No such file or directory.
grub
Le 03/01/2018 à 09:10, Tom Dial a écrit :
On 01/02/2018 11:14 AM, Pascal Hambourg wrote:
This is one of the many possible plans.
But it is uncomplicated and simple to execute using available or easily
obtained tools. The total outage time was around 2 hours and, as pointed
out below, could ha
e beginning, so the first partitions now actually
begin at block 4096.
>
>> 3. reboot using the old grub, kernel, initrd, etc.
>> 4. restore the new (stretch) /boot/grub/*
>
> No need to restore the new /boot/grub/*, grub-install will recreate it.
Another thing I did not know, th
/grub/*, grub-install will recreate it.
5. run grub-install to install the new grub
6. reboot and finish the stretch upgrade.
d core images in a btrfs non-LVM partition, which
> supports GRUB embedding, instead of in the MBR. However IME the minimum
> partition size for btrfs is at least 5 MiB (or 16 MiB, depending on
> btrfs tools version).
>
> - Convert the partition table to GPT with gdisk and create a
onvert the partition table to GPT with gdisk and create a "BIOS boot"
partition which GRUB can use to write the core image. However since you
moved partitions to the very end of the disk there is no room any more
to write the backup GPT partition table.
2. The grub install failed. The curre
a way to shorten it by that much without sacrificing the
capability to boot from an lvm logical volume and jfs file systems?
2. The grub install failed. The current modified grub.cfg was not
changed materially and references most objects by uuid. If I shut down
and move the necessary partitions, i
Many thanks to Christian, David, and Pascal!
With your hints I was able to solve the problems.
Lessons learned:
1. d-i needs to be in "low" questions mode (expert) to allow
manual selection of partition type (e.g. DOS/MBR or GPT).
2. d-i seems to call grub-install on /dev/md
Christian Seiler a écrit :
> On 01/08/2016 02:51 AM, Pascal Hambourg wrote:
>> Current tools won't align for compatibility purpose any more. The
>> default 1-MiB alignment is only for performance purpose, not compatibility.
>
> This is new to me - I always thought that this was entirely for
> comp
On 01/07/2016 04:22 PM, W. Martin Borgert wrote:
I try to install Jessie with a soft RAID6 of four disks, 1 TB each.
The idea is to use the complete disk for RAID and then only on top
separate swap and root. ...
grub does not install on the fourth disk. It turns out, that the
fourth disk is GPT,
On 01/08/2016 02:51 AM, Pascal Hambourg wrote:
> Christian Seiler a écrit :
>> for compatibility reasons every tool that manipulates MBR
>> partitions will therefore want to leave a gap after the MBR.
>
> Current tools won't align for compatibility purpose any more. The
> default 1-MiB alignment i
Christian Seiler a écrit :
>
> Well sure, but MBR also has all the CHS baggage - and while it isn't
> used anymore on modern systems, there still is the de-factor standard
> of aligning the first partition with the first CHS-sector that is so
> ingrained historically that the gap between MBR and t
On 01/08/2016 02:03 AM, Pascal Hambourg wrote:
> Christian Seiler a écrit :
>> Problem is that GPT doesn't have such a gap.
>
> GPT usually also has such a gap for partition alignment purpose.
Well sure, but MBR also has all the CHS baggage - and while it isn't
used anymore on modern systems, the
Christian Seiler a écrit :
>
> Ok, if you use MBR, only the first 512 bytes are used for the MBR
> partition table, so that the gap between those bytes and the first
> partition (and there is *always* a gap, the size depends on the
> details of the logical geometry of the disk) has traditionally
>
there is some small amount of space left, just create a new
partition of type "BIOS boot partition" on the GPT disk and then
grub-install should work. Would be the easiest solution.
> AFAIK, I don't need GPT for such small disks, right?
Not necessarily, no. ~2TB is the limit for
es not install on the fourth disk. It turns out, that the
> fourth disk is GPT, while the others are DOS (= MBR, right?). Also,
> the fourth disks only partition is of type "Linux RAID", while the
> partitions of the other three disks are "Linux raid autodetect".
On a
fourth disk is GPT, while the others are DOS (= MBR, right?). Also,
the fourth disks only partition is of type "Linux RAID", while the
partitions of the other three disks are "Linux raid autodetect".
On a second machine, supposed to be identical, grub-install failed
on all disks,
Thanks for the detail Pascal.
On Tue, Sep 15, 2015 at 2:00 AM, Pascal Hambourg
wrote:
> Muhammad Yousuf Khan a écrit :
> > command "grub-install --modules=part_gpt /dev/sdc" resolved the issue for
> > me.
>
> Glad to hear it.
>
> > however i also w
Muhammad Yousuf Khan a écrit :
> command "grub-install --modules=part_gpt /dev/sdc" resolved the issue for
> me.
Glad to hear it.
> however i also wanted to know that how it actually works.
> what is the difference. i can understand i am mentioning gpt module in
> th
command "grub-install --modules=part_gpt /dev/sdc" resolved the issue for
me. however i also wanted to know that how it actually works.
what is the difference. i can understand i am mentioning gpt module in
the command but what is the theoretical story behind this to work. or
w
cated. Also, ls
showing only the whole disk (hd0) without any partition seems to
indicate that it could not read the partition table. GRUB has specific
modules to read each partition table format, and such module(s) need to
be embedded into the core image by grub-install in order to be able to
read t
On 13/09/15 04:28 PM, Muhammad Yousuf Khan wrote:
I am trying to replacing 1 TB drives with 2TB i am using RAID 1 mdadm
i successfully replaced the first drive and it is synced and working
normally.
i also installed grub by this commad "grub-install /dev/sdc"
/dev/sdc is my new dri
, not hda0.
"ls" should show the disks and their partitions.
Maybe the core image is missing the part_gpt module. You can try to
reinstall it with
grub-install --modules=part_gpt /dev/sdc
I am trying to replacing 1 TB drives with 2TB i am using RAID 1 mdadm
i successfully replaced the first drive and it is synced and working
normally.
i also installed grub by this commad "grub-install /dev/sdc"
/dev/sdc is my new drive.
Please note that i am using gdisk to create GPT pa
ion?
> Is there a way to manipulate udev rules so that I can force my boot
> drive to always enumerate as sda, or is there a way to get
> grub-install to work with more than the first 16 devices (that is
> where I found it to stop working /dev/sdp).
Alternatively, if all of y
I need to install wheezy via pxe boot to many (hundreds) of systems. The
problem I am currently running into in my testing is that my boot drive is
enumerated by udev as /dev/sdat in many of those systems, and the grub-install
routine inside debian-installer will not install to that device
shell on the resulting /dev/md0.
Modified the /etc/fstab so /boot would have the correct blkid. I then ran
grub-install on the small drive (/dev/sdg).
During the grub-install it spewed 25 errors "error: unknown LVM metadata
header". But the command continued on and ended saying "I
On Thu 08 Nov 2012 at 10:39:45 -0500, Tom H wrote:
> grub-install has "--no-floppy" and "--allow-floppy" options so
> installing grub to a floppy should be possible.
Neither option really has any bearing on installing GRUB to a floppy.
--
To UNSUBSCRIBE,
I find is either very narrowly targetted or doesn't explain
> the why of grub-install well enough to figure out what to do.
I'd suggest you don't want to do this, whether it is doable or not.
There are two ways I can think of but let's have some more information
first pleas
ot off the CD and we have to do it all over again.
>
> I want to declare a truce and put a floppy in that will
> call the CD. I think this can be done but all the documentation
> I find is either very narrowly targetted or doesn't explain
> the why of grub-install well en
Tom Grace writes:
> I'm not sure about that, but you might have an easier time customizing
> an existing cdrom chainloading floppy image.
I will look some more because I was more or less leaning
that way.
> I found http://schierlm.users.sourceforge.net/bootdisk/ and you might be
> able to
On Thursday 08 November 2012 14:13:56 Martin McCormick wrote:
> Where are some linear English sentences that de mystify what we
> can get grub-install to do?
+1
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On 08/11/12 14:13, Martin McCormick wrote:
> Should this work?
Yes, it should be possible.
> Where are some linear English sentences that de mystify what we
> can get grub-install to do?
>
I'm not sure about that, but you might have an easier time customizing
an existing cdrom ch
will
call the CD. I think this can be done but all the documentation
I find is either very narrowly targetted or doesn't explain
the why of grub-install well enough to figure out what to do.
That is more or less where I am at this point.
My questions are:
Should this work?
Wher
Andrei POPESCU wrote:
On Jo, 28 iun 12, 21:41:23, Dan B. wrote:
When I run "grub-install /dev/sdb1", it says:
/usr/sbin/grub-setup: error: unable to identify a filesystem in hd1,gpt1;
safety check can't be performed.
and does not install GRUB2. (It's still the same
On Jo, 28 iun 12, 21:41:23, Dan B. wrote:
> When I run "grub-install /dev/sdb1", it says:
>
> /usr/sbin/grub-setup: error: unable to identify a filesystem in hd1,gpt1;
> safety check can't be performed.
>
> and does not install GRUB2. (It's still the sam
When I run "grub-install /dev/sdb1", it says:
/usr/sbin/grub-setup: error: unable to identify a filesystem in hd1,gpt1;
safety check can't be performed.
and does not install GRUB2. (It's still the same if I use the syntax
("grub-install (hd1,gpt1)".)
T
On 09/04/12 04:44 PM, tv.deb...@googlemail.com wrote:
On 08/04/2012 17:42, Frank McCormick wrote:
That worked...but I caused another problem.
I still didn't like Mepis, so I booted into Debian Sid and forgetting
Grub had been last installed by Mepis, formatted the partition. Well you
know what
On 08/04/2012 17:42, Frank McCormick wrote:
That worked...but I caused another problem.
I still didn't like Mepis, so I booted into Debian Sid and forgetting
Grub had been last installed by Mepis, formatted the partition. Well you
know what happened. Next time I booted I ended up at the Grub res
On 12-04-08 12:09 PM, Indulekha wrote:
In linux.debian.user, Frank McCormick wrote:
I mounted sda2, and tried to ChRoot into it. I couldn't...I
kept getting an error message "unable to run /bin/zsh"
Perhaps because it's /usr/bin/zsh?
I don't know...I didn't master the SystemRescue disk :
In linux.debian.user, Frank McCormick wrote:
> I mounted sda2, and tried to ChRoot into it. I couldn't...I
> kept getting an error message "unable to run /bin/zsh"
Perhaps because it's /usr/bin/zsh?
--
❤ ♫ ❤ ♫ ❤ ♫ ❤
Indulekha
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debia
On 08/04/12 08:51 AM, Frank McCormick wrote:
On 08/04/12 05:49 AM, Paul Saunders wrote:
On Sat, 07 Apr 2012 16:37:32 -0400
Frank McCormick wrote:
On 04/07/2012 04:29 PM, Tom H wrote:
On Sat, Apr 7, 2012 at 3:55 PM, Frank McCormick
wrote:
[cut]
The distro runs fine but slow under KDE, b
all grub-pc failed"
>>
>> Any idea how to solve this problem? The system is a x86_64 system with 4
>> gigs of memory.
>
> It seems this is a recurrent issue.
Thanks for your help! The previous install DVD (20111003) had the same
issue and I think it is corrected in curr
4 system with 4
> gigs of memory.
It seems this is a recurrent issue.
Are you using the "expert" installer mode? If yes, retry the GRUB install
several times, I don't know why but the installer usually gets stuck in
this step and after some retries it -sometimes- finally can get
Hello!
I try to install Wheezy with latest install DVD snapshot (20111011)
and when installer try to install grub it failed with "grub-pc package
failed to install into /target/". I switch to terminal four and the
log says:
"Package grub-pc is not available, but is referred to by another package.
Tom H writes:
> On Wed, Oct 12, 2011 at 9:19 AM, Kurt Flex wrote:
>> Currently I guess the real bootloader is not on the raid at all. Maybe
>> it's some other device they are hiding from me. (There is also a rescue
>> system I can boot, but i can't find it in normal state).
>
> It sounds like it'
On Wed, Oct 12, 2011 at 2:03 PM, Martin Steigerwald wrote:
>
> grub2 could use a blocklist (as lilo did), but thats unsafe.
You can use blocklists with grub2 by passing "--force" as a
"grub-install" argument but I would check first whether it's a VM
booted thr
Am Mittwoch, 12. Oktober 2011 schrieb Kurt Flex:
> Tom H writes:
> > On Tue, Oct 11, 2011 at 5:58 PM, Kurt Flex wrote:
> >># grub-install /dev/sda
> >>/usr/sbin/grub-setup: warn: This msdos-style partition label has
> >> no post-MBR gap; embedding won
t; > The same for grub-common.
> >
> > A dialog appeared which asked me to run grub-install. But that
> > failed. So i told the dialog to skip that part. Now I've tried
> > grub-install manually.
> >
> > # grub-install /dev/sda
> > /usr/sbi
Am Mittwoch, 12. Oktober 2011 schrieb Ad L.:
> Regardless of the possibility to use the space, I ALWAYS leave the
> first cylinder of a disk unused (aligning partitions to cylinder
> boundaries). I find the idea of using the first cylinder for "optimal"
> space usage a bit ridiculous, to be honest.
On Wed, Oct 12, 2011 at 9:19 AM, Kurt Flex wrote:
> Tom H writes:
>> On Tue, Oct 11, 2011 at 5:58 PM, Kurt Flex wrote:
>>>
>>> # grub-install /dev/sda
>>> /usr/sbin/grub-setup: warn: This msdos-style partition label has no
>>> post-MBR gap; e
Tom H writes:
> On Tue, Oct 11, 2011 at 5:58 PM, Kurt Flex wrote:
>>
>> # grub-install /dev/sda
>> /usr/sbin/grub-setup: warn: This msdos-style partition label has no
>> post-MBR gap; embedding won't be possible!.
>> /usr/sbin/grub-setup: error:
On Tue, Oct 11, 2011 at 5:58 PM, Kurt Flex wrote:
>
> I've done a safe-upgrade today which upgraded grub:
>
> upgrade grub-pc 1.98+20100804-14 1.98+20100804-14+squeeze1
>
> The same for grub-common.
>
> A dialog appeared which asked me to run grub-install. But
Regardless of the possibility to use the space, I ALWAYS leave the
first cylinder of a disk unused (aligning partitions to cylinder
boundaries). I find the idea of using the first cylinder for "optimal"
space usage a bit ridiculous, to be honest. With thousands of
cylinders on a disk, if not more,
On Tue, Oct 11, 2011 at 11:58:52PM +0200, Kurt Flex wrote:
>
> Hi,
>
> I've done a safe-upgrade today which upgraded grub:
>
> upgrade grub-pc 1.98+20100804-14 1.98+20100804-14+squeeze1
>
> The same for grub-common.
>
> A dialog appeared which ask
Hi,
I've done a safe-upgrade today which upgraded grub:
upgrade grub-pc 1.98+20100804-14 1.98+20100804-14+squeeze1
The same for grub-common.
A dialog appeared which asked me to run grub-install. But that
failed. So i told the dialog to skip that part. Now I've tried
grub-instal
On 20100912_193846, Paul Scott wrote:
> Hi,
>
> I am trying to install from a testing net-install CD a little over a
> year old. I have a hard drive problem and this is all I have to
> build a new system.
>
> I get a screen to choose the devices on which to install grub. No
> matter what combin
n
always try going back from the grub screen).
Did you specify a device to be made bootable??
If look at the install messages (Alt+F4) at the grub install page is
there anything unusual??
Did you choose GRUB2 or GRUB legacy??
Is this a standard hard drive partitioning scheme (no LVM, RAID or
encryption
Hi,
I am trying to install from a testing net-install CD a little over a
year old. I have a hard drive problem and this is all I have to build a
new system.
I get a screen to choose the devices on which to install grub. No
matter what combination I check the next screen tells me I have not
On Fri, 2 Apr 2010 12:35:50 -0400 (EDT), Paul E Condon wrote:
> For installing Squeeze, I think the business card CD is more useful
> than the daily build. The business card CD has far less new stuff
> burnt onto the media, only what is absolutely necessary to setting up
> the local end of the link
On 20100402_120108, Stephen Powell wrote:
> On Fri, 2 Apr 2010 09:50:21 -0400 (EDT), Eric Dantan Rzewnicki wrote:
> >
> > (NB: please Cc: me on replies as I'm not subscribed here)
> >
> > This mail is to determine where to file a bug report. I'm not clear if
> > it is an mdadm, mbr, grub, lilo or
On Fri, 2 Apr 2010 09:50:21 -0400 (EDT), Eric Dantan Rzewnicki wrote:
>
> (NB: please Cc: me on replies as I'm not subscribed here)
>
> This mail is to determine where to file a bug report. I'm not clear if
> it is an mdadm, mbr, grub, lilo or d-i issue or the interaction of
> those within d-i co
(NB: please Cc: me on replies as I'm not subscribed here)
This mail is to determine where to file a bug report. I'm not clear if
it is an mdadm, mbr, grub, lilo or d-i issue or the interaction of
those within d-i context.
I attempted to use the squeeze d-i to install a system on a raid1 pair.
The
Good day.
How I can install grub in MBR on the disk where to I've copied a
warking OS if
grub-install /dev/sda
says:
File stage2 is not read properly
- or something like that. And it is not get installed into MBR.
What I did is:
copied all the files to root on an empty partition
did
[...]
> And why does it say
> "install GRUB images under the directory ..."?
>
> Isn't it installing something in the MBR? Not is a directory? Or do I
> *really* misunderstand what grub-install does? What is a "GRUB image"? Or
> am I parsing this inc
On Wed,01.Apr.09, 08:18:52, Paul E Condon wrote:
[question about --root-dir option]
I think a 'ls /boot/grub' might bring more light to the issue ;)
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
signature.asc
Description: Digital sig
1 - 100 of 137 matches
Mail list logo
