Red Hat :: Unable To Put Both Anaconda-ks.cfg + Boot.iso On Same Cd
Sep 27, 2010
I have successfully install rhel 5 through network installation using ftp nfs and http. Now i want to automate this task. How much i know about this is that i need anaconda-ks.cfg file for this task. My question is this: where i put the ks.cfg file. during googling i found that it should we on installation cd which have boot.iso but i am unable to put both anaconda-ks.cfg + boot.iso on same cd. how can i put both of them on a single cd or there any other way for this
I'm trying to build a dual boot ubuntu 8.10 and fedora 10.I have ubuntu sucessfully installed. with a free partition ready for fedora.I cant seem to get fedora past the beginning of the install. Once it says its loading anaconda, my screen either goes blank, or the anaconda fails and the install exits, telling me to reboot my system.I have downloaded the DVD twice. once from the website, and i think when I bruned it it didn't burn right, I then downloaded it from torrent just to be safe and reburned at the slowest speed. It passes the media test.
I have been reading around it may be cause of my video card?My computer is the following.AMD Athlon +2400 XPXFX Nvidia Geforce 6800 GT or something close.80 gig hard drive1.5 gigs of DDR ram.MSI Motherboard not sure of model off top of my head.I really wanna get this dual boot working, As I feel fedora may have advantages over ubuntu. I was going to try to get ahold of another video card, and maybe try that. What do you think I should do
I have F12 and been using the livecd-creator command since F9 to create liveUSB devices which are used to install Fedora on all the systems (nearly 100) I support at different sites ensuring they have the same build/configuration. About a week ago, I created a new image and when I attempt to install to hard drive, there is an ABRT message displayed;
"A crash in the anaconda-12.46-2.fc12 package has been detected"
Also see attached file.Now I am not able to install to hard drive.
It appears this is a known bug which has been reported at url.and that there is not fix planned. Can anyone confirm this?
If this is the case, does it mean that the �Install to Hard Drive� feature will no longer be available?
i did a preupgrade from fedora 10, i have a new line in grub with the "preupgrade to fedora 11" ... when i choose this.. anaconda run with the normal blue screen running anaconda... but a blacks screen apper with the mouse... the installation not follow and only the black screen with the mouse i can see...some line add to the kernel line of preupgrade fedora 11 to run with another graphical configuration
After installing Fedora 14 and being satisfied with the behaviour and the packages installed for it, i want to replicate the same installation in a few more PCs, so i installed Revisor to make with it an iso file that reflects my actual installation.
The problem is that if i run the software from Applications->System tools->Revisor, nothing happens after giving the user password.
Then i run it from a consele and this error is produced after giving my password: "Cannot find anaconda-runtime in /usr/lib/anaconda-runtime"
But anaconda is the environment used for installation, so it is installed from the very begining. Why this happens?
I'm trying to install F11 on a machine that was running well under F10 just a few hours ago. I made some changes to the disk configuration, involving the addition of a dmraid-controllable fakeRAID card (SiL 3124 I think) and creating a RAID 0 array out of the two drives connected to the motherboard itself (Intel ICH7R). Otherwise the machine's configuration is identical to the way it was when running F10. My problem is thus: when I boot from the installation DVD (64-bit), the boot process doesn't make it even to anaconda. Here is the error I get, right after md devices are autoconfigured:
I'm trying to install F12, over my existing F10. I ran preupgrade, and it installed anaconda into the boot menu, without apparent problems. On reboot, however, it fails with the following message:Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated.Cannot retrieve respository metadata (repomd.xml) for repository: anaconda-InstallationRepo-200911081854.i386. Please verify its path and try again.I must admit to being a bit unclear as to what's going on here. Is it looking in the cached pre-install tree for said repomd.xml, but said tree is somehow corrupt; or is it trying to find it via the network, and failing (for whatever reason).
Tried to install F14 x64 last night, and selected "install or upgrade" from the splash screen. It ran a bunch of text past me a lot faster than I could read it, and the last line (where it ceased all function) said
Code:[ 2.040098] Registered taskstats version 1. I happened to have a 32 bit dvd of the same o/s, and it provides the same error. Anyone know of any parameters that can be entered, perhaps to skip a certain type of test, or whatever it is doing here?
When I'm doing an installation, I select the installation from CD/DVD option for CentOS, but then I don't know how to specify that it should use an anaconda-ks.cfg file that is either on a USB key (or on a Samba network share).
How could I install using the installation DVD, as well as a kickstart file that would specify which packages to enable and other installation settings?
I have a big pb after installing F11 : my partition containing all my photos is now unmountable. Before installing F11, it was in ext3 filesystem
During installing F11 on sda1 (first hard drive), I noticed some strange error messages like "volume doesn't exist" or something like that.
now, when I try to mount my partition of my third hard drive, i get this :
Code: [root@vincent vincent]# mount /dev/sdc1 /home/vincent/sdc1 mount: type inconnu de systme de fichiers 'lvm2pv' which means "mount: filesystem type unknown 'lvm2pv' "
Im actually using Fedora 11 in Dual Boot with VistaI used to have Fedora 11 and then I installed Ubuntu and it (and myself) screwed my partitioning, and Just linux used to run.Ubuntu wrote the boot sector over the NTFS like it was ext3.I tryed everything the get beck my windows partition booting.Reinstalled a Fedora 11 clean, to see if it could help me (thinking in reintstall it later).Using testdisk application I managed to have back access to my disks files, but no boot working. I tryed a lot of things in testdisk and Windows Vista Recorvery, with no work.
So I ran the Acer Recorvery Disks, that reseted my NTFS with Vista to a brand new installation from Acer.Now I want a Full Fresh Fedora Install from DVD but anaconda tells me (in pt-br): "Error in processing the disk sda. Maybe it would be necessary to reinitialize. YOU WILL LOOSE AL THE DATA IN THIS DISK."I really cannot reinitalize it becouse my NB have some recorvery partitions that I use to reinstall the windows to its factory settings, and Im scared of reinitalizing it becouse maybe it could just screw everything and make it not work as well, now with no OS running.The GNOME Partitioning Software just detect a full unpartitioned hard drive. I think the problem is that I changed the LVM to something wierd that anaconda dosent recognizes.Some hardware information (my fedora is in PT-BR):Quote:
I decided to upgrade an old box I use as a server at home. I had been running F8, but after it's end of life and numerous patches since then it was getting a little shaky. I downloaded the KDE Live CD (picked that arbitrarily really since I don't run X on this box - just didn't want to do the whole install over the net) and off I go.
So I booted the CD and added "liveinst" as a boot loader option to kick off the install without starting X and KDE. Just as Anaconda was starting, I got the message "there is not enough memory for a graphical install" and the text based installer starts up. Kinda strange, I thought, since this box had the "recommended" amount of ram mentioned in the F12 release notes. Oh well, so their docs are wrong - wouldn't be the first time and anyway I'm used to doing text based installs from way back.
But this one wasn't like any I'd seen before. After the welcome screen there were only 4 questions - keyboard type, language, timezone, and disk options. Also, at various stages odd characters similar to the Russian alphabet started popping up in various areas on the screen. When it got to the disk options there were 3 - use entire drive, replace existing linux install, and use free space. I picked the 2nd one and moved on. The next screen said my choice was about to be written to disk blah blah blah - but gave me no option to specifiy which partitions to use or how to use them. I should mention here that this box had 3 partitions on it - 1 for swap, 1 for root, and 1 for var...........
I have run preupgrade; the image won't fit on the existing boot sector; so it wants an internet connection, which it has. Then it bombs after it detects the existing installation (Fedora 11), and also detects where the boot record is, which I tell it update. The bug report file generated by anaconda is attached. I would have done this in Bugzilla, but for some reason it will not recognize my login.Critical information:quad x86_64 machine, 8 GB memory, dual boot, two hard drives. hard drive 1 has Linux, hard drive 2 has Vista, the mbr is on hard drive 2.It is possible the unusual configuration is the cause of the problem. I do hope I can get around this, because there is so much stuff installed that it would be a real pain to start from scratch.
When I am trying to install Fedora14_x64 It starts fine upto loading the anaconda.Then The screen goes blank.How to install Fedora14_x64 in my system.I am using Fedora12_x64 currently.
I recently got a shiny new msi notebook and I decided I wanted to dual-boot Linux on it (with Windows 7 Home Premium 64-bit). I started with Ubuntu, when that failed (the GUI wouldn't install properly) I tried Mint. It worked fine, but for some reason, I hate Mint. I deleted the Mint partitions and attempted to claim back the free space in a new partition for Windows 7. For some unbeknownst reason, it failed. Since I didn't desparately need the hard drive space, I said "screw it" and went about my day.
After seeing a friend using Fedora, I figured "why not?" So I downloaded F14 and burned it to a disc and booted it. All went well so I tried installing it. The install process went normal until I reached this screen: I press "Next", and I get this: (Full text here) I start to think that anaconda has something to do with my hard drive partitions, so I open Logical Volume Manager.
Partition 1 is a recovery partition (12 GB). Partition 2, I have no idea, but it's only .1 GB. Partition 3 is the Windows 7 partition (172.29 GB). Partition 4 is 113.20 GB. Unpartitioned space is 113.20 GB.
I know this can't be right, because my hard drive is only 320 GB (and those GB aren't even "real" GB) and the partitions add up to 410.79 GB. I'm thinking that Partition 4 and Unpartitioned space are the same thing, and the existence of the Partition 4 record is the aftermath of the failure to reclaim the disk space for Windows. So how do I go about fixing this (getting rid of Partition 4 or finding a work-around)?
I am trying to install FC 10 from a DVD. It gets to part where it says "Running Anaconda" and the monitor goes "no signal". I am assuming that the video drivers are incorrect. What can I do to change the drivers before anaconda runs?
I am just customizing CentOS and would like to change "Welcome message[image is attached] to something that I wanted. I went trough the anaconda source rpm and found that OS name is being picked by %s and not sure what %s refers to or where is that variable it pointing to.
I am using the "harddrive" option in a kickstart config to have it pick up isolinux files from a USB flash drive. I have been able to get it work by specifying the device name directly, but if I specify a LABEL or UUID, it does not work.Here is what my ks.cfg looks like.
Code: install text harddrive --partition=LABEL="/install" --dir=/ lang en_US.UTF-8
[Code]...
It almost seems like the version of Anaconda in Centos5.4 does not support specifying UUID or LABELs, but I have not been able to confirm that from the Release notes.Appreciate any tips/references/documentation.
I've recently been trying to put Centos on a PC which I have had Windows 2000 server on up until now. The system has an Intel SCSI RAID Controller which seems to be successfully detected before the graphical stage is reached. The system is fairly old now and consists of a p3 processor and 320mb of ram. However when the installer reaches the point of launching Anaconda in graphical mode it seems to start to load but then the system immediately boots itself down Quoting an Abnormal Setup Termination however gives no more details than that. I have tried changing the graphics card to no effect. I am not sure if anyone knows what could be causing the problem the media also shuld be ok as I have used it successfully on other systems.
I have an external DVD burner hooked up to an EEE PC 701SD. The disk has worked on a dell desktop computer, and a 701 (the first eee pc which I built the install on) without a problem, however when I boot up the install disk on the 701SD, I get a message telling me it's unable to download the kickstart file. It's being set to cdrom:/ks.cfg, which should work, but it isn't.... This exact same disk just did a full install on the 701 15 minutes before I ran it on this computer.
I tried to install Fedora 11 on computer with Windows XP as the primary partition, and Fedora 11 as a logical partition. The version of anaconda that ships with Fedora 11 has a bug in the graphical installer, the GUI. The text version of the installer starts up but does not let the user use logical partitions.I have installed Fedora 6 using the graphical installer, and logical partitions.Is there a new version of anaconda for Fedora 11? or Could I use the Fedora 6 anaconda to install Fedora 11?
I'm running F11 and I'd like to run anaconda to install another instance of F11 to a second (blank) hard drive in my system. I'd like to do it without rebooting. The second drive is removable.What's the magic?
I known the Driver Disk can be loaded by anaconda when specifying the 'dd=xx' parameter. But how should I do if I still want to use these drivers which are included in the Driver Disk in an up running Operating System?
I have not a real environment to test it, but looks like the driver modules in the Driver Disk won't be installed into the real installed system. Am I right? Are there some tools which can load Driver Disk in a up running Operating System?
Following situation: I'm trying to make a network-installation of my rootserver with CentOS 5.4 x86_64. This server is hosted by 1and1 a company of the united internet group, which is a big player in europe. The network environment of 1and1 is providing classless static routes via dhcp by using the dhcp option 121. If i'm right anaconda does not support this dhcp option 121 and therefore does not "ask" for the routes. Without the routes configured the traffic does not get through and the network installation fails. An installation from fedora12 (anaconda 12.46) works without any problems.
Is there someone in the dev team that can patch or backport it?
Tried to install Fedora 12 by booting from CD#1 on a Mac G4. First, got a message that video RAM allows only for text installation. OK, but then Anaconda (12.46) just installed some bare-bone software set without any option of package choice! After a longer search I found there`s. no choice for text install! how to configure the net and install things using text mode only (no GNOME present).
I'd like to install Fedora12/13 on a external USB 2.0 HDD. Ive managed to do so with the live image several times, but the DVD installer does not see that particular USB HDD so I cannot install Fedora on it. Its the same with F12 and F13.Ive already tried to start the installation in expert mode. The expert option is ignored or something (linux expert/expert does nothing). Im not sure where exactly to write the options. I chose the rescue line and changed rescue to expert (nothing happend).
Then Ive tried Ctrl+Alt+F2 > "modprobe usb-storage" with no output (that should be right, right?). Again nothing.How to start anaconda (the DVD installer) in expert mode?How to load proper modules (to get the USB Drive to be recognised)?How to install Fedora12/13 from DVD onto USB2.0 HDD?
I want a new kernel RPM in my custom CentOS 5 kickstart distro. I built the kernel, got a nice kernel RPM out, and replaced it in my ks.cfg. The install goes fine until the very end, where Anaconda prints some spurious stuff about mkinitrd failing.I get why it might fail -the kernel version argument to mkinitrd was no doubt for the old kernel. But I have no idea where this is -it's not in the ks.cfg afaict, and so I don't quite get where Anaconda / mkinitrd gets it from.
I'd eventually like to use this kernel for the installer as well, but I think I understand that process much better.How do I tell kickstart / Anaconda / mkinitrd to use the new kernel version number?
I'm trying to install CentOS 5.4 from my local repo, booting the server from centos54-netinstall iso (vmware). I write "linux URL..." during boot. I eventually get prompted for network config, where I choose manual configuration. Hitting OK ignores my config and defaults back to dhcp, which won't work since I don't have any dhcp server available.Whats wrong? Is there a bug in anaconda?
