/srv/irclogs.ubuntu.com/2009/10/14/#ubuntu-installer.txt

CIA-33ubiquity: cjwatson * r3514 ubiquity/ (debian/changelog scripts/check-kernels): Install kernel headers to match the kernel (#413135).00:11
CIA-33ubiquity: cjwatson * r3515 ubiquity/debian/changelog: bump to 2.0.0 for Ubuntu 9.1000:57
=== NCommander is now known as NC|G1
=== NC|G1 is now known as NCommander
CIA-33debian-installer: cjwatson * r1192 ubuntu/ (10 files in 3 dirs): Move to 2.6.31-14 kernels.03:05
mdkeevand: any chance of adding a help button to usb-creator?08:32
mdkeevand: or rather, usb-creator-gtk08:33
CIA-33wubi: Agostino Russo * r157 trunk/ (debian/changelog src/wubi/backends/common/backend.py): Use ext4 by default (lp: #444214)08:38
evandmdke: sure09:12
davmor2evand: Morning, do you know if any changes have gone in to stabilise wubi at all, is it worth testing today?09:15
evanddavmor2: none that I've made.  Remind me what the exact problem you're having is?10:30
CIA-33usb-creator: evand * r234 trunk/ (4 files in 3 dirs): Add a help button for the GTK+ frontend.10:34
evand^ rgreening_ I'm not making that change for the kde frontend as kubuntu-docs does not have the relevant usb-creator pages.10:37
davmor2evand: it will randomly work and randomly not.  It leaves no errors in the logs,  everytime seeming to say it successfully installed.10:37
evanddefine randomly not10:37
davmor21 in 9 install correctly10:37
davmor2but you get no idea if it will or not until it does or doesn't10:38
evandright, but in terms of it failing10:38
evandwhat happens10:38
evandwhere does it fail10:38
evandwhat do you see10:38
evandetc10:38
davmor2multiple issues mostly with grub.  you can drop into grub sh:_  or  No wubildr on a partition error or occasionally it sails through10:40
=== dpm_ is now known as dpm
evandwoo 4.27MB/s to cdimage.11:50
CIA-33debian-installer: cjwatson * r1193 ubuntu/ (3 files in 2 dirs): Move Dove images to 2.6.31-208 kernels.12:26
CIA-33debian-installer: cjwatson * r1194 ubuntu/ (build/config/armel/imx51.cfg debian/changelog): Move iMX51 images to 2.6.31-105 kernels.12:27
wektwhere do bug reports on the 'alternative' debian install program go?  package debian-installer seems to be something different according to the description.12:28
cjwatsondebian-installer is correct.12:30
cjwatsonwhich documentation12:30
cjwatson?12:30
CIA-33debian-installer: cjwatson * r1195 ubuntu/debian/changelog: releasing version 20081029ubuntu6812:32
wektyou want the description i mentioned?  I've lost it.  i don't find it again.  "You are in a maze of twisty passages, all alike."12:33
=== TheMuso` is now known as TheMus
=== TheMus is now known as TheMuso
cjwatsonwekt: do you mean 'apt-cache show debian-installer'? that's about the binary package, which is a bit different. /ubuntu/+source/debian-installer is the right place to file d-i bugs in Launchpad, anyway.12:50
sdhhello all - would this be the right place to enquire about live cd customisations? i've spent three days getting increasingly frustrated :)12:51
cjwatsonsdh: in some cases yes, we may have to redirect you depending on the details12:52
sdhcjwatson: great thanks. i'm basically trying to make a few adjustments to the stock jaunty desktop i386 cd (as per instructions at https://help.ubuntu.com/community/LiveCDCustomization). specifically i am apt-get dist-upgrading the chroot and then installing lvm2 so i can use the resulting cd to rescue some of my servers (that run lvm). the trouble i'm having is - i think - that the initrd is getting confused. boot fails. i have tried mkinitramfs -o /initrd12:54
sdhcomparing the original initrd with mine i notice teh original has a conf/uuid.conf - but it all seems a bit mysterious12:55
sdh:)12:55
sdhif you know enough to help, or can point me in the right direction, i'll basically love you forever :)12:56
cjwatsonhmm, sounds as though maybe you've removed the casper package?12:58
cjwatsonoh, no12:58
sdhnope, heh :)12:58
cjwatsontry, in the chroot:  sudo CASPER_GENERATE_UUID=1 update-initramfs -u12:58
sdhooh :)12:58
cjwatsonthat might help, or it might simply get you onto the next problem along12:59
sdhthanks - humour me, this takes a while to rebuild everything12:59
cjwatsonalso https://wiki.ubuntu.com/DebuggingCasper12:59
sdhooh useful, thanks12:59
sdhback in a few mins then13:00
CIA-33base-installer: cjwatson * r385 ubuntu/debian/changelog: releasing version 1.102ubuntu213:00
sdhcjwatson: that command generated /boot/initrd.img-blahblah in the chroot, as opposed to /initrd.gz - do i need to fix that? i am a bit confused about how the squashfs, iso and casper all sit together to be honest13:01
cjwatsonyou'll need to take that /boot/initrd.img-* and put it wherever the initrd actually gets booted from13:02
sdhor will it be ok so long as i copy it from inside the chroot (squashfs) into casper/initrd.gz13:02
cjwatsonstrictly speaking I think we move it to save space13:02
sdhok i think that's casper/initrd.gz13:02
cjwatsonbut copying would be fine too13:02
cjwatsonyes13:02
sdhthanks..13:02
TheMusocjwatson: If you have a minute? Would you mind having a skim over bug 450214? Its to do with the alternate installer hanging when attempting to format a swap partition on powerpc. If you can possibly give me a pointer to where I might start looking, I am happy to find the bug and try to fix it.13:03
ubottuLaunchpad bug 450214 in partman-base "Parted server appears to hang when attempting to format a swap partition on powerpc." [Undecided,New] https://launchpad.net/bugs/45021413:03
cjwatsonTheMuso: ok, just trying to deal with bug 434173 at the moment but I'll queue that up for afterwards13:03
ubottuLaunchpad bug 434173 in language-selector "[karmic] Regression from 9.04 in getting fully translated Ubuntu installation" [Undecided,Fix committed] https://launchpad.net/bugs/43417313:03
TheMusocjwatson: As I said, only if you have a minute.13:04
TheMusoI completely udnerstand that there are more important things to address.13:04
sdhcjwatson: for info the uuid comes out differently in the chroot-generated version vs the original - that ok?13:04
sdhcjwatson: i'm not actually sure what that uuid is for13:05
sdhsquashfs rebuilding...13:06
sdhcjwatson: i'm guessing the uuid.conf should contain the same as .disk/casper-uuid-generic13:10
sdhthis is far more complex than i had given it credit for13:10
cjwatsonsdh: the reason for the UUID is so that we can reliably match up the initrd with the squashfs on disk13:11
sdhcjwatson: sorry, can you elaborate?13:12
cjwatsonsdh: we can't just look on the CD drive, since there are live USB sticks etc., and there are special cases like people copying live CDs to partitions on the hard disk to act as recovery images13:12
sdhi think this is precisely the problem i am having13:12
cjwatsonso we need to make sure that we've actually found the right image13:12
sdhroger that13:12
sdhi think that's why it broke when i added lvm support perhaps13:12
sdhbecause it saw the lvm disks and tried to mount the wrong one13:12
sdhnot sure.13:13
cjwatsonconf/uuid.conf in the initramfs needs to match /.disk/casper-uuid-generic on the CD13:13
sdhcool ok thanks, i'll set that up now13:13
sdhcjwatson: very much appreciate your help13:13
sdhthis is a rather dark art13:13
cjwatsonthe casper-new-uuid program may help13:13
cjwatsonTheMuso: wasn't implying anything about importance, just an indication of what I was already doing :)13:14
TheMusorighto13:15
sdhcjwatson: ok this version works, but doesn't have lvm support - i'll try adding that now and let you know how it goes13:27
sdhgod, mksquashfs is painfully slow13:37
sdhok cjwatson it fails... :(13:41
sdhcjwatson: first error on the boot screen is "cp: cannot create '/root/var/log': no such file or directory13:42
sdhetc13:42
sdhno init found ... you get the idea13:42
sdhthat's on the box which has an install of ubuntu already (on lvm)13:43
sdhbooting on a blank box (no install) it works just fine13:43
sdhthis is essentially the problem i've been grappling with for 3 days now13:43
sdhfrom casper.log: running /scripts/casper-premount (done, done).. then13:44
sdh/init: line 1: cannot open /dev/sr0: no such file~13:45
TheMusosdh: Is it a custom kernel?13:46
TheMusosdh: i.e are you using a custom compiled kernel?13:47
sdhTheMuso: no, it's from apt-get dist-upgrade inside the squashfs13:48
TheMusohrm ok13:48
TheMusobecause no /dev/sr0 means either no rom drive found, or no sr_mod module loaded, although the ubuntu kernels have that built in.13:48
sdhwhat is /dev/sr0, sorry13:48
sdhoh, should it be the initrd?13:49
TheMusoIts the device node used to access CD/DVD drives via the SCSI subsystem in the kernel13:49
sdhah hm13:49
TheMusosdh: Have a look in /proc/scsi/scsi to see if anything relating to your CD drive is there.13:49
sdhTheMuso: i'm booting off usb13:49
sdhwell actually tell a lie13:50
TheMusoNote that most IDE and all SATA chipsets use tehe SCSI subsystem in the kernel these days13:50
sdhi'm booting off an iso in vmware13:50
TheMusoOh and USB13:50
sdhso "cd"13:50
TheMusoRight13:50
sdhTheMuso: i've got it down to this:13:50
TheMusoUSB, SATA, and most IDE drivers now use the SCSI subsystem in the kernel13:50
sdhTheMuso: if i create a blank machine with no install, the "cd" boots just fine on that13:50
sdhTheMuso: if i boot it on a box (same hardware) with an existing ubuntu install, it doesn't boot13:50
TheMusosdh: Have you run through the initramfs with debugging enabled?13:51
sdhTheMuso: no, how do i do that?13:51
TheMusoThere is a command-line variable that can be given on the kernel command-line.13:51
TheMusoCan't remember what it is off hand however.,13:52
sdhi'll try debug13:52
TheMusoI think "debug" will log to a file, "debug=anything" will log to the tty13:52
sdhok it dropped me to (initramfs) without seeming to do anything before hand13:53
sdhcan i single step from here?13:53
TheMusodon't think so13:53
sdhthis is a real nightmare i must say :)13:54
sdhi thought this would be easy, ha!13:54
TheMusoMake sure that you pass everything else to the kernel as you would normally but add debug at the end13:54
sdhTheMuso: that's what i just did - i'm at (initramfs) minus the errors (because presumably it's dropped me to the shell before doing its stuff)13:54
TheMusoOk, try debug=vc, vc can actually be anything, but =something means log to the tty13:55
TheMusooh and use nosplash so you don't get a splash, and get the terminal13:55
sdhi have taken off splash and quiet, always do13:55
sdhok that did what i expected13:56
sdhi.e. gave me lots of debug13:56
TheMusoright13:57
sdhbasically the first error is a failure to mount /dev on /root/dev and it all goes wrong from there13:57
sdhbut im sure that's because something to do with /root is wrong13:57
TheMusoyou probably need to log the debugging to a file and get the file somewhere else to look at it13:57
sdhyeah im scrolling through on the terminal13:58
=== robbiew-afk is now known as robbiew
sdhbasically i know the problem is to do with the box having lvm partitions14:01
sdhbut i can't get past that14:01
TheMusosdh: No idea at this point sorry.14:03
sdhthat's ok thanks for the help14:04
sdhmaybe cjwatson can shine some light on it when he gets back14:04
cjwatsonit's on the DebuggingCasper page I linked to earlier14:07
cjwatsondebug)14:07
cjwatsonoh, sorry, my scrollback was lagged ...14:07
cjwatsonmy next recommendation would be to boot with debug (not debug=vc), and when it eventually crashes out to a shell, mount a real filesystem somewhere and copy /dev/.initramfs/initramfs.debug to it - then reboot so you have networking, and put that file somewhere we can see it14:09
cjwatsonTheMuso: I can't figure out from the logs why it would be failing at just that point; it's obviously right after a ped_timer_reset but I can't see where that could happen. I think the next step is to run the install afresh, but capture what parted_server is doing across that time interval using strace14:10
TheMusocjwatson: Ok.14:10
TheMusocjwatson: So should I intercept the call to run parted_server and run it through stracem, logging to a file?14:16
TheMusos/stracem/strace/14:16
cjwatsonTheMuso: no need for that, just let it start normally and then, just before you tell partman to commit, get the pid of parted_server and run 'strace -o /tmp/parted_server.trace -s 1024 -p whatever-the-pid-was' on tty214:19
TheMusocjwatson: ok great.14:20
TheMusoOk no change, retrieving the trace file for further examination.14:26
TheMusocjwatson: I'll see if I can find anything, but I've attached the strace log to the bug in case you're interested.14:35
TheMusohrm can't see anything that stands out, but my strace experience is limited.14:48
TheMusoAnyway, gotta sleep, back in 7 hours or so.14:49
cjwatsondavmor2: next time you test wubi, could you please try adding this boot parameter to wubi's second stage (i.e. after the initial Windows bit and the reboot):16:26
cjwatsonpartman/default_filesystem=ext316:26
davmor2cjwatson: sure16:26
davmor2I'll fire up a run now16:26
cjwatsonbased on a hunch that maybe it's not NTFS that's the problem at all16:29
evandcjwatson: didn't wubi already create ext3 partitions up until today?16:47
sdhcjwatson: https://steve.st/tmp/initramfs.debug16:52
sdhi welcome your thoughts ;)16:52
cjwatsonevand: I don't think so17:06
cjwatsonevand: it just uses partman-auto's defaults, as far as I can tell, which were ext3 in jaunty but (as you know :-) ) ext4 now17:07
davmor2cjwatson: Am I planting your line after the rootflags=syncio or after the initrd line?17:07
cjwatsonso I'm thinking that might account for a change in reliability from jaunty17:07
cjwatsondavmor2: the former17:07
cjwatsondavmor2: but not on a line by itself17:08
cjwatsondavmor2: put it on the same line as rootflags=syncio, at the end, with a space before it17:08
davmor2yeah I got that bit figure thanks :)17:08
cjwatsonjust checking :)17:08
evandcjwatson: src/wubi/backends/common/backend.py looks like it wrote filesystem{ ext3 } up until today.17:09
evandbut perhaps I'm just misreading all of this17:09
cjwatsonsdh: hmm, whoops, I forgot about one bit - you'll need to extract /casper.log in the same way17:09
cjwatsonevand: oh, hmm17:09
sdhcjwatson: heh, ok.17:10
cjwatsonin that case maybe I am barking up the wrong tree17:10
davmor2cjwatson: running now17:10
cjwatsondavmor2: given what evand just pointed out, this is probably a waste of time :(17:10
sdhcjwatson: with debug?17:10
sdhcjwatson: https://steve.st/tmp/casper.log17:13
sdhcjwatson: im struggling to get past this tbh - i might have to resort to knoppix but not sure that would be any different and i am more familiar with ubuntu (or so i thought!)17:16
cjwatsonsdh: so you've run into a particularly broken piece of code, but the good news is that your problem has at least been worked around in karmic, and you can apply the fix to your customised image17:19
davmor2that seemed to work cjwatson but I'll try again and see if it was just a fluke17:19
cjwatsonsdh: I'm just digging out the patch for you17:20
cjwatsondavmor2: hmm, now that is doubly odd :-)17:20
sdhcjwatson: oh cool, thanks - i'm keen to see this :)17:20
davmor2cjwatson: could just be the kookiness of whether it installs or not that's why I'm retrying.  If it works a second time I'll try it on kubuntu17:21
cjwatsonif it works then the next stage is to figure out *why* :-)17:22
cjwatsonsdh: http://bazaar.launchpad.net/~ubuntu-core-dev/casper/trunk/revision/706 - the scripts/casper bit of that can be applied to /usr/share/initramfs-tools/scripts/casper, and then you do the initramfs rebuilding dance again17:25
sdhheheh.17:26
sdhcheers, let me see17:26
sdhthat's in... the initrd?17:27
sdhmy mind is about to explode ;>17:27
davmor2cjwatson: second run=fail :(17:43
davmor2cjwatson: this isn't going to be something daft like a flaw in the loop module is it?17:45
evandI've requested that all the "ubiquity explodes nearly instantly after pressing install" bugs that I'm aware of try libwebkit from my ppa.  Fingers crossed.17:48
sdhcjwatson: ha, good one - that seems to have done it17:49
sdhhmm thanks17:52
sdhis that fixed to the same extend in the karmic beta?17:52
cjwatsonsdh: no, it was fixed after the beta release; it's fixed in current daily builds18:04
cjwatsondavmor2: no dea18:04
cjwatsonidea18:04
cjwatsonseems a bit of a stretch18:04
=== djsiegel2 is now known as djsiegel
davmor2cjwatson: that's why I said daft :)18:22
sdhcjwatson: thanks for your help18:33
=== rbelem_ is now known as rbelem
joshkhey, i'm having a problem using floppy preseed in karmic beta119:26
joshki saw that there's been a change in the file-preseed package regarding floppy support19:28
joshkah, it looksl ike mountmedia floppy isn't working because the only thing on the floppy is preseed.cfg19:35
cjwatsonsdh: no problem19:35
cjwatsonjoshk: must admit it's something I'm entirely familiar with; if you track it down I'd be happy to apply fixes ...19:36
cjwatsonentirely UNfamiliar19:36
joshkyeah, i'm getting there19:36
cjwatsonat least once I unbreak my laptop19:36
joshkoh man, this fix is totally broken19:38
joshkhttp://triplehelix.org/~joshk/mountmedia_0.19_0.19ubuntu1.diff19:38
joshk"WANTDRIVERINJECTIONDISK" should have a $ in front of it19:39
joshklet me see if that does the trick... i'm live in a VM and i should be able to make the change and rerun it19:39
joshkthat did it.19:39
joshkshould I file a LP bug?19:40
joshkit's really a 1 character change.. the preseeded install is going fine now19:40
tormodare all disks/partitions supposed to be automounted on the live CD?19:42
cjwatsonjoshk: please file a bug if you could so that I have an audit trail, but I can apply that as soon as I resurrect my laptop19:43
cjwatsontormod: IIRC we ended up with a general consensus of "no"19:43
joshkcjwatson: okey doke19:43
joshkassign to you?19:43
cjwatsonplease19:44
tormodcjwatson, sounds smart, but today's daily does19:44
cjwatsontormod: likely to be a desktop bug, though?19:45
tormodcjwatson, it does not on my up-to-date install for some reason19:45
cjwatson(a) I don't think casper's responsible for any of that, except maybe turning things off, and (b) desktop components should really not be doing that by default19:45
cjwatsonunless there's some crackful bug I've forgotten19:46
tormodlooks like c) then :)19:46
tormodany hints to what I can check?19:47
joshkcjwatson: LP 45153619:47
ubottuLaunchpad bug 451536 in mountmedia ""mountmedia floppy" minor typo in driver injection floppy support" [Undecided,New] https://launchpad.net/bugs/45153619:47
joshkhaha, just beat the bot19:47
cjwatsonjoshk: fixed, thanks19:48
cjwatsonthe bot responded to you19:48
joshkoh19:48
joshkneato19:48
NCommandercjwatson, thanks for changing the seeds yesterday for partman-uboot. I take it now I need to extend ubiquity to use partman-uboot, right?19:49
NCommander(or do you want to handle that?)19:49
cjwatsonNCommander: I don't have cycles, please go ahead if you want it to happen19:50
NCommandercjwatson, sure, I'll take it point on it, and hopefully finish it before Firday19:50
tormodcjwatson, about dmraid support in Ubiquity: now that dmraid is pretty well integrated on the Desktop CD, the biggest issue is that I have to create /var/lib/disk-detect/activate_dmraid otherwise the partitioner will search for and display everything on the hidden raw devices19:52
joshkcjwatson: awesome.. will there be a beta2 of karmic?19:52
tormodjoshk, there's soon RC...19:53
joshkah, RC? cool.19:53
cjwatsonwhat the man said19:53
cjwatsontormod: the fugly quick solution would be to copy that chunk of hw-detect to a script that ubiquity runs just as the partitioner starts, so that it can actually ask the question (which IIRC is important in some corner cases)19:55
cjwatsontormod: though interestingly when I tried this quickly in kvm it all seemed to work for me out of the box ...19:55
tormodcjwatson, what corner cases? if somebody has fakeraids they do not want to use the raw devices19:56
cjwatsontormod: tell that to the people who've complained about this assumption ;)19:56
tormodotherwise they can boot with "nodmraid" and be wonderfully on their own19:56
cjwatsontormod: usually the corner case is that somebody has some dmraid metadata lying around but they aren't actually intentionally using dmraid19:56
cjwatsoni.e. the dmraid tools get it wrong19:56
cjwatsonand I think a kernel parameter is too undiscoverable here19:57
tormoddmraid tools get it wrong usually means the user has done something bad19:57
cjwatsonthat's as may be but I don't want that to become the installer's problem19:57
tormodthe current situation is that "good" users might get into trouble19:58
cjwatsonI want to handle both19:58
tormodwhat chunk of hw-detect are you referring to?19:59
cjwatsonthe bit in disk-detect.sh that creates activate_dmraid19:59
cjwatsonI'm copying it over now19:59
tormodwell my clear opinion is that if dmraid has correctly hidden raw partitions away, the installer should not fish them out again. I think a kernel parameter is a light punishment to the people setting up invalid configurations20:02
cjwatsonand my clear opinion is that anything with a risk of regressions at this point isn't something I want to perpetrate; and I *know* this has been a thorny area in the past.20:02
cjwatsonbut I do want to get this fixed if possible, so I prefer a safe course20:02
cjwatsonfurthermore I insist that d-i and ubiquity have consistent behaviour where possible20:02
cjwatson(and reasonable)20:03
tormodI am not sure what d-i is doing nowadays20:03
cjwatsonit's acting as I described20:03
cjwatsonit asks before activating dmraid20:03
tormodok, if you get that question into ubiquity I will be happy20:04
tormodbut at one point we have to stop encouraging people running broken setups20:04
cjwatsonmm, but I'm the sucker who has to field the problem reports when things go wrong20:05
tormodthey will fail in the future when the dmraid starts to autosync for instance20:05
cjwatsonbug 279288 describes data loss caused by not asking20:06
ubottuLaunchpad bug 279288 in partman-base "User interface exception request: Ask the user if they wish to activate dmraid arrays." [High,Fix released] https://launchpad.net/bugs/27928820:06
cjwatsonor potential data loss anyway20:07
cjwatsonand indicates that it's the fault of the BIOS, not of the user20:08
cjwatsonwhich makes me a lot more sympathetic to the user20:08
tormodthe thing is that turning off raid in the BIOS does not erase the dmraid metadata..20:08
cjwatsonhow's a user meant to know that?20:09
cjwatsonjust because the design of dmraid is faulty, doesn't mean I want us to conspire in that faultiness :)20:09
CIA-33ubiquity: cjwatson * r3516 ubiquity/debian/changelog: indicate bug closure properly20:10
tormodwell currently we do activate all fakeraids on the live CD, so if the user answers "no" to your new question, then you should maybe deactivate the raid so it does not show up in the partitioner20:12
tormodcurrenctly, raid and raw devices show up20:12
cjwatsonwhere do we do that?20:17
tormodudev20:18
cjwatsonthat's unfortunate and may be a serious regression20:18
tormodI don't think that's new?20:18
cjwatsonwe didn't have dmraid on the live CD until very recently20:18
cjwatsonthe live CD is not meant to affect disks; causing dmraid devices to autosync would be bad. Does it do that?20:19
tormodwell I would not call it regression that raw devices are correctly hidden20:19
cjwatsonregressions do not necessarily affect everyone20:19
tormodthey do no autosync yet20:19
tormodmany years from that I reckon20:20
cjwatsonthey must never autosync when merely running the live CD, without actively making use of those devices20:20
cjwatsonthat would be counter to the design of the live CD20:20
tormodwithout dmraid on the live cd, the live cd is extremely dangerous for us with fakeraids20:20
cjwatsonplease understand that I am trying to satisfy both you and other people20:21
cjwatsonI understand your point of view, but it is also my responsibility to take other points of view into account20:21
cjwatsonI am not saying that we need to remove dmraid from the live CD; I think it makes sense there20:21
tormodI understand, but I dataloss for "my" group is as serious as dataloss for the few others20:21
tormods/I/the20:21
cjwatsonI don't think we need to deactivate dmraid devices to cause them to not show up in the partitioner20:22
cjwatsonpartman-base already takes account of the activate_dmraid flag20:22
cjwatsonthat is sufficient20:22
tormodbut currently the raid shows up, without that flag, right?20:22
cjwatsonthat is the one and only thing that that flag file affects20:23
cjwatsonit does absolutely nothing else20:23
cjwatsonactually, no, that's not quite true, it affects grub-installer too20:23
tormodwhen I tried, flag on -> hides raw devices and shows raid, flag off -> shows raw devices AND raid20:24
cjwatsonaha, hang on, I'm misreading the partman-base code20:24
cjwatsonright20:24
cjwatsonso I think that will look a bit odd, but people who aren't using the RAID device will probably be OK to go "hang on, that's weird, what the hell is that disk" and they may be confused but as long as they don't use it it won't hurt20:25
CIA-33ubiquity: cjwatson * r3517 ubiquity/ (configure configure.ac po/Makefile.in.in): bump to 2.020:26
tormodwhat happens later in the installation? the raw device partition are hidden by udev, so where does the installation go if someone sets up root on /dev/sda3 for instance20:26
cjwatsonif they were hidden altogether, then partman wouldn't see them20:27
cjwatsonso I don't think that can be the case20:27
tormodthey are gone from /dev. does partman go through /sys ?20:27
tormodI thought that was was taking so utterly long in ubiquity: for partman to sniff through /dev/sda on its own. it does not?20:28
tormodI mean, it does not do its own partition discovery?20:29
cjwatsonin my tests here, udev does not hide the raw devices20:30
cjwatsonoh, though it does hide the partitions20:32
tormodyes right20:32
cjwatsonhmm, and 'dmraid -an' doesn't bring them back20:37
cjwatsonI think the only viable option here is to add nodmraid as an option accessible from the F6 menu on the CD, then20:38
cjwatsonI'm not happy about this, but I don't see any other way to make it work :(20:39
tormodthe F6 option would be nice, and a note in the release notes20:39
cjwatsonso indeed that means there's no point asking the question. drat.20:40
tormodbut again: does partman discover e.g. /dev/sda3 and propose it for installation, which fails if /dev/sda3 does not exist?20:40
tormodwell the question could be more of a warning, "dmraid is detected, please reboot with "nodmraid" if this is not intended"20:42
cjwatsoncan't add new translatable text at this point ...20:42
cjwatsonparted does device scanning20:42
cjwatsonit does have special dmraid handling; I forget the specifics20:42
tormodI just noted partman took so long, I have logs if you want20:43
cjwatsonubiquity's driving of partman has always been slow20:44
cjwatsonthere's an ancient bug about it20:44
cjwatsonit's actually intrinsically no slower than the underlying partman code you see in d-i, but it appears longer since ubiquity is basically navigating around partman screens under the hood to construct a unified display20:45
cjwatsonthere's definitely room for optimisation; the trick is to do that without ending up effectively maintaining two partitioners20:45
cjwatsonI think that parted is observing the existence of /dev/sda and then analysing its partition table (which after all is kind of part of its job)20:45
cjwatsonbut that should vanish if activate_dmraid is set20:46
cjwatsonthat part itself is not actually particularly slow20:46
NivexLP#441690: Should I try a newer daily and see if this is still happening?20:47
cjwatsonbug 44169020:47
ubottuLaunchpad bug 441690 in debian-installer "Karmic Server Beta: manual partitioner can't connect to iSCSI targets with HD present" [Undecided,New] https://launchpad.net/bugs/44169020:47
cjwatsonyes please20:47
tormodcjwatson, yes partman is many times faster once activate_dmraid is created20:48
cjwatsonNivex: I'm still not sure what's going on with your iSCSI daemon, though, that's weird20:50
cjwatsonI didn't see that kind of problem20:50
cjwatsontormod: precisely N+M times faster where N is the number of raw devices in your dmraid sets and M is the number of dmraid sets, I imagine :)20:51
NivexI'm zsync'ing the current daily.  Hopefully it's gone.  It seemed like whatever script wasn't starting the initiator properly.20:51
cjwatsonoh20:52
cjwatsonin that case I bet I know20:52
Nivexit works if there is no local hard disk.  only breaks when you try to start it from the manual partitioner20:52
tormodcjwatson, felt like even more :) would be nice to have timestamps in the log...20:52
CIA-33hw-detect: cjwatson * r135 ubuntu/debian/changelog: releasing version 1.72ubuntu520:52
cjwatson^- helps to upload my fixes20:52
cjwatsonhw-detect takes a while to get into images, because it needs a reupload of debian-installer20:53
cjwatsonNivex: do you think you could try an experiment by hand for me?20:54
cjwatsonNivex: boot the installer, and run through it until the hostname prompt; stop there, and switch to tty220:54
cjwatsonNivex: run 'nano /bin/disk-detect', search for the line that begins 'if db_fget partman-iscsi/login/address', and change that to 'if db_fget partman-iscsi/login/address seen'20:55
cjwatson... actually pretend I didn't say any of that, it's too late and I appear to be having reading comprehension difficulties20:56
CIA-33partman-iscsi: cjwatson * r30 ubuntu/ (choose_partition/iscsi/do_option debian/changelog):20:59
CIA-33partman-iscsi: Make sure iscsid is running when selecting "Configure iSCSI volumes"20:59
CIA-33partman-iscsi: (LP: #441690).20:59
cjwatsonNivex: ok, should be fixed by tomorrow's daily build, thanks for the nudge21:00
CIA-33partman-iscsi: cjwatson * r31 ubuntu/debian/changelog: releasing version 521:00
Nivexok, I'll try tomorrow's daily and see how it goes21:05
* Nivex says just as the zsync of today's finishes :)21:05
dwolfmanhello, am installing Mustajuuri, having problems getting it built with Ubuntu21:14
dwolfmanwas looking for some support especially if anyone has successfully installed the Mustajuuri app before21:15
dwolfmanhttp://www.tml.tkk.fi/~tilmonen/mustajuuri/index.html21:15
tormoddwolfman, this channel is for the development of the Ubuntu installer itself21:16
dwolfmanoh, so sorry21:16
dwolfmanwhat is the user support channel on this server?21:16
dwolfmanso I don't burst in on anyone else, lol21:17
CIA-33ubiquity: cjwatson * r3518 ubiquity/debian/ (changelog control):21:17
CIA-33ubiquity: Recommend dmraid to ensure consistent behaviour across Ubuntu flavours21:17
CIA-33ubiquity: (it was already present on the Ubuntu desktop CD, but e.g. not on21:17
CIA-33ubiquity: Kubuntu).21:17
dwolfmannm, will not interrupt, sorry21:17
CIA-33ubiquity: cjwatson * r3519 ubiquity/ (3 files in 3 dirs):21:18
CIA-33ubiquity: If dmraid devices are active, then create21:18
CIA-33ubiquity: /var/lib/disk-detect/activate_dmraid so that partman will exclude slave21:18
CIA-33ubiquity: devices, and ensure that dmraid is installed in the target (LP: #90235).21:18
cjwatsontormod: hopefully that should take care of it ...21:19
tormodcjwatson, great! I will test it for real on real devices tomorrow21:19
cjwatsonI tested it but only in kvm, so yeah, please do21:19
tormodbtw, is grub-installer supposed to work with dmraid as well?21:19
cjwatsonshould do now21:19
cjwatsonit was busted until relatively recently21:20
tormodok, I will test in all tomorrow, clean install, and report back21:20
tormods/in/it21:20
cjwatsonit ought to fall back to grub legacy, since grub2 and dmraid aren't really friends yet21:20
tormodaha good to know21:20
cjwatsonI haven't really tested it much though :/21:21
tormodits funny how grub1 is legacy since ten years and grub2 still is only beta :)21:21
tormodcjwatson, back to the automount of all partitions on live CD issue, anything I should check while I am on the live CD?21:25
cjwatsonto be honest I simply don't know21:28
cjwatsonI've lost track of the shifting sands of this kind of area of the desktop21:28
cjwatsonpitti would know a lot better than I, if he's around21:28
tormodthanks, I'll try pitti21:29
CIA-33pkgsel: cjwatson * r150 ubuntu/debian/ (changelog postinst):22:38
CIA-33pkgsel: Use check-language-support if available to select language support22:38
CIA-33pkgsel: packages (LP: #434173).22:38
CIA-33pkgsel: cjwatson * r151 ubuntu/debian/changelog: releasing version 0.25ubuntu322:39
CIA-33ubiquity: cjwatson * r3520 ubiquity/ (debian/changelog debian/control scripts/install.py):22:40
CIA-33ubiquity: Use check-language-support if available to select language support22:40
CIA-33ubiquity: packages (LP: #434173).22:40
CIA-33ubiquity: cjwatson * r3521 ubiquity/ (155 files in 3 dirs): Update translations from Launchpad.23:12
CIA-33ubiquity: cjwatson * r3522 ubiquity/ (d-i/manifest debian/changelog):23:19
CIA-33ubiquity: Automatic update of included source packages: base-installer23:19
CIA-33ubiquity: 1.102ubuntu2, hw-detect 1.72ubuntu5.23:19
CIA-33ubiquity: cjwatson * r3523 ubiquity/debian/changelog: let's have a bit of nostalgia23:55
CIA-33ubiquity: cjwatson * r3524 ubiquity/debian/changelog: 1.99.32 was never uploaded; fold in changelog entry23:58

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