Darren New wrote:
> 
> I think it means you're screwed, since you didn't have a mirrored disk
> (yet).
> 

It can't be known by us (it could by Andrew). Let's say we have disk 0
and disk 1. Disk 1 dies and gets replaced by disk 2, so we'll have disks
0 and 2. Now we'll get the error message. IF the message comes for disk
0, we're screwed, if the messages comes for disk 2, we're not screwed,
but running on one disk again (and taking one hell of backups right away
- again, to stay at the latest point of data).

-- 
Eero "Aero" Ahonen
   http://www.zbxt.net
      aer### [at] removethiszbxtnetinvalid

Post a reply to this message

Darren New wrote:
> Orchid XP v7 wrote:
>> More importantly, DOESN'T THE DISK CONTROLLER KNOW??
> 
> Not necessarily. You've never heard of software raid?

Yes. But this isn't. This is a hardware RAID solution, and the message 
is from the software that talks to the RAID controller.

>> As it happens, I got this error while rebuilding a RAID-1 set. So... 
>> does this mean the data was recovered or not?
> 
> I think it means you're screwed, since you didn't have a mirrored disk 
> (yet).

OK. Cool. Now... if there's a problem with the disk, why wasn't it 
reported sooner? (Like, while there were still 2 working disks?)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

Orchid XP v7 wrote:
> 
> OK. Cool. Now... if there's a problem with the disk, why wasn't it
> reported sooner? (Like, while there were still 2 working disks?)
> 

If there was 2 working disks earlier, why was the controller rebuilding
the array?

-- 
Eero "Aero" Ahonen
   http://www.zbxt.net
      aer### [at] removethiszbxtnetinvalid

Post a reply to this message

Eero Ahonen wrote:
> Orchid XP v7 wrote:
>> OK. Cool. Now... if there's a problem with the disk, why wasn't it
>> reported sooner? (Like, while there were still 2 working disks?)
>>
> 
> If there was 2 working disks earlier, why was the controller rebuilding
> the array?

Because one disk stopped working.

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

Orchid XP v7 wrote:
> Eero Ahonen wrote:
>> Orchid XP v7 wrote:
>>> OK. Cool. Now... if there's a problem with the disk, why wasn't it
>>> reported sooner? (Like, while there were still 2 working disks?)
>>>
>>
>> If there was 2 working disks earlier, why was the controller rebuilding
>> the array?
> 
> Because one disk stopped working.
> 

And it was replaced, right, 'cause the controller was rebuilding the
array? While rebuilding either A) one of the disks (the old with data or
the new, which replaced the broken one) broke down or B) the new disk
was already broken. In either case it's impossible to report the failure
before it exists.

-- 
Eero "Aero" Ahonen
   http://www.zbxt.net
      aer### [at] removethiszbxtnetinvalid

Post a reply to this message

> My favourite is still the most classical Windows error message, which
> says "Unexpected error".
>
 My favorite is the classical Win NT error message:

"Offending Command"

how hilarious is that.

Hildur

Post a reply to this message

>> My favourite is still the most classical Windows error message, which
>> says "Unexpected error".
>>
>  My favorite is the classical Win NT error message:
> 
> "Offending Command"
> 
> how hilarious is that.
> 

There is a "catastrophic failure" message on Office.

Post a reply to this message

>>  My favorite is the classical Win NT error message:
>>
>> "Offending Command"
>>
>> how hilarious is that.
>>
> 
> There is a "catastrophic failure" message on Office.

I'm told various versions of the Linux kernel had absurd messages like 
"Penguin on the SCSI bus" and "The printer is on fire"...

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

> I'm told various versions of the Linux kernel had absurd messages like 
> "Penguin on the SCSI bus" and "The printer is on fire"...
> 

http://upload.wikimedia.org/wikipedia/commons/6/6a/Linux-2.6-oops-parisc.jpg


http://en.wikipedia.org/wiki/Hurd#Error_messages

Post a reply to this message

>> I'm told various versions of the Linux kernel had absurd messages like 
>> "Penguin on the SCSI bus" and "The printer is on fire"...

"The printer is on fire" apparently meaning a [very] unexpected response 
received from the printer. (The kernel has no idea what on earth it 
means, hence the daft message.)

The SCSI bug error is similar.

I have no recollection of where I got these gems from.

> http://upload.wikimedia.org/wikipedia/commons/6/6a/Linux-2.6-oops-parisc.jpg 

Nice ASCII art. :-P

> http://en.wikipedia.org/wiki/Hurd#Error_messages

LMAO @ EIEI0

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message