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 a clean install from karmic stable. it was also
present in an upgrade from jaunty on the same machine.
my situation is two partitions per drive (4 drives) - the first
partition(s) are /boot and are raid1, and the other partition(s) are a
raid5 lvm volume group.
it's not a pr
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
