Can't login to livecd for Fedora 15 any more
by Lars Bjørndal
I have a livecd image built on May 9th. Booting that image, I'm able to
login to console, althouth I need to press ctrl-alt-f2 first. To day, I
built a new image, and with that image, I cannot log on. If I press
ctrl-alt-f2, nothing happens. If I type letters, they are displayed on
the current line in the terminal, but there is no login prompt.
One thing I notice about the two immages that may be related, is that
the image from 9th is about 15 MB larger in size than the immage of
today.
I use the same kickstart file to build the two images.
What could be the reason for this problem, or how should I go on to
solve the issue?
Thanks, and regards,
Lars
13 years
Problems resolved building Fedora 15 remix
by Scott Dowdle
Greetings,
Just wanted to follow up and let everyone know what I was able to successfully build my Fedora 15-based remix again both in the 32-bit and 64-bit flavors so the packages that were breaking livecd-creator's process have been updated, have found their way to where the need to go, and are workiing great.
I'm very excited about the upcoming Fedora 15 release. It is going to be great... even if there is some backlash against GNOME 3 Shell. I'm a KDE user myself but I think GNOME 3 Shell looks pretty sweet.
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
13 years
Problem with Fedora 15 livecd-creator
by Scott Dowdle
Greetings,
I've been keeping up with Fedora 15 development. I'm building a remix of Fedora 15 inside of a Fedora 15 VM. The Fedora 15 VM in question is fully updated as of today. I just recently ran into a problem with my 10th rebuild. I've run into package availability issues here and there over the cycle of my Fedora 15 rebuilds but generally speaking, I haven't really had many problems.
Here's the problem I've run into today... and I've tried rebuilding it 4 times now... with reboots between each attempt and I'm consistently getting the following error:
Error creating Live CD : fsck after resize returned an error!
image to debug at /tmp/resize-image-XXXXXX
Anyone else running into this issue? I've made sure I'm not hitting a full disk or anything else that is ordinary.
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
13 years
Branch 'f15-branch' - 2 commits - imgcreate/creator.py Makefile
by Brian C. Lane
Makefile | 2 +-
imgcreate/creator.py | 7 +------
2 files changed, 2 insertions(+), 7 deletions(-)
New commits:
commit c1863998f95f00006c0f68d8020441b01cdcf131
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Tue May 3 13:27:03 2011 -0700
Version 15.7
diff --git a/Makefile b/Makefile
index 1751834..9832301 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
-VERSION = 15.6
+VERSION = 15.7
INSTALL = /usr/bin/install -c
INSTALL_PROGRAM = ${INSTALL}
commit 9e56f012ea1049871ddce1134163863f68c7de74
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Mon Mar 21 16:11:05 2011 -0700
symlink /etc/mtab to /proc/self/mounts (#688277)
systemd expects the installed system to have this setup.
diff --git a/imgcreate/creator.py b/imgcreate/creator.py
index ec4c1ba..675dcf6 100644
--- a/imgcreate/creator.py
+++ b/imgcreate/creator.py
@@ -536,7 +536,7 @@ class ImageCreator(object):
self.__create_minimal_dev()
- os.symlink("../proc/mounts", self._instroot + "/etc/mtab")
+ os.symlink("/proc/self/mounts", self._instroot + "/etc/mtab")
self.__write_fstab()
@@ -548,11 +548,6 @@ class ImageCreator(object):
from the install root.
"""
- try:
- os.unlink(self._instroot + "/etc/mtab")
- except OSError:
- pass
-
self.__destroy_selinuxfs()
self._undo_bindmounts()
13 years, 1 month
tools/livecd-iso-to-disk.sh
by Brian C. Lane
tools/livecd-iso-to-disk.sh | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
New commits:
commit 3c985ba4735dbf6e75b7e518413b0d02881b3d11
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Thu May 5 16:56:36 2011 -0700
Copy updates and product image files
In order to properly support copying RHEL images to USB we need to
include any updates.img or product.img files that are present on the
original iso.
diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh
index 5261aab..d5c3f65 100755
--- a/tools/livecd-iso-to-disk.sh
+++ b/tools/livecd-iso-to-disk.sh
@@ -1038,7 +1038,11 @@ if [ \( "$srctype" = "installer" -o "$srctype" = "netinst" \) ]; then
echo "Copying DVD image to target device."
mkdir -p $TGTMNT/images/
if [ "$imgtype" = "install" ]; then
- copyFile $SRCMNT/images/install.img $TGTMNT/images/install.img || exitclean
+ for img in install.img updates.img product.img; do
+ if [ -e $SRCMNT/images/$img ]; then
+ copyFile $SRCMNT/images/$img $TGTMNT/images/$img || exitclean
+ fi
+ done
fi
if [ "$srctype" = "installer" -a -z "$skipcopy" ]; then
cp $SRC $TGTMNT/
13 years, 1 month
pxeboot images out of space
by Howard Powell
Hi -
I've been using the livecd set of tools to build a pxeboot image for a set of compute nodes in our local HPC environment. The livecd project has allowed me to make all of the compute nodes diskless, and any software errors are trivial to fix (just reboot).
I've run into one problem - there appears to be a problem with my image where if any process on a node produces a large amount of disk I/O to /tmp - somewhere around 0.5GiB or more in one operation, causes the root filesystem to panic and the node must be rebooted.
Creating the image is as simple as:
# LANG=C livecd-creator --config=/local/nodes/hyades-nodes.cfg --fslabel=hyades -t /local/nodes/
# livecd-iso-to-pxeboot /local/nodes/hyades.iso
The exact error caused during the I/O operation on a compute node is logged as:
May 2 16:11:32 eth-c31.cluster kernel: device-mapper: snapshots: Invalidating snapshot: Unable to allocate exception.
May 2 16:11:32 eth-c31.cluster syslogd: /var/log/messages: Read-only file system
May 2 16:11:32 eth-c31.cluster kernel: Buffer I/O error on device dm-0, logical block 997925
May 2 16:11:32 eth-c31.cluster kernel: lost page write due to I/O error on dm-0
May 2 16:11:32 eth-c31.cluster kernel: Aborting journal on device dm-0.
May 2 16:11:32 eth-c31.cluster kernel: __journal_remove_journal_head: freeing b_committed_data
May 2 16:11:32 eth-c31.cluster last message repeated 5 times
May 2 16:11:32 eth-c31.cluster kernel: journal commit I/O error
May 2 16:11:32 eth-c31.cluster kernel: ext3_abort called.
May 2 16:11:32 eth-c31.cluster kernel: EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
May 2 16:11:32 eth-c31.cluster kernel: Remounting filesystem read-only
May 2 16:11:32 eth-c31.cluster kernel: __journal_remove_journal_head: freeing b_committed_data
May 2 16:11:32 eth-c31.cluster kernel: __journal_remove_journal_head: freeing b_committed_data
May 2 16:11:32 eth-c31.cluster kernel: __journal_remove_journal_head: freeing b_frozen_data
May 2 16:11:32 eth-c31.cluster kernel: __journal_remove_journal_head: freeing b_frozen_data
May 2 16:11:32 eth-c31.cluster kernel: __journal_remove_journal_head: freeing b_committed_data
May 2 16:11:32 eth-c31.cluster kernel: __journal_remove_journal_head: freeing b_frozen_data
May 2 16:11:43 eth-c31.cluster kernel: printk: 259144 messages suppressed.
May 2 16:11:43 eth-c31.cluster kernel: Buffer I/O error on device dm-0, logical block 737
May 2 16:11:43 eth-c31.cluster kernel: lost page write due to I/O error on dm-0
May 2 16:11:43 eth-c31.cluster kernel: Buffer I/O error on device dm-0, logical block 115035
May 2 16:11:43 eth-c31.cluster kernel: lost page write due to I/O error on dm-0
Googling for information suggests that the device underlying the filesystem is running out of space, which explains why the filesystem crashes. df reports that the / filesystem should have space:
[root@c31 ~]# df -h
/dev/mapper/live-rw 6.0G 1.2G 4.8G 19% /
I've adjusted the "part / -size 6144" parameter in my kickstart file, but I see no effective results other than the size that df reports changes to match what I specify. Writing a file to /tmp larger than about 512MB causes the filesystem to continue to crash even if the space is reported as available.
Each compute node has 32GB of system memory, and is running an x86_64 kernel.
I'm open to any suggestions on how to fix this issue.
Thanks!
Howard
Howard Powell
hbp4c(a)virginia.edu
13 years, 1 month
liveinst
by Lars Bjørndal
Hi
I had unsuccess while trying the liveinst command from the livecd. The
command line looked like:
liveinst -T --nofb=NOFB
The log output was:
[...]
19:39:24,831 INFO anaconda: moving (1) to step network
19:39:25,009 CRIT anaconda: anaconda 15.29 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 175, in getActiveNetDevs
nm = bus.get_object(isys.NM_SERVICE, isys.NM_MANAGER_PATH)
File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 100, in getDefaultHostname
for dev in getActiveNetDevs():
File "/usr/lib/python2.7/site-packages/pyanaconda/textw/network_text.py", line 29, in __call__
hname = network.getDefaultHostname(anaconda)
File "/usr/lib/python2.7/site-packages/pyanaconda/text.py", line 553, in run
rc = win(self.screen, instance)
File "/usr/sbin/anaconda", line 932, in <module>
anaconda.intf.run(anaconda)
DBusException: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status' for details.
Did I do any mistake, or is this a bug? Could it be fixed?
Thanks, and best regards,
Lars
13 years, 1 month
Autologin into text console in Fedora 15
by Lars Bjørndal
Previously, in Fedora 14, I had this working.
##from kickstart file:
sed -i 's/exec \/sbin\/mingetty $TTY/exec \/sbin\/mingetty --autologin root $TTY/' /etc/init/tty.conf
Doesn't that work any more? What can I do to autologin root after livcd
bootup?
Regards,
Lars
13 years, 1 month
norhgb doesn't work
by Lars Bjørndal
Hello, list
In my kickstart file, I use 'bootloader --append=nomodeset norhgb'. Even
though, I get the graphical boot when booting the live media. Last, I
tried it, building a Fedora 15 livecd. What can I do to get the old text
output during boot?
Regards,
Lars
13 years, 1 month
