This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of U
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
I have the same issue as comment #17. I have my version of Karmic U.
Studio installed as a software raid with grub 2 in MBR of 1st Sata
drive, & I have /boot as a separate non raid partition on same drive. I
have not flashed my bios yet since it is so recent and the new versions
don't seem to ha
For me, disabling the FDD in BIOS actually much much worsens the situation.
Instead of like 3-5secs wait, I get maybe 30 or more seconds before the message
flashes and boot continues.
--
grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug no
My Dell PowerEdge T610 has no floppy option in BIOS whatsoever. I still
get the biosdisk read error.
--
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.
Hi FriDisch,
If you have a physical FDD connected, as a workaround, try having a
formatted floppy in the drive when you boot.
--
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
@Per Kongstad:
Thats not correct: I actually have a physical FDD connected, but I have
the 'biosdisk read error' anyway
--
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 sub
Hi,
I had same issue.
Resolved by disabling FDD in BIOS.
No connected physical FDD but enabled in BIOS seems to generate the
error.
Running software raid 1.
--
grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug notification because you a
I don't know if this is a solution for those of you who run RAID,
however for me i just run a single Hard Drive so it appears to have
worked.
I disabled my non existent Floppy Drive in the BIOS as per Stephens
workaround, i went a few steps further and configured my bios settings.
I disabled all
I can confirm Shephens workaround too.
--
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 list
ubuntu-bugs@lists.ubuntu.com
http
I can also confirm Stephens workaround: disabling the floppy drive
(actually not present in my machine) in the BIOS solves the problem.
Thanks.
--
grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug notification because you are a member of U
Just to add my 2 cents... I was seeing this error and got here because
I was having problems booting after I'd intentionally degraded an array
to replace a disk in it. It was this error that got me here.
After reading through this I tried the idea mentioned to disable the
floppy drive that was e
Stephen: How are you mounting your raid array? Is it mounted as "/" or
as "/boot". In my case, I mount md0 as /boot and only /boot is in the
raid array. My "/" is mounted from a lvm volume. If yours is similar,
then Fleix's response (message 37) will also apply to you. if md0 is
mounted as /b
Felix,
Here are answers to the questions that you asked...
>Did you install GRUB 2 to a MBR of a different disk then /boot/grub is
>on?
No, I have a RAID1 boot configuration with GRUB 2 installed to the MBR
of both drives so that I can boot from either one.
>Check if `echo $prefix' or just `se
Am Montag, den 07.12.2009, 21:55 + schrieb jim_charlton:
> update-grub
> grub-install /dev/sda
> grub install /dev/sdb
> and then reboot. The grub prefix (set command from the grub shell on
> booting) is still (md0)/grub!
> H?? /etc/grub.d/00_header has
>
> ..
> transform="s,x,x,"
> ..
>
update-grub
grub-install /dev/sda
grub install /dev/sdb
and then reboot. The grub prefix (set command from the grub shell on booting)
is still (md0)/grub!
H?? /etc/grub.d/00_header has
..
transform="s,x,x,"
..
..
..
..
grub_prefix=`echo /boot/grub | sed ${transform}`
..
Is that where the g
I don't mean to hijack the "biosdisk read error" thread... but when I
follow the advice of message 34 above and check my grub "prefix" I find
it is set to (md0)/grub! Shouldn't it be (md0)/boot/grub or simply
(md0)/boot? How do I change it in the grub configuration? I will
reinstall grub and see
Am Samstag, den 05.12.2009, 18:56 + schrieb Stephen Cuka:
> I couldn't find any documentation on the search command in the grub
> wiki, but if the purpose of the search command is to identify all the
> bios devices and raid devices that later grub.cfg commands use to boot
> OS's, shouldn't "--n
I had the same problem in Debian testing, grub2, version 1.97~beta3-1, md and
lvm configuration.
Building grub2 from bazaar repository didn't help.
The delay occurs in biosdisk.mod file somewhere in grub_biosdisk_rw while
accessing disks, especially fdd.
Simple solution for me was to completely
I can confirm Stephens findings: with a floppy in the floppy drive or
with floppy disabled in the BIOS, grub-pc loads well.
Thanks for this workaround.
Regards
Heinz
--
grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug notification bec
I receive the same "biosdisk read error" displayed briefly before my
grub menu is displayed.
On my system, the error occurs right after grub does a seek to the
floppy drive, after grub loads but before the menu is displayed. So
thinking the seek and the error were related, I decided to test that
I tried installing the grub-pc_1.97+20091125-2_amd64.deb and grub-
common_1.97+20091125-2_amd64.deb packages to see if that would help but
the results are the same. It takes ca. 9 seconds after the Grub
loading... message before the grub menu appears. And then there is a 5
second countdown to boo
GRUB 2 is indeed extremely slow in some setups (including my two main
machines, both having two disks and showing the GRUB 'bios disk error'
message at startup). On both machines it takes between 10 and 25 seconds
to get past the GRUB menu. If Ubuntu 10.04 wants to start in 10 seconds,
I guess maki
Actually... the time from the first appearance of the "Grub loading..."
line until it starts to boot is still about 15 seconds. It seems faster
but that is still pretty slow. Why is it so slow? Is this normal?
Seems to me it was faster with Grub Legacy.
--
grub2 shows 'biosdisk read error', t
I took the plunge and compiled grub-1.97~beta4, following the
intstructions in the INSTALL file (run ./autogen.sh; run ./configure;
make; make install). The make install gave me an error. But it was
something about installing man pages and updatedb followed by `locate
bin/grub` showed me that new
Same problem here. Where can I find out the current status of this
problem. Is it a problem only on machines with the AMI BIOS. The error
message appears to be coming from
/grub-1.97~beta4/disk/i386/pc/biosdisk.c (grub2 source). Is there an
incorrect BIOS response to one of the BIOS calls to th
I have the same problem
p...@servidor:~$ uname -a
Linux servidor 2.6.31-15-server #50-Ubuntu SMP Tue Nov 10 15:50:36 UTC 2009
x86_64 GNU/Linux
/dev/sda1 1 30 240943+ fd Linux raid autodetect
/dev/sda2 311003 7815622+ fd Linux raid autodet
ubuntu karmic 9.10 official release same problem fdisk is same as mtx
basically.
this still exists today a good say month after the release date?
something should be done about this, a suprising number of people have
soft raid and therefore a suprising number of people cant have ubuntu...
fix boot
** Description changed:
--
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 list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
I might add that the abovementioned configuration was freshly installed
on a brandnew Dell PowerEdge T610, i.e. no update from an older release.
--
grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You received this bug notification because you are a member of U
I experience the same thing.
Two 1 TB drives are set up with two partitions each: one for /boot, one
for LVM. Inside the logic volumegroups are separate logic volumes for /,
/var, /tmp and swap. Both partitions are mirrored with software RAID
(level 1).
The other eight 1 TB drives are hooked up t
** Bug watch added: GNU Savannah Bug Tracker #27616
http://savannah.gnu.org/bugs/?27616
** Also affects: grub via
http://savannah.gnu.org/bugs/?27616
Importance: Unknown
Status: Unknown
--
grub2 shows 'biosdisk read error', then boots
https://bugs.launchpad.net/bugs/396564
You re
same issue here. "grub loading." stays for a while, then i get "error: biosdisk
read error".
Karmic Koala stable x64 alternative installation. mirror RAID for /boot and an
encrypted mirror RAID for / (root)
> sudo fdisk -l
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track,
I can confirm this on my jaunty to karmic upgrade as well. I did a
network upgrade of a clean jaunty base (ssh only) installation. I'm
getting the same error booting from a valid mirror set via the chainload
option recommended here:
http://www.ubuntu-inside.me/2009/06/howto-upgrade-to-grub2-on-u
I can also confirm this behaviour. I updated from Jaunty to Karmic (I
assume beta at this point), and I have the following configuration:
$ sudo fdisk -l
===
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sect
** Summary changed:
- karmic alpha: grub2 shows 'biosdisk read error', then boots
+ grub2 shows 'biosdisk read error', then boots
--
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, wh
36 matches
Mail list logo
