Stuck in a loop!

[KenB]

Hi Labi

 

"convert GPT to MBR"

Don't do this yet please.

The software has located a more up-to-date version of a Master Boot Record on your system.

GPT [ GUID Partition Table ] is often used with UEFI which, if I remember, if the type of "BIOS" that you have.

 

If we do decide to go with it then you would need to select Win 8.1 - i.e. the OS that is on E: partition.

 

I am off out now [ dentist !! ] I will pick this up when I get back :)

[KenB]

Hi Labi,

 

I don't really want to go down the route of converting to MBR if we can avoid it as I am not sure that GPT / MBR is the problem.

Rebuilding the MBR is a bit different from changing the system completely.

 

The original problem arose when you ran chkdsk /r

We managed to run this on E: earlier and this solved the RAW problem.

 

We tried sfc /scannow /offwindir=e:\windows etc earlier and the system didn't like it.

 

Go back to an elevated command prompt [ Administrator ] please.

Now type in .... sfc /scannow /offwindir=e:\windows

 

If e:\windows doesn't work try sfc /scannow /offwindir=f:\windows

I read somewhere that the system sees d: for c: ....... f: for e: etc - not sure about this but it can't do any harm.

 

To check - at the command prompt type ..... notepad .....Enter

Notepad will open.

Go to "File" > "Open" ......... you should see your drives etc there.

 

If you get nowhere try this:

At the command prompt type ......... dir e:\windows ............ Enter

You should get a list of the directories/folders etc held in "Windows" on E:

 

Let's see if it will perform this operation.

 

=====================

try this too

 

from elevated command prompt:

 

Type in E: ........Enter

wmic ........Enter

diskdrive get status .........Enter

 

This should check the condition of the drive.

Edited May 8, 2018 by KenB

[Labi]

Hi Ken

A couple of pics which I can't make much sense of...do they help at all?

 

Labi.

[Labi]

Update: sorry, missed your last point above.

 

"Status" ok. ok. !

[KenB]

Status OK - this is good.

 

Your first pic showing Directory information is good - at lease E:\windows is shown to exist :)

 

Your second pic [ the sfc /scannow ] the command hasn't run [ again ]

All of the "results" are actually giving the various options available with that command.

 

This is frustrating. [ for both of us :) ]

 

I am wondering if running it from Win7 on a Win 8.1 OS is the cause of the problem.

 

I doubt very much if this will work but give it a try

 

Elevated Command Prompt again ...

 

Type in E: ....hit enter

Type sfc /scannow

[Labi]

Ken

Some good news: the scan was successful.

Verdict: "Windows resource protection found corrupt files but was unable to fix some of them".

"Details are included in the CBS.Log" etc etc.

 

(I got the same message some time ago when I ran a scan of C: drive on this machine. It still works ok...)

 

Labi.

[KenB]

Well - I am surprised ............ something actually worked :)

 

We have managed to run Chkdsk and SFC on the E: partition.

Hopefully this will have corrected whatever was wrong.

 

Time to return the drive to its home and see if it will boot up.

 

Fingers crossed :)

 

EDIT - I wonder if Win 8.1 will boot up if you shut down the Win7 machine and attempt to boot up from the caddy

Assuming that the BIOS is set up to boot from the USB port.

 

Some systems give a message "Press any key to boot from external device" ...... watch for this.

Edited May 9, 2018 by KenB

[Labi]

Ken

I don't recollect running Chkdsk on E:.....?

 

Win7 machine still doesn't open OS 8.1 via USB connection, although USB is top

of Boot order in BIOS.

 

Is there a chance that a more in-depth scan/repair Command would work now...?

Labi.

[KenB]

I don't recollect running Chkdsk on E:

We did.

See posts #75 - #77

This was when we fixed the RAW drive so that you could actually view the contents.

 

Win7 machine still doesn't open OS 8.1 via USB connection

I was hoping that we would be able to boot it up now.

 

Please try the sfc /scannow process again on E: [ see previous post ]

Sometimes running SFC a second time will find and fix problems missed on the first scan.

[Labi]

Ken

Have run the SFC scan again with the same result: "Windows resource protection found corrupt files" etc...

Tried restarting Win 7 with USB connected but still opens with installed OS system.

Also tried Asus with HD attached via USB. May not have correct BIOS settings in place, though...?

 

Labi.

[KenB]

Hi Labi

 

Also tried Asus with HD attached via USB.

Did it boot into the BIOS when you tried this ?

 

There is little else to try from here.

I think it is time to put it back in its original home and see what happens.

Your ASUS machine wasn't set up to boot from USB if I remember correctly.

 

Let's hope we have done enough to allow it to boot up.

[Labi]

Ken

Asus boots to BIOS with/without HD connected via USB.

 

Do I need to reset BIOS for Asus to boot normally with HD reinstated?

Can I erase partition F: at some point as it was obviously created in error?

Labi.

[Labi]

Update: HD back in Asus. Booting straight to BIOS.

 

Will altering BIOS settings make any difference...?

 

Labi.

[KenB]

HD back in Asus. Booting straight to BIOS.

:(

Because you are booting direct into the BIOS [ and it did without the drive in place ] I am wondering if the system is seeing the HDD at all.

 

When you are in the BIOS - take a look [ probably on the main page ]

Is the hard drive listed?

It could show something like Hdd/SSD Hitachi HTS 47550a9e384

Hdd = Hard Disk Drive

[Labi]

Ken

 

No sign of HD in BIOS.

Is there a reliable 'fix' for GPT partition available...?

Labi.

[KenB]

Hi Labi,

 

No sign of HD in BIOS.

 

Can you get at the CMOS battery?

It is disk-shaped and may be in a cover

 

Follow the wires and unplug it - leave it for 30 seconds or so - plug it back in.

This will reset the BIOS to defaults so that we can try again to boot up.

 

If you can access the battery it may be worth replacing it. They are quite cheap.

Usually CR2032 as above.

[Labi]

Ken

Still no sign of HD in BIOS - after disconnecting battery lead for a minute or so,

unless the reference under 'Security' to - "HD password................not installed"

is actually recognising that the HD is in place...?

 

After so many forced shutdowns maybe the OS/boot system is corrupted somehow...?

Labi.

[KenB]

unless the reference under 'Security' to - "HD password................not installed"

is actually recognising that the HD is in place...?

No - this is simply a password option.

 

Still no sign of HD in BIOS

Does it say "None" or is it just not showing anything at all?

 

The fact that the Hard Drive is not showing in the BIOS is a concern - although some are limited with the information they show.

 

I know we have tried this previously .....

When in the BIOS enable CSM > Save and Exit > try booting again.

If no go - disable CSM again.

 

[ CSM is a compatibility mode for older BIOS systems ]

 

==============

 

Switch off - then hold down F9 and switch on again.

If you can get to the Recovery screen we can go from there.

 

==============

 

If F9 is no go ...

Switch on - then power off immediately.

Do this 3 - 5 times.

The machine should go into automatic repair mode.

 

This should help

 

 

If you can get this far try the Startup Repair option first.

This is for Win10 - hoping yours is similar.

[Labi]

Ken

Sorry to report patient not responding to treatment.

Have we reached the 'DNR' moment...?

Perhaps at this point it's worth considering either taking a chance

and converting GPT to MBR(??) - or, giving up on the HD and reformatting it

with a view to reloading Windows. Does that work...?

Labi.

[KenB]

Does it say "None" or is it just not showing anything at all?

In the BIOS - does it actually say "None"

 

If the system isn't seeing the hard-drive it will not matter what we put on by way of OS - it still will not be seen.

 

You don't have a CDROM drive - is this correct?

 

Do you have a USB port on the Asus Win8.1 machine ?

[Labi]

Ken

No reference to the HD whatsoever in BIOS.

No CD ROM built-in to ASUS.

Yes: 2 x ports marked "SS" which take a USB cable/plug.

 

Labi.

[KenB]

Hi Labi

 

I am tempted to try converting GPT to MBR first.

At least we will know that the MBR is OK.

 

We must be close to getting it to boot up - something is corrupt somewhere.

 

We will need to alter the BIOS on the Asus machine after we have converted to MBR.

 

I assume that you don't have Windows on a USB Memory Stick ?

If not - Ubuntu Mint may be a good second best.

[Labi]

Hi Ken

Thanks for sticking with this even over the weekend!

After running the programme to change GPT to MBR, I eventually got

a message asking me to confirm I wanted to "Reload disk information" - Yes/No.

Choosing "Yes" meant the current operation would be cancelled

but choosing "No" seemed to imply that HD data would be lost or overwritten.

I chose "Yes" and it seems the operation to convert to MBR was cancelled.

 

If I run it again and choose "No",will that wipe the disc of files/programmes/data etc

- but preserve the OS/windows...?

Not much helpful guidance with the EaseUs software...

 

Labi.

[KenB]

Hi Labi,

It seems that we are stuck between a rock and a hard place !!

 

If I run it again and choose "No",will that wipe the disc of files/programmes/data etc

It seems that you will lose more than a bit of data !!

 

Before you convert a disk, be sure to backup anything on the GPT disk that you want to convert to MBR disk. Converting the disk requires that all partitions and volumes are deleted on the disk first.

I was under the impression that this could be done with no loss of data - sorry - it seems I was wrong.

Take a look here:

How to free convert GPT disk to MBR disk without any data loss?

 

We will have to see if there is an option to rebuild the GPT - but I am sceptical as we rae now on Win7.

 

I will get back to you.

[KenB]

Something we should have tried earlier ......

 

Go to command prompt [ Administrator ]

Type in ...... E: ......... Enter

Type in ....... rstrui.exe ........Enter

 

The System Restore window should pop up.

Follow the prompts to this page ...

Select a date prior to the start of your problem [your first post was on 17th March ]

 

You can put a tick in the box " Show more ....." for further dates.

Then click "Next" etc etc.

 

This will revert the system settings to a date when the machine was working - [ hopefully ]