GNU GRUB - Bugs: bug #37606, Grub2-install doesn't report a...
You are not allowed to post comments on this tracker with your current authentication level.
bug #37606: Grub2-install doesn't report a failure to write to boot partition
Submitter: | Simon <simd> | ||
Submitted: | Sun 21 Oct 2012 09:56:21 AM UTC | ||
Category: | Installation | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | Fixed | Privacy: | Public |
Assigned to: | None | Originator Name: | sd |
Open/Closed: | Closed | Release: | other |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Jump to the original submission
Sun 03 Nov 2013 06:09:02 PM UTC, comment #11: |
Vladimir Serbinenko <phcoder> |
Tue 23 Oct 2012 07:19:40 AM UTC, comment #10: OK, I've managed to sort out what had happened. Thanks for the help! I'll record the result here in case it's useful to someone else in the future.
|
Simon <simd> |
Mon 22 Oct 2012 03:58:43 PM UTC, comment #9: Do you have "PRIVHEAD" or "VBLK" signatures in either sector 6 or last sector? |
Vladimir Serbinenko <phcoder> |
Mon 22 Oct 2012 03:36:10 PM UTC, comment #8: Well, I've never formatted anything on that disk as an LDM device as far as I'm aware. The partition in question has been the boot partition for my linux for two years! Could you explain what exactly grub is testing for? Parted etc list the disk exactly as normal. |
Simon <simd> |
Mon 22 Oct 2012 12:41:25 PM UTC, comment #7: It's the presence of LDM database with partiton starting at exactly the same sector as the mounted partition. |
Vladimir Serbinenko <phcoder> |
Mon 22 Oct 2012 12:27:50 PM UTC, comment #6: That's interesting. What has established it as an LDM disk as far as grub is concerned?
|
Simon <simd> |
Mon 22 Oct 2012 10:45:38 AM UTC, comment #5: It's LDM/"Dynamic disk" (not LVM). This changes a lot. Installing to LDM isn't currently supported. |
Vladimir Serbinenko <phcoder> |
Mon 22 Oct 2012 10:03:12 AM UTC, comment #4: No, it was being called with /dev/sdb2. From the log output I could only guess that the fact that the disk had LVM partitions on it was throwing grub-install. I've attached the full output. |
Simon <simd> |
Mon 22 Oct 2012 09:48:23 AM UTC, comment #3: If grub-setup as called with a virtual device then most likely the grub-install command was wrong. It has to be
|
Vladimir Serbinenko <phcoder> |
Mon 22 Oct 2012 09:38:21 AM UTC, comment #2: Agree, I misread the 0x400.
|
Simon <simd> |
Sun 21 Oct 2012 11:13:20 AM UTC, comment #1: It's not 400 but 1024. And at this message it writes to core.img file, not to some sector. It's underlying function responsability to set grub_errno (through grub_error). As to apparent writing failure it's due to the lack of necessary flushing ioctl (Linux API is broken in that write doesn't necessarily actually writes unless you add a bunch of ioctl) which is fixed in latest code. |
Vladimir Serbinenko <phcoder> |
Sun 21 Oct 2012 09:56:21 AM UTC, original submission:
I think this bug has come up before in different guises e.g. https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/574883
|
Simon <simd> |
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2013-11-03 | phcoder | Status | None | Fixed | |
Open/Closed | Open | Closed | |||
2012-10-22 | simd | Attached File | - | Added Grub2_dump.txt, #26813 |
Powered by Savane 3.13-758e.
Corresponding source code
Now GRUB ignores dynamic disks unless there is a special partition in MBR.