software updater ask grub setting repeated

Bug #1814364 reported by Seiichi Nakashima
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Dear everyone.

Now, I update ubuntu-18.04.1 at my desktop PC.
software updater updated, and display grub pc setting windows.
grub setting windows say to select install grub device,
/dev/sda
-/dev/sda1
/dev/sdb

my pc environment has mbr(mbm bootloader) and pbr(grub).
I asked #675171, and repare, but now new problem.

I select '-/dev/sda1' and next, and 'do not install grub' not checked,
then again select install grub device,
I select '-/dev/sda1' and next, and 'do not install grub' not checked,
repeat forever.

what actiion need to exit this probrem.

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/1814364/+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
Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

<https://www.dropbox.com/sh/beq6qrrkqv654sx/AAB1L0Y-tlmjZRJMGegfkog7a?dl=0>

I upload file at dropbox.
pic01.png to pic04.png are screen shot.
syslog file append.
I update ubuntu-18.04.1 at 16:00-17:25 japan

Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

<https://www.dropbox.com/sh/4c1dbbor07nasx9/AABD4kQrg0UH3kukdWPYImeva?dl=0>

I challenged to select grub install device /dev/sda and do not install grub.
then sortware updater finished, and kernel updated.

I send screen shot to write before.
I may solved problem.

affects: ubuntu → libinput (Ubuntu)
Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

I missed affects, perhaps grub-pc( or grub).

I have 4 desktop pc, and 1 is UEFI bios.
I use UEFI bios to legacy mode.
other 3 PCs not support UEFI.

UEFI bios PC do not occurd to display select install grub device,
and finished update. but #675171 problem occurd.
My disk(/dev/sda) have 4 partions for 4 ubuntu.
I update to use software updater ubuntu in /dev/sda4,
grub update /dev/sda1 pbr.
so I want to boot ubuntu in /dev/sda1,
but boot up ubuntu in /dev/sda4.
/dev/sda2, /dev/sda3, /dev/sda4 are work fine,
only /dev/sda4 updated to affect /dev/sda1.

I repaired /dev/sda1 pbr to use grub-install command,
but I want to update this problem.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

affects: libinput (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote : Re: [Bug 1814364] Re: software updater ask grub setting repeated

thank you mail.

I upload screenshot and syslog.
please show URL, and I resolved to exit situation.
but another problem occurd.
<https://bugs.launchpad.net/bugs/1814364>

==

2019-02-02 (土) の 23:15 +0000 に Sebastien Bacher さんは書きました:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we cannot work on this bug because your
> description didn't include enough information. You may find it
> helpful
> to read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be
> grateful
> if you would then provide a more complete description of the problem.
>
> We have instructions on debugging some types of problems at
> http://wiki.ubuntu.com/DebuggingProcedures.
>
> At a minimum, we need:
> 1. The specific steps or actions you took that caused you to
> encounter the problem.
> 2. The behavior you expected.
> 3. The behavior you actually encountered (in as much detail as
> possible).
> Thanks!
>
> ** Package changed: libinput (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

today, ubuntu software updated to use software updater.
same situation occured.

I have 4 desktop PCs, one is UEFI(legacy mode), others are legacy BIOS.
all PC has 4 partition in /dev/sda, and all partition installed ubuntu-18.04.1.

UEFI PC update to use software updater at /dev/sda4,
grub update /dev/sda1 pbr, I want to update /dev/sda4 pbr.

but legacy BIOS PC update to use software updater at /dev/sda4.
it update /dev/sda4 pbr.

Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

Dear everyone.

I update PC that has UEFI(legacy mode), and software update.
First I update /dev/sda2 (ubuntu-18.04),
and I install Hyperledger Fabric-1.4 to use docker-ce.
finished install and I reboot PC, but could not bootup.
so I grub-install /dev/sda2.

Second I update /dev/sda3 (ubuntu-18.04).
software updater do not need reboot,
I checked /var/log/syslog, '40grub2: debug: perseing' errors exist in syslog.
ubuntu-18.04 in /dev/sda2 reboot, and still boot up fine.

I upload syslog in dropbox.
I update /dev/sda2 at 16:40, and from 16:44:46, 40grub2 error exist.
<https://www.dropbox.com/sh/puvajsnc3firpqj/AAAC79KZePojpr_cab4PsSqea?dl=0>

Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

I found /dev/sda3 ubuntu-18.03 syslog has a lot of ureadahead messages at 16:50:35.
I grub-install command to use recover /dev/sda3 pbr.

I upload syslog same PC. involved all today log.
<https://www.dropbox.com/sh/w4ks9q19gd1803g/AABI2n6DSigRV_UWaJs7rUjFa?dl=0>

I update at 18:10 to use grub-install by ubuntu-18.04 livecd.
and reboot /dev/sda3 ubuntu-18.04, perhaps work fine.

Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

yestaday I update ubuntu-18.04 to use software-updater.
I update partition 4 ( /dev/sda4) ubuntu-18.04.
finished update, I shutdown PC, and today I boot up PC from /dev/sda4.
but could not bootup.

I found many error message in syslog.
why occured this?

<https://www.dropbox.com/sh/j02g0eec3l2xshf/AABK6FEfA4O0VVeLl4FBEiRNa?dl=0>

now, I use grub-install command, and I recovered /dev/sda4 ubuntu-18.04.

Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

I occured same trouble at same PC.
I clean install ubuntu-18.04.1 at PC, and now no trouble

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Seiichi Nakashima (ubuntu-linuxer) wrote :

Now I use ubuntu-18.04.3 (5.0.0-25).
this probrem cleared from ubuntu-18.04.2 at some day.

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

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.