t [re]boot.
What's the best way to make sure I have a 'get out' if it all goes
pear shaped?
Yes, I know that question about grub-install and grub-mkconfig seems
rather naive but I have to say none of the tutorials, man pages or
other help that I could find actually clarified this.
--
Chris Green
On Sun, Nov 17, 2019 at 03:27:36PM -0800, Randy Goldenberg wrote:
> On Sunday November 17, 2019, Chris Green wrote:
>
> [...]
>
> > I want to add a new SSD to my current desktop system. This in itself
> > isn't a major problem, I've done similar things before w
motivation may include some (but not all) multi-boot setups, or the
> lack of NVMe support by the UEFI firmware in legacy mode.
>
OP here, I've looked and the BIOS doesn't support EFI anyway so the
issue is decided form me anyway! :-)
--
Chris Green
On Mon, Nov 18, 2019 at 08:20:44PM +0100, Pascal Hambourg wrote:
> Le 17/11/2019 à 20:20, Chris Green a écrit :
> >
> > I want to add a new SSD to my current desktop system. This in itself
> > isn't a major problem, I've done similar things before without
> >
should be able to boot from your newly created partition.
> However, you'll need to
> dpkg-reconfigure grub-pc
> (or however the package's name is on xubuntu)
> so that future updates of grub get installed on the right drive.
>
Thank you, that sounds really, really useful.
--
Chris Green
'll need to
> > dpkg-reconfigure grub-pc
> > (or however the package's name is on xubuntu)
> > so that future updates of grub get installed on the right drive.
>
> Good catch. Actually if you are familiar with using chroot you could even do
> this after chrooting to the new root filesystem instead of running
> grub-install and grub-mkconfig (or update-grub) as it will also perform both
> operations.
>
--
Chris Green
dd the ability to boot the xubuntu 19.10 installed on
/dev/nvme0n1p2 to the existing /boot. How do I do this?
--
Chris Green
(a spare SATA spinning disk) boots OK. The device UUID is
correct for /dev/nvme0n1p2 so I guess grub isn't able to read the NVME
SSD for some reason. How do I get over *this* issue! :-)
--
Chris Green
On Thu, Nov 21, 2019 at 09:51:03PM +0100, Pascal Hambourg wrote:
> Le 21/11/2019 à 20:46, Chris Green a écrit :
> >
> > However trying to boot 19.10 from /dev/nvme0n1p2 fails with "No such
> > device c6ca1c2d-4837-48b9-8fa6-1ef47251d7b7" whereas booting it f
On Thu, Nov 21, 2019 at 09:27:48PM +, Chris Green wrote:
> On Thu, Nov 21, 2019 at 09:51:03PM +0100, Pascal Hambourg wrote:
> > Le 21/11/2019 à 20:46, Chris Green a écrit :
> > >
> > > However trying to boot 19.10 from /dev/nvme0n1p2 fails with "No such
>
On Thu, Nov 21, 2019 at 11:43:49PM +0100, Pascal Hambourg wrote:
> Le 21/11/2019 à 22:39, Chris Green a écrit :
> >
> > I.e. does grub insist on its configuration/files being in a directory
> > called /boot?
>
> No, but Ubuntu, like many distributions, puts kernel fi
/dev/sda which prevents my
xubuntu 19.04 from booting (and, yes, I did plug all the drives back
in). Fortunately unplugging /dev/sda has let 19.04 boot now, so I'm
back working but not much nearer getting 19.10 installed.
--
Chris Green
On Fri, Nov 22, 2019 at 07:45:56AM -0500, Nathan Stratton Treadway wrote:
> On Fri, Nov 22, 2019 at 10:18:34 +0000, Chris Green wrote:
> > I run the xubuntu 19.10 installation selecting "something else" at the
> > disk partitioning stage. I have partitioned as follows:-
)
more than one OS installed. Presumably only one grub.cfg gets used
even though there is more than one. How does the initial boot process
(starting with MBR etc.) and created by grub-install decide which
/boot it should use (and is it easy to change which /boot it goes to?).
--
Chris Green
On Fri, Nov 22, 2019 at 10:40:18PM +0100, Pascal Hambourg wrote:
>
>
> Le 22/11/2019 à 18:08, Chris Green a écrit :
> >
> > grub-install installs the 'invisible' bits of grub like the MBR and
> > the code executed after the MBR. These reside on parts of
yone, much appreciated.
--
Chris Green
18036 88742 17% /1904
/dev/sdc1 ext4938772 168648 722415 19% /bak
I want to put /boot where /1904 is and then I can remove sda1. (/1904
was the old OS installation that I mounted for reference while I
configured my new xubuntu 19.10 installation on /dev/nvme0n1p2).
--
Chris Green
basically as above, copy /boot files to new disk (which
would become /boot) using rsync. Then the umount/mount, grub-install
and update-grub. Modify /etc/fstab and that's it.
--
Chris Green
04: Linux kernel ARM boot executable zImage
(little-endian)
vmlinuz-4.19.31-armv7-x31:Linux kernel ARM boot executable zImage
(little-endian)
I wonder if the system can't unpack the LZ4 compressed file so chooses
the other.
--
Chris Green
On Wed, Jan 15, 2020 at 10:32:48AM +, Chris Green wrote:
> initrd.img-4.14.108-ti-r104: gzip compressed data, from Unix, original >
> size modulo 2^32 13529600
> initrd.img-4.19.31-armv7-x31: LZ4 compressed data (v0.1-v0.9)
>
> I wonder if the system can't un
d all the above threads in the list
archive. If you can't get to them for some reason I can send them from
my mail folder to you if you want.
--
Chris Green
the SSD?
>
Mine boots pretty fast, /dev/sdb is what *used* to be my system disk
and is a SATA SSD but my first pass at sorting this out had boot on a
spinning hard disk and while it is somewhat faster on the SATA SSD it
doesn't make a huge difference. There's not much has to be read off
/boot.
--
Chris Green
On Wed, Jan 06, 2021 at 10:32:40AM -0800, Robert Furber via Support requests
for the GRand Unified Bootloader wrote:
>
> On 2020-12-30 1:48 a.m., Chris Green wrote:
> > :
> > > Hm.. It is an old (2012) PC with BIOS. To my knowledge, it is not
> > > aware
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 312580095 312578048 149.1G 83 Linux
The system has booted from /dev/sda1 (its internal disk drive), why does it
choose to boot from this drive rather than /dev/sda1 since both are marked
bootable?
--
Chris Green
is up and
running though.
So what one needs to do is to create a /boot partition on the old
spinning hard disk which will then be able to see and mount the new
SSD which has the / partition on it.
What's the easiest way of doing this, preferably without doing a new
install?
--
Chris Green
7;s the easiest (and least error prone) procedure for doing this?
--
Chris Green
ap I can simply boot the xubuntu 20.10 on /dev/sdc1 and everything
will still work as before (if a little more slowly).
--
Chris Green
On Wed, May 19, 2021 at 01:02:38PM +0100, Chris Green wrote:
> If I simply copy / to /mnt and also copy /boot to / how do I get grub
That should be "... copy /boot to /mnt " of course.
--
Chris Green
On Fri, May 21, 2021 at 08:52:18AM +0200, Pascal Hambourg wrote:
> Le 19/05/2021 à 14:02, Chris Green a écrit :
> >
> > I've realised the easiest thing to do will be to simply duplicate my
> > existing xubuntu 20.10 installation on another partition. As before
> >
On Fri, May 21, 2021 at 01:10:27PM +0200, Pascal Hambourg wrote:
> Le 21/05/2021 à 10:24, Chris Green a écrit :
> >
> > How should I do the changes to /boot/grub/grub.cfg? Do I edit
> > /etc/default/grub and then run grub-mkconfig? However I don't really
> > se
these thoughts and ideas, I'm slowly working my way
towards a workable (for me) solution and every little helps. :-)
--
Chris Green
h the above sequence I've entered into grub. Is it
likely that the above is all that's needed or would one expect more?
Any/all sort of help would be most welcome.
--
Chris Green
On Fri, Jun 25, 2021 at 03:39:29PM +0100, Peter Hillier-Brook wrote:
> On 25/06/2021 12:53, Chris Green wrote:
> > I am trying to create a Virtualbox guest from a real physical Windows
> > 10 image.
> >
> > The initial problem is that the W10 image is from a machine
On Fri, Jun 25, 2021 at 12:53:51PM +0100, Chris Green wrote:
> I am trying to create a Virtualbox guest from a real physical Windows
> 10 image.
>
> The initial problem is that the W10 image is from a machine that also
> runs xubuntu Linux and thus the boot sequence is under grub
On Sun, Jun 27, 2021 at 03:50:27PM +0200, Pascal Hambourg wrote:
> Le 27/06/2021 à 09:48, Chris Green a écrit :
> > >
> > > chainloader /EFI/Microsoft/Boot/bootmgfw.efi
> (...)
> > While I'm here, the above sequence seems to be remembered somehow as
On Sun, Jun 27, 2021 at 05:24:00PM +0200, Pascal Hambourg wrote:
> Le 27/06/2021 à 16:45, Chris Green a écrit :
> > On Sun, Jun 27, 2021 at 03:50:27PM +0200, Pascal Hambourg wrote:
> > >
> > > Maybe Windows boot
> > > manager modified EFI boot e
fb7098ee8 /bakext4relatime
0 2
#
#
# /scratch (/dev/sda2) spare space on 128Gb SATA SSD
#
UUID=7b4de2e8-755d-4cb4-a8cb-82c493d5545a/scratch ext4 relatime
0 2
--
Chris Green
On Tue, Aug 23, 2022 at 01:39:09AM -0500, Glenn Washburn wrote:
> Hi Chris,
>
> On Mon, 1 Aug 2022 14:41:14 +0100
> Chris Green wrote:
>
> > A year or two ago I got a lot of help from this list when I installed
> > an NVME SSD on my system and, because it wasn't
On Tue, Aug 23, 2022 at 09:58:42PM -0500, Glenn Washburn wrote:
> On Tue, 23 Aug 2022 13:44:27 +0100
> Chris Green wrote:
>
> > On Tue, Aug 23, 2022 at 01:39:09AM -0500, Glenn Washburn wrote:
> > > Hi Chris,
> > >
> > > On Mon, 1 Aug 20
T=
> > GRUB_TIMEOUT_STYLE=
> >
Have you run grub-install after making changes to /etc/default/grub ?
--
Chris Green
em is headless and fairly inaccessible so I'd prefer to do
anything necessary via an ssh connection if possible, though if
needed I can connect a display, keyboard, etc.
--
Chris Green
is set up for legacy
> boot. But why then are grub-efi-* packages even installed ?
>
Thanks, can I tell remotely whether it really is set up for legacy
BIOS or EFI?
--
Chris Green
On Mon, Dec 12, 2022 at 03:52:08PM -0800, Randy Goldenberg wrote:
> On Mon, Dec 12, 2022 at 12:05 PM Chris Green wrote:
>
> > Thanks, can I tell remotely whether it really is set up for legacy
> > BIOS or EFI?
>
> If the unit booted EFI the file system will i
On Wed, Dec 14, 2022 at 10:31:40AM +0800, Goh Lip wrote:
>
>
> On 13/12/2022 18:55, Chris Green wrote:
>
> > So, as I suspected, it's not using EFI. So the only question is why
> > it's updating things in /boot/efi (or why there's a /boot/efi at all).
already up and
running? Doing a mount from the command line might produce some
errors which would help you diagnose the problem.
--
Chris Green
45 matches
Mail list logo
