Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #225862 > unrolled thread
| Started by | Long Wind <longwind2@yahoo.com> |
|---|---|
| First post | 2020-08-05 02:10 +0200 |
| Last post | 2020-08-06 02:50 +0200 |
| Articles | 9 — 6 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
how to quickly recover buster boot loader Long Wind <longwind2@yahoo.com> - 2020-08-05 02:10 +0200
Re: how to quickly recover buster boot loader Greg Wooledge <wooledg@eeg.ccf.org> - 2020-08-05 14:20 +0200
Re: how to quickly recover buster boot loader Long Wind <longwind2@yahoo.com> - 2020-08-05 15:30 +0200
Re: how to quickly recover buster boot loader Andrew Cater <amacater@gmail.com> - 2020-08-05 17:20 +0200
Re: how to quickly recover buster boot loader Brian <ad44@cityscape.co.uk> - 2020-08-05 18:50 +0200
Re: how to quickly recover buster boot loader Long Wind <longwind2@yahoo.com> - 2020-08-05 20:10 +0200
[OT] CentOS 6 [Was: Re: how to quickly recover buster boot loader] Liam O'Toole <liam.p.otoole@gmail.com> - 2020-08-05 18:20 +0200
Re: [OT] CentOS 6 [Was: Re: how to quickly recover buster boot loader] Long Wind <longwind2@yahoo.com> - 2020-08-05 20:00 +0200
Re: [OT] CentOS 6 [Was: Re: how to quickly recover buster boot loader] David Wright <deblis@lionunicorn.co.uk> - 2020-08-06 02:50 +0200
| From | Long Wind <longwind2@yahoo.com> |
|---|---|
| Date | 2020-08-05 02:10 +0200 |
| Subject | how to quickly recover buster boot loader |
| Message-ID | <AAfah-6Dm-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
i have win7 at sda1 and buster at sda2i install centos 6 at sda3, it can boot win7, can't see busteri mean i can't boot buster now is there some rescue image that can be written to bootable usb disk? or do you know how to config centos 6 boot loader?is buster's boot code installed at sda2 by default?
[toc] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-08-05 14:20 +0200 |
| Message-ID | <AAqyJ-58e-7@gated-at.bofh.it> |
| In reply to | #225862 |
On Wed, Aug 05, 2020 at 12:04:48AM +0000, Long Wind wrote: > i have win7 at sda1 and buster at sda2i install centos 6 at sda3, it can boot win7, can't see busteri mean i can't boot buster now > is there some rescue image that can be written to bootable usb disk? > or do you know how to config centos 6 boot loader?is buster's boot code installed at sda2 by default? I'm going to assume you're using Legacy/MBR booting, because I don't know enough about UEFI to answer this question in that universe. If you're trying to multi-boot several different Linuxes from one hard drive, the first thing you have to do is make a decision. You must choose which Linux will be in control of the boot loader. Let's say you choose Debian. (If you choose something else, stop reading now, and go ask the other OS's mailing list for help.) First step, then, will be to boot into Debian successfully. For this, you'll probably need to boot into whatever Linux you *can* boot, whether that's the CentOS on the hard drive, or a rescue CD, or whatever. Once you're booted into *a* Linux, then you can do the chroot dance to mount the Debian file system(s) underneath that. According to the IRC bot factoid, that dance goes something like this: Mount your root filesystem with "mount -t ext2 /dev/whatever /target" and make /dev, /proc and /sys usable with "mount --rbind --make-rslave /dev /target/dev ; mount -t proc none /target/proc ; mount -t sysfs none /target/sys". You can then chroot into the system with "chroot /target". There may be other dances that will also work. Once you're chrooted into Debian running under some sort of Linux kernel, first make sure the os-prober package is installed. Then you can write Debian's GRUB into the master boot recor, by running grub-install. After doing grub-install, you should have GRUB in the hard drive's master boot record and it should be configured to read the menu in Debian's version of the /boot directory. In order to make the Debian GRUB menu point to all of the operating systems on your hard drive, make sure os-prober is installed (yes, I know, I already said it; I'm saying it again). Then run update-grub. Exit out of the chroot, unmount it, and reboot. You should get Debian's GRUB menu, and you should be able to boot into Debian, at the very least. If the Debian GRUB menu doesn't contain all of the operating systems that you think it should contain, then you'll have to poke around in the update-grub and os-prober internals and figure out what's wrong. Once you get everything working, you'll need to remember that you have chosen to make Debian the controller of the boot loader. Every time you make a kernel change to any of the *other* Linuxes on your hard drive, you'll need to boot into Debian, and run update-grub, to pick up the changes in the other Linuxes.
[toc] | [prev] | [next] | [standalone]
| From | Long Wind <longwind2@yahoo.com> |
|---|---|
| Date | 2020-08-05 15:30 +0200 |
| Message-ID | <AArEu-5Kf-5@gated-at.bofh.it> |
| In reply to | #225887 |
[Multipart message — attachments visible in raw view] — view raw
Thank Greg!
but chroot dance is new to me, it doesn't seem easyit involves many steps (commands)a small error will lead to failure
i install centos just for funi can install lubuntu at sda3 and it can boot buster
On Wednesday, August 5, 2020, 8:15:14 PM GMT+8, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
On Wed, Aug 05, 2020 at 12:04:48AM +0000, Long Wind wrote:
> i have win7 at sda1 and buster at sda2i install centos 6 at sda3, it can boot win7, can't see busteri mean i can't boot buster now
> is there some rescue image that can be written to bootable usb disk?
> or do you know how to config centos 6 boot loader?is buster's boot code installed at sda2 by default?
I'm going to assume you're using Legacy/MBR booting, because I don't know
enough about UEFI to answer this question in that universe.
If you're trying to multi-boot several different Linuxes from one
hard drive, the first thing you have to do is make a decision. You
must choose which Linux will be in control of the boot loader.
Let's say you choose Debian. (If you choose something else, stop
reading now, and go ask the other OS's mailing list for help.)
First step, then, will be to boot into Debian successfully. For this,
you'll probably need to boot into whatever Linux you *can* boot, whether
that's the CentOS on the hard drive, or a rescue CD, or whatever.
Once you're booted into *a* Linux, then you can do the chroot dance
to mount the Debian file system(s) underneath that.
According to the IRC bot factoid, that dance goes something like
this:
Mount your root filesystem with "mount -t ext2 /dev/whatever /target"
and make /dev, /proc and /sys usable with "mount --rbind --make-rslave
/dev /target/dev ; mount -t proc none /target/proc ; mount -t sysfs none
/target/sys". You can then chroot into the system with "chroot /target".
There may be other dances that will also work.
Once you're chrooted into Debian running under some sort of Linux
kernel, first make sure the os-prober package is installed. Then you can
write Debian's GRUB into the master boot recor, by running grub-install.
After doing grub-install, you should have GRUB in the hard drive's
master boot record and it should be configured to read the menu in
Debian's version of the /boot directory.
In order to make the Debian GRUB menu point to all of the operating
systems on your hard drive, make sure os-prober is installed (yes, I
know, I already said it; I'm saying it again). Then run update-grub.
Exit out of the chroot, unmount it, and reboot. You should get Debian's
GRUB menu, and you should be able to boot into Debian, at the very
least.
If the Debian GRUB menu doesn't contain all of the operating systems
that you think it should contain, then you'll have to poke around in
the update-grub and os-prober internals and figure out what's wrong.
Once you get everything working, you'll need to remember that you have
chosen to make Debian the controller of the boot loader. Every time
you make a kernel change to any of the *other* Linuxes on your hard
drive, you'll need to boot into Debian, and run update-grub, to pick
up the changes in the other Linuxes.
[toc] | [prev] | [next] | [standalone]
| From | Andrew Cater <amacater@gmail.com> |
|---|---|
| Date | 2020-08-05 17:20 +0200 |
| Message-ID | <AAtmV-6P3-7@gated-at.bofh.it> |
| In reply to | #225890 |
[Multipart message — attachments visible in raw view] — view raw
Boot from Debian install media. Use rescue mode. Mount Debian partition when prompted. Run os-prober and update-grub then exit. Machine should reboot into Debian. On Wed, Aug 5, 2020 at 1:28 PM Long Wind <longwind2@yahoo.com> wrote: > Thank Greg! > but chroot dance is new to me, it doesn't seem easy > it involves many steps (commands) > a small error will lead to failure > > i install centos just for fun > i can install lubuntu at sda3 and it can boot buster > > > > > On Wednesday, August 5, 2020, 8:15:14 PM GMT+8, Greg Wooledge < > wooledg@eeg.ccf.org> wrote: > > > On Wed, Aug 05, 2020 at 12:04:48AM +0000, Long Wind wrote: > > > i have win7 at sda1 and buster at sda2i install centos 6 at sda3, it can > boot win7, can't see busteri mean i can't boot buster now > > is there some rescue image that can be written to bootable usb disk? > > or do you know how to config centos 6 boot loader?is buster's boot code > installed at sda2 by default? > > > I'm going to assume you're using Legacy/MBR booting, because I don't know > enough about UEFI to answer this question in that universe. > > If you're trying to multi-boot several different Linuxes from one > hard drive, the first thing you have to do is make a decision. You > must choose which Linux will be in control of the boot loader. > > Let's say you choose Debian. (If you choose something else, stop > reading now, and go ask the other OS's mailing list for help.) > > First step, then, will be to boot into Debian successfully. For this, > you'll probably need to boot into whatever Linux you *can* boot, whether > that's the CentOS on the hard drive, or a rescue CD, or whatever. > > Once you're booted into *a* Linux, then you can do the chroot dance > to mount the Debian file system(s) underneath that. > > According to the IRC bot factoid, that dance goes something like > this: > > Mount your root filesystem with "mount -t ext2 /dev/whatever /target" > and make /dev, /proc and /sys usable with "mount --rbind --make-rslave > /dev /target/dev ; mount -t proc none /target/proc ; mount -t sysfs none > /target/sys". You can then chroot into the system with "chroot /target". > > There may be other dances that will also work. > > Once you're chrooted into Debian running under some sort of Linux > kernel, first make sure the os-prober package is installed. Then you can > write Debian's GRUB into the master boot recor, by running grub-install. > > After doing grub-install, you should have GRUB in the hard drive's > master boot record and it should be configured to read the menu in > Debian's version of the /boot directory. > > In order to make the Debian GRUB menu point to all of the operating > systems on your hard drive, make sure os-prober is installed (yes, I > know, I already said it; I'm saying it again). Then run update-grub. > > Exit out of the chroot, unmount it, and reboot. You should get Debian's > GRUB menu, and you should be able to boot into Debian, at the very > least. > > If the Debian GRUB menu doesn't contain all of the operating systems > that you think it should contain, then you'll have to poke around in > the update-grub and os-prober internals and figure out what's wrong. > > Once you get everything working, you'll need to remember that you have > chosen to make Debian the controller of the boot loader. Every time > you make a kernel change to any of the *other* Linuxes on your hard > drive, you'll need to boot into Debian, and run update-grub, to pick > up the changes in the other Linuxes. > > >
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2020-08-05 18:50 +0200 |
| Message-ID | <AAuM2-7xr-5@gated-at.bofh.it> |
| In reply to | #225895 |
On Wed 05 Aug 2020 at 15:14:33 +0000, Andrew Cater wrote: > Boot from Debian install media. Use rescue mode. Mount Debian partition > when prompted. Run os-prober and update-grub then exit. Machine should > reboot into Debian. No need to run os-prober; update-grub does it. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Long Wind <longwind2@yahoo.com> |
|---|---|
| Date | 2020-08-05 20:10 +0200 |
| Message-ID | <AAw1r-8sw-3@gated-at.bofh.it> |
| In reply to | #225895 |
[Multipart message — attachments visible in raw view] — view raw
Thank Andrew and Brian!i will try rescue mode.
On Wednesday, August 5, 2020, 11:14:46 PM GMT+8, Andrew Cater <amacater@gmail.com> wrote:
Boot from Debian install media. Use rescue mode. Mount Debian partition when prompted. Run os-prober and update-grub then exit. Machine should reboot into Debian.
On Wed, Aug 5, 2020 at 1:28 PM Long Wind <longwind2@yahoo.com> wrote:
Thank Greg!
but chroot dance is new to me, it doesn't seem easyit involves many steps (commands)a small error will lead to failure
i install centos just for funi can install lubuntu at sda3 and it can boot buster
On Wednesday, August 5, 2020, 8:15:14 PM GMT+8, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
On Wed, Aug 05, 2020 at 12:04:48AM +0000, Long Wind wrote:
> i have win7 at sda1 and buster at sda2i install centos 6 at sda3, it can boot win7, can't see busteri mean i can't boot buster now
> is there some rescue image that can be written to bootable usb disk?
> or do you know how to config centos 6 boot loader?is buster's boot code installed at sda2 by default?
I'm going to assume you're using Legacy/MBR booting, because I don't know
enough about UEFI to answer this question in that universe.
If you're trying to multi-boot several different Linuxes from one
hard drive, the first thing you have to do is make a decision. You
must choose which Linux will be in control of the boot loader.
Let's say you choose Debian. (If you choose something else, stop
reading now, and go ask the other OS's mailing list for help.)
First step, then, will be to boot into Debian successfully. For this,
you'll probably need to boot into whatever Linux you *can* boot, whether
that's the CentOS on the hard drive, or a rescue CD, or whatever.
Once you're booted into *a* Linux, then you can do the chroot dance
to mount the Debian file system(s) underneath that.
According to the IRC bot factoid, that dance goes something like
this:
Mount your root filesystem with "mount -t ext2 /dev/whatever /target"
and make /dev, /proc and /sys usable with "mount --rbind --make-rslave
/dev /target/dev ; mount -t proc none /target/proc ; mount -t sysfs none
/target/sys". You can then chroot into the system with "chroot /target".
There may be other dances that will also work.
Once you're chrooted into Debian running under some sort of Linux
kernel, first make sure the os-prober package is installed. Then you can
write Debian's GRUB into the master boot recor, by running grub-install.
After doing grub-install, you should have GRUB in the hard drive's
master boot record and it should be configured to read the menu in
Debian's version of the /boot directory.
In order to make the Debian GRUB menu point to all of the operating
systems on your hard drive, make sure os-prober is installed (yes, I
know, I already said it; I'm saying it again). Then run update-grub.
Exit out of the chroot, unmount it, and reboot. You should get Debian's
GRUB menu, and you should be able to boot into Debian, at the very
least.
If the Debian GRUB menu doesn't contain all of the operating systems
that you think it should contain, then you'll have to poke around in
the update-grub and os-prober internals and figure out what's wrong.
Once you get everything working, you'll need to remember that you have
chosen to make Debian the controller of the boot loader. Every time
you make a kernel change to any of the *other* Linuxes on your hard
drive, you'll need to boot into Debian, and run update-grub, to pick
up the changes in the other Linuxes.
[toc] | [prev] | [next] | [standalone]
| From | Liam O'Toole <liam.p.otoole@gmail.com> |
|---|---|
| Date | 2020-08-05 18:20 +0200 |
| Subject | [OT] CentOS 6 [Was: Re: how to quickly recover buster boot loader] |
| Message-ID | <AAuj0-7nY-15@gated-at.bofh.it> |
| In reply to | #225862 |
On Wed, 05 Aug, 2020 at 00:04:48 +0000, Long Wind wrote: > i have win7 at sda1 and buster at sda2 > i install centos 6 at sda3, it can boot win7, can't see buster > i mean i can't boot buster now > is there some rescue image that can be written to bootable usb disk? > or do you know how to config centos 6 boot loader? > is buster's boot code installed at sda2 by default? An off-topic question: do you have a particular need for CentOS 6? It reaches its end of life in November.
[toc] | [prev] | [next] | [standalone]
| From | Long Wind <longwind2@yahoo.com> |
|---|---|
| Date | 2020-08-05 20:00 +0200 |
| Subject | Re: [OT] CentOS 6 [Was: Re: how to quickly recover buster boot loader] |
| Message-ID | <AAvRM-89R-21@gated-at.bofh.it> |
| In reply to | #225898 |
[Multipart message — attachments visible in raw view] — view raw
no, i try centos for fun and fedora and opensusemy hardware is old and old software usually require less memory/diskthese old software are new to me, i might discover interesting app
http://archive.debian.org/http://archives.fedoraproject.org/
i don't think update is important
On Thursday, August 6, 2020, 12:15:04 AM GMT+8, Liam O'Toole <liam.p.otoole@gmail.com> wrote:
On Wed, 05 Aug, 2020 at 00:04:48 +0000, Long Wind wrote:
> i have win7 at sda1 and buster at sda2
> i install centos 6 at sda3, it can boot win7, can't see buster
> i mean i can't boot buster now
> is there some rescue image that can be written to bootable usb disk?
> or do you know how to config centos 6 boot loader?
> is buster's boot code installed at sda2 by default?
An off-topic question: do you have a particular need for CentOS 6? It
reaches its end of life in November.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-08-06 02:50 +0200 |
| Subject | Re: [OT] CentOS 6 [Was: Re: how to quickly recover buster boot loader] |
| Message-ID | <AACgx-3C6-3@gated-at.bofh.it> |
| In reply to | #225907 |
On Wed 05 Aug 2020 at 17:51:36 (+0000), Long Wind wrote: > no, i try centos for fun and fedora and opensuse > my hardware is old and old software usually require less memory/disk > these old software are new to me, i might discover interesting app > http://archive.debian.org/ > http://archives.fedoraproject.org/ > i don't think update is important Bear in mind that when you install some distribution "just for fun", then unless you take precautions, it will naturally take control of the boot process. So you probably want to have a well-practised method standing by for restoring your preferred distribution's. Cheers, David.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web