中国DOS联盟

Previously, it was normal on IDE hard drives.

For a Lenovo branded computer, a SATA hard drive, in the BIOS it has been set as:

SATA mode : Legacy IDE

Lenovo Yangtian T5900V,

Hard drive: WD800BD

C: 40G NTFS primary partition
D: 30G NTFS
E: 3G FAT32
F: 7G FAT32 primary partition

GRUB4DOS is on drive F:

Special note: This is a one-key restore program downloaded from the internet, and it has been used for more than two months on other IDE hard drives,

Moreover, at the same time, when installing, the IDE is normal and the SATA is abnormal



This is the content of menu.lst

find --set-root /boot/grub/menu.lst
#The above command is prepared for manual loading of the menu

default 0
timeout 2

#splashimage /Boot/Grub/Splash.gz
#foreground ffff00
fontfile /Boot/Grub/Fonts.gz
#cdrom --init

title One-key restore system
map --mem /Boot/IMG/OneKeygh/ghost.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)
boot



title Boot Micro PE
chainloader /Boot/WXPE/LDRXPE
boot


title Restart the computer to restore normal boot
map --mem /Boot/img/reboot.ima (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)
boot


title Shutdown computer
halt

I want to start the one-key restore system

The result prompts:

map --mem /boot/img/onekeygh/ghost.img (fd0)

Warning: unrecognized partition table for drive 80. Please rebuild it using
a microsoft-compatible FDISK tool(err=7). Current C/H/S=16383/255/63
FAT16 BPB found with 0xEB (jmp) leading the boot sector.

Warning: BPB total_sectors(17280) is greater than the number of sectors in the
whole disk image (17220). The int13 handler will disable any read/write operations
across the image boundary. That means you will not be able to read/write sectors
(in absolute address, i.e., lba) 17220-17279, though they are logically inside your
file system.

probed C/H/S = 240/2/36, probed total sectors = 17280

floppies_orig=0, harddrives_orig=1, floppies_curr=1, harddrives_curr=1
mpa --hook
chainloader (fd0)+1
rootnoverify (fd0)

Warning: unrecognized partition table for drive 80. Please rebuild it using
a microsoft-compatible FDISK tool(err=7). Current C/H/S=16383/255/63

root

Last edited by ww111222 on 2008-4-14 at 11:19 PM ]

What is your partition situation? FAT? or NT? What's the size of the partition?

Lenovo ThinkCentre T5900V,

Hard disk: WD800BD

C: 40G NTFS
D: 30G NTFS
E: 3G FAT32
F: 7G FAT32

Last edited by ww111222 on 2008-4-14 at 11:12 PM ]

If you care a lot, just use Microsoft's fdisk and format to wipe this disk, then install grub. You can also ignore this warning.

Originally posted by Budian at 2008-4-14 11:30 PM:
If you care about it very much, just use Microsoft's fdisk and format to wipe this disk, then install grub. You can also ignore this warning.

Thanks, Master Budian,


It doesn't work,


It is not booting that IMG file now, but restarting directly,


The result is a boot loop

Could it be that because your img is based on the FAT format, and yours is in NTFS format and exceeds 32G, causing the inability to boot ghost.img (fd0)? (I'm a newbie, don't laugh at me, please)

It seems that the partition table really affected grub, you can only rebuild it. Use FDISK of Windows 98 or Windows ME to do it. It is best to use Windows ME's because Windows ME's FDISK supports partitions larger than 32G. Of course, back up all data in advance.

After entering DOS, use FDISK to do it. Pay attention not to make a mistake with the disk and destroy your other disks.

The poster encountered the so-called "bad partition table" problem, that is, Windows can recognize the partition table, but GRUB cannot recognize it. In addition to rebuilding with fdisk, you can also manually modify the partition table to repair it.

Originally posted by fujianabc at 2008-4-15 10:39:
The LZ encountered the so-called "bad partition table" problem, that is, Windows can recognize the partition table, but GRUB cannot recognize it. In addition to rebuilding with fdisk, you can also manually modify the partition table to repair it.

Are there any specific modification examples for reference?

Someone encountered a similar problem when using gghost. Under Windows, there are 3 partitions displayed, but in DOS, Ghost can only recognize 2 partitions. Later, formatting that unrecognized partition solved the problem.

Yes, try with the following method.

1. Capture the partition table (that is, one sector of the MBR), it is best to capture 63 sectors or more. Save it to a file, for example, called mymbr

2. Use bootlace mymbr to try to load the boot code of grldr into this mymbr file. At this time, because there is a problem with the partition table in mymbr, you will get an error message.

3. Manually modify the partition table in mymbr with a hex editor and save it. Of course, you need to know how to modify it. Actually, this is not easy. Generally, you can only modify the CHS values at the end of each partition in the four partition table entries, and others cannot be changed randomly.

4. Run bootlace mymbr again to see if there is an error. If there is no error, you can copy this partition table to your corresponding real hard disk. If there is still an error, you go back to step 3.

=========

Important supplement: Your hard disk should support LBA. If so, you don't need to modify it, and it won't be of much use if you do. Because for disks that support LBA, grub can run well. The problem of the building owner may be caused by the poor production of the IMG file.

Last edited by 不点 on 2008-4-15 at 11:17 AM ]

Originally posted by 不点 at 2008-4-15 11:05 AM:
Yes, try with the following method.

1. Intercept the partition table (that is, one sector of MBR), preferably intercept 63 sectors or more. Save it into a file, for example, called mymbr

2. Try with bootlace mymbr...

I have already set SATA in BIOS to IDE mode, but it still doesn't work