On Sun 06 Jun 2021 at 14:14:38 (+0300), Andrei POPESCU wrote:
> On Sb, 05 iun 21, 12:46:13, Martin McCormick wrote:
> >
> > One should be able to write a program to get the
> > appropriate UUID's out of fstab on the working system
> > and translate them in to corresponding UUID's for the syste
Felix Miata writes:
> This is a big lurking booby trap that could have been the problem both
> last time
> and this time. It's one of the reasons why installation systems and Grub
> switched
> from using device names to using UUIDs: inconsistent and/or unpredicable
> device
> enumeration.
>
>
Martin McCormick composed on 2021-06-06 16:59 (UTC-0500):
...
> Swap is the last partition.
> Disk /dev/sde:
This is a big lurking booby trap that could have been the problem both last time
and this time. It's one of
I admit I made several big mistakes, here. The first was not
having a backup of /boot as I thought I did. The next is
thinking I could just copy the whole boot directory from a
known working system and be able to get it to work by using sed to
replace the UUID's of the system it was on with those
Felix Miata writes:
> IMO you gave up too soon. IIRC you never showed us output from parted -l
> or fdisk
> -l. Very likely on the problem PC the / filesystem was/is not on the first
> partition, where often lies a swap partition. Very likely root=/dev/sda2
> would
> have been/be correct.
Sorry
Martin McCormick composed on 2021-06-06 13:30 (UTC-0500):
> The sample that Greg Wooledge showed looked very close to
> how my grub.cfg looked after doctoring the drive references to
> point to hd0,1msdos. and I tried booting that way and set the
> root parameter to /dev/sda1, /dev/sdb1 and
Thanks to all for the advice and knowledge you shared about how
grub works. I am writing this on June 6 and early this morning,
I edited the boot command in the grub shell after
verifying that my stubborn no-boot drive truly was sitting at
hd0,1msdos and grub-install had picked out hd2,1msdos for
On Sat, Jun 05, 2021 at 08:17:38PM -0400, Cindy Sue Causey wrote:
> On 6/5/21, Martin McCormick wrote:
> > First I greatly appreciate all this information as the idea is to
> > fix a problem I probably created long ago though I am not sure
> > how but the short story is that apt-get upgrade ran up
On Sb, 05 iun 21, 12:46:13, Martin McCormick wrote:
>
> One should be able to write a program to get the
> appropriate UUID's out of fstab on the working system
> and translate them in to corresponding UUID's for the system on
> the operating table.
Alternatively you might want to consider
On Saturday 05 June 2021 20:17:38 Cindy Sue Causey wrote:
> On 6/5/21, Martin McCormick wrote:
> > First I greatly appreciate all this information as the idea is to
> > fix a problem I probably created long ago though I am not sure
> > how but the short story is that apt-get upgrade ran update-gr
On 6/5/21, Martin McCormick wrote:
> First I greatly appreciate all this information as the idea is to
> fix a problem I probably created long ago though I am not sure
> how but the short story is that apt-get upgrade ran update-grub
> and update-initramfs late last Fall and I was able to rescue i
Martin McCormick composed on 2021-06-05 16:28 (UTC-0500):
> the short story is that apt-get upgrade ran update-grub
> and update-initramfs late last Fall and I was able to rescue it
> but it happened again at the end of April so I figured I had
> better fix it correctly since I didn't know it was
On Sat, Jun 05, 2021 at 04:28:20PM -0500, Martin McCormick wrote:
> There's 1 UUID for the root file system in /boot/grub/grub.cfg
> which is the file one must not normally edit by hand. It
> reads
>
> menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
> --class os $menue
First I greatly appreciate all this information as the idea is to
fix a problem I probably created long ago though I am not sure
how but the short story is that apt-get upgrade ran update-grub
and update-initramfs late last Fall and I was able to rescue it
but it happened again at the end of April
Martin McCormick composed on 2021-06-05 12:46 (UTC-0500):
> I have a plan but I need some more information. Is there any
> personalization done by the boot setup process? Do our UUID's
> or any other specific information pertaining to the installation
> make it in to the initrd files?
Dracut in
Reco writes:
> On Sat, Jun 05, 2021 at 12:46:13PM -0500, Martin McCormick wrote:
> > I have a plan but I need some more information. Is there any
> > personalization done by the boot setup process?
>
> Yes. One of the GRUB's tasks is to supply kernel which is about to boot
> with root=... cmdlin
On Sat, Jun 05, 2021 at 12:46:13PM -0500, Martin McCormick wrote:
> I have a plan but I need some more information. Is there any
> personalization done by the boot setup process?
Yes. One of the GRUB's tasks is to supply kernel which is about to boot
with root=... cmdline parameter. Root filesyst
Martin McCormick wrote:
> As an aside, one ought to be able to do something like
> this. It makes life a lot simpler. Both systems are using the
> same kernel and versions of the same processor the only real
> differences are the UUID's. The grub configurations of both are
> the same down to th
I have a plan but I need some more information. Is there any
personalization done by the boot setup process? Do our UUID's
or any other specific information pertaining to the installation
make it in to the initrd files?
While reading about the boot process, it doesn't appear
that the ini
19 matches
Mail list logo
