99 replies to this topic

[Wonko the Sane]

Look, I don' t want to seem more grumpy than usual, but it is you that (reportedly) installed UBUNTU, so you should know where (and how exactly) you installed it.

 

Is there something you don't understand in:

 

Try on each volume (i.e. looping through n=0,1,4,5,6):
root (hd0,n)
ls
ls /boot/ <- only if "boot" is listed in the above
ls /boot/grub <- only if "grub" is listed in the above

 

You had NOT "4 local disks", you have a SINGLE disk containing 5 (five) volumes, two of which are primaries and three are logical inside extended, it is very likely that one of the two primaries was "hidden", that the second was C:\ and the other three volumes were D.\, E:\ and F:.

Still, there is seemingly nowhere a volume where an UBUNTU "install" could have been made.

Possibly you did NOT "install" it but you used it as a LiveCD, i.e. you copied a .iso of it somewhere?.

 

IF the first partition (like it seems) contains only the boot files, it is normally set to ID 27 (and not the "normal" NTFS 07, but I don' think it can make a difference, in the sense that in the worse case it would show a bootmgr error.

Since:
root (hd0,0)
ls

does list BOOTMGR, you can reboot and issue commands:

root (hd0,0)
chainloader /bootmgr
boot

What happens?

It is entirely possible that the bootmgr itself or the \boot\BCD is/are corrupted, though as said you should at least have an error generated by the bootmgr.

 

If the above does not change anything, try:

root (hd0,0)
parttype (hd0,0) 0x27
chainloader /bootmgr
boot

But as said the partition ID shouldn't be related.

 

Wonko

[Wonko the Sane]

There is something that escapes me.

In post #76 you posted that you ran commands:

root (hd0,0)
ls

and that the result was:

Boot bootmgr BOOTNXT BOOTSECT.BAK grldr System\ Volume\ Information SYSTEM~1 win7.ld

 

 

How is it possible that the chainloader command cannot find it?

 

Try again.

run:

root (hd0,0)

then type:

chainloader /

 

and press the [TAB] key

you should see the same:

Boot bootmgr BOOTNXT BOOTSECT.BAK grldr System\ Volume\ Information SYSTEM~1 win7.ld

 

continue typing one letter at the time b o o t m pressing the [TAB] key after each letter, when you will have reached the m, the line should autocomplete to  

chainloader /bootmgr

 

when it does, press the [ENTER] key.

If you still have the FILE NOT FOUND error it means that the filesystem has been somehow corrupted, and you need a Windows based repair disk or PE of some kind to check it and hopefully repair it.

 

Also you just posted you ran 

parttype (hd0,0) 0*27

but you should have run:

parttype (hd0,0) 0x27

 

* is NOT the same as x !

 

Run again the geometry (hd0) command and confirm that the the output is now 

 

drive 0*80(LBA): C/H/S=1024/255/63, Sector COunt/Size=16450560/512

Partition num: 0, active, Filesystem type is ntfs, partition type 0x27

....

 

Wonko

[Wonko the Sane]

It surely sounds like you are having a hardware issue of some kind.

 

Still, if it boots to grub4dos the issue is not that one.

 

What do you mean by "button like x", how do you write x-ray or Xerox or Xylix?

 

Try again issuing the command:

parttype (hd0,0) 0x27

using the x and NOT the *. 

You should get a message like:

Partition type for (hd0,0) set to 0x27 successfully

(if you actually run the command with 0*27, you had a message saying that it was set to 0x00, i.e. made it invisible to Windows and at risk of being overwritten)

 

Them run the geometry command and report it's output.

 

Wonko

[Wonko the Sane]

My bad.....   i was thinking "x"   was multiplication....

Yep, though 0*27 would make 0 anyway.
It is a common convention (used also in grub4dos besides on DOS/Windows) to distinguish a HEX number from a decimal one:
0x01=1
0x02=2
...
0x09=9
0x0A=10
...
0x0F=15
...
0x27=39

The value that we wanted to change is a single byte partition ID, see:
http://www.win.tue.n...on_types-1.html
which is usually expressed/represented as hex number.

 

Thanks for your help... and please tell me where to learn windows (command prompt) and linux commands...??

No prob .
About learning command line in Windows (which is one thing), Linux commands (which is another thing) and grub4dos (which is yet another thing) *anything* will do there are thousands of resources on the internet for these, for grub4dos read the guide:
http://diddy.boot-la...os/Grub4dos.htm
and here and several other pages on the same site:
http://www.rmprepusb...orials/grub4dos


Wonko

[Yvonneg98]

Can someone help me plz? I have the same problem. When i switch on my computer a black window appears and the start to shows "Fatal! Inconsistent data read from (0x80) 41910+127" several times and some other staff shows and i goes to another window that starts with grub> . I dont know what to do i dpnt have the disk bt

[Wonko the Sane]

Yep (someone can help you, hopefully) .

Can you explain/report what you did before getting into the situation you describe?

Can you explain/report what happened BEFORE? (i.e. what happened before or what is the expected result, like *say* "booting Windows 7", "booting a Linux", etc.)

Some details on your PC (desktop/laptop, disk drives in it, etc.) would also be useful.

Please consider that the more details that you can provide the more likely it is that someone will be able to assist you.

 

The "(0x80) 41910+127" is probably part of an attempt to "map" to *something" an area on first disk (0x80) at offset 41910 sectors for the length of 127 sectors.

Both the 41910 and 127 are "unusual" numbers, and it is not common that a menu.lst is made to map a hardcoded extent, so most probably you attempted to (or were tricked into) install *something*, can you remember what happened?

 

Wonko

[Yvonneg98]

My charger on the laptop doesnt work so my brother tripped of him and the laptop switched off. Thrn when i started it everything was normal and after waiting to see my desktop i only saw a black screen and this "fatal! Inconsistent data read from (0x80)...." Then it shows the grub> thats all. The laptop is dell windows 7 home premium

[Wonko the Sane]

The laptop is dell windows 7 home premium

Yes and no, meaning that not Microsoft, nor Dell install grub4dos, so *someone* must have installed grub4dos or *something* including it.

At the grub> prompt, try issuing:

cat /menu.lst

[ENTER]

and post output, the command should output to screen the contents of menu.lst, which is the main configuration file for grub4dos.

Or (if the file is not found) try:

find --set-root /menu.lst
cat /menu.lst

[ENTER]

The error in itself seems like due to some form of corruption on the hard disk, so you will likely need a bootable CD/DVD or USB to attempt to repair it, but maybe - if we can find out what the settings were - we can manage to boot to the Windows and check from there .

 

Wonko 

[Yvonneg98]

So i typed the first one and it sayis error 15: file not found.Then i typed the next one and it says the same thing.

[Wonko the Sane]

Maybe then the *whatever* uses an "embedded" menu.lst of some kind.
Can you access the hard disk?

Like:

geometry (hd0)
root (hd0,0)

Try:

find --set-root /bootmgr
chainloader /bootmgr
boot

if the default Windows 7 boot manager has not been renamed it may boot.

 

Otherwise try listing the contents (depending on the result of the geometry command above) of the partition(s):

ls (hd0,0)/
ls (hd0,1)/
...

Wonko

[Yvonneg98]

When i type geometry (hd0) it says drive 0x80(Lba): c/h/s=60802/255/63 sector count/size=976784130/512 partition num:0 active filrsystem typr is ntfs patition typr 0x07 partition :1 filesystem type is ntfs,partition typr 0x07 and partition num:2 the same like 1

[Yvonneg98]

Root (hd0,0) filesystem type is ntfs partition type 0x07 and when i try find --set-root /bootmgr it says fatal! Inconsistent data read from (0x80)41910+127 (hd0,0)

[Yvonneg98]

Ls (hd0,0)/ $attrdef $badclus $bitmap $boot $extend $logfilr $mft $mftmirr $secure $upcase $volume boot bootmgr bootsect.bak system/volume/ingormation xeonc

[Yvonneg98]

When i type ls (hd0,1) program/files/(x86)users $attrdef $badclus $bitmap $boot $extend $logfile $mft $mftmirr $recycle.bin $secure $upcase $volume $windows. ~bt programdata recovery rei securityscanner.dll ssuupdater.log system /volume/information w7p_backups windows ai_recyclebin asc_rdf lag avscanner.ini config. Msi console.log documents/and/settings found.000 found.001 found.002 founf.004 hibrrfil.sys intel msocachenetfilter2 pagrfile.sys perflogs program/files

[Wonko the Sane]

This seemingly confirms that there is an issue with the actual sectors used by the bootmgr file.

 

You seem like having the first volume being the small one that only contains the bootmgr and \boot\bcd, most probably you have the \Windows\ directory on the second volume.

Try this:
http://reboot.pro/to...s-7-unbootable/

find --set-root /windows/boot/pcat/bootmgr
chainloader --edx=0x0080 /windows/boot/pcat/bootmgr
boot

IF the "other copy" of bootmgr is accessible AND the \boot\BCD on the first volume is readable MAYBE you can boot.

 

What is needed is however to run a CHKDSK on the volume, you really need a boot CD/DVD or USB, if - by pure chance - you can boot, you need to run immediately a CHKDSK on that volume, since very likely that volume is not mounted, you will need to assign a drive letter to it via Diskpart, if you don' t know how to do that, ask before attempting to do it. 

 

Wonko

[Yvonneg98]

When i typed find --set-root /windows/boot/pcat/bootmgr it says (hd0,1) then chainloader --edx=0x0080 /windows/boot/pcat/bootmgr it says will boot ntldr from drive=0x80, partition=0x0(hidden sectors=0x800) and boot error 8:kernel must be loaded before booting.

what should i do?

Edited by Yvonneg98, 15 November 2016 - 05:42 PM.

[Wonko the Sane]

The "(hd0,1)" and the "will boot ntldr from drive=0x80, partition=0x0(hidden sectors=0x800)" are "good" signs, it means that the other copy of the bootmgr is readable OK, but *something else* is preventing the booting (the "will boot ..." should mean that the bootmgr is read as valid.

Last possibility (if for *whatever* reason the \boot\BCD in use is actually on (hd0,1) and the one in (hd0,0) is just a remain of the original install ):

find --set-root /windows/boot/pcat/bootmgr
chainloader /windows/boot/pcat/bootmgr
boot

Otherwise you really need an install/repair disk or a PE of some kind.

 

Wonko

[Yvonneg98]

When i typed chainloader /windows/boor/pcat/bootmgr will boot ntldr from drive=0x80 partition=0x1(hidden sectors=0x32800)

[Yvonneg98]

I dont have a repair disk. What can i do i have another laptop but it doesnt have cd slot?

Edited by Yvonneg98, 16 November 2016 - 09:21 AM.

[Wonko the Sane]

When i typed chainloader /windows/boor/pcat/bootmgr will boot ntldr from drive=0x80 partition=0x1(hidden sectors=0x32800)

And what happens when you follow typing "boot"?

 

 

I dont have a repair disk. What can i do i have another laptop but it doesnt have cd slot?

You can get *any* windows (7 or later) install DVD (if you have the DVD drive in your laptop) or you will need a USB key.

Cannot you borrow a Windows 7 install DVD from any friend?

Otherwise you can download a Windows iso from MS and create a bootable USB stick, though getting a Windows 7 .iso has been made stupidly difficult:
https://www.raymond....al-distributer/

(scroll down until "Download Windows 7/8.1 from The Windows 10 Download Page")

 

Please understand how the "install" disk is not suitable to actually (re-)install the OS (as your installed Windows is very likely a OEM DELL version) but can be used to attempt recovering your current system.

 

Wonko

[davidsmith150]

useful link thank you.

Regards,
David