[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
** Changed in: grub (Ubuntu) Status: New = Fix Released -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://bugs.launchpad.net/bugs/61578 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
This bug is old and was fixed in subsequent version. It is no longer applicable to me and I am happy for it to be closed. Regards Warren -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://bugs.launchpad.net/bugs/61578 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
I upgraded to 6.10 two days ago from 6.06. My newly installed kernel is 2.6.17-10. My grub menu.lst also was translated incorrectly, leaving me with a non- booting machine. It drops me in a busybox prompt. The error was resolved by replacing the root=UUID-not-very-human- readable-string with root=/dev/hda7. FSTAB: cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 # /dev/hda7 -- converted during upgrade to edgy UUID=8ab6cfdb-6149-4b97-89ac-42e91681f91d / reiserfs defaults 0 1 # /dev/hda1 -- converted during upgrade to edgy UUID=1bf33064-2774-4739-93ce-53728123ed7d /boot ext2 defaults 0 2 # /dev/hda6 -- converted during upgrade to edgy UUID=dae1d23a-97b0-4372-8880-c10959f27fe9 /data reiserfs defaults 0 1 # /dev/hda5 -- converted during upgrade to edgy UUID=a63febd0-537a-4471-a697-a4329ece9dea none swap sw 0 0 /dev/hdc/media/dvd udf,iso9660 ro,user,noauto 0 0 /dev/hdd/media/cdromudf,iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy autorw,user,noauto 0 0 /dev/casio /media/casiovfatrw,user,noauto 0 0 /dev/hp618 /media/hp618vfatrw,user,noauto 0 0 /dev/olympus/media/olympus vfatrw,user,noauto 0 0 none/proc/bus/usb usbfs defaults0 0 MENU.LST title Ubuntu, kernel 2.6.17-10-386 root(hd0,0) #kernel /vmlinuz-2.6.17-10-386 root=UUID=a63febd0-537a-4471-a697-a4329ece9dea ro quiet splash kernel /vmlinuz-2.6.17-10.386 root=/dev/hda7 ro quiet splash initrd /initrd.img-2.6.17-10-386 savedefault boot FDISK sudo fdisk -l /dev/hda Disk /dev/hda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 3 24066 83 Linux /dev/hda2 4 14594 117196695+ f W95 Ext'd (LBA) /dev/hda5 4 88 682731 82 Linux swap / Solaris /dev/hda61277 14594 106971322+ 83 Linux /dev/hda7 891276 9542578+ 83 Linux Partition table entries are not in disk order This is a problem that started in 6.06 and has been carried over into 6.10. And it's probably my fault for having partitions in a wierd order? Shout if I can tell more... -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
This bug was originally found on a Knot 2 installation that was upgraded until the kernel was reached 2.6.17-7. However, I recently reinstalled the machine with Xubuntu Edgy Daily 24102006 and everything is as it should be. Therefore, I suspect that this will not affect new installations and can be closed from my perspective. -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
I'm not positive this is the right place for this report, let me know if it isn't. I have a Toshiba Portege S100 https://wiki.ubuntu.com/LaptopTestingTeam/ToshibaPortegeS100 this laptop has an intel sata raid controller, Breezy was unable to detect the drive at boot, Dapper resolved this issue, at least when using the graphical installer cd, the issue was documented here: https://launchpad.net/distros/ubuntu/+source/initramfs-tools/+bug/19749 I have this laptop with dapper installed and working fine, I installed edgy beta1, removing the swap and ext3 partitions, creating new ones. During the graphical install process it gets stuck at 94%, at the step: installing grub boot loader running update-grub... If I try doing the text based install I get: installing the base system debootstrap warning warning: failure trying to run: chroot /target mount -t proc proc /proc -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
This is still the case with 2.6.17-10. -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
Latest update of grub and kernel (9/27) adds what appears to be a correct kopt entry to /boot/grub/menu.lst (in my case root=UUID=67f18326-0ffc-4835-9de5-67d173f6ca84 ro) however it also adds a /hda1 entry as well which causes update-grub to produce a root=/hda1 which causes the boot to fail. If this latter kopt is removed an update-grub produces a workeable menu.lst with root=UUID=67f18326-0ffc-4835-9de5-67d173f6ca84 ro as a kernel option for the edgy kernels. I do have a ide (as well as scsi) disk on hda which must be being detected and incorrectly inserted in menu.lst (I never have a root file system attached to the ide drive). -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
I had a similar problem which I originally reported as a kernel issue. After 2.6.17-7 (8 and 9) the system would not boot with the error: Begin: Waiting for root file system My /etc/fstab shows: # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 # /dev/sda10 -- converted during upgrade to edgy UUID=67f18326-0ffc-4835-9de5-67d173f6ca84 / ext3 defaults,errors=remount-ro 0 1 # /dev/sda5 -- converted during upgrade to edgy UUID=2aed16dc-cfb2-49c7-b656-ae238b383997 /media/sda5 ext3 defaults 0 2 # /dev/sda6 -- converted during upgrade to edgy UUID=f8048a1c-68e7-4f26-9d6e-0e43de790488 /media/sda6 ext3 defaults 0 2 # /dev/sda7 -- converted during upgrade to edgy UUID=2f0175ef-bd42-41e2-8e32-c92a155da5ab /media/sda7 ext3 defaults 0 2 # /dev/sda9 -- converted during upgrade to edgy UUID=2854cb27-da6e-44bd-ba7c-18879b5621e3 /media/sda9 ext3 defaults 0 2 # /dev/sdb5 -- converted during upgrade to edgy UUID=6707952b-349c-4cc4-96e4-34147b25930d /media/sdb5 ext3 defaults 0 2 # /dev/sda8 -- converted during upgrade to edgy UUID=fb837170-93eb-45bf-a8e5-6b7e8f0f4d06 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 But in /boot/grub/menu.lst the relevant boot line showed: /boot/vmlinuz-2.6.17-9-generic root=/dev/sda10 ro If I replaced this with the right root location according to /etc/fstab i.e. with /boot/vmlinuz-2.6.17-9-generic root=UUID=67f18326-0ffc-4835-9de5-67d173f6ca84 ro then the system booted without problem. It seems that in upgrading from dapper the filesystem or partition information in /etc/fstab has been changed but this change has not been reflected in the grub entry. Following a suggestion by Ben Collins I removed kopt lines in /boot/grub/menu.lst and ran grub-update. This had the effect of replacing root=/dev/sda10 with root=/dev/hda1 which was veru strange and this also did not help the system boot. I think this is a major bug because I installed a standard dapper and then did a standard upgrade to edgy and the sytem did not boot. -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
** Tags added: edgy grub -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61578] Re: [Edgy] Wrong boot disk parameter since 2.6.17-7
** Changed in: Ubuntu Sourcepackagename: None = grub -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
