Printable View
I have a Windows 2000 Pro system on my notebook which fails to boot. Using Koppix 3.3 I can read the whole of my hard drive and copied relevant files through the network to my PC.
What I would now like to do is repair my original boot problem.
In Koppix when I take the fsck /mnt/hda1 command I get the error message fsck.ntfs not found message.
Any suggestions?
:roll:
I think this is saying that the fsck command does not know how to check an NTFS filesystem - in other words it cannot find a helper program called fsck.nfts whose job it would be to do the check.
This does not surprise me greatly, as NTFS write capability is still quite experimental, and something like a file system check would need quite in-depth knowledge of the filesystem - something that MS just won't tell anyone.
I think that in order to solve your boot problem you are going to have know what is wrong with it so that you can manually fix it.
tearinghairout is absolutely right. After all, windows does not come with the tools to let you view -let alone fix - unix filesystems either, does it ? Google for "windows 2000 recovery console". Or take the plunge and install linux on that laptop of yours ;-)
In what way does Win2K fail to boot? Any error messages?
Error Message is:
Boot up starts, does some disk activity and goes into the starting windows screen with the rolling scroll across the bottom of the screen then halts with a blue screen stating INACCESSIBLE_BOOT_DEVICE
:(
Hey
I have exactly the same problem. NTFS gone down, windows not booting, same error message, but partition readable from knoppix (files corrupt though). I haven't found a way to scan the disk for errors yet. Win2k Install CDs don't even see the partition.
G M
searching for a ntfs-reading windows boot disk
Hi chyro, it seems you're not alone and this can happen with the latest release of knoppix (or its installer). Check eg this thread. Not sure which post/advice helped in the end, but there _is_ hope ;-)
you have to get a win install disk
then you boot the disc
let the installer go to install or repair question
>repair
>select the os to repair
then
cd winnt
cd system32
fixboot + enter
this will fix your prob
regard
sounds like the captive driver is not stable enough.
Maybe this is related to the problem that has been identified when using some version of parted under some version of the 2.6 kernel? Se here. Dunno if debian/knoppix is affected, though.