Same here with Karmic beta i386
boot on raid1 (md0)
lvm on raid0 (md1) containing root, home, swap
Several seconds Grub loading., then error: biosdisk read error. A
menu is displayed though.
--
karmic alpha: grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
I can confirm this with the most recent version of grub2. Having three
RAID 1 partitions (on sda and sdb), I briefly get a biosdisk read
error for about half a second, then everything continues without
problems.
** Changed in: grub2 (Ubuntu)
Status: New = Confirmed
--
grub2 shows
i did install karmic alpha 4(or 5) with /dev/md0 as raid1 for /boot and
/dev/md1 as raid5. At the current beta the bug is still there.
I have exactly the same error: error: biosdisk read error After some
seconds the boot goes on.
--
karmic alpha: grub2 shows 'biosdisk read error', then boots
I installed using karmic alpha 6, upgraded now to karmic beta, I'm
seeing this as well.
I have /boot on /dev/md0 as raid1, and the rest of the partitions are on
lvm using /dev/md1 which is raid10.
I see Loading GRUB. for a few seconds, then I see something like
error: biosdisk read error for
fwiw, I'm seeing the same error on current Debian unstable. RAID1 mirror
/dev/md0, on top of which is an LVM physical volume containing /, /home
and one or two other logical volumes.
I get the grub2 loading grub primpt on boot, then nothing for 10 seconds
or so, then biosdisk read error followed
I'm using the Karmic Beta, I have legacy grub chain loading grub2.
On boot I get the legacy grub prompt, I select chain load grub2, then I
get biosdisk read error then the system boots without showing the
grub2 prompt.
I am using a separate /boot and raid1+lvm for other partitions.
--
karmic
I can confirm this on Ubuntu 9.10 beta. I have a RAID1 array with no
separate /boot partition. At boot, the message Grub loading. comes up
and stays more than 10 seconds, then for half a second biosdisk read
error is displayed and finally I can reach the menu, which works
normally for both Ubuntu
I can confirm that this is present in the beta.
I have a Raid 0 setup, and installed the AMD64 beta.
Thanks,
--
karmic alpha: grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I also found this issue in Karmic beta. I have (software) RAID1 set up
with AMD64. Fortunately grub boots into default selection, so the
system still works overall.
--
karmic alpha: grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug
I had this issue on the last alpha, and just burned a CD with the newest
beta released today and can confirm that this issue is still present in
a fresh install of the Oct 1 beta release. I also have no grub menu as
a previous poster mentioned, and also find that it automatically boots
the default
Thank you for taking the time to report this bug. Can you try this out
on Karmic Alpha 6 and see if it is still an issue?
** Changed in: grub2 (Ubuntu)
Status: New = Incomplete
--
karmic alpha: grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You
Can I install debs from Karmic Alpha 6 on Debian unstable?
--
karmic alpha: grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I have the same problem, too. Note that the grub menu is not offered.
Rather the preselected menu-entry is booted directly.
My partition tables:
/dev/sda1 1 60770 488134993+ fd Linux RAID autodetect
/dev/sda2 60771 60801 249007+ 5 Erweiterte
I saw the same on one of my Debian machine. I have md devies on that
machine. Maybe it's related.
--
karmic alpha: grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
14 matches
Mail list logo
