[Bug 396564] Re: grub2 shows 'biosdisk read error', then boots
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, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0002d4ad Device Boot Start End Blocks Id System /dev/sda1 * 1 134 1076323+ fd Linux raid autodetect /dev/sda2 135 30401 243119677+ fd Linux raid autodetect Disk /dev/sdb: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00025c92 Device Boot Start End Blocks Id System /dev/sdb1 * 1 134 1076323+ fd Linux raid autodetect /dev/sdb2 135 30401 243119677+ fd Linux raid autodetect Disk /dev/md0: 1102 MB, 1102053376 bytes 2 heads, 4 sectors/track, 269056 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 249.0 GB, 248954421248 bytes 2 heads, 4 sectors/track, 60779888 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x0804 Disk /dev/md1 doesn't contain a valid partition table sudo mdadm --detail /dev/md0 /dev/md0: Version : 00.90 Creation Time : Fri Oct 30 15:40:33 2009 Raid Level : raid1 Array Size : 1076224 (1051.18 MiB 1102.05 MB) Used Dev Size : 1076224 (1051.18 MiB 1102.05 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Tue Nov 10 10:56:31 2009 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 47c9a647:473c1802:9515e672:ee318adb Events : 0.229 Number Major Minor RaidDevice State 0 810 active sync /dev/sda1 1 8 171 active sync /dev/sdb1 sudo mdadm --detail /dev/md1 /dev/md1: Version : 00.90 Creation Time : Fri Oct 30 15:40:47 2009 Raid Level : raid1 Array Size : 243119552 (231.86 GiB 248.95 GB) Used Dev Size : 243119552 (231.86 GiB 248.95 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Tue Nov 10 11:10:50 2009 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 026cf484:89dec43d:3b5e59a4:166e8441 Events : 0.169383 Number Major Minor RaidDevice State 0 820 active sync /dev/sda2 1 8 181 active sync /dev/sdb2 cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md1 : active raid1 sda2[0] sdb2[1] 243119552 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 1076224 blocks [2/2] [UU] unused devices: none -- 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-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 396564] Re: grub2 shows 'biosdisk read error', then boots
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 problem - the system boots just fine after a delay waiting
for that message.
some data on the disk layout - /dev/md0 is the /boot raid1:
--
### BEGIN /etc/grub.d/10_linux ###
menuentry Ubuntu, Linux 2.6.31-14-generic {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod raid
insmod mdraid
insmod ext2
set root=(md0)
search --no-floppy --fs-uuid --set 41a623ac-fd6d-428d-abc9-472bd6caf9dd
linux /vmlinuz-2.6.31-14-generic root=/dev/mapper/vger2-sys ro
quiet splash
initrd /initrd.img-2.6.31-14-generic
}
--
r...@vger:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid1] [linear] [multipath] [raid0]
[raid10]
md1 : active raid5 sdd2[3] sdc2[1] sda2[2] sdb2[0]
1464260160 blocks level 5, 64k chunk, algorithm 2 [4/4] []
md0 : active raid1 sdb1[0] sdd1[3] sdc1[1] sda1[2]
297088 blocks [4/4] []
unused devices: none
r...@vger:~# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xda56cdd4
Device Boot Start End Blocks Id System
/dev/sda1 * 1 37 297171 fd Linux raid autodetect
/dev/sda2 38 60801 488086830 fd Linux raid autodetect
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000bad08
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 37 297171 fd Linux raid autodetect
/dev/sdb2 38 60801 488086830 fd Linux raid autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa5357bed
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 37 297171 fd Linux raid autodetect
/dev/sdc2 38 60801 488086830 fd Linux raid autodetect
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 37 297171 fd Linux raid autodetect
/dev/sdd2 38 60801 488086830 fd Linux raid autodetect
Disk /dev/md0: 304 MB, 304218112 bytes
2 heads, 4 sectors/track, 74272 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 1499.4 GB, 1499402403840 bytes
2 heads, 4 sectors/track, 366065040 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x
Disk /dev/md1 doesn't contain a valid partition table
--
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-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 396564] Re: grub2 shows 'biosdisk read error', then boots
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-ubuntu- jaunty.html I'm also seeing a , bss=0x0 entry being output before the Starting... message. Its also odd but fdisk is complaining that neither device has a valid partition table. Related? Not sure how you get to that state or if it's related to me using Rieser on that system, but things boot OK. r...@alphamail:~# fdisk -l Disk /dev/sda: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000bae9f Device Boot Start End Blocks Id System /dev/sda1 * 1474138082051 fd Linux raid autodetect /dev/sda247424865 996030 fd Linux raid autodetect Disk /dev/sdb: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000954d1 Device Boot Start End Blocks Id System /dev/sdb1 * 1474138082051 fd Linux raid autodetect /dev/sdb247424865 996030 fd Linux raid autodetect Disk /dev/md1: 1019 MB, 1019805696 bytes 2 heads, 4 sectors/track, 248976 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md0: 39.0 GB, 38995951616 bytes 2 heads, 4 sectors/track, 9520496 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x Disk /dev/md0 doesn't contain a valid partition table -- 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-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 396564] Re: grub2 shows 'biosdisk read error', then boots
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 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 fd Linux RAID autodetect /dev/sda2 14 121601 976655610 fd Linux RAID autodetect === $ sudo mdadm --detail /dev/md0 === /dev/md0: Version : 00.90 Creation Time : Mon Apr 23 00:17:47 2007 Raid Level : raid1 Array Size : 104320 (101.89 MiB 106.82 MB) Used Dev Size : 104320 (101.89 MiB 106.82 MB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Thu Oct 22 08:12:49 2009 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 UUID : 74ad3d60:5074597c:0324c307:5941c2e9 Events : 0.7296 Number Major Minor RaidDevice State 0 000 removed 1 811 active sync /dev/sda1 === $ sudo mdadm --detail /dev/md1 === /dev/md1: Version : 00.90 Creation Time : Mon Apr 23 00:18:02 2007 Raid Level : raid1 Array Size : 976655488 (931.41 GiB 1000.10 GB) Used Dev Size : 976655488 (931.41 GiB 1000.10 GB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Thu Oct 22 08:32:24 2009 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 UUID : 58a33554:66ab860b:f095819a:ef47ab1e Events : 0.108323780 Number Major Minor RaidDevice State 0 000 removed 1 821 active sync /dev/sda2 === $ sudo pvs === PV VG Fmt Attr PSize PFree /dev/md1 rootvg lvm2 a- 931.41G 772.00M === $ sudo vgs === VG #PV #LV #SN Attr VSize VFree rootvg 1 4 0 wz--n- 931.41G 772.00M === $ sudo lvs === LV VG Attr LSize Origin Snap% Move Log Copy% Convert mythtv rootvg -wi-ao 901.66G root rootvg -wi-ao 25.00G swap rootvg -wi-ao 1.00G varlog rootvg -wi-ao 3.00G === It is worth noting that I have a RAID 1 which was created with a second disk of `missing', but by the sound of it - most folks here are seeing this with RAID setups which are not running degraded like mine. -- 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-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 396564] Re: grub2 shows 'biosdisk read error', then boots
** 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
