SATA ntfs boot error

[Guest]

Hi got a PC that won't boot, in fact it gives an error regarding
\windows\system32\config\system not being accessible or corrupt

if only it were that simple

system setup is as follows

dual sata drives configured as striped raid array with win xp home sp2
installation on and some important data stored there.
third hdd with my documents stored
fourth hdd with some backups of installation scripts

all formatted ntfs

I've accessed the recovery console without loading the SATA drivers on and
everything works as it should apart from my inability to access the my
documents folder to try and copy it to another removable drive. I suspect
that if I removed it and connected it to another pc I would still have the
same problem. Oh obviously I can't see the raid array either which is a
problem for fixing the config error.

If I add the required sata drivers as soon as the recovery console attempts
to analyse the striped discs i get a stop error.

STOP: 0x00000024 (0x001902FA,0xF7CA6B70,0xF7CA6870,0xF744283D)
ntfs.sys - Address F744283D base at F7431000, DateStamp 3d6de5c1

This error occurs if I select reinstall windows or recovery console.

running chkdsk or any other software seems to be out of the question as I
can't get to an kind of gui or command prompt while still having access to
the sata drives.

can anyone advise on how to recover this machine, access the data or just
plain fix it???

TIA


Randalf

 

[John John]

Hi got a PC that won't boot, in fact it gives an error regarding
\windows\system32\config\system not being accessible or corrupt

if only it were that simple

system setup is as follows

dual sata drives configured as striped raid array with win xp home sp2
installation on and some important data stored there.
third hdd with my documents stored
fourth hdd with some backups of installation scripts

all formatted ntfs

I've accessed the recovery console without loading the SATA drivers on and
everything works as it should apart from my inability to access the my
documents folder to try and copy it to another removable drive. I suspect
that if I removed it and connected it to another pc I would still have the
same problem.

Probably not. By design the Recovery Console has certain security
restrictions, in the Recovery Console you can only use the following
folders:

• The root folders
• The %SystemRoot% folder and the subfolders of the Windows installation
you are currently logged on to
• The Cmdcons folder
• Removable media drives such as CD-ROM drives

NOTE: If you try to obtain access to other folders, you receive an
"Access Denied" error message. Also, while you are using the Windows
Recovery Console, you cannot copy a file from the local hard disk to a
floppy disk. You can copy a file from a floppy disk or CD-ROM to a hard
disk, and from one hard disk to another hard disk.

The above restrictions can be changed but only from the up and running
Windows installation, before the installation fails and becomes
unbootable, or after the fact only by remote registry editing. With a
Bart's PE disk or similar live cd or via a parallel installation, or by
mounting the disk to another XP installation you should be able to
access the files on the non RAID disks. The Recovery Console is a
rather clumsy tool to use to salvage files.


Oh obviously I can't see the raid array either which is a

problem for fixing the config error.

If I add the required sata drivers as soon as the recovery console attempts
to analyse the striped discs i get a stop error.

STOP: 0x00000024 (0x001902FA,0xF7CA6B70,0xF7CA6870,0xF744283D)
ntfs.sys - Address F744283D base at F7431000, DateStamp 3d6de5c1

This error occurs if I select reinstall windows or recovery console.

running chkdsk or any other software seems to be out of the question as I
can't get to an kind of gui or command prompt while still having access to
the sata drives.

can anyone advise on how to recover this machine, access the data or just
plain fix it???

What type of RAID controller is this? Is the Windows XP CD at SP2
level? There was an issue with certain RAID controllers and ntfs.sys
when trying to install Windows XP or use the Recovery Console with an
SP2 cd, apparently when using a gold cd or one with SP1 the issue was
not present or it disappeared.

John

 

[kimiraikkonen]

Have you tried "fixmbr" ?

Or set SATA HDD's in BIOS to emulate in order to be seen as "IDE" by
Windows.
There must be some setting in BIOS not to requirement of installing of
SATA drivers.

Also if possible, backup important data as connection HDD into another
machine as additional disk if you can,
then re-format it with correct File system, probably NTFS.

These can be generated more and more...

 

[Guest]

Probably not. By design the Recovery Console has certain security
restrictions, in the Recovery Console you can only use the following
folders:

• The root folders
• The %SystemRoot% folder and the subfolders of the Windows installation
you are currently logged on to
• The Cmdcons folder
• Removable media drives such as CD-ROM drives

NOTE: If you try to obtain access to other folders, you receive an
"Access Denied" error message. Also, while you are using the Windows
Recovery Console, you cannot copy a file from the local hard disk to a
floppy disk. You can copy a file from a floppy disk or CD-ROM to a hard
disk, and from one hard disk to another hard disk.

The above restrictions can be changed but only from the up and running
Windows installation, before the installation fails and becomes
unbootable, or after the fact only by remote registry editing. With a
Bart's PE disk or similar live cd or via a parallel installation, or by
mounting the disk to another XP installation you should be able to
access the files on the non RAID disks. The Recovery Console is a
rather clumsy tool to use to salvage files.

I've not heard of a barts pe disk, will have to look into that.

currently I'm trying to recover the files off the non raid disks and will
then attempt to reinstall windows onto one of those.

from there I'm going to try and copy data off the raid array

Oh obviously I can't see the raid array either which is a

What type of RAID controller is this? Is the Windows XP CD at SP2
level? There was an issue with certain RAID controllers and ntfs.sys
when trying to install Windows XP or use the Recovery Console with an
SP2 cd, apparently when using a gold cd or one with SP1 the issue was
not present or it disappeared.

John

The RAID controller is a silicon image motherboard bios, I never managed to
get it working with windows out of the box, ultimately I copied the drivers
to a floppy disc and hit the f6 key when booting up the xp installer


randalf

 

[Guest]

Have you tried "fixmbr" ?

Or set SATA HDD's in BIOS to emulate in order to be seen as "IDE" by
Windows.
There must be some setting in BIOS not to requirement of installing of
SATA drivers.

Also if possible, backup important data as connection HDD into another
machine as additional disk if you can,
then re-format it with correct File system, probably NTFS.

These can be generated more and more...

Unfortunately not on this particular mobo

 

[neil]

If you have been able to access the recovery console have you considered a
repair install.
http://michaelstevenstech.com/XPrepairinstall.htm

Neil

 

[Guest]

Sorry

no access to the recovery console, at least if I want to see the boot drive(s)

 

[thecreator]

Hi Randalf72,

If you installed Windows XP Home Edition Service Pack 2 on a SATA Hard
Drive, check the boot order in your Computer BIOS for the Hard Drives, Boot
Order.

You have a regular Boot Order of Floppy, CD then Hard Drive. But if you
have Multiple Hard Drives, it should give you the option of which Hard Drive
to boot from first.

If you moved your Hard Drives physically in the Computer or have changed
the default order in Computer BIOS to a different order, you will have a
Boot Problem.

Example of what it looks like from my own. I dual-boot between Windows
Vista and Windows XP Home Edition:
;
;Warning: Boot.ini is used on Windows XP and earlier operating systems.
;Warning: Use BCDEDIT.exe to modify Windows Vista boot options.
;
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home
Edition" /FASTDETECT /NOEXECUTE=OPTIN


Look at this portion on your own system:
multi(0)disk(0)rdisk(0)partition(2).

This is probably your problem. I have a SATA Hard Drive on a different
computer, but I don't use Raid configuration. I use IDE.

 

[neil]

The reason I asked if you had been able to access the recovery console is
because that should mean you have a retail Home XP disk. You did say in your
original post you had accessed the recovery console. If you have a retail
copy of XP then you should be able to carry out a repair install.
MS also have a routine for accessing a system with the error that you
describe but you would need to be able to load the SATA drivers for that and
you say you get a STOP error when you try to do that. But have a look
anyway:
http://support.microsoft.com/kb/307545/en-us

best of luck
Neil

 

[John John]

Hi Neil,

His problem is that Windows is installed on a RAID array and he has to
use the F6 method and a floppy diskette to supply the RAID drivers to
the Windows setup program. Without the RAID drivers the Windows setup
or the Recovery Console cannot see and access the RAID array. When he
supplies the drivers on floppy via the F6 method the setup gives him
BSOD with an 0x24 error in ntfs.sys and he cannot get around the BSOD,
so he cannot install Windows or use the Recovery Console on the boot volume.

I think his only hope might be to install Windows on the disk that is
not in the array then install the raid drivers to that installation and
then see if he can rebuild or bring the disk array back online and run a
chkdsk on it or copy files around as per the instructions in the article
that you mention. If that doesn't work he may have to blow the array
away and start again from scratch.

John