Thanks Christoph for the solution.
The report will be closed now. Should there be any new information about
this issue to warrant it to re-open, please feel free to do so.
Thanks
** Changed in: grub (Ubuntu)
Status: Incomplete => Invalid
--
Booting fails after installation (GRUB error)
Before you close it, JFTR: I had a similar problem (GRUB error) with
Feisty. The solution was to reinstall the boot manager in the MBR.
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification because you are a member of Ubuntu
Bug
yes thanks
--- Ralph Janke <[EMAIL PROTECTED]> wrote:
> Is it ok to close this report?
>
> Thanks
>
> --
> Booting fails after installation (GRUB error)
> https://bugs.launchpad.net/bugs/107951
> You received this bug notification because you are a
> direct subscriber
> of the bug.
>
__
Is it ok to close this report?
Thanks
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
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.co
I file a new bug for the problems with my optical drives (I really need
them!). Thanks so far!
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
It's really weird: I can boot from the Ubuntu disk if the Debian disk is
plugged in. But then neither my CD-ROM drive nor my DVD drive is usable.
No medium is recognized and I have no glue to which device they are
connected to. I tried /dev/hda--/dev/hdf and /dev/sda--/dev/sdf---but
nothing is foun
Ok. But how can I fix my original problem that I can't boot the Ubuntu
disk if the Debian disk isn't plugged in?
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
The new kernel structures all disks under SATA irrespective if they are
or not. It wraps a SATA-emulator around the IDE interface in order to
streamline things.
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification because you a
Ubuntu detects its drive as /dev/sdb if the Debian drive is plugged in.
But I still wonder why it is detected resp. mounted as a SCSI device.
It's an IDE drive---no SCSI, no S-ATA ...
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug not
Does ubuntu detect the drive with a different hardware address depending
if the debian drive is plugged in or not?
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
Yes, I did but it results in Error 25. But I just tried to boot with the
Debian HDD plugged in (I can choose a boot medium from a "Boot selection
popup menu" of my mainboard) and it worked! I don't know why especially
because the Debian HDD wasn't plugged in when I installed Ubuntu. But
even if it
Christoph,
I just see that you lshw shows: bus info: [EMAIL PROTECTED] Did you ever try to
map hd2 to /dev/hde and put (hd2,0) in the root ?
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification because you are a member of Ubun
Doesn't work for me. Now---without changing the BIOS settings---I get
"Error 16: Inconsistent filesystem structure" or the boot device isn't
found. But the Debian installation still works fine, thus I exclude a
hardware defect.
--
Booting fails after installation (GRUB error)
https://bugs.launchp
I figured it out... disabling DMA transfer access in the IDE bus BIOS
settings fixed it... no more stage1.5Read errors
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
I have a similar problem with a Hitachi Travelstar 40G harddrive taken
from a Thinkpad T30. I'm trying to use it with a new VIA CN700 Mini-ITX
board. Basically the harddisk works with the the Thinkpad (w/ either
Dapper or Feisty) but does not want to work with the VIA giving the same
"stage1.5Read
I did not change "root (hd0,0)" to "root (hd0) /dev/hde" in menu.lst as
I wrote above but in device.map. Without changing this I don't even can
access the GRUB menu.
Now I tried every reasonable combination---at least I hope so---of the
root and the kernel line but it did not work. I'm at a loss .
The command
root (hd0,0)
means the first drive and the first partition. You can not change this
into "root (hd0) /dev/hde" or something like this. You can only change
the numbers (i.e. hd1,2 would be the second drive and the third
partition on it).
The kernel line as as root either the device or
Any idea what I can do to get this installation boot?
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
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@
I attach the output of lshw from the ubuntu-live-cd. I installed the HDD
as master again.
** Attachment added: "lshw.out"
http://librarian.launchpad.net/7386057/lshw.out
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification
Could you please run the command
sudo lshw -C disk
from the ubuntu live-CD that we can see how the ubuntu kernel recognises
the disks.
Thanks
--
Booting fails after installation (GRUB error)
https://bugs.launchpad.net/bugs/107951
You received this bug notification because you are a member of U
IMPORTANT HINT: Actually the HDD named /dev/hdf (Samsung, 80 GB) in the
following is /dev/hde within Ubuntu! It's only hdf now because I use the
Debian HDD (Maxtor) as master and the Ubuntu HDD (Samsung) as slave to
access the Ubuntu (Samsung) HDD.
Ubuntu machine: Samsung = /dev/hde
Debian machine
Error 25 identifies an unrecognized command. Could you attach your
menu.lst ? And also please the output of
sudo lshw -C disk
and the output of
sudo fdisk -l
and the contents of /etc/fstab
and the output of
blkid
Thanks
--
Booting fails after installation (GRUB error)
https://bugs.launchpa
The UUID-labels are used (I can access the HDD from my Debian
installation):
title Ubuntu, kernel 2.6.20-15-generic
root(hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic
root=UUID=fb7e259a-4de7-4810-9041-c981d9946e94 ro quiet splash
initrd /boot/initrd.img-2.6
Thanks for your bug report.
In feisty, grub does not access the drives anymore via hda or sda but
via UUID-label.
Please boot up the system with the live CD and check the file
/boot/grub/menu.lst if the UUID-labels are used.
** Changed in: grub (Ubuntu)
Assignee: (unassigned) => txwikinger
24 matches
Mail list logo
