Re: More boot questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/15/20 12:57 AM, Samuel Sieb wrote:
On 6/14/20 9:40 PM, Robert McBroom via users wrote:
On 6/14/20 3:12 PM, Samuel Sieb wrote:
On 6/14/20 9:39 AM, Robert McBroom via users wrote:
Copied my fedora 29 system to an SSD partition. Booting takes me to Grub-rescue>

SuperGrub2 2.04s1 finds the system and boots it but it is read only.?? Knoppix reads and writes to the system with no problem. Used Knoppix to fix /etc/fstab and grub.cfg. I think grub-install is needed from fedora but have to be able to write to the drive.

You need to provide more details.  What do you mean it's read only? And grub-install write to the raw hard drive, not to a filesystem.  A Fedora live boot or a net install rescue boot is a good way to fix things.
_______________________________________________
Any attempt to write to the system gets a message that the file system is read only.  grub2-install /dev/sda fails trying writes to
/boot/grub2/i386-pc. ls -l gives a list that looks completely normal with the expected permissions owners and groups.

Oh, right, it wants to set up the modules too.
What does "mount" show?  Try running "mount -o rw,remount /".  Or use "/boot" instead if you have a separate partition for it.

The simplest method though is still to download a Fedora net install image and use the rescue mode.  It sets everything up for you to chroot to the installed system and run whatever you want.  Just be aware that it will do a full relabel on reboot.  If you're sure you didn't change anything important, you can remove the /.autorelabel file before rebooting.
Found my problem and it is a curiosity on how the disk designations
interact.  In entering the / UUID in fstab a 6 became a b.  The entries
in grub.cfg were correct and apparently allowed the system to boot and
run as long as there was nothing needing to be written to the drive.  I
boot to a terminal and then start the graphical display which could not
happen without writing to the .serverauth.xxx and .Xauthority files
among others.  Corrected, the system is working without problems and
upgraded from f29 to f32.  Didn't have to dig out the warranty on the
drive after all.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux