 |
 |
FireWire HD isn't bootable anymore after updating to 9.1
|
|
|
|
|
Simon C. Leemann
|
|
I have an iMac DV+ and a LaCie 20GB FireWire HD. Under 9.0.4 I could select the FireWire disk as the startup volume and all worked well. Since I upgraded to 9.1 (I installed the newest drivers from LaCie as well) this no longer works, i.e. I can select the disk in the startup volume control panel but when my iMac boots it just hangs after getting the happy mac. 
If I boot holding down option I see my internal 9.1 volume and the FireWire disk. If I select the FireWire disk it hangs after the happy mac as well. 
Does anybody have an idea what's screwed here? The drivers are the newest ones, 9.1 was a clean install, my FireWire disk has a perfectly new and complete 9.1 installed.
scl
|
|
|
| |
|
|
|
|
|
|
|
Bobby
|
|
I'm surprised you were ever able to boot off your firewire drive. I thought firewire drives wern't bootable (I know at the very least OS X says it will NOT boot off a firewire drive). Most likely a change in Firewire 2.7 is causing it. It may have been a "bug fix", as I said I don't believe firewire drives are supposed to be bootable...
------------------
|
|
|
| |
|
|
|
|
|
|
|
Simon C. Leemann
|
|
Originally posted by Bobby:
I'm surprised you were ever able to boot off your firewire drive. I thought firewire drives wern't bootable (I know at the very least OS X says it will NOT boot off a firewire drive).
Well, it booted fine from the FireWire HD under 9.0.4. This was made possible by one of the FireWire Updates, that was released well before my iMac DV+.
OS X will boot from FireWire drives and will support them natively. OS X public beta however didn't include this feature yet - the final version will.
Most likely a change in Firewire 2.7 is causing it. It may have been a "bug fix", as I said I don't believe firewire drives are supposed to be bootable...
Yes, this is possible, but then Apple must be aware of this problem, since there are many people that use FireWire drives (and also boot from them). Up to now, I haven't been able to find something about this problem in the TIL. I was hoping, someone knew more about this problem and possibly had a work-around...
scl
|
|
|
| |
|
|
|
|
|
|
|
Simon C. Leemann
|
|
OK, I found the solution and thought that I'd post it in case anybody is having similar difficulties.
The firewire drive seemed to be fragmented pretty much, so that the boot-selected system folder was spread over almost the whole disk (20GB). Then I recalled that there was some kind of silly problem, that OS 9.1 couldn't boot if the system was not in the first 8 GB of a volume. So I defragmented my firewire disk, so that the system was placed at the beginning of the volume. I rebooted and everything was fine.
I guess this goes to show that if you want to be able to ALWAYS boot from a volume (no matter how fragmented it is), it has to be <8GB.
scl
|
|
|
| |
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Feb 2001
Location: Riga
Status:
Offline
|
|
>silly problem, that OS 9.1 couldn't boot if the system was not in the first 8 GB of a volume
Win NT and Win2K as well as some linux loaders has that problem you are the first one that Mac os does have that as well.
The problem is tha PC ("IBM comatible" aka "win box") bios rom in most systems is unable TO READ hard drives beyond 8 GB limit (thus win98 does poorly with large drives as well)
More probably was some hard drive format problem that was fixed by defragging.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
