Red Hat Bugzilla – Bug568367 Mounting disks read-only in rescue mode presents error Last modified: 2013-09-02 02:45:54 EDT Home | New | Search | [?] | Reports | Requests | Help ks.cfg is just to mkdir /tmp/mytestI have used KS configurator and anaconda-ks.cfg template for ks.cfg. Bug568367 - Mounting disks read-only in rescue mode presents error Summary: Mounting disks read-only in rescue mode presents error Status: CLOSED RAWHIDE Aliases: None Product: Fedora Classification: Fedora Component: anaconda (Show IMHO bug can be closed. have a peek here
Boot the installer into rescue mode on a previously installed system 2. Note You need to log in before you can comment on or make changes to this bug. Actual results: 20:11:39,561 INFO loader: kernel command line: initrd=initrd.img stage2=hd:LABEL="Fedora" xdriver=vesa nomodeset BOOT_IMAGE=vmlinuz 20:11:39,561 DEBUG loader: no ifcfg files found in /etc/sysconfig/network-scripts 20:11:39,561 INFO loader: anaconda version 13.32 on x86_64 starting Insert it, using the rest of the file as an example, so it goes below the kernel /vmlinuz line and above the line the reads title Fedora ....12 kernel /vmlinuz-220.127.116.11-124.fc13.x86_64 ro https://bugzilla.redhat.com/show_bug.cgi?id=568367
Status: NEW Aliases: None Product: Red Hat Enterprise Linux 7 Classification: Red Hat Component: python-blivet (Show other bugs) Sub Component: --- Version: 7.1 Hardware: Unspecified Unspecified Priority unspecified Severity unspecified TargetMilestone: Note You need to log in before you can comment on or make changes to this bug. What exactly do I need to change? ---/etc/grub.conf--- title Upgrade to Fedora 13 (Goddard) kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=df634edf-e7b9-401e-9589-4c0e6e36aa8a:/upgrade/ks.cfg stage2=http://mirrors.rit.edu/fedora/linux/releases/13/Fedora/x86_64/os/images/install.img initrd /upgrade/initrd.img title Fedora (18.104.22.168-124.fc13.x86_64) root (hd0,0) kernel /vmlinuz-22.214.171.124-124.fc13.x86_64 ro root=/dev/mapper/vg_the-lv_root The │ │ system will reboot automatically when │ │ you exit from the shell. │ │ │ │ ┌────┐ │ │ │ OK │ │ │ └────┘ │ │ │
After some time the installation fails with following anaconda exception anaconda 19.28-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1194, in _selectYumGroup raise NoSuchGroup(groupid) File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1299, Comment 6 David Shea 2013-08-06 09:25:58 EDT Glad to hear it's working. This information is useful for debugging build issues, since the last messages usually indicate where a problem resides. The upgrade crashes with the "the root for the previously installed system was not found".
Please modify your kickstart file to use this updated syntax.") % _("Script"), DeprecationWarning) 06:36:22,960 INFO anaconda: ISCSID is /usr/sbin/iscsid 06:36:22,960 INFO anaconda: no initiator set 06:36:23,070 INFO anaconda: no /tmp/fcpconfig; not I do set log level as debug. Note You need to log in before you can comment on or make changes to this bug. Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Red Hat
if use "askmethod" argument to boot, select URL to provide stage2 location, it will download install.img Version-Release number of selected component (if applicable): anaconda of f13 ga How reproducible: 100% more Summary: Text mode installation fails with anaconda exception. which failed > because the filesystem was RO. Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results.
When I hit CTRL-ALT-F3, I saw: INFO storage: FOund sda for biosdev 80 WARNING anaconda: step installtype does not exist WARNING anaconda: step checkdeps does not exist WARNING anaconda: step dependencies navigate here I then tried blowing away all of the Fedora 13 references in /etc/grub.conf. This syntax has been deprecated. Thanks.
Status: CLOSED NOTABUG Aliases: None Product: Fedora Classification: Fedora Component: anaconda (Show other bugs) Sub Component: --- Version: 19 Hardware: s390x All Priority unspecified Severity high TargetMilestone: --- TargetRelease: --- Assigned SANT
The root for the previous system was not found. [Exit installer]. The only thing I need to mention in particular is I use VMWare fussion to install a virtual centOS. Comment 2 Michał Piotrowski 2010-03-11 15:00:35 EST Language - Polish Keyboard - pl2 Comment 3 Michał Piotrowski 2010-03-11 15:04:03 EST What if I change locale?
Yes. It will make things faster Top Larkin38 Posts: 2 Joined: 2012/01/05 10:29:42 Re: kickstart issues Quote Postby Larkin38 » 2012/01/05 10:47:23 Kickstart is used by numerous organizations to automate Redhat, Fedora Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Red Hat Bug609379 - modification to stage2 in grub command line doesn't work Summary: modification to stage2 in grub command line doesn't work Status: CLOSED NOTABUG Aliases: None Product: Fedora Classification: Fedora Component:
After going through the options, I finally was presented again with: Upgrade root not found. So instead of them asking for it, I'm taking the liberty to ask it from you for them to analyze. Please modify your kickstart file to use this updated syntax. http://silkiconfinder.com/failed-to/failed-to-create-context-0x3005.html Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Red Hat
Comment 5 IBM Bug Proxy 2013-08-06 02:41:11 EDT ------- Comment From email@example.com 2013-08-06 06:31 EDT------- This problem was due to issue with repository being used for installation. setting it up 06:36:07,384 DEBUG loader: configuring device eth0 06:36:16,393 INFO loader: get_connection (2098): NetworkManager connected 06:36:16,394 INFO loader: file location: http://10.66.65.92/ks.cfg 06:36:16,394 INFO loader: transferring http://10.66.65.92/ks.cfg 06:36:16,787 INFO loader: setting Closing the bug. Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Red Hat
See if the UUID's are different. warnings.warn(_("%s does not end with %%end. This syntax has been deprecated. Examine /var/log/anaconda/anaconda.storage.log Actual results: Couple of SELinux related warnings present Expected results: No SELinux related warnings Additional info: Comment 1 Ladislav Jozsa 2015-01-28 08:32:24 EST Created attachment 985149 [details] anaconda.ifcfg.log Comment
David Lehman 2009-12-15 18:28:03 UTC PermalinkRaw Message ---isys/isys.py | 8 ++++++--1 files changed, 6 insertions(+), 2 deletions(-)diff --git a/isys/isys.py b/isys/isys.pyindex 14d2a5d..9341c6b 100755--- a/isys/isys.py+++ b/isys/isys.py@@ -612,9 +612,13 @@ def matchPathContext(fn):# @param instroot which failed because the filesystem was RO. The errors I receive are: "The root for the previous installed system was not found" and "INFO Stage: Product Fedora version 13 found on vg-the-lv_root is not upgradable". Once both directives are enabled, you will get output similar to the following each time a host builds:May 20 22:36:15 drfeelgood INFO trying to mount sda1 on /May 20 22:36:15 drfeelgood
© Copyright 2017 silkiconfinder.com. All rights reserved.