Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.
This was surprising since Vista was on another E Drive inside and not used since first upgraded to W/7
McAfee
During online activity, suddenly again the old BSOD from which I could not recover and all the stuff posted before applies.
Was advise to remove all but the one drive on which I'm planning to install Windows 7 again, which I'd love to avoid
Many of the LIVE analyses I've read in logs, etc. find 3 WD drives but don't all find the SCSI drives.
I hasten to add that using the Knoppix Live DVD and File Manager lets me view content on all drives, which leads me to believe that the drives are OK. Maybe I can get to an elevated DOS prompt to run chkdsk /f or scandisk if that can help. ????
Wonder if I were to remove only that WD drive and try to repair again if it would work to save my recent installations. What do you think? Hope?
something in all my recovery efforts corrupted all kinds of boot files that are required
Using either Knoppix Adriane Live or UBCD tools to analyse the drives and content has worked for all the drives, but the content seems to vary, depending on what tools I use. For one of the partitions on the WD drive where E and F reside (E partition had Vista, F partition data files)... the F drive only shows System Volume Information, as is true for the other smaller WD drive, both of which had more content and only show the System Volume Information. There are 3 internal WD drives, the main new one with W7 which is 1.5 GV, one is the WD2500, data stuff and the other WD1200 has the old Vista and the two partitions above.
Other anomoly, when using the UBCD and the SeaTools to scan disks, it only showed the WD main W/7 1.5 TB drive..C drive and the two internal WD drives, none of the sCSI drives.
When you mentioned NTFS, I recall that on one of the many Startup Repair processes for Windows 7, the following were found to be root causes of boot failure and it was mfewfpk.sys reported as corrupt and repair action failed - error code = 0x2, and system restore also failed error 0x1f after an all night run and also states that ntfs.sys file corrupt but that Repair did fix this one.
How would I do this which you recommend? you can write a big file with dd and check for errors in dmesg Should I try this on all the internal drives before removing them to test?
Also when you said if you have a hardware issue, it is probably unrelated to that drive. possibly a mess with the SCSI controller working erratically. Since the strange behavior on one of the last week's processes after the Windows 7 new installation there were driver detection problems for the Adaptec driver for the IBM SCSI drives, that could be a source. But would that be likely to stop me from being able to boot Windows with all these errors and BSOD results?
And YES, thank you also for that; I understand I cannot boot from the USB drive.
I'll try updating and copying the Driver files, especially for the Adaptec Ultra 160 drivers.
First Q
Reinstall process on new drive at a reboot in the process said NTSF CHKDSK running to correct many errors in index $I30 many; then chkdsk is running through tons of RECOVERING Orphaned files. Gads, hope it's good stuff and chkdsk is able to recover the corrupted items and fix the corrupted file system.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Boot with the Windows DVD, go to repair then select "Restore using previously created system image" then point to the USB drive.
HTH,
Dan