GNU GRUB - Bugs: bug #43062, boot-directory not in core.img
You are not allowed to post comments on this tracker with your current authentication level.
bug #43062: boot-directory not in core.img
Submitter: | Jay Michael <jmichael> | ||
Submitted: | Sun 24 Aug 2014 05:18:18 AM UTC | ||
Category: | Configuration | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | Invalid | Privacy: | Public |
Assigned to: | None | Originator Name: | Jay Michael |
Open/Closed: | Closed | Release: | 2.02~beta1 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Jump to the original submission
Fri 23 Jan 2015 09:41:12 AM UTC, comment #9: |
Vladimir Serbinenko <phcoder> |
Fri 23 Jan 2015 06:26:06 AM UTC, comment #8: I'm sure my disk is using 4K sectors.
|
Jay Michael <jmichael> |
Thu 22 Jan 2015 08:24:56 PM UTC, comment #7: Most likely your disk uses 4K sectors. I haven't found a single BIOS which will consider such a disk bootable. So not a GRUB problem as GRUB can't do anything about this. |
Vladimir Serbinenko <phcoder> |
Fri 05 Dec 2014 06:54:09 PM UTC, comment #6: core.img is compressed; BIS is using heuristic to find start of compressed data. |
Andrei Borzenkov <arvidjaar> |
Mon 24 Nov 2014 03:11:31 AM UTC, comment #5: If I do a * grub-install --boot-directory=${VDOS}/boot /dev/sdc *, is the core.img that's copied to sector 1 of /dev/sdc the same as the core.img that ends up in * ${VDOS}/boot/grub/i386-pc * ?
|
Jay Michael <jmichael> |
Fri 21 Nov 2014 06:42:41 AM UTC, comment #4: /dev/sdc is using 4K native sector size which is likely why your BISO does not recognize it as boot device and why Seagate says it is unbootable. There is not much we can do from grub side here.
|
Andrei Borzenkov <arvidjaar> |
Thu 20 Nov 2014 04:36:47 AM UTC, comment #3: What was supposed to change?
I get
I don't know when or why in installing Ubuntu in EFI boot mode it would have wiped out the BIOS-boot bits.
|
Jay Michael <jmichael> |
Tue 18 Nov 2014 02:02:08 PM UTC, comment #2: BIS from sourceforge has problems with new grub. Try one from https://github.com/arvidjaar/bootinfoscript/blob/master/bootinfoscript |
Andrei Borzenkov <arvidjaar> |
Sun 24 Aug 2014 09:28:12 PM UTC, comment #1: When BIOS tries to boot, I get
|
Jay Michael <jmichael> |
Sun 24 Aug 2014 05:18:18 AM UTC, original submission:
The boot-directory doesn't seem to be getting into the core.img produced by running grub-install.
output of grub-install --debug --force --no-floppy --recheck --boot-directory=/media/ubuntu/VDOS/boot /dev/sdc 2>&1
RESULTS.txt from bootinfoscript
|
Jay Michael <jmichael> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 7 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-01-22 | phcoder | Status | None | Invalid | |
Open/Closed | Open | Closed | |||
2014-11-20 | jmichael | Attached File | - | Added bis-061-results.txt, #32482 | |
Attached File | - | Added bis-20140825-results.txt, #32483 | |||
2014-08-24 | jmichael | Attached File | - | Added grub-install.log, #31943 | |
Attached File | - | Added core.img, #31944 | |||
Attached File | - | Added grub-install.bisresults, #31945 |
Powered by Savane 3.13-02a9.
Corresponding source code
No and no. Bootsector is boot.img. And it prints "GRUB" very early unless you use ubuntu version (in that case revert to upstream or ask support at ubuntu forums). The message about unbootable disk is not coming from GRUB but most likely from BIOS itself. If you see string "GRUB" then at least a bootsector is loaded and we may be able to adjust GRUB, if you don't, then there is nothing GRUB can do.