New Posts  All Forums:Forum Nav:

Raid 0-disc array problem

post #1 of 13
1/3/04 at 7:38pm
Thread Starter 
I have been using my 8890 for two months - problem free...that is until I was capturing some video and something made a loud whinning sound and I shut down my computer (without recognizing the source) as it did not sound good.

When I attempted to reboot, I received the message: "problem is detected with array 1" ... the next screen read "no operating system". I have been unable to boot and have not reinstalled windows xp pro from the recovery disc for fear of losing two months of data, if it is not already gone.

I am running raid 0 with 3-60gb hard drives which were installed by SAGER. I am looking for some direction, that is, what to do and what not to do, to recover my data, if possible, and return to normal.
Reply
Reply
post #2 of 13
1/3/04 at 9:43pm
Bad bad bad I am afraid.

Ok, my recommendation - do you have a spare hard disk that you could insert into the third disk bay? (You said you had 3 already - does the third have anything useful on it?). If you can insert a third disk, I would put a copy of XP onto that and boot it. At least that way you have something that is stable (just thinking about it that is such a good idea I think I will do that myself as a spare - anyway).

When you power up do you still get the whining sound or has that stopped? The whining sound is a disk bearing normally (if the sound was more like fingers going across a chalk board it is a head crash and a quick death is the only solution on your part ).

I am not a Windows expert on file recovery (Computer Potato seems to have better knowledge about that btw - try a PM to him). If one of your bearings has gone it may have only caused minor corruption on part of the file system as it went down.

What you need to do is to find out if the failing disk is still operational at least until you can get the data off the RAID set onto a backup - you will obviously need some form of backup storage in order to copy your data out.

Sorry I can't offer any better help. If it was a Unix box I could but windows filesystems are n00bies to me.

Another question - is your data on a seperate partition from the operating system? If it is then you might get away with just restoring the OS. Bottom line is still going to be to find out if the disk that sounded funny is still operational.
Reply
Reply
post #3 of 13
1/3/04 at 10:05pm
Dennis, if you do manage to get a copy of XP loaded also grab this AIDA program. It might help sorting out your disk status.
Link to posting on AIDA
Reply
Reply
post #4 of 13
1/4/04 at 2:59am
Thread Starter 
Aussie - Thanks for your fast response.

The loud whinning sound (sounded electronic rather than mechanical) stopped when I shut the computer down. It has not returned and neither has windows. Windows and my data were on the same disk. With reference to the third drive I am not sure how the disks were configured under Raid 0...I will talk to a tech at Sager on Monday AM and consider your suggestions. I will keep you posted.

When I reinstall windows, I will definately download the AIDA program...it sounds interesting.
Reply
Reply
post #5 of 13
1/4/04 at 3:11am
From what I know about the 8890 the third disk is not part of the RAID array. Only the disk under the touchpad and the disk next to the DVD/CD are.

Basically booting of a third disk may be the only way to test your system without destroying any data (if it is recoverable at all ). Keep us posted, I am interested to find out what the cause is.
Reply
Reply
post #6 of 13
1/5/04 at 1:59pm
Thread Starter 

Happy ending

Aussie

After working with a helpful senior techie at Sager, we deleted the problem RAID array and configured a new array (same RAID 0). Unbelieveable!! Windows booted up and all data was intact.

I took your advice and installed windows on the third drive and will now use this drive to backup my data (in addition to DVD and external hard drive backup). This will also make windows available to boot up in the 3rd drive if the RAID array fails again. I also downloaded the your recommended AIDA program. Awesome utility.

Thanks for your input

Reply
Reply
post #7 of 13
1/5/04 at 7:08pm
Good to hear Dennis.
Could you expand a bit on the steps that the Sager tech went thru.
I gather the problem was in the RAID driver config rather than a faulty disk (although the source of the noise bothers me ).
So what were the exact steps?
Obviously you had to get to a point were you could access the RAID setup utility - from memory you get to that by pressing one of the Function keys during boot up.

The more specific you can be the better because I will assimilate your unique characteristics into the collective aussie 8890 review .
Reply
Reply
post #8 of 13
1/5/04 at 9:42pm
Thread Starter 

Surreal Experience

The problem:
When I powered up after the traumatic experience (internal screaming noise), there appeared a black screen with a flashing message...."problem detected with array1". That screen changed a few seconds later to a screen that read "no operating system found"....which was about when I hit the ground.

The cure:
After the next startup, as the "problem with array 1" message flashes, you are prompted to press Contr +F which leads to a menu for FAST BUILD UTILITY 2.01 with choices 1 to 5. Choice 4 is --delete array-- which we did. Then back to choice 1 which is --Auto setup. We setup a new raid which we set up, but did not initialize. If you initialize, you will lose all your data. After saving, exiting and rebooting, windows magically appeared with all data intact.

Hopefully this will helpful to anyone that has the same experience.
Reply
Reply
post #9 of 13
1/6/04 at 4:06am
Thanks Dennis, I will put it into my review - glad to hear your data came back. I would expect you will be backing up a bit more often then?

Was there any indication from the Sager tech about the source of the noise and/or what the cause was?
Reply
Reply
post #10 of 13
1/6/04 at 1:51pm
Thread Starter 
The Sager rep mentioned that my description sounded similar to two previous instances that he was aware of. He assumed that the sound was coming from the hard drive, but could not be positive without inspecting them.
Reply
Reply
post #11 of 13
1/6/04 at 6:32pm
I've had the EXACT same problem with my 8890....happens once every couple of weeks or so, though I use my machine heavily.

In fact, I pm'd you the message with the same solution Sager gave you.

It is disturbing that something is causing the boot sector to get trashed every now and then, and an accompanying reboot.

Which BIOS do you have? Perhaps that's the source of the problem.

I'll look mine up and report it here as well.
Reply
Reply
post #12 of 13
1/6/04 at 9:38pm
Maybe it was just the drive getting all confused and just curling up into a foetal position .

Thanks for the feedback, I will put it into my review .
Reply
Reply
post #13 of 13
1/6/04 at 9:52pm
Quote:
Originally Posted by SagerMadness
It is disturbing that something is causing the boot sector to get trashed every now and then, and an accompanying reboot.

Which BIOS do you have? Perhaps that's the source of the problem.
Would it be the BIOS or is something in Windows screwing up? Is it the boot sector that is being trashed, because from what Dennis indicated you don't have to actually reinstall any boot stuff, all it requires is the RAID config to be reconstructed.

Hold on - I just realised of course - it has to be something to do with the boot sector because that is where the RAID driver and config is stored so when the system boots it reads that out in order to initialise the RAID controller and load the rest of the system in.

So the question then becomes what is playing with the boot sector and/or raid configs. Does Windows XP scribble stuff down in the boot sector before it shuts down?

However you guys seem to indicate that the initial problem occurs whilst you are using the system not directly after a normal shutdown, am I correct in this?
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home