RAID Array Disappears when Program Crashes
Moderator: Ken Berry
-
gomactrading
- Posts: 47
- Joined: Tue Dec 20, 2005 5:06 pm
RAID Array Disappears when Program Crashes
Did anyone encounter a situation when a RAID Array (IDE) can no longer be accessed after Video Studio 9.0 crashes? To make matter worse, after rebooting, the drive (RAID Array) is not even seen by OS (XP Pro). It takes a couple of reboots to bring it back. Very peculiar!
-
THoff
Videostudio as an application can't crash the RAID driver. Have you considered the reverse, namely that a problem with the RAID array or its driver may be crashing Videostudio? Another possibility is that a weak or dying PSU is unable to deliver enough current while Videostudio is rendering, which would cause a system crash and possibly RAID array corruption.
-
Terry Stetler
- Posts: 973
- Joined: Thu Mar 17, 2005 3:34 pm
- Location: Westland, Michigan USA
The latter is quite possible.
It's also possible that his CPU is overheating from either dust collecting on the cooler fins, a weak fan or the heat compound between the CPU and fins deteriorating. This is a particular problem with Intel and AMD AthlonXP chips. Athlon64's run much cooler and the compound lasts longer.
A flaky mainboard can also cause this problem. In fact I just replaced one a few months ago for exactly this reason. First the RAID and audio cards started getting flakey with the RAID being unstable and some I/O's on the sound card getting noisy. Next major software lost stability then the whole mainboard went POOF. Took a couple of weeks or so and swapping in a new one fixed all the systems ills.
Dr. Mordrid
It's also possible that his CPU is overheating from either dust collecting on the cooler fins, a weak fan or the heat compound between the CPU and fins deteriorating. This is a particular problem with Intel and AMD AthlonXP chips. Athlon64's run much cooler and the compound lasts longer.
A flaky mainboard can also cause this problem. In fact I just replaced one a few months ago for exactly this reason. First the RAID and audio cards started getting flakey with the RAID being unstable and some I/O's on the sound card getting noisy. Next major software lost stability then the whole mainboard went POOF. Took a couple of weeks or so and swapping in a new one fixed all the systems ills.
Dr. Mordrid
Terry Stetler
-
gomactrading
- Posts: 47
- Joined: Tue Dec 20, 2005 5:06 pm
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
If your computer 'Hard Locks" then the RAID array is still in an open state and probable corruption.
Usually you can rebuild the array using the BIOS feature (be very careful not to delete the array).
Use the XP "Disk Manager" to see what's up with the array.
You probably can re-initialize it in manager and scandisk it.
Hope this helps,
MD
Usually you can rebuild the array using the BIOS feature (be very careful not to delete the array).
Use the XP "Disk Manager" to see what's up with the array.
You probably can re-initialize it in manager and scandisk it.
Hope this helps,
MD
You should check your Software and System logs to see if there is an error message, might give you some indication of your problem.
I had a problem with a Promise controller and a hard drive. The computer would slow down and lockup. Found out the controller thought the hard drive had bad sectors and indicated in the system log the promise driver was out of date. When I rebooted the controller BIOS would not find the drive, it took a complete power off and restart to get the hard drive to show up. I ended up changing the hard drive and not having problems so far. Try running ChKDSK and reboot the computer to see if there is any problems with your partition/file system on the array.
I had a problem with a Promise controller and a hard drive. The computer would slow down and lockup. Found out the controller thought the hard drive had bad sectors and indicated in the system log the promise driver was out of date. When I rebooted the controller BIOS would not find the drive, it took a complete power off and restart to get the hard drive to show up. I ended up changing the hard drive and not having problems so far. Try running ChKDSK and reboot the computer to see if there is any problems with your partition/file system on the array.