=== mgalvin [n=mgalvin@ubuntu/member/mgalvin]  has joined #ubuntu-boot
=== tgnx [n=tgnb@dsl-9-161.cofs.net]  has joined #ubuntu-boot
[03:07] <tgnx> hello
[03:07] <tgnx> i'm just installed ubuntu on a pc and after installation it won't boot
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin]  has joined #ubuntu-boot
=== Keybuk [n=scott@c51008D91.inet.catch.no]  has joined #ubuntu-boot
=== makx [n=max@baikonur.stro.at]  has joined #ubuntu-boot
=== allee [n=ach@allee.exgal.mpe.mpg.de]  has joined #ubuntu-boot
[11:26] <allee> Keybuk: Sun Galaxy X4100 sda1 versus sdi1 root dev mistery: After netbooting dapper with preseeding, reboot fails can't mount /dev/sdi1. In grub dialog s/sdi1/sda1/ and boots successful. df shows root it now mounted on /dev/sdi1
[11:27] <Keybuk> come again?
[11:28] <Keybuk> what is root= k
[11:29] <allee> in grub append?  root=/dev/sdi1.  I need to change it to /dev/sda1
[11:31] <Keybuk> ok, but then df says something different?
[11:32] <allee> yes, when I login df says /dev/sdi1 for /
[11:33] <allee> ah, and afair fdisk -l listed /dev/sda not sdi.  checking ...
[11:33] <Keybuk> that makes no sense
[11:33] <Keybuk> sorry, but if /dev/sda1 is mounted as the root device, that's what will show up in df
[11:33] <Keybuk> it doesn't suddenly jump to sdi1 half way through the boot sequence
[11:34] <Keybuk> what are sda-sdh ?
[11:34] <allee> Keybuk: no idea, sorry.  There only one harddisk.  lsmod lists usb-storage as first loaded.
[11:35] <Keybuk> I can't help you
[11:35] <Keybuk> what you're saying makes zero sense
[11:35] <Keybuk> you'll need to get your facts sorted out first
[11:35] <Keybuk> is your hard disk /dev/sda1 or /dev/sdi1, for example ... you're claiming it's both
[11:36] <allee> Keybuk: during install it says it always says sdi.  menu.lst contains sdi. fine so far
[11:37] <allee> Keybuk: boot fails with can mount sdi1 and I'm on 'sh#' prompt.  Reboot and in grub dialog set root=/dev/sda1 and it boots successfully
[11:38] <Keybuk> ok
[11:38] <Keybuk> and then after booting, what does "cat /proc/mounts" say?
[11:38] <crispinf> Keybuk: many thanks for that udev fix - it worked perfectly, so I marked the bug as "Fix released"
[11:39] <allee> Keybuk: one moment, I tried a reboot and now I'm on '#' prompt again.  I'll reboot and change to sda1 again ..
[11:45] <Keybuk> allee: either way, this sounds like an installer bug to me
[11:45] <Keybuk> if sda-sdh are being given to removable devices, that's a bug
[11:45] <Keybuk> file it on hw-detect
[11:47] <allee> proc mounts only shows /dev/sda1, df / lists sdi1
=== fabbione [i=fabbione@gordian.fabbione.net]  has joined #ubuntu-boot
[11:49] <Keybuk> ok
[11:49] <Keybuk> iz installer bug
[11:50] <allee> Keybuk: ok, I'll file bug against hw-detect
[12:51] <allee> done: https://launchpad.net/distros/ubuntu/+source/hw-detect/+bug/33249
[12:53] <Kamion> er, what? hw-detect doesn't assign device names
[12:53] <Kamion> Keybuk: what do you think should change in hw-detect?
[12:54] <Keybuk> it shouldn't load usb-storage before the scsi/raid/sata controller
[12:55] <Keybuk> otherwise the kernel will allocate sda-sdX to whatever USB keys and devices are plugged in
[12:55] <Keybuk> and then finally sdX+1 to the intended root filesystem
[12:55] <Keybuk> which means they better damned well leave everything connected next time they boot ;)
[12:58] <Keybuk> I assume that's what's grabbing sda-sdh anyway
[01:01] <Keybuk> either way, the installer is arranging matters so that the intended root filesystem is sdi, where udev/
[01:01] <Keybuk> initramfs are making it sda
[01:01] <Keybuk> and I think the installer is at fault, as sdi is a rather far-fetched name for it
[01:07] <allee> Should I but another X4100 with sda preseeded?  Then it stop in partition menu, and I can send you more infos if needed
=== Kamion cuts and pastes the above to the bug
[01:08] <Kamion> allee: no need, thanks
[01:09] <allee> Kamion: 'k.   Saves me some time ;)
[01:14] <allee> Keybuk: mhmm, after boot mpt* drivers are loaded before usb-storage.  Point I don't understand is why can the system still access / via sdi1
[01:15] <Keybuk> it can't
[01:15] <Keybuk> it's just lying to you
[01:15] <Keybuk> "mount" just outputs a text file that's created after the system has booted
[01:15] <Keybuk> and that just seeds the root filesystem information from /etc/fstab, which is wrong
[01:16] <Keybuk> it has nothing to do with where the root filesystem REALLY IS :)
[01:16] <Keybuk> it's just all there for compatibility with old shit
[02:00] <allee> Keybuk: cool. not the first time old shit drives me crazy. thx for this info!
[02:43] <crispinf> /etc/mtab is something I don't understand, /proc/mounts is much more reliable :-)
[03:01] <Kamion> AFAIK the only reason /etc/mtab hasn't been replaced with a symlink to /proc/mounts is that /proc/mounts doesn't give you all the information that /etc/mtab gives you about loopback mounts
[03:01] <Kamion> at least that was the problem last time it was suggested in Debian
[03:04] <crispinf> sounds to me like minor bug compared to the fact that mtab can sometimes just give you plain wrong info :-)
[03:08] <Kamion> it's not a huge deal, but it was a regression ... sometimes the bugs you know about are better than shiny new ones ;-)
[03:09] <crispinf> true :-)
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin]  has joined #ubuntu-boot
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin]  has joined #ubuntu-boot