diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010540.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010540.html | 231 |
1 files changed, 231 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010540.html b/zarb-ml/mageia-dev/2011-December/010540.html new file mode 100644 index 000000000..b8d836a05 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010540.html @@ -0,0 +1,231 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Issues with dracut + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Issues%20with%20dracut&In-Reply-To=%3C20111216235247.0157a2ff%40werewolf.home%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010617.html"> + <LINK REL="Next" HREF="010542.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Issues with dracut</H1> + <B>JA Magallon</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Issues%20with%20dracut&In-Reply-To=%3C20111216235247.0157a2ff%40werewolf.home%3E" + TITLE="[Mageia-dev] Issues with dracut">jamagallon at ono.com + </A><BR> + <I>Fri Dec 16 23:52:47 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010617.html">[Mageia-dev] Issues with dracut +</A></li> + <LI>Next message: <A HREF="010542.html">[Mageia-dev] Issues with dracut +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10540">[ date ]</a> + <a href="thread.html#10540">[ thread ]</a> + <a href="subject.html#10540">[ subject ]</a> + <a href="author.html#10540">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Fri, 16 Dec 2011 12:35:22 +0000 +Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote: + +><i> Hiya, +</I>><i> +</I>><i> 'Twas brillig, and JA Magallon at 16/12/11 12:06 did gyre and gimble: +</I>><i> > After those couple previous thread it looks like move to dracut is +</I>><i> > ongoing, so I decided to try it. +</I>><i> +</I>><i> Good! This is exactly the kind of feedback we need! +</I>><i> +</I>><i> > I found a couple problems: +</I>><i> > +</I>><i> > - dracut inists on loading nouveau driver. With mknitrd, just booting with nokmsboot +</I>><i> > works. Booting with a dracut generated initrd ignores that. I think it is plymouth +</I>><i> > that forces it, even if I added 'blacklist nouveau' in a .conf file in modprobe.d: +</I>><i> > +</I>><i> > dracut -f: +</I>><i> +</I>><i> I'll include it but if it's blacklisted, it shouldn't ultimately be used +</I>><i> in the ramfs even if it's included. That said, it's clearly inefficient +</I>><i> to include it if it is blacklisted so we should try and fix that. Anssi, +</I>><i> could this be your code to detect the h/w that causes it to bypass any +</I>><i> blacklist checks (not sure if there are actually any blacklist checks +</I>><i> when building the initrd... not relaly looked at it much)ç +</I> +Clue... +Let's state all my findings. As 'nokmsboot' was ignored, i remembered CentOS +where the nvidia installer achived the same blacklisting nouveau. +I added the blacklist in /etc/modprobe.d/display-driver.conf, which is a +symlink to /etc/nvidia-current/modprobe.conf. It didn't work. +After the fiasco with symlinks in systemd, i tried creting a new file. +And it worked. So there is something strange with symlinked files... + +><i> +</I>><i> I think the nokmsboot parameter is not working in dracut because the +</I>><i> udev rule that interprets it uses the grep command and that is not +</I>><i> currently included in the ramdisk. I could hack it in easy enough, but +</I>><i> we should maybe see if a more minimal method of detecting it in the +</I>><i> commandline is possible. +</I>><i> +</I> +At boot I get a message about (bin/grep non existent, right... + +><i> +</I>><i> > - initrd from dracut fails to detect one of my drives, and booting stops: +</I>><i> +</I>><i> OK, this is more interesting. +</I>><i> +</I>><i> > systemd[1]: Job dev-sdd1.device/start timed out. +</I>><i> > systemd[1]: Job fedora-autorelabel.service/start failed with result 'dependency'. +</I>><i> > systemd[1]: Job fedora-autorelabel-mark.service/start failed with result 'dependency'. +</I>><i> > systemd[1]: Job mandriva-boot-links.service/start failed with result 'dependency'. +</I>><i> > systemd[1]: Job local-fs.target/start failed with result 'dependency'. +</I>><i> > systemd[1]: Triggering OnFailure= dependencies of local-fs.target. +</I>><i> > systemd[1]: Job export-video.mount/start failed with result 'dependency'. +</I>><i> > systemd[1]: Job home-shared-media-video.mount/start failed with result 'dependency'. +</I>><i> > systemd[1]: Job dev-sdd1.device/start failed with result 'timeout'. +</I>><i> +</I>><i> +</I>><i> When this happens you should get an emergency shell right? In this shell +</I>><i> you should be able to do: "mount /home/shared/media/video" and it should +</I>><i> work, then you should be able to do "systemctl start local-fs.target" +</I>><i> and it should succeed. And you can then do "systemctl start +</I>><i> graphical.target" to continue to a normal boot. +</I>><i> +</I> +I found the problem: + +lsscsi: +werewolf:~/dr# cat lsscsi* +[0:0:0:0] disk ATA ST3250310AS 3.AA /dev/sda +[1:0:0:0] disk ATA WDC WD3200AVJS-6 12.0 /dev/sdb +[2:0:0:0] disk ATA ST3320620AS 3.AA /dev/sdc +[3:0:0:0] disk ATA ST3500418AS CC38 /dev/sdh +[5:0:0:0] cd/dvd HL-DT-ST DVDRAM GH22NS50 TN01 /dev/sr0 +[6:0:0:0] disk Generic USB CF Reader 0.00 /dev/sdd +[6:0:0:1] disk Generic USB SD Reader 0.00 /dev/sde +[6:0:0:2] disk Generic USB MS Reader 0.00 /dev/sdf +[6:0:0:3] disk Generic USB SM Reader 0.00 /dev/sdg + +The disk has been renamed as sdh !! +I changed the mounting points from devices to labels and all worked fine. + +This will probably not be an issue with standard install, using UUIDs, +but the real problem is that drive name asssignment is even more random +(well, interlaced ;)). + +><i> > If I rengerate initrd with mkinitrd, system boots fine. +</I>><i> +</I>><i> Sadly mkinitrd fails with anything relating to LVM when used with +</I>><i> systemd so we really do need to solve the problem with dracut to get +</I>><i> this nailed. I'm sure it's possible :) +</I>><i> +</I>><i> +</I>><i> > fstab is like: +</I>><i> > +</I>><i> > /dev/sda1 / ext4 acl,relatime 1 1 +</I>><i> > none /proc proc defaults 0 0 +</I>><i> > /dev/sda2 /opt ext4 acl,relatime 1 2 +</I>><i> > /dev/sda3 swap swap defaults 0 0 +</I>><i> > /dev/sdb1 /home ext4 acl,relatime 1 2 +</I>><i> > /dev/sdc1 /home/shared/media/music ext4 acl,relatime 1 2 +</I>><i> > /dev/sdd1 /home/shared/media/video ext4 acl,relatime 1 2 +</I>><i> > +</I>><i> > /home/shared/media/music /export/music bind bind 0 0 +</I>><i> > /home/shared/media/video /export/video bind bind 0 0 +</I>><i> > /home/shared/in /export/in bind bind 0 0 +</I>><i> > /opt/soft /export/soft bind bind 0 0 +</I>><i> +</I>><i> +</I>><i> That all looks OK to me. +</I>><i> +</I>><i> > lsscsi: +</I>><i> > werewolf:~# lsscsi +</I>><i> > [3:0:0:0] disk ATA ST3500418AS CC38 /dev/sdd +</I>><i> +</I>><i> I guess sdd translates to ata4... +</I>><i> +</I>><i> > ata4: SATA max UDMA/133 abar <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">m2048 at 0xf9ffe800</A> port 0xf9ffea80 irq 43 +</I>><i> +</I>><i> > ata4.00: ATA-8: ST3500418AS, CC38, max UDMA/133 +</I>><i> > ata4.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) +</I>><i> > ata4.00: configured for UDMA/133 +</I>><i> +</I>><i> +</I>><i> Hmm. +</I>><i> +</I>><i> Well, systemd uses the information in udev to determin when the disks +</I>><i> are ready/available, so it seems that some kind of metadata goes missing +</I>><i> somewhere. +</I>><i> +</I> +Well, as I said above, the disk was still there, but I was looking for it +under sda, that now pointed to my usb flash card reader :(. + +><i> +</I>><i> Can you try and boot with the dracut again, verify you can ultimately +</I>><i> make it to a regular boot via the commands I listed above from the +</I>><i> emergency shell. +</I>><i> +</I>><i> You can pass splash=verbose to disable any graphical stuff and and you +</I>><i> can also pass rd.debug=1 to get extra info. +</I>><i> +</I>><i> If you boot like that and them post the dmesg, that might offer some clues. +</I>><i> +</I>><i> There is also some udevadm stuff to run too after booting. +</I>><i> +</I>><i> udevadm info --query env --name=/dev/sdd1 +</I>><i> +</I>><i> It's this info systemd uses to work out if the disk is ready or not, so +</I>><i> this is probably quite important. +</I>><i> +</I>><i> All the best +</I>><i> +</I>><i> Col +</I>><i> +</I>><i> +</I> +</PRE> + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010617.html">[Mageia-dev] Issues with dracut +</A></li> + <LI>Next message: <A HREF="010542.html">[Mageia-dev] Issues with dracut +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10540">[ date ]</a> + <a href="thread.html#10540">[ thread ]</a> + <a href="subject.html#10540">[ subject ]</a> + <a href="author.html#10540">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |