Error setting up base repository, under install source.

Latest response

I booted up the machine and started the install process (new hardware, never had an OS installed on it) and immediately hit a snag. There are a couple things I needed to deal with on the main install screen. One, it asks me to pick the boot disks, so I checked all 4 of them and chose RAID 10. So far so good, but then the fun begins.

The main problem I am running into is that it lists the repository as an error. It says under Installation source, error setting up base repository. If I click on it, it initially shows something like /dev/sde1/ (14.6 Gig MB) EFI system partition as one choice, which isn't selected when I go into that screen, and on the network as the other option, which is selected but greyed out I presume because the NIC isn't enabled yet, that is on another screen.

I tried being clever and copied both of the .iso files to another USB drive and inserted it in the machine, but it doesn't appear to see it. One thing I noticed when I was downloading the software after I purchased it was there were actually 2 files, I grabbed them both: rhel-workstation-7.4-x86_64-boot.iso and rhel-workstation-7.4-x86_64-dvd.iso. I made the bootable USB out of the 2nd one, not sure why there were 2, the boot .iso is about 470 meg, and the other is about 4.4 gig, and it obviously boots and starts the install from it.

So... this thing isn't smart enough to use the files that it is booting up from, to do the installation with? Am I possibly missing something?

It says in the help file of that page, that if installing from a USB device or DVD, it is supposed to automatically detect it, and this error shouldn't appear. I can't find any way around this dilemma. Any suggestions would be appreciated, I'd sure like to get this box loaded and configured tonite.

edit Think I might have figured it out. After letting Google be my friend, I eventually came across a post that explained it:

Make sure you have not inadvertently tried to use the boot.iso for rhel7 as your installation media; it will generate the error you are reporting because the boot.iso does not contain any of the installation repositories virtualbox will need. Instead you need to download the dvd iso which is approx 3+ GB in size.

Well, pulled out the USB stick, put it in my machine, and did a properties of the entire drive. Turned out to be under 500 meg total.... Doh! So, re-burnt it, being sure to pick the dvd file not the boot file, and started over. System boots up, and wa-la!

ha
Log in to join the conversation

Responses

R. Hinton.'s picture Guru 10133 points
22 January 2018 4:27 AM

Alan,

Very glad you sorted it out!

Let us know if you need assistance, someone will chime in,

-RJ

ha Newbie 15 points
22 January 2018 8:23 PM

Thanks for the reply, I just noticed an email from the support team, and replied with a long message, as I am still having a lot of trouble getting to where I need to with this install. Unfortunately, it is fighting me all the way, which mirrors my last number of attempts at installing running or updating previous Linux tries. The gist of my issues, well, I will copy/paste the final bit of the email I sent to the support dept:

So, right now, the user SETI that I had set up can log in to the non-graphical interface, but it doesn't have admin rights apparently, and nothing I do can change that. I also can no longer get into the graphical side of RedHat, it is stuck in the command line, even after rebooting. I am almost at the point of giving up, and trying to re-install it. Also, I can't seem in the command line bootup to be able to log in as Admin, which is probably a huge problem at this point for me, because I can't sudo, and without sudo, I really can't do anything. I'm pretty frustrated at this point, I knew that it has a learning curve, but I had hoped that things had improved substantially since the last (first) time in the late 90s that I had tried running RedHat, especially since I paid for it this time. Well, hopefully we will be able to get it working without having to reinstall it, it's not the end of the world or anything, but it is another 3-4 hours wasted when it's all said and done.

Just so you know, my main goals are to get RedHat installed and updated, get the Nvidia drivers installed, and download and run BOINC.

Here is one more comment that was said towards the beginning of this adventure:

I'm guessing this host hasn't made an appearance in BOINC or Seti yet? From the look at your other Linux hosted Xeon, I assume that the new one won't have AVX either? I could suggest you try the SSE4.1 cpu app instead of the SSSE3 app. I would first benchmark both app in the Linux benchmark tool to see whether the SSE4.1 app is faster than what you are currently using.

All the apps you need are over at the Crunchers Anonymous site. You can pick up either the 7.4.44 or 7.8.3 BOINC versions which ***** has compiled. They are neat in that they all can be put into your /Home directory. I have my BOINC folder on the Desktop. No issues with needing to figure out how to change permissions on the dual directory repository BOINC versions. ***** also makes a strong case to put your /Home directory on another drive that allows you to update your OS or remove it entirely without it affecting BOINC ever.

BOINC All-In-One Build to run zi3v CUDA 8.0 in Ubuntu 12.04 to 17.04

Read the instructions in the post about checking for dependencies and to make sure the execute bits are set on the main files.

BOINC 7.8.3 for Linux

Again read the post about execute and dependencies. Make sure to install the libwebgtk package.

The current most stable special app is ***** Linux CUDA Special Apps

Again read the post. The bottom of the post has the link to the CUDA90 zi3v app with the included CUDA libraries.

This the app_config I am using for my Ryzen 1800X with GTX1070Ti's. You will have to adjust the max_current parameter for your host. Just watch the cpu task run_times versus the cpu_times on the cpu tasks to ensure the processor isn't overloaded.

Thanks for any help you might be able to give me, I would really like to get this working, but as seemingly with all things Linux, nothing is as easy as it (in my humble opinion) should be, it's always a struggle every time I've tried it over the last 20+ years, but that is why I spent so much money on your OS this time, I really wanted something that worked, and actually had support. Oh, and here are links to some of the resources I have tried to use and follow:

https://access.redhat.com/solutions/5238 https://access.redhat.com/discussions/3101441 https://access.redhat.com/sites/default/files/attachments/rhel_5_6_7_cheatsheet_27x36_1014_jcs_web.pdf https://www.tecmint.com/fix-user-is-not-in-the-sudoers-file-the-incident-will-be-reported-ubuntu/ (tried, didn't work) http://www.advancedclustering.com/act_kb/installing-nvidia-drivers-rhel-centos-7/

Thanks guys, I really want to get this thing up and running, my guess is all that it will take is the patience of Job... ;-)

R. Hinton.'s picture Guru 10133 points
23 January 2018 4:39 PM

Hi Alan,

Sorry you've got some troubles with your install.

If sudo is not working, do you at minimum have the root password? If not you can recover the root password use this link for instructions https://access.redhat.com/solutions/1276063. Remember the touch /.autorelabel that's important.

You can add the user you wish for sudo access with the procedure here (Red Hat Docs) (that document is for OpenStack overall, but the portion I sent you to does sufficiently cover setting up sudo)

If you are having trouble getting to graphical mode, the first question is whether or not you have the necessary packages installed (you just might) and the 2nd question is the setting of the default target.

Examine this discussion https://access.redhat.com/discussions/1311854 and namely the comments by ir. Jan Gerrit Kootstra, and the Red-Hatter Petr Bokoc. (The solution in the next paragraph is useful as well, examine it along with the link in this paragraph).

If you actually need to install the packages to get a graphical interface, use this link https://access.redhat.com/solutions/5238, and this covers setting the proper target as well.

I've made CUDA work for some customers at work, and in some cases it ... took a bit of work, and it's been a while. I'm not at that customer site at the moment, and do not have access to my notes on that.

Let us know how this goes, and come back and someone ought to chime in and assist you,

Kind Regards, -RJ

ha Newbie 15 points
23 January 2018 5:57 PM

RJ, thanks for the reply, First want to let you know I really appreciate your assistance, thank you. Also, I started using the software in the graphical (normal 'Windows' to me) mode for a while after the installation, but then did that crtl-alt-something to get to the command line, to run those commands in the instructions, to be able to install the Nvidia graphics package and such, and haven't been able to find a way to get out of it.

When I set up the system, I had to install a password for (I thought) the Admin account, it wouldn't let me proceed without doing it. But then I set up the 2nd account (SETI), which I had thought (or probably hoped) was also Admin level, but without needing to put in a password, so I didn't. I know, great security, but this is a first time through, so I was figuring that I would probably change it all once it was up and running properly, or at least nuke the rights down to plebe status.

Now, stuck here at the command prompt after booting up, it asks for user name, so I tried putting in Administrator with the password I used, and it says invalid login, but when I put in the user SETI, it now for some reason requires a password, and allows a login using the admin PW I had chosen. Strange.

Of course, after logging into SETI, and then trying to run one of those sudo commands, I get the tsk tsk, oh no you don't! message, so I know that it doesn't have proper rights, but seeing as I can't seem to log into the admin account to change any of those things, am I dead in the water?

Oh, and glad to know that it is at least possible to get CUDA working, though hearing that it was, well, "interesting" for a Linux master to get accomplished is a little bit frightening, but I suppose where there's a will, there's a way! With proper help from people with Much more knowledge than I, of course. I'll wait on your thoughts to what I've written, and when I get back to the machine (unfortunately might be a few days now), I'll dive in and see what I can get accomplished. Thanks again, I do appreciate it!

R. Hinton.'s picture Guru 10133 points
23 January 2018 9:49 PM

Hey Alan,

First things first, let's resolve your access problem you're experiencing on your system. I recognize you have a number of things to deal with, but let's focus on you getting access on your system as the first step.

So I realize you can't use sudo. and your account is not an admin.

Questions:

  • Do you or do you not have the root password? If you do have the root password then do this: 
/bin/su - 
<enter the password>

You can add the user you wish for sudo access with the procedure here (Red Hat Docs) (that document is for OpenStack overall, but the portion I sent you to does sufficiently cover setting up sudo)

After you have root access to your system and can become root (without sudo) using /bin/su - or su - then come back here and we'll take it from there.

**if you DO have the root password, then you can establish sudo as you desired with the procedure I placed in a link in this post and the previous one.

Come back after you are certain you have root (or have restored the root password) and if you wish, set up sudo per the instructions.

Will be happy to assist,

Kind regards,

RJ

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.