On 06/25/2022 09:37 AM, Stephen P. Molnar wrote:
I have four hard drives ion my Bullseye platform; Three SSD's and one
HDD. My current copy of Bullseye is on /dev/sdd1. I have installed a
pristine copy of Bullsye on /dev/sda.
The installer found the copy of Bullseye on /dev/ssd1 and I instal
"Stephen P. Molnar" writes:
> Assistanc will be mucn appeciated.
You didn't really specify what you want assistance with but I guess you
want to boot the new Bullseye too? I don't really see the point of
having two copies of the same OS installed though.
Assuming a BIOS system and os-prober pac
On Sat 25 Jun 2022 at 09:37:32 (-0400), Stephen P. Molnar wrote:
>
> I have four hard drives ion my Bullseye platform; Three SSD's and one
> HDD. My current copy of Bullseye is on /dev/sdd1. I have installed a
> pristine copy of Bullsye on /dev/sda.
>
> The installer found the copy of Bullseye on
On 25/06/2022 14:37, Stephen P. Molnar wrote:
The installer found the copy of Bullseye on /dev/ssd1 and I installed
grub on /dev/sda1.
You supposed to install GRUB in a disk, not in a partition. So,
/dev/sda, not /dev/sda1. You select /dev/sda during installation.
At the end of the installati
before any action ... comes diagnosis:
please fill in missing pieces:
- SDD's, HDD are formatted GPT? or is the dinosaur using MBR?
- is your computer configured to boot UEFI-style? Or are you still using
BIOS-style/compatibility-mode?
- can you show (and comment) the output from lsblk and (sudo) b
I have four hard drives ion my Bullseye platform; Three SSD's and one
HDD. My current copy of Bullseye is on /dev/sdd1. I have installed a
pristine copy of Bullsye on /dev/sda.
The installer found the copy of Bullseye on /dev/ssd1 and I installed
grub on /dev/sda1. At the end of the install
On Fri 08 Aug 2014 at 21:42:01 +0200, Artifex Maximus wrote:
> On Thu, Aug 7, 2014 at 7:44 PM, Brian wrote:
> > On Tue 05 Aug 2014 at 09:36:18 +0200, Artifex Maximus wrote:
> >
> >> Hello!
> >>
> >> I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian
> >> partition installe
On Thu, Aug 7, 2014 at 7:44 PM, Brian wrote:
> On Tue 05 Aug 2014 at 09:36:18 +0200, Artifex Maximus wrote:
>
>> Hello!
>>
>> I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian
>> partition installed. Not recommended I know but basically works. Until last
>> upgrade when my
On Tue 05 Aug 2014 at 09:36:18 +0200, Artifex Maximus wrote:
> Hello!
>
> I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian
> partition installed. Not recommended I know but basically works. Until last
> upgrade when my GRUB loader only writes GRUB then halts. Or at least
On Tue, Aug 5, 2014 at 4:14 PM, Gary Dale wrote:
> On 05/08/14 03:36 AM, Artifex Maximus wrote:
>
>> Hello!
>>
>> I have a Wheezy system shared with MS XP. GRUB is not in MBR but in
>> Debian partition installed. Not recommended I know but basically works.
>> Until last upgrade when my GRUB loade
On 05/08/14 03:36 AM, Artifex Maximus wrote:
Hello!
I have a Wheezy system shared with MS XP. GRUB is not in MBR but in
Debian partition installed. Not recommended I know but basically
works. Until last upgrade when my GRUB loader only writes GRUB then
halts. Or at least not continue loading.
Hello!
I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian
partition installed. Not recommended I know but basically works. Until last
upgrade when my GRUB loader only writes GRUB then halts. Or at least not
continue loading. No errors just stops. I have tried latest (7.6.0)
On Thu, 2013-03-14 at 00:00 +0100, Sven Joachim wrote:
> dpkg-divert
http://www.debian-administration.org/articles/118
I wasn't aware that it's that easy :D, not especially regarding to the
GRUB issue, but it would have saved me some work with other packages.
OTOH, because I wasn't aware of this,
On Wed 13 Mar 2013 at 23:19:57 +0100, Ralf Mardorf wrote:
> On Wed, 2013-03-13 at 21:16 +0100, Sven Joachim wrote:
> > For anyone who actually thinks about following Ralf's advice: if you
> > do
> > that, it is also necessary to divert /usr/sbin/update-grub and replace
> > it with something harmle
On 2013-03-13 23:19 +0100, Ralf Mardorf wrote:
> On Wed, 2013-03-13 at 21:16 +0100, Sven Joachim wrote:
>> For anyone who actually thinks about following Ralf's advice: if you
>> do
>> that, it is also necessary to divert /usr/sbin/update-grub and replace
>> it with something harmless, say a symli
On Wed, 2013-03-13 at 21:16 +0100, Sven Joachim wrote:
> For anyone who actually thinks about following Ralf's advice: if you
> do
> that, it is also necessary to divert /usr/sbin/update-grub and replace
> it with something harmless, say a symlink to /bin/true. Otherwise the
> local changes to gru
On 2013-03-13 12:59 +0100, Ralf Mardorf wrote:
> On Thu, 2013-03-14 at 00:28 +1300, Chris Bannister wrote:
>> On Wed, Mar 13, 2013 at 10:00:35AM +0100, Ralf Mardorf wrote:
>> > The automation for GRUB2 is crap, edit the grub.cfg manually, then you
>> > also could tidy up grub.cfg and get rid of al
On Wed, 2013-03-13 at 09:07 -0400, Tom H wrote:
> > menuentry 'Ubuntu Quantal, kernel 3.6.5-rt14' {
> > set root='(hd1,9)'; set legacy_hdbias='0'
> > legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
> > 'root=/dev/sdb9' 'ro' 'quiet' ''
> > legacy_initrd '/boot/initrd.img-3.6.5-rt
On Wed, Mar 13, 2013 at 5:00 AM, Ralf Mardorf
wrote:
> On Wed, 2013-03-13 at 04:34 -0400, Tom H wrote:
>> You can set the default in "/etc/default/grub" as
>> 'GRUB_DEFAULT="Debian GNU/Linux (6.0.4)"'.
>
> The automation for GRUB2 is crap, edit the grub.cfg manually, then you
> also could tidy u
On Thu, 2013-03-14 at 00:28 +1300, Chris Bannister wrote:
> On Wed, Mar 13, 2013 at 10:00:35AM +0100, Ralf Mardorf wrote:
> > The automation for GRUB2 is crap, edit the grub.cfg manually, then you
> > also could tidy up grub.cfg and get rid of all the nonsense.
>
> root@tal:~# ls -al /boot/grub/gr
On Wed, Mar 13, 2013 at 10:00:35AM +0100, Ralf Mardorf wrote:
> The automation for GRUB2 is crap, edit the grub.cfg manually, then you
> also could tidy up grub.cfg and get rid of all the nonsense.
root@tal:~# ls -al /boot/grub/grub.cfg
-r--r--r-- 1 root root 3356 Mar 1 22:53 /boot/grub/grub.cfg
On Wed, 2013-03-13 at 04:34 -0400, Tom H wrote:
> On Tue, Mar 12, 2013 at 2:59 PM, Stephen P. Molnar
> wrote:
> >
> > My main Linux computer (64bit CPU) is about six or seven years old now
> > and has had a number of distributions running. As I haven't had any
> > luck with upgrades, I've always
On Tue, Mar 12, 2013 at 2:59 PM, Stephen P. Molnar
wrote:
>
> My main Linux computer (64bit CPU) is about six or seven years old now
> and has had a number of distributions running. As I haven't had any
> luck with upgrades, I've always done a complete installation.
>
> Currently the Grub boot me
On 03/12/2013 02:59 PM, Stephen P. Molnar wrote:
My main Linux computer (64bit CPU) is about six or seven years old now
and has had a number of distributions running. As I haven't had any
luck with upgrades, I've always done a complete installation.
Currently the Grub boot menu has a number of
My main Linux computer (64bit CPU) is about six or seven years old now
and has had a number of distributions running. As I haven't had any
luck with upgrades, I've always done a complete installation.
Currently the Grub boot menu has a number of choices:
openSUSE
Advanced options for openSUSE
op
On Sat, Sep 29, 2012 at 7:50 PM, Brian wrote:
> On Sat 29 Sep 2012 at 18:56:43 +0200, Artifex Maximus wrote:
>
>> On Sat, Sep 29, 2012 at 12:24 PM, Brian wrote:
>> >
>> > At the GRUB prompt press the 'e' key. Please post what you see. There
>> > will probably be a long UUID. To save some typing p
On Sat, Sep 29, 2012 at 7:50 PM, Brian wrote:
> On Sat 29 Sep 2012 at 18:56:43 +0200, Artifex Maximus wrote:
>
>> On Sat, Sep 29, 2012 at 12:24 PM, Brian wrote:
>> >
>> > At the GRUB prompt press the 'e' key. Please post what you see. There
>> > will probably be a long UUID. To save some typing p
On Sat 29 Sep 2012 at 18:56:43 +0200, Artifex Maximus wrote:
> On Sat, Sep 29, 2012 at 12:24 PM, Brian wrote:
> >
> > At the GRUB prompt press the 'e' key. Please post what you see. There
> > will probably be a long UUID. To save some typing put 123 for it.
>
> Thanks. Might I was not clean. Thi
On Sat, Sep 29, 2012 at 12:24 PM, Brian wrote:
> On Fri 28 Sep 2012 at 22:24:16 +0200, Artifex Maximus wrote:
>
>> I would like to move from old 320GB HDD to a new 1TB HDD. I have the
>> following partition structure:
>>
>> sda1 - XP
>> sda2 - Debian 7 x86_64 (boot partition)
>> sda3 - swap
>>
>>
On Fri 28 Sep 2012 at 22:24:16 +0200, Artifex Maximus wrote:
> I would like to move from old 320GB HDD to a new 1TB HDD. I have the
> following partition structure:
>
> sda1 - XP
> sda2 - Debian 7 x86_64 (boot partition)
> sda3 - swap
>
> The GRUB is on the sda2 partition not in the MBR. That's
Hello!
I would like to move from old 320GB HDD to a new 1TB HDD. I have the
following partition structure:
sda1 - XP
sda2 - Debian 7 x86_64 (boot partition)
sda3 - swap
The GRUB is on the sda2 partition not in the MBR. That's why sda2 is
the boot partition. If I set sda1 as boot partition XP run
On Saturday 08 November 2008 16:03, Sjoerd Hiemstra wrote:
> Op Sat, 8 Nov 2008 22:22:15 +0200 Bela Balazs wrote:
> > The two menu.lst entries:
> >
> > title Debian GNU/Linux, kernel 2.6.24-1-686
> > root(hd0,1)
> > kernel /boot/vmlinuz-2.6.24-1-686
> > root=UUID=5dd1
On Sat, Nov 08, 2008 at 11:03:48PM +0100, Sjoerd Hiemstra wrote:
> Op Sat, 8 Nov 2008 22:22:15 +0200 Bela Balazs wrote:
> > The two menu.lst entries:
> >
> > title Debian GNU/Linux, kernel 2.6.24-1-686
> > root(hd0,1)
> > kernel /boot/vmlinuz-2.6.24-1-686
> > root=UU
On Sat, Nov 08, 2008 at 10:22:15PM +0200, Bela Balazs wrote:
> Hello all.
> I installed Debian, but the installer failed to install grub.
I have that problem whenever I install Etch: the installer says its
installing Etch but it doesn't. I end up rebooting the installer in
rescue mode and doing
Op Sat, 8 Nov 2008 22:22:15 +0200 Bela Balazs wrote:
> The two menu.lst entries:
>
> title Debian GNU/Linux, kernel 2.6.24-1-686
> root(hd0,1)
> kernel /boot/vmlinuz-2.6.24-1-686
> root=UUID=5dd1a349-c311-40ca-82f4-a7a39ca134a3 ro
> initrd /boot/initrd.img-2
On Saturday 08 November 2008 21:22:15 Bela Balazs wrote:
> Hello all.
> I installed Debian, but the installer failed to install grub.
Did it fail or din"t propose?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello all.
I installed Debian, but the installer failed to install grub.
I also have Ubuntu, so I installed grub manually by chrooting to the Debian
partition.The two systems are installed on separate disks.
Debian is installed on a SATA disk.I didn't have a Sata controller on the
motherboard so I
On Sat,19.Jul.08, 11:50:10, Andrei Popescu wrote:
> On Sat,19.Jul.08, 10:36:44, Peibol wrote:
>
> [...]
>
> > As you can see hda3 is the last primary partition and it is beyond the
> > last logical partition.
> > Debian + grub is on hda6 and it boots ok. But I have other Linux
> > distributio
On Sat,19.Jul.08, 10:36:44, Peibol wrote:
[...]
> As you can see hda3 is the last primary partition and it is beyond the
> last logical partition.
> Debian + grub is on hda6 and it boots ok. But I have other Linux
> distribution (Suse) installed on hda3 and when I tried to boot it, it
> fai
Hi all
I have a issue with grub using Debian etch. The picture is simple: PC
with only one hard disk (hda) and the following partition table.
cfdisk 2.12r
Disk Drive: /dev/hda
Size: 80026361856 bytes, 80.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 9729
Name Flags Part Type FS Type [Lab
> However, that script DOES exist in the stated path. So what gives with
> this?
That path ("usr/sbin/update-grub") is relative to the current directory of
the process using it. You probably want "/usr/sbin/update-grub".
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently
made the recommended change in /etc/kernel-img.conf to include:
postinst_hook = usr/sbin/update-grub
postrm_hook = usr/sbin/update-grub
When I run the apt-get install, the configuration fails with the error
about
"C
What is the current working directory when this script gets run. You
told it
usr/sbin/update-grub
not
/usr/sbin/update-grub
Note the difference.
I still don't know why this is necessary. During the most recent kernel
upgrade in Etch, I watched carefully for the usual warning message about
not
John Fleming wrote:
I'm trying to install linux-image-2.6.18-6-686 using apt-get. I
recently made the recommended change in /etc/kernel-img.conf to include:
postinst_hook = usr/sbin/update-grub
postrm_hook = usr/sbin/update-grub
When I run the apt-get install, the configuration fails with
On Wed, May 14, 2008 at 09:43:14PM -0400, John Fleming wrote:
> I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently
> made the recommended change in /etc/kernel-img.conf to include:
>
> postinst_hook = usr/sbin/update-grub
> postrm_hook = usr/sbin/update-grub
>
> When I run
On Wed May 14 2008 18:43:14 John Fleming wrote:
> I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently
> made the recommended change in /etc/kernel-img.conf to include:
>
> postinst_hook = usr/sbin/update-grub
> postrm_hook = usr/sbin/update-grub
>
> When I run the apt-get inst
I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently
made the recommended change in /etc/kernel-img.conf to include:
postinst_hook = usr/sbin/update-grub
postrm_hook = usr/sbin/update-grub
When I run the apt-get install, the configuration fails with the error
about
"C
Keith Willis schreef:
> Hi,
>
> Here's a weird one... I've noticed that as soon as the GRUB
> boot-loader runs, I lose my DVD-RW drive. It functions normally if I
> jump into the BIOS setup at boot time, then ceases to respond the
> moment GRUB runs, so that even if I boot into WinXP, the drive
Hi,
Here's a weird one... I've noticed that as soon as the GRUB
boot-loader runs, I lose my DVD-RW drive. It functions normally if I
jump into the BIOS setup at boot time, then ceases to respond the
moment GRUB runs, so that even if I boot into WinXP, the drive does
not show up. Restoring the
On Wed, Jun 07, 2006 at 12:27:34PM -0300, Marcelo Chiapparini wrote:
> Hello,
>
> I have a machine with Windows XP and Debian (sarge) installed. The boot
> manager is GRUB. The machine was working fine, but suddently GRUB
> doesn't boot the system any more. At boot time I get the following:
>
> >
}}Hello,Hi.}} But how can I reinstall GRUB from the Debian CD without}}passing through the partitioner?Probably booting with a live-cd (Knoppix) and chroot-ing!!Hope it help you!Bye
Hello,
I have a machine with Windows XP and Debian (sarge) installed. The boot
manager is GRUB. The machine was working fine, but suddently GRUB
doesn't boot the system any more. At boot time I get the following:
> GRUB loading stage 1.5
> GRUB loading, please wait...
and the system freezes. I w
On Friday 24 February 2006 17:06, Joey Hess wrote:
> Hal Vaughan wrote:
> > It didn't just remove an entry. Update-grub completely overwrites
> > the file so any entries for kernels on other partitions are gone.
>
> ### BEGIN AUTOMAGIC KERNELS LIST
> ## lines between the AUTOMAGIC KERNELS LIST mar
Hal Vaughan wrote:
> It didn't just remove an entry. Update-grub completely overwrites the
> file so any entries for kernels on other partitions are gone.
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script exc
On Saturday 25 February 2006 06:26, Andrei Popescu wrote:
> On Fri, 24 Feb 2006 17:19:19 -0500
> Hal Vaughan <[EMAIL PROTECTED]> wrote:
>
> [snip]
>
> > Okay. That's easy and makes sense. But there is still a problem,
> > but may be more with grub. I went through the man pages of grub
> > and di
On Fri, 24 Feb 2006 17:19:19 -0500
Hal Vaughan <[EMAIL PROTECTED]> wrote:
[snip]
> Okay. That's easy and makes sense. But there is still a problem, but
> may be more with grub. I went through the man pages of grub and did a
> lot of research to figure out how to make the changes I needed. No
On Friday 24 February 2006 16:56, Justin Guerin wrote:
> On Friday 24 February 2006 12:07, Hal Vaughan wrote:
> > On Friday 24 February 2006 13:24, Justin Guerin wrote:
> > > On Thursday 23 February 2006 18:23, Hal Vaughan wrote:
>
> [snip]
>
> > > You aren't given a choice of keeping your old grub
On Friday 24 February 2006 12:07, Hal Vaughan wrote:
> On Friday 24 February 2006 13:24, Justin Guerin wrote:
> > On Thursday 23 February 2006 18:23, Hal Vaughan wrote:
[snip]
> >
> > You aren't given a choice of keeping your old grub config file,
> > because without an update, you can't boot the n
On Friday 24 February 2006 13:24, Justin Guerin wrote:
> On Thursday 23 February 2006 18:23, Hal Vaughan wrote:
> > I posted earlier this week about some problems I had after doing:
> >
> > aptitude update && aptitude upgrade
> >
> > on a Sarge system. It required rebooting and was immediately
> >
On Friday 24 February 2006 11:51, Chris Lale wrote:
> Hal Vaughan wrote:
[snip]
> > A couple of thoughts come to mind. I don't kow if they will help you.
> >
> > 1. Use
> >
> > aptitude update && aptitude dist-upgrade
> >
> > instead of aptitude update && aptitude upgrade. This will deal
> > intell
On Thursday 23 February 2006 18:23, Hal Vaughan wrote:
> I posted earlier this week about some problems I had after doing:
>
> aptitude update && aptitude upgrade
>
> on a Sarge system. It required rebooting and was immediately unbootable
> -- ON SARGE!!! This is the very stuff I am using stable
On Friday 24 February 2006 11:51, Chris Lale wrote:
> Hal Vaughan wrote:
> > I posted earlier this week about some problems I had after doing:
> >
> > aptitude update && aptitude upgrade
> >
> > on a Sarge system. It required rebooting and was immediately
> > unbootable -- ON SARGE!!! This is t
Hal Vaughan wrote:
I posted earlier this week about some problems I had after doing:
aptitude update && aptitude upgrade
on a Sarge system. It required rebooting and was immediately
unbootable -- ON SARGE!!! This is the very stuff I am using stable
to avoid!
I lost a day tracking it dow
I posted earlier this week about some problems I had after doing:
aptitude update && aptitude upgrade
on a Sarge system. It required rebooting and was immediately unbootable -- ON
SARGE!!! This is the very stuff I am using stable to avoid!
I lost a day tracking it down and finally found that
Antonio Rodriguez wrote:
On Wed, Sep 28, 2005 at 03:11:18PM -0500, Mike McCarty wrote:
I know I created a GRUB floppy some time back. I'd have to find
some old notes to remember the exact steps.
Mike
This way from /usr/share/doc/grub/README.Debian.gz
cat /boot/grub/stage1 /boot/grub/stage2
On Wed, Sep 28, 2005 at 03:11:18PM -0500, Mike McCarty wrote:
>
> I know I created a GRUB floppy some time back. I'd have to find
> some old notes to remember the exact steps.
>
> Mike
This way from /usr/share/doc/grub/README.Debian.gz
cat /boot/grub/stage1 /boot/grub/stage2 > /dev/fd0
works f
Antonio Rodriguez wrote:
On Wed, Sep 28, 2005 at 10:34:43AM -0500, Mike McCarty wrote:
described. and since, i've adopted a habit of keeping a GRUB boot disk
around. (it's fairly trivial to create a bootable floppy. only slightly
tougher to create a bootable CD.) i then use grub shell, to do
hi ya
On Wed, 28 Sep 2005, Mike McCarty wrote:
:-)
> > you keep going to filesytem
>
> No, you do.
i see we're assumign too many stuff ..
i never once said aything but servo info being the
same as fs info .. etc..etc
> > am not talking about the head alignment and gaps or anything
>
> B
Alvin Oga wrote:
hi ya
On Wed, 28 Sep 2005, Mike McCarty wrote:
[snip]
Yes, I'm talking about servo data, which cannot be seen
by dd or any other normal (or even driver level) accesses.
i think we;re talking about the different kidns of servo
data ... created/maintained at different lev
On Wed, Sep 28, 2005 at 10:34:43AM -0500, Mike McCarty wrote:
> >described. and since, i've adopted a habit of keeping a GRUB boot disk
> >around. (it's fairly trivial to create a bootable floppy. only slightly
> >tougher to create a bootable CD.) i then use grub shell, to do a 'setup'
> >of
>
hi ya
On Wed, 28 Sep 2005, Mike McCarty wrote:
> You are obviously smart
> and intelligent, but you weren't THERE. I was.
i been playing with them removable 14" disk platters
and stripping um and reassemble um and stick it back
into the dg/dec/si washing machines
> > the disk controller on th
anoop aryal wrote:
On Tuesday 27 September 2005 07:05 pm, Jeremy Merritt wrote:
I have been having a problem getting my GRUB
bootloader to return on boot. No matter what I do, it
keeps going to XP. I consulted with other people on
this list and got some good input. But have run into a
dead end
Alvin Oga wrote:
hi ya mike
Hi yourself. Glad to meet you.
I hope this message doesn't seem pugnacious. It isn't intended
to be. But your response seems to me to contain some factual
and comprehensional errors. Since this is a technical forum,
I don't feel comfortable allowing what I percieve
On Tuesday 27 September 2005 07:05 pm, Jeremy Merritt wrote:
> I have been having a problem getting my GRUB
> bootloader to return on boot. No matter what I do, it
> keeps going to XP. I consulted with other people on
> this list and got some good input. But have run into a
> dead end again. Can so
hi ya mike
On Tue, 27 Sep 2005, Mike McCarty wrote:
> >
> > the "tracking info" is dependant on the filesystem
>
> It is not.
i beg to differ ... different fs has different disk
structure to tune itself for various things to make
it better or worst than other fs
> It is used by the uControll
Mike McCarty wrote:
[...]
So, here is a brief tutorial on disc partitioning
and how boot proceeds.
[...]
Thanks for the explanation, it was very useful.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Jeremy Merritt wrote:
Wow, what a great explanation. I have read through it,
but am going to do another to make sure it's all taken
in. Thanks.
Thank you. I realize that it is very condensed and long. But even
so, it glosses over quite a bit of detail (e.g. LBA and the fact
that one can actuall
Alvin Oga wrote:
hi ya mike
:-) i'm even more sleepy now :-)
HEY! I SAID it was long!
:-)
but, some comments
On Tue, 27 Sep 2005, Mike McCarty wrote:
I think you need a little more information about how
boot is accomplished on IBM PC style computers.
if a user can't get the machine
hi ya mike
:-) i'm even more sleepy now :-)
but, some comments
On Tue, 27 Sep 2005, Mike McCarty wrote:
> I think you need a little more information about how
> boot is accomplished on IBM PC style computers.
if a user can't get the machine to boot .. this much
detail is probably more than th
Wow, what a great explanation. I have read through it,
but am going to do another to make sure it's all taken
in. Thanks.
--- Mike McCarty <[EMAIL PROTECTED]> wrote:
> Jeremy Merritt wrote:
> > I have been having a problem getting my GRUB
> > bootloader to return on boot. No matter what I do,
> i
Mike McCarty wrote:
[some stuff about formatting discs and boot]
I forgot one more layer of format: OS install.
A volume may have a file system without an OS
on it.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have fo
Jeremy Merritt wrote:
I have been having a problem getting my GRUB
bootloader to return on boot. No matter what I do, it
keeps going to XP. I consulted with other people on
this list and got some good input. But have run into a
dead end again. Can someone analyze these steps and
tell me what I'm
If you can boot from cdrom, use cfdisk to toggle the boot properties of
the partitions (as root, of course).
Art Edwards
Jeremy Merritt wrote:
If having multiple partitions is the problem or part
of the problem, how do I make /dev/hda2 bootable and
make the others not bootable? Is that the
On Tue, 27 Sep 2005, Jeremy Merritt wrote:
> If having multiple partitions is the problem or part
> of the problem,
NOT the problem
> how do I make /dev/hda2 bootable and
> make the others not bootable?
take it out with the bios so that it doesn't check it
or
# delete the M
Andy wrote:
>
> On Tuesday 27 September 2005 12:42, Tom Pfeifer wrote:
> > Since your WinXP on /dev/hda1 is a FAT32 partition, one thing that might
> > work is to use the backup boot sector that is kept on FAT32 file systems
> > to restore the WinXP boot sector on /dev/hda1.
> >
> > dd if=/dev/hda
If having multiple partitions is the problem or part
of the problem, how do I make /dev/hda2 bootable and
make the others not bootable? Is that the only thing
that needs to be done in addition to the other steps?
--- Art Edwards <[EMAIL PROTECTED]>
wrote:
> Jeremy Merritt wrote:
>
> >I have been
Jeremy Merritt wrote:
I have been having a problem getting my GRUB
bootloader to return on boot. No matter what I do, it
keeps going to XP. I consulted with other people on
this list and got some good input. But have run into a
dead end again. Can someone analyze these steps and
tell me what I'm
I have been having a problem getting my GRUB
bootloader to return on boot. No matter what I do, it
keeps going to XP. I consulted with other people on
this list and got some good input. But have run into a
dead end again. Can someone analyze these steps and
tell me what I'm doing wrong, or what I n
On Tuesday 27 September 2005 12:42, Tom Pfeifer wrote:
> Since your WinXP on /dev/hda1 is a FAT32 partition, one thing that might
> work is to use the backup boot sector that is kept on FAT32 file systems
> to restore the WinXP boot sector on /dev/hda1.
>
> dd if=/dev/hda1 of=/dev/hda1 bs=512 count
Andy wrote:
>
> On Monday 26 September 2005 3:17, Dennis Stosberg wrote:
> > Windows XP is on /dev/hda, which is (hd0,0) in GRUB's notation. So,
> > if you install the GRUB boot sector into /dev/hda1, you overwrite
> > Windows XP's boot sector in that partition. That means you won't be
> > able
On Monday 26 September 2005 3:19, Roby wrote:
> Add the hide/unhide commands shown below:
> > title Windows NT/2000/XP
>
> hide (hd0,4)
> unhide (hd0,0)
>
> > root(hd0,0)
> > savedefault
> > makeactive
> > chainloader +1
> >
> > title Windows 95/98/Me
>
> hide
On Monday 26 September 2005 3:17, Dennis Stosberg wrote:
> Windows XP is on /dev/hda, which is (hd0,0) in GRUB's notation. So,
> if you install the GRUB boot sector into /dev/hda1, you overwrite
> Windows XP's boot sector in that partition. That means you won't be
> able to boot Windows XP at all
Add the hide/unhide commands shown below:
> title Windows NT/2000/XP
hide (hd0,4)
unhide (hd0,0)
> root(hd0,0)
> savedefault
> makeactive
> chainloader +1
>
> title Windows 95/98/Me
hide (hd0,0)
unhide (hd0,4)
> root(hd0,4)
> savedefault
> makea
Am 26.09.2005 um 14:17 schrieb Andy:
> Anyway, here is the deal:
> I have a few drives, one with win98 (don't ask!), one with win xp, and one
> with Debian Sid. I had grub happily booting everything until recently when
> WinXP experienced some HDD corruption and I had to do a repair. Obviously,
I'm sure that to many people on this list, not being able to run WinXP would
be considered a good thing (TM), but trust me, I have lots of important
reasons for needing it :)
Anyway, here is the deal:
I have a few drives, one with win98 (don't ask!), one with win xp, and one
with Debian Sid. I
On Tue, 12 Jul 2005, Eugen Wintersberger wrote:
> (I'm not sure if this was the exact error message). If I do the
> same installation procedure but install LILO the machine reboots as
> expected (means that the bootloader works).
if lilo works ( boots properly ), than there is nothing wrong wi
Hi there
I have a problem with GRUB on one of our school machines.
When I install Sarge with default settings (meaning I press only
enter at all options during installation) and install GRUB into the MBR
the machine cannot reboot. GRUB reports something like
GRUB hardisk error!
(I'm not sure
On Wed, Jun 22, 2005 at 08:30:47PM +0100, Chris Robinson wrote:
> Hi
>
> I was running woody on my hda disk (120GB). I got a new disk 20GB(hdb).
>
> So I thought I would run Sarge on hdb, and mount my woody disk as required
> to
> get any files I needed. I therefore do not need dual boot. I
Hi
I was running woody on my hda disk (120GB). I got a new disk 20GB(hdb).
So I thought I would run Sarge on hdb, and mount my woody disk as
required to get any files I needed. I therefore do not need dual boot.
I can install Sarge (3.10) fine but then I get to the question of where
to in
Have a buddy that just called. He's having trouble getting debian
testing installed. On first reboot, He gets no grub screen at all, the
system simply reboots. As I recall, he has a epox board with onboard
raid and the hard drive is hooked to the raid port. (He's a combo cd and
a regular cd-rom
1 - 100 of 154 matches
Mail list logo
