Via grub4dos-0.4.6a (dec 2018) / tftp / pxe, I need to map a large Windows2016 «.vhd» file (about 15 GB).
The system produce the following error (I presume related to this line «map (pd)/win2016.vhd (hd1)»: Error 61: too many fragments win2016.vhd was defragmented via Sysinternal Contig, Defraggler and also MyDefragGUI.
You will find below the menu.lst used for:
pxe detect 1432 menu.lst
color blue/green yellow/red white/magenta white/magenta
timeout 10
default /default
title Windows
root (pd)
map (pd)/win2016.vhd (hd1)
map —hook
map —mem (hd1) (hd0)
map —hook
root (hd0,0)
chainloader /bootmgr
Thank you for your help!
Does it work with any other VHD files? Is it just that one file that gives the error or all files?
Can you go to the grub4dos command shell and type
blocklist (pd)/win2016.vhd
what does it report?
can you type the lines in the menu one at a time to see which one gives any error
Hi,
Without pxe this vhd map without problem.
blocklist do not work with pxe (pd) .
The line in error is the one with map …
Kind regards,
Gatoa
…
On 25 Jan 2019, at 10:11, Steve Si ***@***.***> wrote:
Does it work with any other VHD files? Is it just that one file that gives the error or all files?
Can you go to the grub4dos command shell and type
blocklist (pd)/win2016.vhd
what does it report?
can you type the lines in the menu one at a time to see which one gives any error
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Hi,
With another big vhd, same error again.
…
On 25 Jan 2019, at 11:31, ga5potu ***@***.***> wrote:
Hi,
Without pxe this vhd map without problem.
blocklist do not work with pxe (pd) .
The line in error is the one with map …
Kind regards,
Gatoa
> On 25 Jan 2019, at 10:11, Steve Si ***@***.***> wrote:
>
> Does it work with any other VHD files? Is it just that one file that gives the error or all files?
> Can you go to the grub4dos command shell and type
> blocklist (pd)/win2016.vhd
> what does it report?
> can you type the lines in the menu one at a time to see which one gives any error
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
I am not sure map can work with (pd) device.
Does map (pd) work with any VHD ?
I can not find a way to do it.
With map : fragment error
With map —mem: file to big for memory but vhd is about 15GB and Ram is 32GB
With kernel memdisk and initrd : loading is done but trying to boot result in a disk error
…
On 25 Jan 2019, at 11:36, Steve Si ***@***.***> wrote:
I am not sure map can work with (pd) device.
Does map (pd) work with any VHD ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
well (pd) points to a file across a network. It is not physical data.
if you use —mem then it streams the file across the network and stores it in local memory.
But I am not sure you can use
map (pd)/xxx (hd1)
for any file even if very small — I am not sure it is a legal command even if the file is very small???
Ok is there a way via pxe to “copy” a file in local and then to map it in memory?
…
On 25 Jan 2019, at 11:49, Steve Si ***@***.***> wrote:
well (pd) points to a file across a network. It is not physical data.
if you use —mem then it streams the file across the network and stores it in local memory.
But I am not sure you can use
map (pd)/xxx (hd1)
for any file even if very small — I am not sure it is a legal command even if the file is very small???
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
http://diddy.boot-land.net/grub4dos/files/pxe.htm
There are some differences between disk device and pxe device:
- You can’t list files in the pxe device.
- The blocklist command will not work with a file in the pxe device.
- You must use —mem option if you want to map a file in the pxe device.
So you need to use —mem.
I think this issue should be stated as ‘loading a 15GB VHD using —mem does no work’
…
On 25 Jan 2019, at 11:56, Steve Si ***@***.***> wrote:
http://diddy.boot-land.net/grub4dos/files/pxe.htm
There are some differences between disk device and pxe device:
You can’t list files in the pxe device.
The blocklist command will not work with a file in the pxe device.
You must use —mem option if you want to map a file in the pxe device.
So you need to use —mem.
I think this issue should be stated as ‘loading a 15GB VHD using —mem does no work’
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Can you try the map —mem command using a smaller file (it does not matter what file you use, vhd, iso, img, etc. — the map command will either work or not). Try a 1GB file, 5GB, 17GB, etc. and see if there is a limit.
Also please run
displaymem
command and report output.
I will try later cause I have to go
Thanks for helping
…
On 25 Jan 2019, at 12:01, Steve Si ***@***.***> wrote:
Can you try the map —mem command using a smaller file (it does not matter what file you use, vhd, iso, img, etc. — the map command will either work or not). Try a 1GB file, 5GB, 17GB, etc. and see if there is a limit.
Also please run
displaymem
command and report output.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
With Map —mem
Ok with a file: 2147483648 Bytes 2048MB
Ko with a file: 2147483649 Bytes
…
On 25 Jan 2019, at 12:05, ga5potu ***@***.***> wrote:
I will try later cause I have to go
Thanks for helping
> On 25 Jan 2019, at 12:01, Steve Si ***@***.***> wrote:
>
> Can you try the map —mem command using a smaller file (it does not matter what file you use, vhd, iso, img, etc. — the map command will either work or not). Try a 1GB file, 5GB, 17GB, etc. and see if there is a limit.
> Also please run
> displaymem
> command and report output.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
displaymem output please?
Try also
map --mem-min=4G
first before map —mem command
if it still does not work try
map --mem-min=8G
Not working:
…
On 26 Jan 2019, at 01:37, Steve Si ***@***.***> wrote:
Try also
map —mem-min=4G
first before map —mem command
if it still does not work try
map —mem-min=8G
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Try both —mem-min and mem-max, e.g.
map --mem-min=4G
map --mem-max=20G
map (pd)/win2016.vhd (hd1)
also try —mem-max=1 before map —mem line
also try map —mem=900000 (pd)/win2016.vhd (hd1)
and map —mem —top (pd)/win2016.vhd (hd1)
I still need to see the displaymem output…
put in your menu.lst
displaymem
displaymem --s
pause
or use commandline command and enter commands
type help map to see syntax and help text extract below.
It sounds like the memory size is limited to 2GB. This may be because of your memory map which can be seen if you use the displaymem commands.
map —add-mbt= option to be used with —mem. If =0 master boot track will not
be added automatically.
map —top option to be used with —mem. map —mem will try to allocate memory
at highest available address.
map —mem-max=, map —mem-min options to be used before map —mem. Allow user
to manually limit range of address that map —mem can use.safe_parse_maxint_with_suffix function parses K,M,G,T suffix after number.
KO:
map —mem-min=4G
map —mem-max=20G
map —mem (pd)/win2016.vhd (hd1)
map (pd)/win2016.vhd (hd1)
also KO with —mem-max=1
OK partially (a.vhd=win2916.vhd):
map —mem=900000 (pd)/a.vhd (hd1)
After finishing nicely, at grub>
Displaymem
Displaymem —s
Map —hook
Root (hd1,0)
Result in “cannot mount selected partition”
Please look at the following printscreen:
…
On 26 Jan 2019, at 10:16, Steve Si ***@***.***> wrote:
Try both —mem-min and mem-max, e.g.
map —mem-min=4G
map —mem-max=20G
map (pd)/win2016.vhd (hd1)
also try —mem-max=1
I still need to see the displaymem output…
put in your menu.lst
displaymem
displaymem —s
pause
or use commandline command and enter commands
also try map —mem=900000 (pd)/win2016.vhd (hd1)
type help map to see syntax
It sounds like the memory size is limited to 2GB. This may be because of your memory map which can be seen if you use the displaymem commands.
map —add-mbt= option to be used with —mem. If =0 master boot track will not
be added automatically.
map —top option to be used with —mem. map —mem will try to allocate memory
at highest available address.
map —mem-max=, map —mem-min options to be used before map —mem. Allow user
to manually limit range of address that map —mem can use.
safe_parse_maxint_with_suffix function parses K,M,G,T suffix after number.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
900000 sectors is approx 460MB
try
map —mem=17G (pd)/a.vhd (hd1)
or reduce it (start at 1G).
Do a fresh boot each time because each time you issue the command it reduces available memory
Can you use the issues page to add displaymem results because you need to attach them.
KO: No luck with all of those try: not fit into memory or file not found or cannot mount partition… tests take a very long time, pxe is so slow.
I see in the help that ipxe is available and much more recent but i cannot find any syntax to use it with tftp:
Ok: Kernel (pd)/ipxe.krn
Ok and fast: Inetrd (pd)/a.vhd
And after???
…
On 26 Jan 2019, at 17:37, Steve Si ***@***.***> wrote:
900000 sectors is approx 460MB
try
map —mem=17G (pd)/a.vhd (hd1)
or reduce it (start at 1G).
Do a fresh boot each time because each time you issue the command it reduces available memory
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Hi Steve,
Thanks for your message.
Yes, with —top —mem the multi GB vhd is now loading like a charm.
But when used with pxe :
Pxe
Pxe keep
Map —top —mem (pd)/win.vhd (hd0)
Map —hook
Rootnoverify (hd0,0)
Chainloader (hd0)+1
Boot
>At this line, this now result with the following problem: “A Disk read error occurred Press ctrl+alt+del to restart”
If you have any ideas, thanks to share it…
In any event, the initial problem is now solved, thank you very much.
Kind regards
Gato
…
Note: If you have too many ‘set’ variables in your _ISOMyE2B.cfg file, it can cause many different grub4dos errors to occur in various menus. Try without a MyE2B.cfg file to check if it still gives you an error.
1 ERR_BAD_FILENAME Filename must be either an absolute pathname or blocklist
2 ERR_BAD_FILETYPE Bad file or directory type
3 ERR_BAD_GZIP_DATA Bad or corrupt data while decompressing file
4 ERR_BAD_GZIP_HEADER Bad or incompatible header in compressed file
5 ERR_BAD_PART_TABLE Partition table invalid or corrupt
6 ERR_BAD_VERSION Mismatched or corrupt version of stage1/stage2
7 ERR_BELOW_1MB Loading below 1MB is not supported
8 ERR_BOOT_COMMAND Kernel must be loaded before booting
9 ERR_BOOT_FAILURE Unknown boot failure
10 ERR_BOOT_FEATURES Unsupported Multiboot features requested
11 ERR_DEV_FORMAT Unrecognized device string or you omitted the required DEVICE part (e.g. '(hd0,0)' or '(cd)') which should precede the filename.
12 ERR_DEV_VALUES Invalid device requested
13 ERR_EXEC_FORMAT Invalid or unsupported executable format
14 ERR_FILELENGTH Filesystem compatibility error cannot read whole file
15 ERR_FILE_NOT_FOUND File not found 15
16 ERR_FSYS_CORRUPT Inconsistent filesystem structure
17 ERR_FSYS_MOUNT Cannot mount selected partition
18 ERR_GEOM Selected cylinder exceeds maximum supported by BIOS
19 ERR_NEED_LX_KERNEL Linux kernel must be loaded before initrd
20 ERR_NEED_MB_KERNEL Multiboot kernel must be loaded before modules
21 ERR_NO_DISK Selected disk does not exist 21
22 ERR_NO_PART No such partition
23 ERR_NUMBER_PARSING Error while parsing number
24 ERR_OUTSIDE_PART Attempt to access block outside partition
25 ERR_READ Disk read error
26 ERR_SYMLINK_LOOP Too many symbolic links
27 ERR_UNRECOGNIZED Unrecognized command
28 ERR_WONT_FIT Selected item cannot fit into memory
29 ERR_WRITE Disk write error
30 ERR_BAD_ARGUMENT Invalid argument
31 ERR_UNALIGNED File is not sector aligned
32 ERR_PRIVILEGED Must be authenticated
33 ERR_DEV_NEED_INIT Device not initialized yet
34 ERR_NO_DISK_SPACE No spare sectors on the disk
35 ERR_NUMBER_OVERFLOW Overflow while parsing number
36 ERR_DEFAULT_FILE Invalid DEFAULT file format. Please copy a valid DEFAULT file from the grub4dos release and try again. Also note that the DEFAULT file must be uncompressed. 36
37 ERR_DEL_MEM_DRIVE You should delete other mem drive first or use `--mem' option to force the deletion
38 ERR_DISABLE_A20 Failed to turn off Gate A20!
39 ERR_DOS_BACKUP GRUB was not booted from DOS or the backup copy of DOS at physicalnaddress 0x200000 is corrupt
40 ERR_ENABLE_A20 Failed to turn on Gate A20!
41 ERR_EXTENDED_PARTITION Extended partition table is invalid or its CHS values conflict with the BPB in a logical partition
42 ERR_FILENAME_FORMAT The leading DEVICE of the filename to find must be stripped offntand DIR for set-root must begin in a slash(/).
43 ERR_HD_VOL_START_0 The BPB hidden_sectors should not be zero for a hard-disk partition boot sector
44 ERR_INT13_ON_HOOK The int13 handler already on hook
45 ERR_INT13_OFF_HOOK The int13 handler not yet on hook
46 ERR_INVALID_BOOT_CS Invalid boot CS. Should be between 0 and 0xFFFF
47 ERR_INVALID_BOOT_IP Invalid boot IP. Should be between 0 and 0xFFFF
48 ERR_INVALID_FLOPPIES Invalid floppies. Should be between 0 and 2
49 ERR_INVALID_HARDDRIVES Invalid harddrives. Should be between 0 and 127
50 ERR_INVALID_HEADS Invalid heads. Should be between 0 and 256(0 means auto)
51 ERR_INVALID_LOAD_LENGTH Invalid load length. Should be between 512 and 0xA0000
52 ERR_INVALID_LOAD_OFFSET Invalid load offset. Should be between 0 and 0xF800
53 ERR_INVALID_LOAD_SEGMENT Invalid load segment. Should be between 0 and 0x9FFF
54 ERR_INVALID_SECTORS Invalid sectors. Should be between 0 and 63(0 means auto)
55 ERR_INVALID_SKIP_LENGTH Invalid skip length. Should be less than the file size
56 ERR_INVALID_RAM_DRIVE Invalid ram_drive. Should be between 0 and 254
57 ERR_IN_SITU_FLOPPY Only hard drives could be mapped in situ.
58 ERR_IN_SITU_MEM Should not use --mem together with --in-situ.
59 ERR_MD_BASE When mapping whole mem device at a fixed location you must specify --mem to a value > 0.
60 ERR_NON_CONTIGUOUS File for drive emulation must be in one contiguous disk area
61 ERR_MANY_FRAGMENTS Too many fragments
62 ERR_NO_DRIVE_MAPPED Refuse to hook int13 because of empty drive map table
63 ERR_NO_HEADS The number of heads must be specified. The `--heads0' option tells map to choose a value(but maybe unsuitable) for you
64 ERR_NO_SECTORS The number of sectors per track must be specified. The `--sectors-per-track0' option tells map to choose a value(but maybe unsuitable) for you
65 ERR_PARTITION_TABLE_FULL Cannot use --in-situ because the partition table is full(i.e. all the 4 entries are in use).
66 ERR_RD_BASE RD_BASE must be sector-aligned and non-zero for mapping at a fixed location
67 ERR_SPECIFY_GEOM Should not specify geometry when mapping a whole drive or when emulating a hard disk with a logical partition
68 ERR_SPECIFY_MEM Should not specify `--mem' when mapping a whole drive
69 ERR_SPECIFY_RESTRICTION Options --read-only --fake-write and --unsafe-boot are mutually exclusive. Should not specify them repeatedly.
70 ERR_MD5_FORMAT Unrecognized md5 string. You must create it using the MD5CRYPT command.
71 ERR_WRITE_GZIP_FILE Attempt to write a gzip file
72 ERR_FUNC_CALL Invalid function call
73 ERR_INTERNAL_CHECK Internal check failed. Please report this bug.
74 ERR_KERNEL_WITH_PROGRAM Kernel cannot load if there is an active process
75 ERR_HALT Halt failed.
76 ERR_PARTITION_LOOP Too many partitions.
77 ERR_NOT_ENOUGH_MEMORY Not enough memory
78 ERR_NO_VBE_BIOS VBE not detected.
79 ERR_BAD_VBE_SIGNATURE VESA signature not present.
80 ERR_LOW_VBE_VERSION VBE version too old. Must be 2.0+.
81 ERR_NO_VBE_MODES No modes detected for 24/32 bits per pixel.
82 ERR_SET_VBE_MODE Set VBE mode failed.
83 ERR_SET_VGA_MODE Set VGA mode failed.
84 ERR_LOAD_SPLASHIMAGE Failed loading splashimage.
85 ERR_UNIFONT_FORMAT Wrong unifont format.
86 ERR_DIVISION_BY_ZERO Division by zero 86
1 ERR_BAD_FILENAME Filename must be either an absolute pathname or blocklist
2 ERR_BAD_FILETYPE Bad file or directory type
3 ERR_BAD_GZIP_DATA Bad or corrupt data while decompressing file
4 ERR_BAD_GZIP_HEADER Bad or incompatible header in compressed file
5 ERR_BAD_PART_TABLE Partition table invalid or corrupt
6 ERR_BAD_VERSION Mismatched or corrupt version of stage1/stage2
7 ERR_BELOW_1MB Loading below 1MB is not supported
8 ERR_BOOT_COMMAND Kernel must be loaded before booting
9 ERR_BOOT_FAILURE Unknown boot failure
10 ERR_BOOT_FEATURES Unsupported Multiboot features requested
11 ERR_DEV_FORMAT Unrecognized device string or you omitted the required DEVICE part which should lead the filename.
12 ERR_DEV_VALUES Invalid device requested
13 ERR_EXEC_FORMAT Invalid or unsupported executable format (not bootable) - the ISO(?) you are trying to boot from is not bootable - maybe it is an Update CD instead of an Install CDDVD? Maybe BIOS has the 128GB USB drive limit bug and file is too far on drive?
14 ERR_FILELENGTH Filesystem compatibility error cannot read whole file
15 ERR_FILE_NOT_FOUND File not found [check filename does not contain non-standard characters such as ( or % or = or & ]
16 ERR_FSYS_CORRUPT Inconsistent filesystem structure (maybe due to 128GB-limit BIOS bug?)
17 ERR_FSYS_MOUNT Cannot mount selected partition
18 ERR_GEOM Selected cylinder exceeds maximum supported by BIOS
19 ERR_NEED_LX_KERNEL Linux kernel must be loaded before initrd
20 ERR_NEED_MB_KERNEL Multiboot kernel must be loaded before modules
21 ERR_NO_DISK Selected disk does not exist
22 ERR_NO_PART No such partition
23 ERR_NUMBER_PARSING Error while parsing number
24 ERR_OUTSIDE_PART Attempt to access block outside partition
25 ERR_READ Disk read error (make sure file is contiguous)
26 ERR_SYMLINK_LOOP Too many symbolic links
27 ERR_UNRECOGNIZED Unrecognized command
28 ERR_WONT_FIT Selected item cannot fit into memory (file may not be contiguous) - if using map --mem, also add --top if not enough contiguous upper memory (use displaymem to check)
29 ERR_WRITE Disk write error
30 ERR_BAD_ARGUMENT Invalid argument
31 ERR_UNALIGNED File is not sector aligned
32 ERR_PRIVILEGED Must be authenticated
33 ERR_DEV_NEED_INIT Device not initialized yet
34 ERR_NO_DISK_SPACE No spare sectors on the disk
35 ERR_NUMBER_OVERFLOW Overflow while parsing number
36 ERR_DEFAULT_FILE Invalid DEFAULT file format. Please copy a valid DEFAULT file from the grub4dos release and try again. Also note that the DEFAULT file must be uncompressed.
37 ERR_DEL_MEM_DRIVE You should delete other mem drive first or use `--mem' option to force the deletion
38 ERR_DISABLE_A20 Failed to turn off Gate A20!
39 ERR_DOS_BACKUP GRUB was not booted from DOS or the backup copy of DOS at physical address 0x200000 is corrupt
40 ERR_ENABLE_A20 Failed to turn on Gate A20!
41 ERR_EXTENDED_PARTITION Extended partition table is invalid or its CHS values conflict with the BPB in a logical partition
42 ERR_FILENAME_FORMAT The leading DEVICE of the filename to find must be stripped off and DIR for set-root must begin in a slash(/).
43 ERR_HD_VOL_START_0 The BPB hidden_sectors should not be zero for a hard-disk partition boot sector
44 ERR_INT13_ON_HOOK The int13 handler already on hook
45 ERR_INT13_OFF_HOOK The int13 handler not yet on hook
46 ERR_INVALID_BOOT_CS Invalid boot CS. Should be between 0 and 0xFFFF
47 ERR_INVALID_BOOT_IP Invalid boot IP. Should be between 0 and 0xFFFF
48 ERR_INVALID_FLOPPIES Invalid floppies. Should be between 0 and 2
49 ERR_INVALID_HARDDRIVES Invalid harddrives. Should be between 0 and 127
50 ERR_INVALID_HEADS Invalid heads. Should be between 0 and 256 (0 means auto)
51 ERR_INVALID_LOAD_LENGTH Invalid load length. Should be between 512 and 0xA0000
52 ERR_INVALID_LOAD_OFFSET Invalid load offset. Should be between 0 and 0xF800
53 ERR_INVALID_LOAD_SEGMENT Invalid load segment. Should be between 0 and 0x9FFF
54 ERR_INVALID_SECTORS Invalid sectors. Should be between 0 and 63 (0 means auto)
55 ERR_INVALID_SKIP_LENGTH Invalid skip length. Should be less than the file size
56 ERR_INVALID_RAM_DRIVE Invalid ram_drive. Should be between 0 and 254
57 ERR_IN_SITU_FLOPPY Only hard drives could be mapped in situ.
58 ERR_IN_SITU_MEM Should not use --mem together with --in-situ.
59 ERR_MD_BASE When mapping whole mem device at a fixed location you must specify --mem to a value > 0.
60 ERR_NON_CONTIGUOUS File for drive emulation must be in one contiguous disk area
61 ERR_MANY_FRAGMENTS Too many fragments
62 ERR_NO_DRIVE_MAPPED Refuse to hook int13 because of empty drive map table
63 ERR_NO_HEADS The number of heads must be specified. The `--heads0' option tells map to choose a value (but maybe unsuitable) for you
64 ERR_NO_SECTORS The number of sectors per track must be specified. The `--sectors-per-track0' option tells map to choose a value (but maybe unsuitable) for you
65 ERR_PARTITION_TABLE_FULL Cannot use --in-situ because the partition table is full (i.e. all the 4 entries are in use).
66 ERR_RD_BASE RD_BASE must be sector-aligned and non-zero for mapping at a fixed location
67 ERR_SPECIFY_GEOM Should not specify geometry when mapping a whole drive or when emulating a hard disk with a logical partition
68 ERR_SPECIFY_MEM Should not specify `--mem' when mapping a whole drive
69 ERR_SPECIFY_RESTRICTION Options --read-only --fake-write and --unsafe-boot are mutually exclusive. Should not specify them repeatedly.
70 ERR_MD5_FORMAT Unrecognized md5 string. You must create it using the MD5CRYPT command.
71 ERR_WRITE_GZIP_FILE Attempt to write a gzip file
72 ERR_FUNC_CALL Invalid function call
73 ERR_INTERNAL_CHECK Internal check failed. Please report this bug.
74 ERR_KERNEL_WITH_PROGRAM Kernel cannot load if there is an active process
75 ERR_HALT Halt failed.
76 ERR_PARTITION_LOOP Too many partitions.
77 ERR_NOT_ENOUGH_MEMORY Not enough memory
78 ERR_NO_VBE_BIOS VBE not detected.
79 ERR_BAD_VBE_SIGNATURE VESA signature not present.
80 ERR_LOW_VBE_VERSION VBE version too old. Must be 2.0+.
81 ERR_NO_VBE_MODES No modes detected for 24/32 bits per pixel.
82 ERR_SET_VBE_MODE Set VBE mode failed.
83 ERR_SET_VGA_MODE Set VGA mode failed.
84 ERR_LOAD_SPLASHIMAGE Failed loading splashimage.
85 ERR_UNIFONT_FORMAT Wrong unifont format.
86 ERR_DIVISION_BY_ZERO Division by zero
grub error numbers
Here is an interpretation of the grub4dos error codes based on the grub error code documentation (they may not be 100% correct for grub4dos but may help).
1 : Filename must be either an absolute filename or blocklist
This error is returned if a file name is requested which doesn't fit the syntax/rules listed in the section Filesystem syntax and semantics.
2 : Bad file or directory type
This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO.
3 : Bad or corrupt data while decompressing file
This error is returned if the run-length decompression code gets an internal error. This is usually from a corrupt file.
4 : Bad or incompatible header in compressed file
This error is returned if the file header for a supposedly compressed file is bad.
5 : Partition table invalid or corrupt
This error is returned if the sanity checks on the integrity of the partition table fail. This is a bad sign.
6 : Mismatched or corrupt version of stage1/stage2
This error is returned if the install command is pointed to incompatible or corrupt versions of the stage1 or stage2. It can't detect corruption in general, but this is a sanity check on the version numbers, which should be correct.
7 : Loading below 1MB is not supported
This error is returned if the lowest address in a kernel is below the 1MB boundary. The Linux zImage format is a special case and can be handled since it has a fixed loading address and maximum size.
8 : Kernel must be loaded before booting
This error is returned if GRUB is told to execute the boot sequence without having a kernel to start.
9 : Unknown boot failure
This error is returned if the boot attempt did not succeed for reasons which are unknown.
10 : Unsupported Multiboot features requested
This error is returned when the Multiboot features word in the Multiboot header requires a feature that is not recognized. The point of this is that the kernel requires special handling which GRUB is likely unable to provide.
11 : Unrecognized device string
This error is returned if a device string was expected, and the string encountered didn't fit the syntax/rules listed in the section Filesystem syntax and semantics.
12 : Invalid device requested
This error is returned if a device string is recognizable but does not fall under the other device errors.
13 : Invalid or unsupported executable format
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD). If an ISO file is being booted, the ISO is probably not bootable or is corrupt.
14 : Filesystem compatibility error, cannot read whole file
Some of the filesystem reading code in GRUB has limits on the length of the files it can read. This error is returned when the user runs into such a limit.
15 : File not found
This error is returned if the specified file name cannot be found, but everything else (like the disk/partition info) is OK.
16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB. If using a Virtual Machine and a .vmdk file for the E2B USB drive, it can be caused by invalid parameters used within the .vmdk file. Re-make the .vmdk file or if using DavidB's VMUB utility, re-select the USB drive for your VM so that the .vmdk file is recreated on the next run. If you see this message when booting from a real system, but not when booting from QEMU or VBox for some payload files, then suspect the BIOS has the 137GB USB bug - it cannot access files beyond 137GB on the USB disk.
17 : Cannot mount selected partition
This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB.
18 : Selected cylinder exceeds maximum supported by BIOS
This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general).
19 : Linux kernel must be loaded before initrd
This error is returned if the initrd command is used before loading a Linux kernel. Similar to the above error, it only makes sense in that case anyway.
20 : Multiboot kernel must be loaded before modules
This error is returned if the module load command is used before loading a Multiboot kernel. It only makes sense in this case anyway, as GRUB has no idea how to communicate the presence of location of such modules to a non-Multiboot-aware kernel.
21 : Selected disk does not exist
This error is returned if the device part of a device- or full file name refers to a disk or BIOS device that is not present or not recognized by the BIOS in the system.
22 : No such partition
This error is returned if a partition is requested in the device part of a device- or full file name which isn't on the selected disk.
23 : Error while parsing number
This error is returned if GRUB was expecting to read a number and encountered bad data.
24 : Attempt to access block outside partition
This error is returned if a linear block address is outside of the disk partition. This generally happens because of a corrupt filesystem on the disk or a bug in the code handling it in GRUB (it's a great debugging tool).
25 : Disk read error
This error is returned if there is a disk read error when trying to probe or read data from a particular disk.
26 : Too many symbolic links
This error is returned if the link count is beyond the maximum (currently 5), possibly the symbolic links are looped.
27 : Unrecognized command
This error is returned if an unrecognized command is entered into the command-line or in a boot sequence section of a configuration file and that entry is selected.
28 : Selected item cannot fit into memory
This error is returned if a kernel, module, or raw file load command is either trying to load its data such that it won't fit into memory or it is simply too big. If a file is not contiguous, E2B may try to load it into memory.
29 : Disk write error
This error is returned if there is a disk write error when trying to write to a particular disk. This would generally only occur during an install of set active partition command.
30 : Invalid argument
This error is returned if an argument specified to a command is invalid.
31 : File is not sector aligned
This error may occur only when you access a ReiserFS partition by block-lists (e.g. the command @command{install}). In this case, you should mount the partition with the `-o notail' option.
32 : Must be authenticated
This error is returned if you try to run a locked entry. You should enter a correct password before running such an entry.
60: File not contiguous
The file has been split into several different places on the drive. For E2B, most payload files and most ext2 files need to be contiguous. Run WinContig or Defraggler to make all files on the drive contiguous.
- Печать
Страницы: 1 2 3 [4] 5 Вниз
Тема: Grub4dos. Использование переменных (унификация, универсализация). (Прочитано 28921 раз)
0 Пользователей и 1 Гость просматривают эту тему.
«загрузка из *.iso»
— если у кого есть какой-нибудь «заведомодефрагментироанный» *.iso — просьба уведомить о (?не)работоспособности.
Записан
Gr4D, Grub2; HP Mini 210 VT — Intel Atom N470 @ 1.83GHz, Intel GMA3150, RAM=2 ГБ ;
Sams-n110: N270 — 1,6 ГГц, Intel GMA 950, RAM=2 ГБ.
Насчет загрузки именно «дефрагментированных .исо» точно не скажу — у меня каталог с *.iso на ext4 ( работает).
Точно могу сказать, что дефрагментированные исо граб4дос не может загрузить. Есть вариант с предварительным копированием в ОЗУ. Ну не удивительно, что на ext4 у вас работает, там это дело редкое, только когда уже нет возможности без фрагментации записать.
Записан
вариант с предварительным копированием в ОЗУ
— наверное на этой странице :
http://tdkare.ru/sysadmin/index.php/Grub4dos
— строки Гр4д для «такого действа» —> Как «получить» дефрагментированный образ(чтоб попробовать)?
p.s.
не удивительно, что на ext4 у вас работает
в файловых системах пока «несилён»
« Последнее редактирование: 24 Декабрь 2018, 16:17:51 от knn »
Записан
Gr4D, Grub2; HP Mini 210 VT — Intel Atom N470 @ 1.83GHz, Intel GMA3150, RAM=2 ГБ ;
Sams-n110: N270 — 1,6 ГГц, Intel GMA 950, RAM=2 ГБ.
наверное на этой странице :
Цитата: knn от Сегодня в 12:19:23
http://tdkare.ru/sysadmin/index.php/Grub4dos
Ага, я так и делал через условие «если не одно так другое»
Как «получить» дефрагментированный образ(чтоб попробовать)?
Вы хотите это попробовать?:
map --sectors-per-track=0 --heads=0 /<ОБРАЗ>.iso (0xff) || map --sectors-per-track=0 --heads=0 --mem /<ОБРАЗ>.iso (0xff)К примеру у вас есть образ размером 1 гиг. Тогда забиваете весь раздел под завязку файлами меньше чем этот размер в несколько раз следующей командой:
split -d -b 300M /dev/zeroУ вас на диске появятся файлы соответствующего размера с именами x00, x01 и так далее.
Затем когда раздел забьется полностью удалите столько файлов сколько будет достаточно для копирования туда вашего образа. Но удалять надо файлы с номерами идущими не по порядку, чтоб на разделе освободилось место на разных его участках. Когда вы скопируете на это свободное пространство ваш исо образ он гарантированно будет фрагментирован.
Записан
Спасибо, в общих чертах метод понятен — буду пробовать(fat или ntfs) —
map —sectors-per-track=0 —heads=0 /<ОБРАЗ>.iso (0xff) || map —sectors-per-track=0 —heads=0 —mem /<ОБРАЗ>.iso (0xff)
p.s.
Как «теоретически» к этому методу(фрагментации) «отнесётся» EXT4 — не дефрагментирует ли(обратно) ? (интересно для «расширения кругозора»)
Записан
Gr4D, Grub2; HP Mini 210 VT — Intel Atom N470 @ 1.83GHz, Intel GMA3150, RAM=2 ГБ ;
Sams-n110: N270 — 1,6 ГГц, Intel GMA 950, RAM=2 ГБ.
« Последнее редактирование: 24 Декабрь 2018, 20:25:49 от knn »
Записан
Gr4D, Grub2; HP Mini 210 VT — Intel Atom N470 @ 1.83GHz, Intel GMA3150, RAM=2 ГБ ;
Sams-n110: N270 — 1,6 ГГц, Intel GMA 950, RAM=2 ГБ.
—возможно в «обоих случаях» маппинг происходит ч/з RAM…
Нет, для этого должна быть команда —mem. Загрузка iso в память этой командой происходит очень медленно, если iso большой, то проще его дефрагментировать.
Мне удалось получить ошибку на ext4:
Error 61 …….
Too many fragments.
С этим конфигом http://forum.puppyrus.org/index.php?topic=19544.msg152031#msg152031
Копировал большой изошник (1.8Gb), в ту же папку с переименованием. Но раз на раз не приходится, получилось фрагментировать таким способом только один раз.
Дефрагментировать .iso можно с e4defrag (файл, папку или всю директорию.):
http://rus-linux.net/MyLDP/admin/defragment-ext4.html
Записан
Записан
Too many fragments.
… похоже всплывает Вопрос о Границе: «Too-many/Не-Too-many» 
.
==========
p.s.
Где(какой) взять относительно-небольшой Негибридный .img «на пробу»? (x-86)
Записан
Gr4D, Grub2; HP Mini 210 VT — Intel Atom N470 @ 1.83GHz, Intel GMA3150, RAM=2 ГБ ;
Sams-n110: N270 — 1,6 ГГц, Intel GMA 950, RAM=2 ГБ.
« Последнее редактирование: 24 Декабрь 2018, 22:43:23 от knn »
Записан
Gr4D, Grub2; HP Mini 210 VT — Intel Atom N470 @ 1.83GHz, Intel GMA3150, RAM=2 ГБ ;
Sams-n110: N270 — 1,6 ГГц, Intel GMA 950, RAM=2 ГБ.
Как «теоретически» к этому методу(фрагментации) «отнесётся» EXT4 — не дефрагментирует ли(обратно) ?
Думаю не дефрагментирует.
успешно грузится
Если вы в загрузчике прописали:
map /<ОБРАЗ>.iso (0xff) || map --mem /<ОБРАЗ>.iso (0xff)То загрузиться должно в любом случае. Там в принципе видно когда в ОЗУ копируется.
Записан
Где(какой) взять относительно-небольшой Негибридный .img «на пробу»? (x-86)
ИСО МагОС негибридный, но он не маленький.
Для grub4dos гибридный или нет думаю не важно, потому что я грузил всякого рода восстановительные исошки типа Hiren’sBootCD без проблем и вряд ли они были гибридные.
Записан
Насчет загрузки именно «дефрагментированных .исо» точно не скажу — у меня каталог с *.iso на ext4 ( работает).
Дефрагментировать .iso можно с e4defrag
Пробовал грузить исошки из grub4dos с ext4. Ругается на фрагментированность и даже e4defrag не помогает. Может у меня файлы со временем по всему разделу расположились и нет доасточных свободных участков или e4defrag немного халтурит. Мне вообще кажется он не ставит себе задачу полностью дефрагментировать файл. Ощущение, что он только доводит его до более менее дефрагментированного состояния.
Записан
Мне вообще кажется он не ставит себе задачу полностью дефрагментировать файл.
Мне так же показалось, но при этом iso грузятся с grub4dos.
% e4defrag -v /mnt/sda3/iso/
[249/254]/mnt/sda3/iso/prar-1811-lxqt-01.iso: 100% extents: 22 -> 8 [ OK ]
[251/254]/mnt/sda3/iso/Fedora-Workstation-Live-x86_64-29-1.2.iso: 100% extents: 16 -> 16 [ OK ]
[253/254]/mnt/sda3/iso/pra03-1808retro.iso: 100% extents: 4 -> 2 [ OK ]
P.s. Хотел полный вывод под кат, но вспомнил о проблемах на хромиеподобных. Хорошая реклама для firefox или palemoon. )
Записан
при этом iso грузятся с grub4dos.
Создал новый раздел с ext4. Дал права на запись обычному юзеру. Скопировал туда файловым менеджером iso образ. Пробую запамить, grub4dos ругается. ЧЯДНТ?
e4defrag -c MX-18_x64.iso
<File> now/best size/ext
MX-18_x64.iso 11/1 128000 KB Total/best extents 11/1
Average size per extent 128000 KB
Fragmentation score 0
[0-30 no problem: 31-55 a little bit fragmented: 56- needs defrag]
This file (MX-18_x64.iso) does not need defragmentation.
Done.
Записан
- Печать
Страницы: 1 2 3 [4] 5 Вверх