EBIOS read error: Error 0x01 [SOLVED]

Chameleon > Bug Reports

(1/4) > >>

d00d:
I have Chameleon booting OS X on a RAID 0 pair of X25-Ms, and storage and backup partitions on a RAID 1 pair of Seagate 1.5TBs;

[mac05:~] root# diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *74.5 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_RAID 74.2 Gi disk0s2
3: Apple_Boot Boot OSX 128.0 Mi disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *74.5 Gi disk1
1: EFI 200.0 Mi disk1s1
2: Apple_RAID 74.2 Gi disk1s2
3: Apple_Boot Boot OSX 128.0 Mi disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS mac05 *148.4 Gi disk2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.4 Ti disk3
1: EFI 200.0 Mi disk3s1
2: Apple_RAID 500.0 Gi disk3s2
3: Apple_Boot Boot OSX 128.0 Mi disk3s3
4: Apple_RAID 896.8 Gi disk3s4
5: Apple_Boot Boot OSX 128.0 Mi disk3s5
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.4 Ti disk4
1: EFI 200.0 Mi disk4s1
2: Apple_RAID 500.0 Gi disk4s2
3: Apple_Boot Boot OSX 128.0 Mi disk4s3
4: Apple_RAID 896.8 Gi disk4s4
5: Apple_Boot Boot OSX 128.0 Mi disk4s5
/dev/disk5
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS storage *500.0 Gi disk5
/dev/disk6
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS backup *896.8 Gi disk6
[mac05:~] root#

With RC1 I get sixteen repeating sets of `EBIOS read error: Error 0x01' and `Block -1364952312 Sectors 64' lines before the Chameleon countdown timer. If I then press a key during the countdown timer I get eight sets of `EBIOS read error: Error 0x01' and `Block -1364952310 Sectors 64' lines, eight sets of `EBIOS read error: Error 0x01' and `Block -1364950248 Sectors 64' lines, and four sets of `EBIOS read error: Error 0x01' and `Block -13649550224 Sectors 64' lines before it freezes.

At least with RC1 it can boot, but with RC2 the Chameleon countdown timer never shows, and it goes through all thirty six sets of ebios error lines before it freezes.

This seems to be related to libsaio's sys.c inability to cope with the Seagate 1.5TB drive, and fdisk reports negative geometry as well;

[mac05:~] root# fdisk -e /dev/rdisk3
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> p
Disk: /dev/rdisk3 geometry: -5415437/4/63 [-1364690128 sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - -1364690129] <Unknown ID>
2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
fdisk: 1> q
[mac05:~] root#

There's a similar Solaris problem here;

http://opensolaris.org/jive/thread.jspa?threadID=86669&tstart=0

awulf:
I too have the exact same error, two 1.5TB Seagate SATA drives in mirrored RAID. Same behaviour in RC1 and RC2 as the post above. If I format the drives to individual drives, then no errors occur.

zef:
Need to check how the booter handles the int 13h EBIOS read calls, but unfortunately i don't have such large disks to test it.

d00d:
Zef, I could run a debug version of the booter against the drives if you could supply one as source or binary.

The problematic Seagate drives have the fixed CC1H BIOS that seemingly has resolved the Solaris issue, but not the Chameleon one.
MB is a Gigabyte GA-EX58-UD5 with the current F7 non beta BIOS, and the drives are attached to the ICH10R SB in AHCI mode.
The Intel RAID 0 is CCC'd to Seagate RAID 1 `backup', and configured to boot with Chameleon 2.
Seagate RAID 1 `storage' doesn't have an OS, and is not configured with Chameleon 2.

One Seagate drive was originally attached via USB in a non RAID configuration to an OS X and Chameleon 2 Lenovo T61.
It didn't have any boot errors, and I was able to select it in the Chameleon 2 GUI, but I wasn't able to actually boot from it unless I was doing so from a Kalyway DVD.

d00d:
Correction: I wasn't able to boot from a single external Seagate 1.5TB with a Kalyway DVD, I was using an external 100GB drive instead.

Navigation

[0] Message Index

[#] Next page

Go to full version