Errors while post-processing grub installation

Bug #1377826 reported by T. K. on 2014-10-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Undecided
Unassigned

Bug Description

Some days ago I did a dist-upgrade on my Ubuntu 12.04 system (HP Microserver N54L, configured as RAID 1). At the end of the upgrade process a new grub.cfg is build with the following errors displayed:

...
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-69-generic
Found initrd image: /boot/initrd.img-3.2.0-69-generic
Found linux image: /boot/vmlinuz-3.2.0-67-generic
Found initrd image: /boot/initrd.img-3.2.0-67-generic
Found memtest86+ image: /memtest86+.bin
ERROR: ddf1: seeking device "/dev/dm-2" to 18446744073709421056
ERROR: hpt37x: seeking device "/dev/dm-2" to 4608
ERROR: hpt45x: seeking device "/dev/dm-2" to 18446744073709547008
ERROR: isw: seeking device "/dev/dm-2" to 18446744073708469760
ERROR: sil: seeking device "/dev/dm-2" to 18446744073709289984
ERROR: ddf1: seeking device "/dev/dm-2" to 18446744073709421056
ERROR: hpt37x: seeking device "/dev/dm-2" to 4608
ERROR: hpt45x: seeking device "/dev/dm-2" to 18446744073709547008
ERROR: isw: seeking device "/dev/dm-2" to 18446744073708469760
ERROR: sil: seeking device "/dev/dm-2" to 18446744073709289984
done
Trigger für libc-bin werden verarbeitet ...
ldconfig deferred processing now taking place

Now I fear, I'm left with a productive and critical system that cannot reboot anymore!

See also:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1073108/comments/11
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1073108/comments/12

Attached you find a file with more information about the update, dist-upgrade, dpkg.log, syslog and lvm configuration.
Please ask for more information if needed . Thank you.

T. K. (stuttgart-live) wrote :
T. K. (stuttgart-live) wrote :

According to Louis Bouchard this is a side effect of another fix (https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1073108).

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1377826/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
T. K. (stuttgart-live) on 2014-10-06
affects: ubuntu → grub2 (Ubuntu)
Louis Bouchard (louis) wrote :

T.K. I did not say that it was a side-effect of the fix, I said that the situation was a side effect of installing the newer package.

Basic search shows that this error is apparently issued by dmraid. You might want to verify the status of your RAID setup and test with the dmraid function to identify the source of those errors.

You may want to look at the following bug for ideas :

https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918

Phillip Susi (psusi) wrote :

Those messages come from dmraid, and you can safely ignore them. FYI, you should avoid using fakeraid unless you must dual boot with windows, as it is not well supported.

Changed in grub2 (Ubuntu):
status: New → Invalid
T. K. (stuttgart-live) wrote :

@Louis:
You wrote "This is a side effect of the upgrade" so this was my interpretation - please accept my apologies.

@Phillip: Thank you for clarifying this. I'm currently about to set up a new (more powerful) server, this time I decided to use software RAID1, which is supported much better.

Phillip Susi (psusi) wrote :

Indeed, mdadm is much better supported. FYI, you might want to use raid10 instead of raid1. You can get both full redundancy of raid1, and performance comparable to raid0 that way. You want to manually create the array with mdadm though, and specify a chunk size of 512k to 4M, and to use the offset layout instead of the default near layout. My current desktop does that across 3 cheap 1 TB WD blue drives to get both good reliability and performance.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers