search

MaxTyutyunnikov / grub4dos-chenall

Automatically exported from code.google.com/p/grub4dos-chenall
0 stars 0 forks source link

grldr not found when booting an USB disk connected to an ASUS P5KPL-VM motherboard #115

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Prepare a NTFS formatted "Toshiba STOR.E Basics 1 TB" USB harddisk with 
grldr and  menu.lst
2. Boot it on a ASUS P5KPL-VM board (AMI BIOS: SM BIOS 2.5, P5KPL-VM 1003 BIOS)

What is the expected output? What do you see instead?
Expect to boot grldr (as same disk boots correctly into (hd0,0)/menu.lst on 
other computers) but with this ASUS P5KPL-VM board there is only:
Try (hd0,0): NTFS5: 2
Try (hd0,1): INVALID OR NUL
Try (hd0,2): INVALID OR NUL
Try (hd0,3): INVALID OR NUL
Can not find GRLDR
(By the way what does this "NTFS5: 2" mean?)

What version of the product are you using? On what operating system?
Any

Please provide any additional information below.
The mentioned USB harddisk did already boot on this ASUS P5KPL-VM with ancient 
GRUB4DOS versions (like grub4dos-0.4.4-2009-06-21), but there had always been 
file not found errors (error 15) with mapping ISO files. So I installed later 
versions and suddenly the disk didn't boot any longer as for "Can not find 
GRLDR". This even remained with returning to previously running GRUB4DOS 
versions.
The missing file or grldr issue seems to depend on where certain files are 
located in the disk's master file table.

A Windows 7 OS's chkdsk doesn't find any file system errors on this disk and 
grldr and all other missing files are correctly shown on the disk.

With newer versions of GRUB4DOS (exactly any greater than 
grub4dos-0.4.4-2009-02-01) there are file not found errors (error 15) also on a 
FAT32 formatted USB stick (2 GB) with file related commands like map, kernel... 
if booting from this ASUS P5KPL-VM board. Same as the USB harddisk the stick 
perfectly boots on other computers.
grub4dos-0.4.4-2009-02-01 and previous versions do map the concerned ISO files 
correctly even on this specific ASUS board, but the missing grldr issue on the 
Toshiba USB harddisk even remains with this ancient GRUB4DOS versions.

A Windows 7 OS installed on a SATA built in 64 GB SSD gets perfectly booted by 
this ASUS P5KPL-VM board and all later USB related read and write operations 
with the mentioned USB harddisk and stick work flawlessly.

Original issue reported on code.google.com by LeonH1...@googlemail.com on 14 Feb 2013 at 10:26

GoogleCodeExporter commented 9 years ago 
It seems the buggy ASUS BIOS cannot access files at big sector address numbers.

You may re-fdisk and re-format your USB storage. Copy grldr and menu.lst first, 
so they could be placed in lower sector addresses and hopefully could be 
accessible by the buggy ASUS BIOS. 

You may also try installing wee63.mbr onto the MBR and let it search for GRLDR. 
You may download weesetup here:

https://code.google.com/p/grubutils/downloads/list

The source code for WEE is here:

https://code.google.com/p/grubutils/source/browse/#svn%2Fgrubutils%2Fwee

The source code for WEESETUP is here:

https://code.google.com/p/grubutils/source/browse/#svn%2Fgrubutils%2Fweesetup

It also contains the latest binary build of wee63.mbr.

It seems the problem is not caused by grub4dos, but by your buggy BIOS. So we 
might not be able to solve it by fixing some bugs inside grub4dos(since there 
could be nothing wrong with grub4dos). You might have to solve the problem by 
yourself in one way or two as mentioned above. And this issue will be closed 
later.

Original comment by tinyb...@gmail.com on 15 Feb 2013 at 8:35

GoogleCodeExporter commented 9 years ago 
You might also want to format your USB storage with the fbinstTool and get more 
success on booting.

Here are some other ways you might want to try:

Boot to DOS, syslinux, NTLDR, BOOTMGR as an initial boot, and then, boot 
grub4dos secondly.

Original comment by tinyb...@gmail.com on 15 Feb 2013 at 8:51

GoogleCodeExporter commented 9 years ago 
Thank you very much for the extremely fast response!

I will try the wee63.mbr and the BOOTMGR initial boot aproaches.

Original comment by LeonH1...@googlemail.com on 15 Feb 2013 at 9:31

GoogleCodeExporter commented 9 years ago

Original comment by tinyb...@gmail.com on 1 Mar 2013 at 3:34