Problem with build after udev update
by Scott Dowdle
Greetings,
I've noticed that my most recent remix builds will not boot. I get the following error:
- - - -
No root device found
Boot has failed, sleeping forever.
- - - -
I think it is because of a change made to udev causing the need for a change in dracut. Can anyone duplicate this problem? See bug:
https://bugzilla.redhat.com/show_bug.cgi?id=627364
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
13 years, 7 months
mkbackup as LiveOS doubles as mkclone was: Development of biarch live CD script.
by Frederick Grose
Starting new thread:
with Forwarded conversation
Subject: was: [Fedora-livecd-list] Development of biarch live CD script.
------------------------
From: *Jasper Hartline* <jasper.hartline(a)gmail.com>
Date: Sat, Aug 28, 2010 at 4:50 PM
To: livecd(a)lists.fedoraproject.org
Here is another one I've started work on:
http://autopsy.liveprojects.info/scripts/mkbackup.py
It's purpose is to create a LiveDVD out of the running system.
This LiveDVD in conjunction with Anaconda's liveinst method of doing a
direct copy
of sr0 to sda or similar lays the basis for using this as a possible
installable, backup solution.
Also has LiveCD/DVD capability, which is ok.
If you come up with anything we can do on that one too I would be glad to
know.
I looked at the patch you sent for mkbiarch.py and the directory part isn't
a good thing, we don't want to make it so non-dynamic.
If we create /x86 and /x64 we could even create /x86/{kde,gnome}
/x64/{kde,gnome} which would in thoery, be able to create USB disk
image fitting all 4 ISO discs, two for x86 and two for x64.
Also adding Live.ISO capability, we want to keep extlinux and isolinux dirs.
mkbiarch.py still needs checkisomd5() though.
It is apparently only available in Anaconda, but I can't find where.
I am pretty sure it implants a MD5SUM file somewhere hidden on the
ISO,m which can be checked against
the ISO files to make sure they are not corrupt. This was really
something that could be useful.. and thank you for bringing it, up.
----------
From: *Frederick Grose* <fgrose(a)gmail.com>
Date: Sat, Aug 28, 2010 at 6:02 PM
To: livecd(a)lists.fedoraproject.org
See https://bugzilla.redhat.com/show_bug.cgi?id=448030 , in particular, the
edit-livecd and edit-liveos attachments. This posting has some more
background,
http://lists.fedoraproject.org/pipermail/livecd/2010-August/006098.html .
It's good to see someone else working on this goal.
--Fred
----------
From: *Jasper Hartline* <jasper.hartline(a)gmail.com>
Date: Sat, Aug 28, 2010 at 6:19 PM
To: livecd(a)lists.fedoraproject.org
Well. These are similar but not the same.
mkbackup.py would create a LiveCD/LiveDVD out of a running system.
I don't know what edit-liveos does or edit-livecd but to my knowledge
they are only for inserting packages into an already built LiveCD ISO.
The mkbackup.py script does not do that, it simply would create a
LiveCD/DVD out of the current installed system as a means for a Live
bootable backup image, which with Anaconda, can be reinstalled to a
machine in case of disk failure or other problems.
----------
From: *Frederick Grose* <fgrose(a)gmail.com>
Date: Sat, Aug 28, 2010 at 6:34 PM
To: livecd(a)lists.fedoraproject.org
Yes, and as the running system may have been modified, it is much like an
intentional
customization (if the dump procedure does not exclude changes).
edit-livecd is for inserting packages or files; edit-liveos is proposed as a
new version to accommodate customization and branding.
Not being familiar with dump, I found this thread interesting,
http://lists.samba.org/archive/linux/2005-April/013361.html .
--Fred
----------
From: *Bruno Wolff III* <bruno(a)wolff.to>
Date: Sat, Aug 28, 2010 at 7:04 PM
To: Jasper Hartline <jasper.hartline(a)gmail.com>
Cc: livecd(a)lists.fedoraproject.org
On Sat, Aug 28, 2010 at 22:19:04 +0000,
That's a pretty neat feature. It even gives you a good way to test that
your backups work. You'd still want to have some incremental backups to
save space.
This might be worth calling a feature for F15.
----------
From: *Jasper Hartline* <jasper.hartline(a)gmail.com>
Date: Sat, Aug 28, 2010 at 10:28 PM
To: livecd(a)lists.fedoraproject.org
Ok. I thought it was pretty neat too, you really have some range of
motion in your backups
when and if you can do it this way, instead of you know, the random
disk-backup image file laying around on CD.
The only really limitation I see it has, is the fact, a DVD is 4.7GB.
This means, if we
squash the root filesystem of any given system, files there must not
be larger than the maximum of what will
fit squashed in 4.7GB. Smaller of course is not an issue, but until
Blueray is more popular..
I think this Live backup media limitation would need to be limited to
a single DVD size.
There may be ways around this, maybe not. I will be at least working on
getting
some base level functionality working with it here in the coming days
and would be glad to hear suggestions.
----------
From: *Jasper Hartline* <jasper.hartline(a)gmail.com>
Date: Sat, Aug 28, 2010 at 10:35 PM
To: livecd(a)lists.fedoraproject.org
Hm. I'm not sure I follow yet, but maybe I'm just not understanding.
What I want to work on with mkbackup.py is creating a LiveCD/LiveDVD
out of the running system, not a LiveCD system created with livecd-creator.
mkbackup.py will take the root filesystem of any given host and squash it up
and create a Live media out of it, essentially making an exact backup
of the machine's drive, which has the ability to run as a Live operating
system, but
also is installable with Anaconda's liveinst method.
++++++++++++++++++++++++++
(end of forwarded conversation)
For those who are interested in taking a stock LiveOS image and customizing
it with specific content, such as adding or removing features, documents,
images, bookmarks, ebooks, etc., the procedure you describe will serve those
purposes as well.
(The Sugar on a Stick Spin folks, http://spins.fedoraproject.org/soas/, have
be working on customization kits for this purpose. We use Live USB devices
to provide a portable learning platform, and would like to allow teachers
and students replicate a course or semester of study or work (or proposed
study or work) from their working Live USB device to their students,
classmates, or playmates.
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone describes the
project and provides a more crude, copy-overlay and copy-home solution based
on the livecd-iso-to-disk script.)
So one feature we would need to achieve is to be able to mkbackup/mkclone
with a running LiveOS image.
--Fred
13 years, 7 months
/dev/live no longer being created since udev-153 update?
by Aaron Cohen
Hi all,
If I "rdbreak" on the kernel command line, I see that /dev/live is
created correctly (though it now points to
/dev/disk/by-uuid/<aBunchOfDigits> where formerly it pointed to
/dev/disk/by-label/DiskLabel).
After switch_root though, /dev/live is gone.
If I add "udevlog" to the command line, I see the following in
/dev/.udev/udev.log (see particularly where it says, "link_update: no
reference left, remove '/dev/live'"). I'm not positive it's the udev
update that is causing my problem, but it's my current best guess.
1282809066.068591 [1006] util_run_program: '/sbin/blkid' (stdout)
'ID_FS_UUID=154d47db-ab8e-4e6b-9968-196322d73e50'
1282809066.068610 [1006] util_run_program: '/sbin/blkid' (stdout)
'ID_FS_UUID_ENC=154d47db-ab8e-4e6b-9968-196322d73e50'
1282809066.068616 [1006] util_run_program: '/sbin/blkid' (stdout)
'ID_FS_SEC_TYPE=ext2'
1282809066.068621 [1006] util_run_program: '/sbin/blkid' (stdout)
'ID_FS_VERSION=1.0'
1282809066.068626 [1006] util_run_program: '/sbin/blkid' (stdout)
'ID_FS_TYPE=ext3'
1282809066.068631 [1006] util_run_program: '/sbin/blkid' (stdout)
'ID_FS_USAGE=filesystem'
1282809066.068942 [1006] util_run_program: '/sbin/blkid -o udev -p
/dev/sdb2' returned with exitcode 0
1282809066.068991 [1006] udev_rules_apply_to_event: LINK
'disk/by-uuid/154d47db-ab8e-4e6b-9968-196322d73e50'
/lib/udev/rules.d/60-persistent-storage.rules:66
1282809066.069164 [1006] udev_rules_apply_to_event: IMPORT
'fstab_import sdb2 block/8:18
disk/by-id/usb-Corsair_VoyagerGT_A034000000000085-0:0-part2
disk/by-path/pci-0000:00:1d.7-usb-0:5:1.0-scsi-0:0:0:0-part2
disk/by-uuid/154d47db-ab8e-4e6b-9968-196322d73e50 mapper/'
/lib/udev/rules.d/79-fstab_import.rules:1
1282809066.069183 [1006] util_run_program: 'fstab_import sdb2
block/8:18 disk/by-id/usb-Corsair_VoyagerGT_A034000000000085-0:0-part2
disk/by-path/pci-0000:00:1d.7-usb-0:5:1.0-scsi-0:0:0:0-part2
disk/by-uuid/154d47db-ab8e-4e6b-9968-196322d73e50 mapper/' started
1282809066.072679 [1006] util_run_program: 'fstab_import sdb2
block/8:18 disk/by-id/usb-Corsair_VoyagerGT_A034000000000085-0:0-part2
disk/by-path/pci-0000:00:1d.7-usb-0:5:1.0-scsi-0:0:0:0-part2
disk/by-uuid/154d47db-ab8e-4e6b-9968-196322d73e50 mapper/' returned
with exitcode 1
1282809066.072745 [1006] udev_rules_apply_to_event: IMPORT
'udisks-part-id /dev/sdb2' /lib/udev/rules.d/80-udisks.rules:85
1282809066.072766 [1006] util_run_program: 'udisks-part-id /dev/sdb2' started
1282809066.081692 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'libudev: udev_device_new_from_syspath: '
1282809066.081727 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'device 0x9f4e110 has devpath
'/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb2''
1282809066.081924 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'libudev: udev_device_new_from_syspath: '
1282809066.081943 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'device 0x9f4fca0 has devpath
'/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/host2/target2:0:0/2:0:0:0/block/sdb''
1282809066.082100 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'libudev: udev_device_read_db: '
1282809066.082118 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'device 0x9f4fca0 filled with db file data'
1282809066.082386 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'using device_file=/dev/sdb
syspath=/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/host2/target2:0:0/2:0:0:0/block/sdb,
offset=3372364800 ao=0 and number=2 for /dev/sdb2'
1282809066.083758 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'Entering MS-DOS parser (offset=0, size=4143972352)'
1282809066.083784 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.083807 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'MSDOS_MAGIC found'
1282809066.083823 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.083844 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'looking at part 0 (offset 32256, size 3372332544, type
0x07)'
1282809066.083859 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.083874 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'new part entry'
1282809066.083888 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.083917 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'looking at part 1 (offset 3372364800, size 764951040, type
0x83)'
1282809066.083933 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.083949 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'new part entry'
1282809066.083963 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.083980 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'looking at part 2 (offset 0, size 0, type 0x00)'
1282809066.083995 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.084010 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'new part entry'
1282809066.084024 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.084041 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'looking at part 3 (offset 0, size 0, type 0x00)'
1282809066.084056 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.084070 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'new part entry'
1282809066.084085 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.084100 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'Exiting MS-DOS parser'
1282809066.084115 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.084130 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) 'MSDOS partition table detected'
1282809066.084145 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stderr) ''
1282809066.084206 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION=1'
1282809066.084238 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_SCHEME=mbr'
1282809066.084262 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_NUMBER=2'
1282809066.084285 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_TYPE=0x83'
1282809066.084308 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_SIZE=764951040'
1282809066.084331 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_LABEL='
1282809066.084353 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_UUID='
1282809066.084375 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_FLAGS=boot'
1282809066.084401 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/host2/target2:0:0/2:0:0:0/block/sdb'
1282809066.084424 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_OFFSET=3372364800'
1282809066.084447 [1006] util_run_program: '/lib/udev/udisks-part-id'
(stdout) 'UDISKS_PARTITION_ALIGNMENT_OFFSET=0'
1282809066.084753 [1006] util_run_program: 'udisks-part-id /dev/sdb2'
returned with exitcode 0
1282809066.085062 [1006] udev_rules_apply_to_event: RUN
'socket:@/org/freedesktop/hal/udev_event'
/etc/udev/rules.d/90-hal.rules:2
1282809066.085084 [1006] udev_event_execute_rules: no node name set,
will use kernel supplied name 'sdb2'
1282809066.085279 [1006] udev_device_update_db: created db file for
'/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb2'
in '/dev/.udev/db/block:sdb2'
1282809066.085291 [1006] udev_node_update_old_links: update old name,
'/dev/live' no longer belonging to
'/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb2'
1282809066.085349 [1006] link_update: no reference left, remove '/dev/live'
1282809066.085365 [1006] udev_node_add: creating device node
'/dev/sdb2', devnum=8:18, mode=0660, uid=0, gid=6
1282809066.085376 [1006] udev_node_mknod: preserve file '/dev/sdb2',
because it has correct dev_t
1282809066.085382 [1006] udev_node_mknod: set permissions /dev/sdb2,
060660, uid=0, gid=6
1282809066.086706 [1006] node_symlink: preserve already existing
symlink '/dev/block/8:18' to '../sdb2'
1282809066.086907 [1006] link_find_prioritized: found 'b8:18' claiming
'/dev/.udev/links/disk\x2fby-id\x2fusb-Corsair_VoyagerGT_A034000000000085-0:0-part2'
1282809066.086920 [1006] link_update: creating link
'/dev/disk/by-id/usb-Corsair_VoyagerGT_A034000000000085-0:0-part2' to
'/dev/sdb2'
1282809066.086936 [1006] node_symlink: preserve already existing
symlink '/dev/disk/by-id/usb-Corsair_VoyagerGT_A034000000000085-0:0-part2'
to '../../sdb2'
1282809066.087013 [1006] link_find_prioritized: found 'b8:18' claiming
'/dev/.udev/links/disk\x2fby-path\x2fpci-0000:00:1d.7-usb-0:5:1.0-scsi-0:0:0:0-part2'
1282809066.087023 [1006] link_update: creating link
'/dev/disk/by-path/pci-0000:00:1d.7-usb-0:5:1.0-scsi-0:0:0:0-part2' to
'/dev/sdb2'
1282809066.087037 [1006] node_symlink: preserve already existing
symlink '/dev/disk/by-path/pci-0000:00:1d.7-usb-0:5:1.0-scsi-0:0:0:0-part2'
to '../../sdb2'
1282809066.087109 [1006] link_find_prioritized: found 'b8:18' claiming
'/dev/.udev/links/disk\x2fby-uuid\x2f154d47db-ab8e-4e6b-9968-196322d73e50'
1282809066.087118 [1006] link_update: creating link
'/dev/disk/by-uuid/154d47db-ab8e-4e6b-9968-196322d73e50' to
'/dev/sdb2'
1282809066.087133 [1006] node_symlink: preserve already existing
symlink '/dev/disk/by-uuid/154d47db-ab8e-4e6b-9968-196322d73e50' to
'../../sdb2'
1282809066.087233 [1006] udev_monitor_send_device: passed -1 bytes to
monitor 0x95f9278
1282809066.087249 [1006] udev_watch_begin: adding watch on '/dev/sdb2'
1282809066.087523 [1006] udev_device_update_db: created db file for
'/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb2'
in '/dev/.udev/db/block:sdb2'
-- Aaron
13 years, 8 months
Re: [Fedora-livecd-list] Bring me up to speed on using git for livecd-tools
by Jasper Hartline
On Thu, Aug 12, 2010 at 1:33 PM, Bruno Wolff III <bruno(a)wolff.to> wrote:
> For a simple fix, I would use git clone to get a local copy of the
> repo if I didn't already have one. Otherwise I would use git pull to get
> in sync with upstream changes.
Right, this is a good practice especially if you have patches or
something you have changed over a period of a few days, like say 6
patches you have been testing locally over a period of 3 days or so.
> Then git commit -a commits all of the local changes you have made locally.
Aha. So git commit -a actually syncs your local git checkout to say that
when you want to push, the local changes actually should remain. Ok.
> Then git push pushes the changes upstream. If something changed upstream
> then this will fail. I am not sure off hand the best way to work
> around it. But there should be something that is easy.
I am pretty sure there is a gitmerge tool.
Check this section if it seems correct:
https://fedoraproject.org/wiki/Using_Fedora_GIT#Using_git_mergetool_to_re...
> For fedpkg, I am using that and a mixture of native git commands to do
> work. But I haven't really settled on a process yet.
I would agree fedpkg isn't fully featured yet.
Will keep this message for reference.
13 years, 8 months
Karma for livecd-tools-033
by Bruno Wolff III
If anyone has tested livecd-tools-033 on F14, F13 or F12 (but especially F14)
please add appropriate karma in bodhi.
I want to get the F14 release into stable before we put another update into
testing.
Thanks.
13 years, 8 months
033-3 for f12 and F13
by Bruno Wolff III
I built livecd-tools for f12 and f13 and have requested a push to testing.
I think we are going to bring our next build back to f12 and f13 as well,
so those builds will likely be replaced before they would get pushed to
stable.
They should provide a relatively easy way to let people build images using
an f14 repo on f12 or f13. (There are also squashfs-tools updates for people
running into the large inode issue.)
13 years, 8 months
