Even after removing all drive partitions from the ZFS drives, I am still
having this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770173
Title:
18.04 install stuck on grub install when a
I have just run into this same problem on both 18.04 Server and 19.04
Server Beta. After finding this bug report, I unplugged the drive array
full of ZFS disks and the local write cache disk only to still run into
the issue due to my nvme used for read cache.
--
You received this bug notification
same bug, when I install
http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.1-server-
amd64.iso with kinston datatraveler 2.0
I write ubuntu-18.04.1-server-amd64.iso into kinston with rufus-3.1p
The host machine is Think server ts250 with 2 1TB SATA hard disk, host
raid 1.
tail /var
So it looks like it is getting stuck running this command:
31197 root 26996 Sdmsetup create -r osprober-linux-sdb1
It also looks like in the cases where it does not hang, there is a
message about not recognizing what filesystem is in /dev/sdb1 and it
can't be mounted, but in the one where
Ok, new experiment. I'm including the steps here and in an attached
README along with outputs captured at various points in the process in a
tar.gz file.
I've moved drives around throughout this debugging process, but for this
experiment they were;
/dev/sda - 80GB spinner (os install drive)
/dev/
-- I'm still not seeing the output of os-prober with the set -x option
working.
I updated /target/usr/bin/os-prober with the -x option added. I was
expecting it to show up in the syslog. Apparently still having trouble
following the twisty maze of passages all alike. I will try again.
-- Also you
Strange, yes, a USB stick should not cause it to hang. I'm still not
seeing the output of os-prober with the set -x option working. Also you
were able to manually run it with this zfs usb stick plugged in and it
did not hang right?
--
You received this bug notification because you are a member
** Attachment added: "ps.log.postgrub"
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1770173/+attachment/5155893/+files/ps.log.postgrub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770
Problem solved. There was a USB stick plugged directly in to the
motherboard which I had forgotten about since changing this box over
from a freeNAS install. Once that was removed, the install completed
with no hangup.
I'll include the output from the point where it was hung. Both from ps,
and fro
** Attachment added: "syslog.postgrub"
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1770173/+attachment/5155894/+files/syslog.postgrub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770
If it isn't os-prober that hung, then I'll have to look up the next step
the installer takes. Or you might see some other program in ps that is
hung and the installer is waiting on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Ok, I understand now what your previous question meant.
Yes, I believe the os-prober completed normally (returned to the command
prompt) with the output as in the previously attached os-prober.log. I
ran it with 2>&1, so both stdout and stderr would be included in that
file, and I didn't notice an
The interesting information I'm trying to get is exactly where os-prober
froze, so if it finishes correctly then that information isn't going to
help. I think at that point in the installer if you look, you will see
the hard disk mounted under /target, and it has its own copy of os-
prober, so mak
Sorry, this is my first time trying to debug os-level installer. I don't
know how to switch the install from auto to manual, then back to auto.
I ran the auto install through to the point where it was waiting for me
to confirm the grub install on the master boot record, where I would
normally say
Did it get stuck that time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770173
Title:
18.04 install stuck on grub install
To manage notifications about this bug go to:
https://bugs.launchpad.net
I've attached the os-prober output when run as the install was waiting
for me to confirm installing grub on the master boot record.
** Attachment added: "os-prober.log"
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1770173/+attachment/5155546/+files/os-prober.log
--
You received t
Hrm.. if the second line shows "set -ex" then running os-prober should
produce a lot of debug output showing every line of the script that is
executed. Oh, try running it yourself instead of letting the installer
do it.
--
You received this bug notification because you are a member of Ubuntu
Bug
Yes, its reproducible.
Dell PowerEdge T110 (circa ~2009). I can give more details if it would
be helpful.
I found a /bin/os-prober (no /usr/bin/os-prober), and added the x
option. Resulting syslog is the same as before, no additional
information. Is there another file I should be looking in?
--
What sort of system is this on and can you reproduce it? If so can you
edit /usr/bin/os-prober and add an x to the set -e line at the top of it
then reproduce the issue to get more information?
** Changed in: os-prober (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug no
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: os-prober (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770173
Title:
20 matches
Mail list logo
