/srv/irclogs.ubuntu.com/2011/06/29/#ubuntu-installer.txt

CIA-37debian-installer: cjwatson * r1479 ubuntu/debian/changelog: releasing version 20101020ubuntu4009:33
maxbHrm. It looks like grub-probe assumes the incorrect path for any md devices created during the natty installer, causing the grub-install call to fail19:50
CarlFKif my netboot installer append has BOOTIF=01-00-14-22-94-06-6a  should I also need netcfg/choose_inter20:32
CarlFKface=eth0 ?20:32
v12hi, i'm having trouble using the alternate installer from USB.  i have grub installed and launch the installer from USB via loopback.  it fails with "searching for Ubuntu installation", and more specifically "cdrom mount failed".  i do not have a boot=... parameter in the kernel line.  how do i tell the installer where its root is?22:35
v12or, put another way, what is the appropriate boot=... directory for the alternate installer?22:36
v12topic points to 404 webpage (~scott).  bad sign...22:39
cjwatsonCarlFK: nope, the default (=auto) should do22:55
cjwatsonhm, that link is definitely stale - it was for performance measurements22:55
CarlFKcjwatson: on a dell laptop whos wifi shows up as eth0, the default gave me "pick an interface"22:56
cjwatsonCarlFK: oh, right, it won't be marked as seen.  use netcfg/choose_interface=auto then22:56
=== cjwatson changed the topic of #ubuntu-installer to: Don't ask to ask, just ask (and stick around, we aren't all here 24/7) | Please include installer syslog with problem reports | http://wiki.ubuntu.com/Installer/FAQ | Development of d-i and ubiquity in Ubuntu | http://wiki.ubuntu.com/Installer/Development | If nobody answers, try ubuntu-installer@lists.ubuntu.com
cjwatsonv12: you should definitely never need to tell the installer where its root is by hand22:57
CarlFKcjwatson: ah, got it.  thanks.  was thinking there was a bug.  will try auto, that sounds sane.22:57
cjwatsonv12: that's sufficiently so that I'm not even sure how one might tell it ...22:57
cjwatsonI don't believe we pass root= normally22:58
cjwatsonboot= is nonexistent AFAI22:58
cjwatsonK22:58
CarlFKcjwatson: you mind looking at bug 728710 - this has been annoying me for a few releases.  just now got to reporting it but it seems to be slipping into a crack.22:58
ubot2Launchpad bug 728710 in debian-installer "d-i apt-setup/local0/repository not working" [Undecided,New] https://launchpad.net/bugs/72871022:58
cjwatsonCarlFK: ask me when I haven't just got back from the pub :)22:59
cjwatsonv12: what version of Ubuntu is this?22:59
CarlFKroger that :)22:59
cjwatsonv12: if it's earlier than natty, cdrom-detect/try-usb=true might help23:00
v12cjwatson: it's Natty.  i omitted "auto"  i'll try that23:00
v12is there somewhere i can check for the "auto" logic?  i'm not sure where to browse the source23:01
cjwatsonv12: the auto bit wasn't directed at you23:01
cjwatsonand won't help you23:01
v12ahh23:01
cjwatsonCarlFK: the snippets of syslog you've posted there aren't very useful - they just describe the bit where d-i is processing the preseed file into the debconf database, not the bit much later on when it actually tries to use them.  could you attach a full DEBCONF_DEBUG=developer syslog?23:02
v12does the iso need to be in a root directory?  mine is in /boot/isos/natty.iso23:02
CarlFKcjwatson: will do23:02
cjwatsonv12: let me check23:03
cjwatsonv12: oh, you're doing it that way?  you actually need something a bit different23:03
* cjwatson hunts down the doc link23:03
cjwatsonhttps://help.ubuntu.com/11.04/installation-guide/i386/boot-usb-files.html23:05
lifelesscjwatson: oh hai23:06
cjwatsonyou can set up a similar boot entry with grub of course, although that describes syslinux23:06
lifelesscjwatson: could I grab a couple of tips about grub2 & dmraid ?23:06
cjwatsonI suspect the standard loopback.cfg bits may only work properly with the desktop cd23:06
cjwatsonlifeless: maybe, see above comment about just being back from pub23:06
lifelesscjwatson: heh; I am doing nose following, I hopefully just need broad advice23:07
lifelesscjwatson: I've filed a bug 803658 about this. the tl;dr version is:23:07
ubot2Launchpad bug 803658 in grub2 "grub-install /dev/mapper/isw_$UUID_$NAME0 failing with ICH10R raid 1+0" [Undecided,New] https://launchpad.net/bugs/80365823:07
lifelessdmraid 1+0  (striped layered on mirrored)23:07
lifelessgrub-probe errors out 'cannot find a grub drive for ...'23:08
cjwatsonwhat's the device.map look like?23:08
cjwatsonif you have one23:08
lifelessinside the target?23:08
cjwatson/boot/grub/device.map in whatever filesystem namespace grub-install is running in, yes23:08
lifelessno such file23:09
cjwatsonok, failure to autodetect is a bad sign, but two things23:09
lifelesscjwatson: I wanted to check my understanding, which is that grub will happily read the bios provided mapped array at boot, and that its just a logic failure figuring this out in the prober23:10
cjwatson(a) figure out what grub-probe command is being run (sh -x /usr/sbin/grub-install <args>, check somewhere near the end), run it with -vv and attach output to bug23:10
v12cjwatson: says nothing about how to tell the iso not to worry about the CD. i am already booting the kernel in /install.amd/vmlinuz23:10
v12whoops i mean /install/23:11
cjwatson(b) you may be able to work around this by creating /boot/grub/device.map (grub-mkdevicemap can create a skeleton); an entry in device.map constitutes a promise that the BIOS can read from that drive23:11
cjwatsonv12: those directions instruct you to use a different build of the installer which has different logic in this area23:11
v12unfortunately i am trying to use efi23:11
cjwatsonthat shouldn't particularly matter23:12
cjwatsonyou'll have to translate the boot instructions into grub-speak, certainly, since syslinux won't work23:12
cjwatsonlifeless: yes, at boot time grub should be able to read from anything that the BIOS INT 13h facilities provide23:13
lifelesscjwatson: attached23:13
lifelesscjwatson: perhaps grub2 has the same broken filtering that parted does for raid 1+023:14
cjwatsonit won't be the same as such, but may produce similar results; I agree it's a logic failure in grub-probe23:14
cjwatsonin general we need to probe the root device in order to figure out which modules to build into the core image23:15
lifelessthe probe seems to entirely ignore the array0 device (dm-2)23:16
cjwatsonI *think* an explicit device.map entry should work around this; it doesn't particularly matter what you call it, I'd just use (hdN) where N is one greater than the last entry in what grub-mkdevicemap produces23:17
v12cjwatson: how does the alternate installer get used for USB?  has anyone done it before?23:18
cjwatsonv12: follow the directions I provided, using the hd-media image23:19
cjwatsonor else, it should be possible to boot the alternate installer by running isohybrid on the ISO and then writing it directly to the entire USB disk23:19
cjwatson(whether that will work on EFI I don't recall)23:19
lifelesscjwatson: it still errors on probe23:19
lifelesssame error23:20
v12aha i'll look for the hd-media image...23:20
cjwatsonlifeless: exactly what line did you put in device.map?23:20
lifelessI'll paste to the bug (not ircing from that machine)23:21
lifelesscjwatson: is there now23:22
cjwatsonwe certainly seem to need logic in find_partition_start for striped devices23:22
cjwatsonlifeless: if you could attach the output of 'dmsetup table' as well, I can probably attack this tomorrow; I'm afraid it requires a greater level of alertness than I possess right now23:24
lifelessattached.23:24
lifelessI'll poke around a bit23:25
lifelessthanks!23:25
cjwatsonthis is partly arising from the need to map partitions onto their offsets from the start of the disk23:25
lifelessthe partition table isn't accurate?23:26
cjwatsonit is, but we do this in order to be able to map partition devices onto their containing disk devices23:26
cjwatsonwhich is actually startlingly difficult to do in the general case23:26
lifelesscjwatson: I can imagine - in the striped case it seems impossible to me23:26
cjwatsonshouldn't be, we can get all the links from device-mapper's table23:26
lifelesscjwatson: doesn't htat imply grub having to reimplement the stripe logic?23:27
cjwatsonsince the "containing disk" that we care about is the striped device, not either mirrored device23:27
cjwatsonI don't think so, at least not much, but I'll have to look tomorrow23:27
lifelesscjwatson: I'm probably misunderstanding the direction of containing there ;)23:27
lifelessbut its late for you23:27
cjwatsonyeah, I don't think I'm being very clear23:28
cjwatsonanyway, bed :)23:28
lifelessI'll see if I can wipe my disk out at least twice before lunch23:28
cjwatsonsorry not to be able to solve immediately23:28
lifelessde nada23:28
lifelessnow if I can just remember how to get debian/patches applied23:28
cjwatsonI don't think I've seen the striped case before.  might need to set something up in a vm23:28
lifelessto build normally23:28
cjwatsondebian/rules patch23:28
cjwatsonin the case of grub223:28
lifelessthanks!23:28
cjwatson(which 'debian/rules build' does for you, but 'debian/rules build/grub-pc' doesn't - that's a bug)23:29
CarlFKcjwatson: thanks for =auto.  worked as advertised23:30
cjwatsonCarlFK: oh good23:37

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!