🚀 go-pugleaf

Neil Barker <neil@nemesis.nu> verbally sodomised  in
news:MPG.202c5baa71653c3d989a93@127.0.0.1: 

> In article <omqwh.4467$9S5.3161@text.news.blueyonder.co.uk>, 
> l.d.wilmer@NOJUNKMAILblueyonder.co.uk says...
>> Advice please - son recently passed me his old PC system, based on
>> NF7-S with 1 Gb of dual channel RAM running at 400, and 2 WD 40Gbs in a
>> Raid 0 array.
>> 
>> Fast - very fast for the modest 2Gb cpu onboard. But I'm had a lot of 
>> problems,
>> "Windows XP could not start because the following file is missing or 
>> corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
>> etc several times.
>> Have undone all overclocking, but it just happened again on a boot
>> failure. 
> 
> Based on previous experience, you may be looking at the wrong thing for 
> a solution.
> 
> I had a PC with a RAID 1 array and I got this same form of error 
> message once on boot-up, after the machine had been switched off for 
> about a week. After some digging around and investigation, I discovered 
> that the RAID array was classed as degraded - it was only operating on 
> one of the two drives.
> 
> What had actually happened was that the CMOS had lost its RAID 
> configuration (a simple controler on/off) and had reverted to using 
> just one drive.
> 
> The cure was to remove the drive from the machine and then boot-up - it 
> would then do so, flagging up a degraded RAID system. I then shut-down 
> and re-introduced the drive I had taken out. The system was the booted-
> up again and immediately on boot, my system alerted me to a degraded 
> RAID system and offered to rebuild the drive with the contents of the 
> mirror. After about 10 minutes, things were all back to normal.
> 
> Hence, first of all, go into your CMOS memory and check to make sure 
> your system is not just configured accidentally for non-RAID operation.
> 

Done any email RAIDing lately, Ballaty?

-- 
Phil Kyle�  

T    
h i  
i s  
s   l 
  f i l
S o n o
i u e n
g r s g