T
Torben Zck
Hi folks,
i'm in need of help:
i've tried to execute some stuff from windowsupdate.microsoft.com to patch
my costumers w2k sp4 box. halfway the updateprocedure came up with the
message, that there were no space left on systemdrive. nethertheless,
explorer said sth about 400 megs of free space. ok, don't wory, skip that
file an d go an. then reboot and *bang* process_initiliazation_failed stop
0x6b (0xC00000102). Now i'm in trouble.
every option (last known good, safe mode and so on) leads to the same blue
screen.
don't panic, so i tried to recover from the bootcd. nope, even with the disk
the recovery isn't able to find the windows installation. then i've decided
to install a second system on the drive, but if you come to the point to
choose the partition, it shows the correct sizes of them but says something
about 'unpartioned or corrupted' (dunno the exact phrase, cause i've got
here the german version and there it says 'unpartioniert oder beschaedigt'.
here a few facts about the system: it is some of that intel-barebone
servers, 2* 1GHz pentium iii, 2 gig of ram (ECC) and a intel raid controller
SRCU31L. there are 5 18 gig hds and 2 raid5 volumes on them. (history: first
it was configured as 4 drives raid5 with a spare, later reconfigured to use
all of the drives)
i think, the partitiontable is defect in a manner that let the driver go
wild. is there any possibility to edit that table? which tool can i use? is
it possible to access the array thru bios for backup (ghost or sth like
that) ? or have i go thru hell and restore the backup? (and by the way,
loose a half days work) (ok ok, i hear ya laugh)
do you have any recommendations for the next actions?
hope, that sbd can help, thanx a lot
torben
i'm in need of help:
i've tried to execute some stuff from windowsupdate.microsoft.com to patch
my costumers w2k sp4 box. halfway the updateprocedure came up with the
message, that there were no space left on systemdrive. nethertheless,
explorer said sth about 400 megs of free space. ok, don't wory, skip that
file an d go an. then reboot and *bang* process_initiliazation_failed stop
0x6b (0xC00000102). Now i'm in trouble.
every option (last known good, safe mode and so on) leads to the same blue
screen.
don't panic, so i tried to recover from the bootcd. nope, even with the disk
the recovery isn't able to find the windows installation. then i've decided
to install a second system on the drive, but if you come to the point to
choose the partition, it shows the correct sizes of them but says something
about 'unpartioned or corrupted' (dunno the exact phrase, cause i've got
here the german version and there it says 'unpartioniert oder beschaedigt'.
here a few facts about the system: it is some of that intel-barebone
servers, 2* 1GHz pentium iii, 2 gig of ram (ECC) and a intel raid controller
SRCU31L. there are 5 18 gig hds and 2 raid5 volumes on them. (history: first
it was configured as 4 drives raid5 with a spare, later reconfigured to use
all of the drives)
i think, the partitiontable is defect in a manner that let the driver go
wild. is there any possibility to edit that table? which tool can i use? is
it possible to access the array thru bios for backup (ghost or sth like
that) ? or have i go thru hell and restore the backup? (and by the way,
loose a half days work) (ok ok, i hear ya laugh)
do you have any recommendations for the next actions?
hope, that sbd can help, thanx a lot
torben