Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I upgraded from 16.04 to 18.04 (from kernel 4.4.0-193-generic to
4.15.0-122-generic) and I had this exact issue. Same HP Microserver Gen
8 as the others, probably there's something in their motherboard that
makes SATA disks discovery particularly slow, and the kernel (or initrd
scripts harness?) do
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Artful)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Change
I just updated to Debian "4.19.0-0.bpo.1-amd64 #1 SMP Debian
4.19.12-1~bpo9+1 (2018-12-30) x86_64 GNU/Linux"
Even without the "rootdelay" boot option, the boot process proceeds now
as it should again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Dear Christian,
Thank you for your reply.
I took another route which worked.
First i booted with kernel 4.4 normally.
I edited /usr/share/initramfs-tools/scripts/local-premount/btrfs by adding
sleep=5 before "/bin/btrfs device scan" line, then i ran the following commands:
update-initramfs -u
upda
Hi Bogdan!
Sorry to hear, that it doesn´t work for you.
I fear that you did add the parameter in the same way then I did. So there
might be some other difference.
This is my kernel cmdline (cat /proc/cmdline):
BOOT_IMAGE=/vmlinuz-4.18.0-0.bpo.3-amd64
root=UUID=bda00e2f-ad36-46eb-a81a-cceb7736ab6
Dear Christian,
Can you please detail a little how/where you added the rootdelay parameter.
I am facing the same problem with a 4 drive raid1 on a HP MicroServer Gen8, on
update from Ubuntu server 16.04 to 18.04 (kernel 4.4 to kernel 4.15).
I tried to add the parameter to /etc/default/grub in both
I did my upgrade from Debian stable to stretch-backports and therefore from 4.9
to 4.18 today.
Wrong distribution, I know ;-)
Interestingly, I´m also facing the issue on a HP MicroServer Gen8.
Reason for posting is, that I was able to work around the issue by specifying
"rootdelay=5" at the ker
v4.17 final has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications abou
Thanks for retesting. Can you test v4.17 final? It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel
I retested the last 2 builds from the original bisection, and I'm pretty
confident that the results were correct:
362f672 has the bug.
6836796 does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Mainline 4.20-rc2 has the bug.
I went back and tested mainline 4.18-rc1 and mainline 4.18 a few more
times, and they actually do have the bug. So it appears that the bug is
not fixed upstream after all.
Shall we go back to bisecting for the change that introduced the bug?
--
You received this
We may have to go back and retest for the bisect then.
A best next step would be to test the current mainline kernel and see if
the bug is already fixed upstream. It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc2/
--
You received this bug notification because you ar
It looks like I made a mistake on a previous build. I retested d60dafd,
built on 20180911, and it actually does have the bug. Sorry!
(Being an apparent race condition, a buggy kernel actually does work
sometimes.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
18f1837 has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications about th
I built the next test kernel, up to the following commit:
18f1837632783fec017fd932a812d383e3406af0
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
Agreed. 68cc38f has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications
68cc38ff33f38424d0456f9a1ecfec4683226a7e has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
I built the next test kernel, up to the following commit:
68cc38ff33f38424d0456f9a1ecfec4683226a7e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
6a8b25a has the bug.
I also tried 4.18.0-10.11 from cosmic, and it appears to still have the
bug. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for de
I rebuilt the kernel, so they should be there now:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for device
The packages appear to still be the build from 10/01.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
I built the next test kernel, up to the following commit:
6a8b25abf1b79db6877645335c73ad6a5061d9b0
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
fdea70d has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications about th
I built the next test kernel, up to the following commit:
fdea70d26a471e002f2afc3a48821323b699f1e6
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
d60dafd does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
d60dafdca4b463405e5586df923f05b10e9ac2f9
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
1c8c5a9 has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications about th
I reviewed the btrfs commits in v4.18-rc1, but the are quite a few of
them. We should perform a "Reverse" bisect to identify the correct on
that fixes this bug.
I started a "Reverse" bisect between v4.17 final and v4.18-rc1.
I built the first test kernel, up to the following commit:
1c8c5a9d38f6
Both 4.18-rc1 and 4.18-rc4 do NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To ma
Thanks for testing. We need to narrow down the specific version of 4.18
that has the fix. Can you test the following kernels:
v4.18-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1/
v4.18-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc4/
--
You received this bug notific
Both 4.15.18 and 4.17.17 have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage noti
That's good news. We now have to identify the fix in 4.18 and ensure it
is applied to Ubuntu. Can you test the following two upstream stable
kernels to see if the fix was already sent to stable:
4.15.18: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
4.17.17: http://kernel.ubuntu.com/~k
It looks like 4.18 does not have the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage
Commit 362f6729cbb1d6bbab59e069f19441b0622ff7ec was reported as the
first bad commit. However, this commit is a merge tag, so we'll need to
bisect into that merge.
Before we start that process, this bug has been open a while and 4.18
final is now available. Could you test that kernel to see if t
6836796 does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
6836796de4019944f4ba4c99a360e8250fd2e735
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
362f672 has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications about th
The latest test kernel is for commit
362f6729cbb1d6bbab59e069f19441b0622ff7ec
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices
Sorry for the delay. I missed the email regarding you're test results
of the last kernel.
I built the next test kernel, up to the following commit:
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug
Any new build to test?
This issue is still present in 4.15.0-30.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
878c33a does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
878c33a78811f90795f17333bc3a7c819a1589a7
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
409acdd does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
409acdd0412e9343095d965a9228f6e6a83a416f
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
0cf9f50 does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
0cf9f5096da2200b52cee0e38139c99c4fc0151c
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
c94dc34 does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
c94dc34f771a25b8c3e0955147fdc4f5e3d79908
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
44c891a does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
44c891af576997763d1d4c790d50d10db9eff00f
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
24040a5 does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
24040a58379e2f2fa6aa9466911b758073b6bdfa
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
4422d80 does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
4422d80ed7d4bdb2d6e9fb890c66c3d9250ba694
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
cbf4b38 does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
cbf4b3867875206aa548a8c6d7c886f3299d619e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
1b044f1 does NOT have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
I built the next test kernel, up to the following commit:
1b044f1cfc65a7d90b209dfabd57e16d98b58c5b
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
cbcd4f0 has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications about th
Sorry for the delay.
I built the next test kernel, up to the following commit:
cbcd4f08aa637b74f575268770da86a00fabde6d
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next
1849f80 has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications about th
I built the next test kernel, up to the following commit:
1849f800fba32cd5a0b647f824f11426b85310d8
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
I guess it's less ambiguous to say that e5f76a2 has the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
disc
e5f76a2e0e84ca2a215ecbf6feae88780d055c56 (4.12.0-041200.201805301435)
does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all
I started a kernel bisect between v4.12 final and v4.13-rc1. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
e5f76a2e0e84ca2a215ecbf6feae88780d055c56
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsa
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Status: Confirmed
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
FWIW, v4.12.14 also works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notifications ab
v4.12 Final works. v4.13-rc1 does not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage not
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the last kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kernel
This issue started with the version 4.13 series. The last version that
did not have the issue is 4.11.0-14.
Mainline kernel version 4.17-rc4 also exhibits the issue.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have bee
apport information
** Tags added: apport-collected apport-hook-error bionic
** Description changed:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for dev
** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
dis
This problem is still present as of 4.15.0-20.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To man
76 matches
Mail list logo