Brad Hill wrote:
I've seen reports of a recent Seagate firmware update
bricking drives again.
What's the output of 'zpool import' from the LiveCD?
It sounds like
ore than 1 drive is dropping off.
r...@opensolaris:~# zpool import
pool: tank
id: 16342816386332636568
state: FAULTED
I guess you could try 'zpool import -f'. This is a pretty odd status,
I think. I'm pretty sure raidz1 should survive a single disk failure.
Perhaps a more knowledgeable list member can explain.
On Sat, Jan 24, 2009 at 12:48 PM, Brad Hill wrote:
>> I've seen reports of a recent Seagate firmware
> I've seen reports of a recent Seagate firmware update
> bricking drives again.
>
> What's the output of 'zpool import' from the LiveCD?
> It sounds like
> ore than 1 drive is dropping off.
r...@opensolaris:~# zpool import
pool: tank
id: 16342816386332636568
state: FAULTED
status: The p
I've seen reports of a recent Seagate firmware update bricking drives again.
What's the output of 'zpool import' from the LiveCD? It sounds like
more than 1 drive is dropping off.
On Thu, Jan 22, 2009 at 10:52 PM, Brad Hill wrote:
>> I would get a new 1.5 TB and make sure it has the new
>> fi
> I would get a new 1.5 TB and make sure it has the new
> firmware and replace
> c6t3d0 right away - even if someone here comes up
> with a magic solution, you
> don't want to wait for another drive to fail.
The replacement disk showed up today but I'm unable to replace the one marked
UNAVAIL:
