On Thursday 06 November 2014 14:27:31 James B. Byrne wrote:
> On Wed, November 5, 2014 19:41, Richard wrote:
> > ------------ Original Message ------------
> >
> >> Date: Wednesday, November 05, 2014 15:53:53 -0500
> >> From: "James B. Byrne" <byrnejb@xxxxxxxxxxxxx>
> >> To: centos@xxxxxxxxxx
> >> Subject: CentOS-7 re-install
> >>
> >> I have booted the system from a live cd. I am looking at a
> >> 1.1GB volume that I presume is the /boot partition I created in
> >> the installer. Inside I see this:
> >>
> >> config-3.10.0-123.el.x86_64
> >> /grub
> >> /grub2
> >> initramfs-0-rescue-[md5. . .].img
> >> initramfs-3.10.0-123.el.x86_64
> >> initrd-plymouth.img
> >> symvers-3.10.0-123.el.x86_64
> >> System-map-3.10.0-123.el.x86_64
> >> vmlinuz-0-rescue-[md5 as above]
> >> vmlinuz-3.10.0-123.el.x86_64
> >>
> >> /grub contains:
> >> splash.xpm.gz
> >>
> >> /grub2 contains:
> >> /themes
> >>
> >> /grub2/themes contains:
> >> /system
> >>
> >> /grub2/themes/system contains:
> >>
> >> nothing at all
> >>
> >> So, what does CentOS-7 boot from? I take it that this is not
> >> normal? So where are the boot configuration files? Note, that
> >> I have only been working on this system through the GUI and I I
> >> did was install, update, played around with Gnome3, installed
> >> KDE, shutdown and re-installed over the original.
> >>
> >> So, whatever happened it is not because of anything one can only
> >> screw up from the cli. Since the re-install I have not been
> >> able to boot from the HDD. Seeing as there are no boot
> >> configuration files I can see why booting is a problem. But,
> >> how does the installer operate such that these critical files
> >> were not provided?
> >
> > The /boot/grub2 directory should have the files:
> >
> > device.map
> > grub.cfg
> > grubenv
> >
> > The grub.cfg looks kind of like grub/grub.conf and can be
> > generated using grub2-mkconfig (based on the files in /etc/grub.d
> > and /etc/default/grub).
> >
> > If you booted from a live cd I suspect that the full boot setup
> > isn't completed on the installed system, which would be why you
> > don't seem to be seeing the grub2 boot files.
>
> I booted from the liveCD simply to see what the regular installer
> had done to the HDD. Eventually I did install from the liveCD and
> that has allowed the system to boot from the HDD again.
>
> I am sort of perplexed as to why there is no simple provision to
> reuse the entire disk as I recall was the case with previous
> versions of CentOS. Why the laborious requirement to delete each
> mount point from an install one wishes to remove entirely?
>
> In any case, I have gotten past the difficulty and have built zfs
> for 3.10.0-123-9.2. Now to see if I can figure out how to rebuild
> the system using zfs
Hi James,
>From an old email of mine to the list.
> >
> Hi Tony
>
> Did you receive an answer to your question ? I didn't see anything
> on the list ! I'm interested too.
>
> Thank you
No but I sorted it out myself. I just took a chance, it was on a test
server anyway ;-)
In the disk partitioning screen you will see the old 6.5 installation.
Clicking on it will bring up the existing 6.5 partitions. Then select
each of the existing partitions and a configuration menu comes up which
allows you to reformat the partition if required. So just don't
reformat the partitions you want to keep .They then become part of the
new 7.0 installation.
Hope this helps.
Regards,
Tony
--
Linux nogs.tonyshome.ie 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31
17:20:51 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
--
Linux nogs.tonyshome.ie 2.6.32-504.el6.x86_64 #1 SMP Wed Oct 15
04:27:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
