: system wont boot after zfs
I suspect a lack of an MBR could cause some BIOS implementations to
barf ..
Why?
Zeroed disks don't have that issue either.
What appears to be happening is more that raid controllers attempt
to interpret the data in the EFI label as the proprietary
hardware raid labels
I had the same thing happen to me twice on my x86 box. I installed ZFS (RaidZ)
on my enclosure with four drives and upon reboot the bios hangs upon detection
of the newly EFI'd drives. I've already RMA'd 4 drives to seagate and the new
batch was frozen as well. I was suspecting my enclosure,
On 29-Nov-06, at 9:30 AM, David Elefante wrote:
I had the same thing happen to me twice on my x86 box. I installed
ZFS (RaidZ) on my enclosure with four drives and upon reboot the
bios hangs upon detection of the newly EFI'd drives. ... This
seems to me to be a serious problem.
On 11/30/06, David Elefante [EMAIL PROTECTED] wrote:
I had the same thing happen to me twice on my x86 box. I
installed ZFS (RaidZ) on my enclosure with four drives and
upon reboot the bios hangs upon detection of the newly EFI'd
drives. I've already RMA'd 4 drives to seagate and the new
batch
This is a problem since how can anyone use ZFS on a PC??? My motherboard is a
newly minted AM2 w/
all the latest firmware. I disabled boot detection on the sata channels and
it still refuses to b
oot. I had to purchase an external SATA enclosure to fix the drives. This
seems to me to be a
I suspect a lack of an MBR could cause some BIOS implementations to
barf ..
Why?
Zeroed disks don't have that issue either.
What appears to be happening is more that raid controllers attempt
to interpret the data in the EFI label as the proprietary
hardware raid labels. At least, it seems
