Forums

Resolved
0 votes
Hi,
I want to upgrade to ClearOS 7, on new hardware.
Downloaded ClearOS-7.9.1.328147-x86_64.iso and dd it to my usb-stick.
My new hardware stops in UEFI BIOS, without the usb.
With the usb it stops with grub> .

Found two files BOOTX64.EFI and grubx64.efi, in the usb-directory /EFI/BOOT.

What should I do?

BR, Henrik
Monday, December 13 2021, 12:22 PM
Share this post:
Responses (27)
  • Accepted Answer

    Monday, December 13 2021, 03:57 PM - #Permalink
    Resolved
    0 votes
    For my UEFI server, those files are in /boot/efi/EFI/clearos. I have no idea what the error is and also I've never tried burning an iso in Linux. I always use Win32DiskImager or Rufus in Windows. Have you made sure any motherboard RAID is disabled? You could also try the testing iso where there has been zero feedback.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, December 13 2021, 06:24 PM - #Permalink
    Resolved
    0 votes
    In https://documentation.clearos.com/content:en_us:kb_o_clearos_usb_installer, the recommended tool for "burning" an iso-file, are dd.
    The usb-stick seems to be bootable, maybe a problem in grub-config.

    Here is a listing of the usb-stick (part of), mounted on my fedora:

    [henrik@uw006 ~]$ ls -l /run/media/henrik/ClearOS-7.9.1.328147-x86_64/
    total 132
    drwxrwsr-x. 3 henrik henrik 2048 19 maj 2021 EFI
    drwxrwsr-x. 3 henrik henrik 2048 19 maj 2021 images
    drwxrwsr-x. 2 henrik henrik 2048 19 maj 2021 isolinux
    drwxrwsr-x. 2 henrik henrik 2048 19 maj 2021 LiveOS
    drwxrwsr-x. 2 henrik henrik 120832 19 maj 2021 Packages
    drwxrwsr-x. 2 henrik henrik 4096 19 maj 2021 repodata
    -r--r--r--. 1 henrik henrik 1973 19 maj 2021 TRANS.TBL
    [henrik@uw006 ~]$ ls -l /run/media/henrik/ClearOS-7.9.1.328147-x86_64/EFI/
    total 3
    drwxrwsr-x. 3 henrik henrik 2048 19 maj 2021 BOOT
    -r--r--r--. 1 henrik henrik 216 19 maj 2021 TRANS.TBL
    [henrik@uw006 ~]$ ls -l /run/media/henrik/ClearOS-7.9.1.328147-x86_64/EFI/BOOT/
    total 5948
    -rwx------. 1 henrik henrik 963416 13 apr 2019 BOOTIA32.EFI
    -rwx------. 1 henrik henrik 1202952 13 apr 2019 BOOTX64.EFI
    drwxrwsr-x. 2 henrik henrik 2048 19 maj 2021 fonts
    -rw-r--r--. 1 henrik henrik 1393 19 maj 2021 grub.cfg
    -rwx------. 1 henrik henrik 756496 7 apr 2019 grubia32.efi
    -rwx------. 1 henrik henrik 1091344 7 apr 2019 grubx64.efi
    -rwx------. 1 henrik henrik 917224 13 apr 2019 mmia32.efi
    -rwx------. 1 henrik henrik 1152232 13 apr 2019 mmx64.efi
    -r--r--r--. 1 henrik henrik 1774 19 maj 2021 TRANS.TBL
    [henrik@uw006 ~]$
    The reply is currently minimized Show
  • Accepted Answer

    Monday, December 13 2021, 09:53 PM - #Permalink
    Resolved
    0 votes
    I know there is a how to for burning and ISO to USB. It is just that I have never tried it and don't have the hardware to try it as ,my UEFI system is doing some serious testing at the moment. I was ahead of you when I gave you my server file layout and I thought you were trying to install or boot post-install and weren't just trying to boot the USB. I don't know how a USB drive should be laid out. Can you try a legacy boot off the USB?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 14 2021, 05:00 PM - #Permalink
    Resolved
    0 votes
    A boot from the usb, same result, the only bootable device are the usb.
    The planned disk are an unused SSD (250 GB).
    Also filming the screen during boot and seen at least 17 error-messages, see attachment.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 14 2021, 05:09 PM - #Permalink
    Resolved
    0 votes
    Have you tried the testing ISO? Also what is the make and model of the motherboard?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 14 2021, 06:07 PM - #Permalink
    Resolved
    0 votes
    Have you tried the testing ISO? Not yet.

    Also what is the make and model of the motherboard?
    "ASUS PRIME H510M-A WIFI, LGA1200", found in the specs on paper.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 14 2021, 06:29 PM - #Permalink
    Resolved
    0 votes
    I really don't know with this one. Can you try googling the error message you see on boot when it drops to the grub prompt (perhaps use one of the centos or rhel or redhat key words as well)? Is it anything to do with Secure Boot and can it be disabled?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, December 15 2021, 05:16 PM - #Permalink
    Resolved
    0 votes
    I checked some grub-variables and it seems OK:
    grub> set
    fw_path=(cd0)//EFI/BOOT
    prefix=(cd0)/EFI/BOOT
    root=cd0

    The problem was that grub.cfg wasn't an ascii-file, the instruction to use dd, are not complete.

    Made a new copy of iso to usb, with mediawriter.

    The computer boots from usb, I can see a menu:
    - Install ClearOS 7.9.1.328147
    - Test this media & install ClearOS 7.9.1.328147
    - Troubleshooting -->
    Troubleshooting menu:
    - Install ClearOS 7.9.1.328147 in basic graphics mode
    - Rescue & ClearOS system

    All menu-entries clear the screen and that's all.
    My screen is connected with D-sub, also added another screen with hdmi.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, December 15 2021, 05:35 PM - #Permalink
    Resolved
    0 votes
    That sounds like success which is great.

    When you say the instructions for dd are not complete, do you know how to complete them? It is not so easy for me to test as my server is headless in the attic. I may be able to try on my backup server. As I mentioned before, I've only ever used Windoze tools to make the USB stick.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, December 15 2021, 08:05 PM - #Permalink
    Resolved
    0 votes
    There are two tools, for checking filetypes in Fedora: file and properties in Files (file manager)
    The file grub.cfg should be of type 'ASCII text' (file) or 'plain text document (text/plain)' (Files)
    The unreadable grub.cfg had type 'Binary (application/octet-stream)' (Files), I didn't check type with file.
    I tried to reproduce the error on an other usb and I couldn't.


    The install of ClearOS are not in progress, as far as I can see, the screen are still black after more than 30 mins.
    This a new problem, not shure what.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, December 15 2021, 08:35 PM - #Permalink
    Resolved
    0 votes
    Henrik Johansson wrote:

    There are two tools, for checking filetypes in Fedora: file and properties in Files (file manager)
    The file grub.cfg should be of type 'ASCII text' (file) or 'plain text document (text/plain)' (Files)
    The unreadable grub.cfg had type 'Binary (application/octet-stream)' (Files), I didn't check type with file.
    I tried to reproduce the error on an other usb and I couldn't.
    This almost sounds like a file corruption. Have you checked the checksum of the download?

    Having said that I've done:
    [root@microserver ~]# rpm -q --whatprovides /boot/efi/EFI/clearos/grub.cfg
    grub2-efi-x64-2.02.2-0.87.v7.6.0.3.x86_64
    Yet the file is not packaged in grub2-efi-x64-2.02.2-0.87.v7.6.0.3.x86_64 so I don't know.

    Are you doing a text or graphics install? If graphics, then you have a problem, possibly with graphics drivers, and should perhaps try a text mode install.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, December 15 2021, 09:44 PM - #Permalink
    Resolved
    0 votes
    I've checked the downloaded iso with sha256sum

    The installed file grub.cfg, may be built during install, in Fedora the file is rebuilt after kernel-update.

    I've tested all menu-entries, with same result, a black screen
    - Install ClearOS 7.9.1.328147
    - Test this media & install ClearOS 7.9.1.328147

    - Install ClearOS 7.9.1.328147 in basic graphics mode
    - Rescue & ClearOS system

    The install-entry with basic graphics mode, sets xdriver=vesa and nomodset in grub.cfg.
    Starting a basic graphics install over night.





    PS. Why are the forum contacting facebook, when I reply?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, December 15 2021, 09:54 PM - #Permalink
    Resolved
    0 votes
    You can do a text mode installation (no graphics at all). See https://documentation.clearos.com/content:en_us:7_b_installation_wizard.

    No idea what the forum is doing at all. It really needs replacing.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, December 16 2021, 12:25 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    You can do a text mode installation (no graphics at all). See https://documentation.clearos.com/content:en_us:7_b_installation_wizard.

    No luck with the [TAB]-key
    Accepted keys in menu-mode are: [UP], [DOWN], 'e' (edit), 'c' (command prompt, [ENTER] and [ESCAPE] (back).
    Special keys in edit-mode are: Ctrl-x (start), Ctrl-c (command prompt), [ESCAPE] (discard) and [TAB] (list possible completions).

    Tried to add inst.text at the end of three entries, the same results as without editing.
    First menu

    setparams 'Install ClearOS 7.9.1.328147'
    linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=ClearOS-7.9.1.328147-x86_64 quiet inst.text
    initrdefi /images/pxeboot/initrd.img

    setparams 'Test this media & install ClearOS 7.9.1.328147'
    linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=ClearOS-7.9.1.328147-x86_64 rd.live.check quiet inst.text
    initrdefi /images/pxeboot/initrd.img

    Trouble-shooting-menu

    setparams 'Install ClearOS 7.9.1.328147 in basic graphics mode'
    linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=ClearOS-7.9.1.328147-x86_64 xdriver=vesa nomodeset quiet inst.text
    initrdefi /images/pxeboot/initrd.img

    setparams 'Rescue a ClearOS system'
    linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=ClearOS-7.9.1.328147-x86_64 rescue quiet
    initrdefi /images/pxeboot/initrd.img


    I don't know what to do at the grub-prompt, tried this:

    grub> linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=ClearOS-7.9.1.328147-x86_64 xdriver=vesa nomodeset quiet inst.text
    grub> initrdefi /images/pxeboot/initrd.img
    grub> boot

    Don't know if something happens after boot (and Enter), it doesn't react on my key-strokes.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, December 16 2021, 12:57 PM - #Permalink
    Resolved
    0 votes
    When the boot screen comes up and you have 3 options (roughly):
    Install ClearOS 7.9.1.xxxxxx
    Test this media & Install ClearOS 7.9.1.xxxxxx
    Troubleshooting

    with the cursor the first or second option highlighted (the second is the default but it is hard to see; just try using the up/down arrow keys), hit [TAB]. A command line will appear further down where you can add the inst.text. If that does not work, then I don't think I can do any more.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, December 16 2021, 08:20 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    When the boot screen comes up and you have 3 options (roughly):
    Install ClearOS 7.9.1.xxxxxx
    Test this media & Install ClearOS 7.9.1.xxxxxx
    Troubleshooting

    with the cursor the first or second option highlighted (the second is the default but it is hard to see; just try using the up/down arrow keys), hit [TAB]. A command line will appear further down where you can add the inst.text. If that does not work, then I don't think I can do any more.

    [TAB] stops the clock, but nothing else.
    Tested with another keyboard also.
    Tested [TAB] in other OS-installations CentOS-8.5, Rocky-8.5, Fedora-31 and CentOS-7.0, it stopped the clock and nothing else.
    Are there a diffrence between [TAB] in keyboards with US and Swedish layout?

    The default menu-entry seemed to work with CentOS-8.5.2111-x86_63-boot and Rocky-8.5-x86_64-boot, I stopped after media-check at localization.
    Where can i download ClearOS-netinst-x86_64-7.9.1.328147.iso?
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, December 16 2021, 08:40 PM - #Permalink
    Resolved
    0 votes
    I have a UK keyboard layout. For me, moving the line with the up/down arrow keys stops the count and then hitting the tab key brings up the editable line.

    You can download from any of the mirrors - https://mirrorlist.clearos.com/clearos/7/iso/x86_64/.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, December 16 2021, 09:25 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    You can download from any of the mirrors - https://mirrorlist.clearos.com/clearos/7/iso/x86_64/.


    Same result with ClearOS-netinst-x86_64-7.9.1.328147.iso as ClearOS-DVD-x86_64-7.9.1.328147.iso :(

    Next try:
    Removed 'quiet' from first menu-entry
    menuentry 'Install ClearOS 7.9.1.328147' --class fedora --class gnu-linux --class gnu --class os {
    linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=ClearOS-7.9.1.328147-x86_64
    initrdefi /images/pxeboot/initrd.img
    }

    No visible difference, black screen for hours.

    How can I debug the menu-entries?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 18 2021, 01:55 PM - #Permalink
    Resolved
    0 votes
    Are Hard disk mandatory for ClearOS, my computer has one 250GB SSD and no HDD?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 18 2021, 03:44 PM - #Permalink
    Resolved
    0 votes
    SSD should be fine. The main thing to note is that any motherboard RAID must be disabled.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, December 19 2021, 08:58 PM - #Permalink
    Resolved
    0 votes
    Nothing about RAID, STRIPE or MIRROR in UEFI BIOS setup.

    Also tested ClearOS-DVD-x86_64-7.9.1.342252.iso, with no visible result (only a black screen).

    Are any other way to install ClearOS?
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, December 19 2021, 10:04 PM - #Permalink
    Resolved
    0 votes
    The only other way I know is to install on a different system and do a disk transplant afterwords. The main proviso is that you will need a UEFI system as that is what your intended system is. After the transplant, if it works OK, you will need to go into the Console and sort your interfaces out. Afterwards, at the command line, you may want to check out /etc/clearos/network.conf and remove any non-existent interfaces from the file.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 06 2022, 05:31 PM - #Permalink
    Resolved
    0 votes
    Hi again,

    The new computer seems to be, too new for ClearOS from May 2021.
    Tested install of CentOS and Rocky Linux and it worked.
    Moved a Win10 to the new computer, had to download new network-drivers thru WiFi.

    Work-around för ClearOS: Installed ClearOS on the old Win10 computer.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 06 2022, 06:36 PM - #Permalink
    Resolved
    0 votes
    That is possible if Centos and Rocky were version 8. They have much more recent kernels.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 06 2022, 08:05 PM - #Permalink
    Resolved
    0 votes
    I tested install of CentOS-8.5.2111 and Rocky-8.5.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, January 08 2022, 12:20 PM - #Permalink
    Resolved
    0 votes
    Up and running with ClearOS release 7.9.1 (Final) on the old computer.
    When are ClearOS 8 planed?
    Are ClearOS 7 possible to upgrade to ClearOS 8?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, January 08 2022, 06:09 PM - #Permalink
    Resolved
    0 votes
    I don't know when 8 is planned. The best I can do is https://www.clearos.com/clearfoundation/social/community/is-clearos-still-under-active-development#reply-329571. I guess if it is delayed long enough 8 could even be skipped and we do directly to 9 if we follow the Redhat path. Their 9 Beta was released in November.
    The reply is currently minimized Show
Your Reply