Post by Dariusz Piatkowski
Looks like my main boot partition on my WD VelociRaptor SATA drive took a
dump...but the real strange thing is that for some reason even as I attempt to
boot off of a maintenance partition (same drive) the boot process gets stuck
during the HPFS386 FS load.
Specifically, the HPFS386 message comes up on the screen (normal '...HPFS386
file system...' stuff), but as the scan of the 'bad' partition begins the drive
goes silent and the boot process stops right there...it will NOT go past this
step. I can listen to the drive execute various seek commands and see the HD
light flashing as the maintenance partition is scanned, but I believe the boot
stops when the bad partition is encountered.
I attempted to boot off of my emergency floppies...boot gets stuck in the same
I am going to try booting with plain HPFS (not using ACLs in my HPFS386
implementation) next...but this one has me stumped. I would have expected that
if the partition was bad it would be marked as such and skipped...so I'm quite
puzzled how a presumably bad partition is hanging the whole boot process.
I'm not sure how closely related this is...
A couple of days ago I was running WindowsXP Pro in a VPC/2 when XP
I could not switch to my eCS2.0RC6a Desktop to kill VPC/2 and trying
seemed to cause eCS to lockup as well - clock stopped, no movement in
eComCenter Activity Monitor, no response to keyboard, mouse had stopped
moving, No Ctrl-Alt-Del...
I pressed the system box Reset switch and the system failed to display
the Boot Manager after the POST.
I have 2 SATA2 drives. Disk1 is 160Gb and has volumes C: through I:
Disk2 is 80Gb and has volumes J: through L:
I was booted from L: at the time of the crash; VPC/2 is on J: with it's
disks (*.vhd files) on I:
As I could not boot from hard drive I thought Boot Manager may have
somehow got mangled so attempted to boot from eCS2.0RC7 CD. That failed
I left the system powered off while I went for a coffee and spliff - and
Having refreshed myself I had another look at the problem and, as I was
booted from Disk2 at the time of the crash I thought that maybe I could
get somewhere if I disconnected Disk2 and retried booting from eCS2.0RC7 CD.
That worked so I booted to the "Maintenance Console" and performed
chkdsks on volumes G: through I: (all JFS); volumes E: and F: are FAT16
so they had been automatically checked/corrected. Volumes C: (NTFS) and
D: (FAT32) I hoped to be able to check at a later time.
I then had a look at the disk using LVM.
As the drive had failed to display Boot Manager I deleted the existing
installation, reinstalled it and added eCS2.0RC7 (H:) to the boot menu.
I then rebooted and allowed boot from hard drive when asked by the
eCS2.0 CD. Boot Manager appeared.
Looks like the problem is with Drive2...
Fearing the worst (dead disk) I powered off the system and added Disk2
back into the mix.
I decided to boot from eCS2.0RC7 CD again - it has a "disk integrity
check" which Disk2 failed. I elected to not let eCS fix the problem
which results in the system stopping there as eCS will not continue when
it detects a disk fault that the user will not let it fix.
I rebooted from the CD but this time declined the disk integrity check
in order to see if Disk2 was accessible at all. I got to the Maintenance
Console and ran chkdsk against volumes J: through L: which worked fine;
I could now access those drives without problems.
I then ran LVM.
Disk2 showed 7Mb Free Space where I expected it to have a 7Mb Boot
Manager partition. I reinstalled Boot Manager and added L: eCS2.0Rc6a to
the boot menu.
I then rebooted the system, with the ecS CD removed, and was rewarded by
Boot Manager appearing and displaying the 2 boot options "Disk 1
eCS2.0RC7" and "Disk 2 eCS2.0RC6a".
I tested that both boot options work fine and am currently using the
RC6a installation and have been since resolving the problem so doubt it
was a hardware failure related event.
MY XP in VPC/2 installation seems to have survived intact as well.
I am not sure what caused the original problem which seemed to involve
deleting Boot Manager from Disk2 but there was a "pop under" Internet
Explorer window - ie a popup window that hides under other open windows
- that appeared in the XP VPC/2 session immediately prior to the XP
VPC/2 and then eCS lockups.
I do wonder if that had interfered with the Boot Manager on Disk2; maybe
downloading some code to wipe the 1st primary (Boot Manager) partition
As I said earlier: I'm not sure how closely related this is...