On Sun, Apr 25, 2021, 10:36 AM Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:
> On Sat, 24 Apr 2021, Chris Murphy wrote:
>
> > You need to use -B to bind mount the pseudo filesystems, and probably
> also
> > need to include /sys
>
> > grub2-install /dev/sda
>
> mount /dev/sda3 /mnt/a3
On Sat, 24 Apr 2021, Chris Murphy wrote:
You need to use -B to bind mount the pseudo filesystems, and probably also
need to include /sys
grub2-install /dev/sda
mount /dev/sda3 /mnt/a3 # already done
mount -B /proc /mnt/a3/proc
mount -B /dev /mnt/a3/dev
mount -B /dev/pts
On Sat, Apr 24, 2021, 6:18 AM Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:
>
> mount /dev/sda3 /mnt
> mount /proc /mnt/proc
> mount /dev /mnt/dev
> mount /dev/pts /mnt/dev/pts
>
> You need to use -B to bind mount the pseudo filesystems, and probably also
> need to include
sda3/etc/fstab :
#
# /etc/fstab
# Created by anaconda on Tue Nov 24 17:36:35 2020
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to
On Fri, Apr 23, 2021 at 11:17 PM Samuel Sieb wrote:
>
> On 4/23/21 3:37 PM, Michael Hennebry wrote:
> >> With the hard disk only does it find grub and does it display a menu
> >> or drop you to the grub> prompt?
> >
> > I get the grub prompt.
>
> And this is where you can only see (hd0)? That
On Fri, Apr 23, 2021 at 11:11 PM Samuel Sieb wrote:
> His partition list has "extended" on sda4, so it looks like he's correct
> about it being BIOS.
Yep, I missed that.
grub2-install --force /dev/sdXY can work, even though it's not
recommended upstream. I think it's still some confusion over
On 4/23/21 3:37 PM, Michael Hennebry wrote:
On Fri, 23 Apr 2021, Roger Heflin wrote:
What is the exact error you are getting?
Something along the lines of
UUID 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a not found.
When are you getting this error? Since you say grub isn't booting from
the hard
On 4/23/21 7:39 PM, Chris Murphy wrote:
I'm actually betting dollars to donuts that this is a UEFI system, and
grub2-install was used, and now it's looking for grub.cfg in the wrong
location.
His partition list has "extended" on sda4, so it looks like he's correct
about it being BIOS.
On 4/23/21 1:05 PM, Roger Heflin wrote:
But if the windows system is gone and you don't care about it, then I
would set sda3 to be bootable.
The bootable flag is not relevant.
rescue it and then grub-install /dev/sda3 but make sure the newuuid is
grub needs to be installed to the raw hard
On Fri, Apr 23, 2021 at 2:51 PM Michael Hennebry
wrote:
> I've read that I need --force to grub2-install onto a partition.
That's sufficiently unreliable that upstream GRUB has recommended
against it for almost a decade.
First, what firmware type is this?
[ -d /sys/firmware/efi ] && echo UEFI
On Thu, Apr 22, 2021 at 1:41 PM Michael Hennebry
wrote:
>
> I'm trying to move my root directory from sda5 to sda3.
This is much harder to do without LVM or Btrfs. For LVM there's more
steps but basically it depends on 'pvmove'. And for Btrfs it's 'btrfs
replace' - both are live migrations and
From what I can see with mine 7 places would be about right.
Is that uuid the current one for sda3 or the old uuid for sda5? if it
is not the one for sda3 that would be an issue. It kind of looks like
the *3a uuid is from the bootcd so that would be wrong, if you run the
grub2-mkconfig and the
On Fri, 23 Apr 2021, Roger Heflin wrote:
What is the exact error you are getting?
Something along the lines of
UUID 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a not found.
With the hard disk only does it find grub and does it display a menu
or drop you to the grub> prompt?
I get the grub prompt.
What is the exact error you are getting?
With the hard disk only does it find grub and does it display a menu
or drop you to the grub> prompt?
If it displays a menu and you select one of them what does it then do?
The uuid will also be on the kernelopts line, but if that was the
error you would
The grub rescue mode finds only (hd0), no paritions at all.
On Fri, 23 Apr 2021, Roger Heflin wrote:
if you are doing the grub-install/grub2-mkconfig from inside the
chroot then it should find the correct uuid (if it works like it
should).
I did stuff in the chroot, but apparently not well.
if you are doing the grub-install/grub2-mkconfig from inside the
chroot then it should find the correct uuid (if it works like it
should).
any of the test commands for grub need to be in the chroot otherwise
they will think they are the livecd and not do the right thing or show
the right thing as
On Fri, 23 Apr 2021, Roger Heflin wrote:
I assume it is still not bootable.
But if the windows system is gone and you don't care about it, then I
would set sda3 to be bootable.
Did that. Forgot to mention it.
rescue it and then grub-install /dev/sda3 but make sure the newuuid is
I've
I assume it is still not bootable.
But if the windows system is gone and you don't care about it, then I
would set sda3 to be bootable.
rescue it and then grub-install /dev/sda3 but make sure the newuuid is
in both fstab (you have done that I think) and matches what is in the
On Fri, 23 Apr 2021, Roger Heflin wrote:
If you used rsync to copy from one disk to the other then the uuid
would have changed on the new fs as compared to the old fs. I
Yup.
Needed to change fstab.
typically copy /boot the hard crude way (dd) and copy LVM using the
LVM tools (pvmove and
If you used rsync to copy from one disk to the other then the uuid
would have changed on the new fs as compared to the old fs. I
typically copy /boot the hard crude way (dd) and copy LVM using the
LVM tools (pvmove and friends) and in both cases that maintains the
same UUID on the old and new.
On Fri, 23 Apr 2021, Roger Heflin wrote:
I am not sure which it needs. If it did not stop windows from
booting then it may have updated the wrong thing.
It did stop windows from booting.
No menu. Nuthin.
--
Michael henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an
I have BIOS, not UEFI.
On Fri, 23 Apr 2021, Roger Heflin wrote:
I am not sure which it needs. If it did not stop windows from
booting then it may have updated the wrong thing.
Windows will not boot either.
Try /dev/sda3 it will either work or give you an error in my experience.
From
On 23/04/2021 00:30, Roger Heflin wrote:
Nothing in dracut cares about what partition it is on,
That is not completely true. The correct file system kernel modules (or
what else is needed to access the root partition) have to be included in
the intitrd. If the root file system type is
I am not sure which it needs. If it did not stop windows from
booting then it may have updated the wrong thing.
Try /dev/sda3 it will either work or give you an error in my experience.
What OS does the main boot loader come from and/or is the machine EFI?
Something in the main boot loader
When I ran grub2-install, I used /dev/sda .
Should I have used /dev/sda3 ?
--
Michael henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
On Thu, 22 Apr 2021, Michael Hennebry wrote:
On Thu, 22 Apr 2021, Roger Heflin wrote:
My general plan would be to set the new partition bootable with the
partitioning program (fdisk there are options to find the option to
set bootable) (this all assumes you aren't using EFI).
liveboot it.
On Thu, 22 Apr 2021, Roger Heflin wrote:
Then whatever windows is using to boot is pointing to grub, and that
needs to be repointed to the new device.
I'll try changing the bootable flag.
There has never been a windows partition in sda5,
so something else, possibly the Fedora installer,
must
Then whatever windows is using to boot is pointing to grub, and that
needs to be repointed to the new device.
I don't believe grub-install does anything with that.
On Thu, Apr 22, 2021 at 6:03 PM Michael Hennebry
wrote:
>
> On Thu, 22 Apr 2021, Roger Heflin wrote:
>
> > Nothing in dracut cares
On Thu, 22 Apr 2021, Roger Heflin wrote:
Nothing in dracut cares about what partition it is on, and grub is not
finding the initramfs. Grub is failing to find the boot.cfg files and
vmlinuz and inittramfs. So either you have the wrong grub being
started or the right grub but it cannot find
On Thu, 22 Apr 2021, Joe Zeff wrote:
On 4/22/21 3:46 PM, Michael Hennebry wrote:
What is dracut?
Try using man dracut. Man is your friend; trust man.
My kernel version is not changing.
Should not dracut recreate the same image for the same kernel?
Is the partition of the binary or the
Nothing in dracut cares about what partition it is on, and grub is not
finding the initramfs. Grub is failing to find the boot.cfg files and
vmlinuz and inittramfs. So either you have the wrong grub being
started or the right grub but it cannot find its config files.
Are you trying to move
On 4/22/21 3:46 PM, Michael Hennebry wrote:
What is dracut?
Try using man dracut. Man is your friend; trust man.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code
On Thu, 22 Apr 2021, Lester M Petrie wrote:
On 4/22/21 4:19 PM, Joe Zeff wrote:
On 4/22/21 1:40 PM, Michael Hennebry wrote:
I'm trying to move my root directory from sda5 to sda3.
After running grub2-install and grub2-mkconfig,
my machine will not boot.
I don't see any mention of your
On 4/22/21 4:19 PM, Joe Zeff wrote:
On 4/22/21 1:40 PM, Michael Hennebry wrote:
I'm trying to move my root directory from sda5 to sda3.
After running grub2-install and grub2-mkconfig,
my machine will not boot.
I don't see any mention of your using dracut to rebuild your initramfs
after
On 4/22/21 1:40 PM, Michael Hennebry wrote:
I'm trying to move my root directory from sda5 to sda3.
After running grub2-install and grub2-mkconfig,
my machine will not boot.
I don't see any mention of your using dracut to rebuild your initramfs
after making the changes.
I'm trying to move my root directory from sda5 to sda3.
After running grub2-install and grub2-mkconfig,
my machine will not boot.
I performed the changes using a F33 live DVD which also fails to boot.
After plugging in a USB-connected SD card with Centos 7 on it,
the F33 live DVD decided to boot.
36 matches
Mail list logo
