Voodooprojects
Chameleon => Bug Reports => Topic started by: d00d on July 28, 2009, 02:03:09 AM
-
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
-
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.
-
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.
-
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.
-
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.
-
Add me to the list of people with the ebios read error problem. 3 Samsung 1.5 TB drives mirrored on Apple software raid. Chameleon will not boot after the error - had to go back to efi v9 1.0.12.
Gigabyte X58-UD3r w core i7 920 ...
-
As a work-around, I've been manually disconnecting the apple software raid with my 3 samsung 1.5TB drives and then re-connecting them after chameleon starts ...
Noticed that the volume Apple Software raid creates is Apple_HFS format vs GUID or MBR - Wonder if this has anything to do with the problem or whether it might offer a work around that's compatible w Chameleon ... ?
cheers ...
:-\
-
What do you mean HFS vs. GUID or MBR?
HFS is a file system, GUID and MBR are partition types.
-
Just got this problem myself. Weird, all of a sudden, after a day or so of having the raid, this problem started happening. Is there a way to create the HSF+ raid without the 3 partitions that OSX creates? I believe that the problem may be one of partitioning.
-
I have figured out a (temporary, I hope) solution to this problem. Edit your com.apple.Boot.plist file and set a new key/value pair Scan Single Drive - YES
This is using Chameleon 2 rc 2 r640. I don't know if any previous versions allow this.
-
@cmsimike: that works, thanks
-
The above solution works but we're limited to one drive. Anyone know of a way (the syntax) to exclude scanning the problematic drives while still including all other drives ...?
-
I think it would be better to fix the issue instead adding such options to exclude specific drives.
At the moment i don't have access for such large disks...
-
I have the same issue with my Seagate 500 gb drive, it is formated ntfs and if I unplug it chameleon works normally. This issue occurs when using both chameleon 2 rc1 and rc2. Hope there will be a fix soon...
-
Hopefully the >1TB addressing issue is fixed by now :)
-
Hopefully the >1TB addressing issue is fixed by now :)
Are you suggesting chameleon has been updated to address this issue ... ???
cheers.
-
Are you suggesting chameleon has been updated to address this issue ... ???
cheers.
No, it will be in the next release.
-
thanks - RC3 works great ....
-
I can't necessarily say I have solved this problem. But, it is "fixed" for now on my machine. I have a multi-boot Win7, multi-partition system with SL, Lion and Mt Lion and installer partitions running. I started to get this EBIOS error everything. First, I reset the mb bios, then turned off/on the legacy usb with differnet boots. Nothing.
Then I noticed I had a Canon scanner/printer usb plugged in at boot and showing up in the boot setup list. It had been plugged in and "on" when I tested a installer usb. That is when it all started for me.
I turned off the printer and all devices and the EBIOS boot error went away. Simple as that... I suspect this has something to do with non-bootable usb devices being plugged in at boot. Thought I'd share. :)