I solved my problem!
Recently I have published a guide on how to install linux on loopback
LVM devices booting from USB (so without have to install grub on the
internal disk, leaving it as original). Here is the guide:
https://github.com/DareDevil73/linux-on-loopback-usb .
Then I fallen in the fr
Lancillotto (antonio-petricca), it will help immensely if you filed a new
report with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I have the same problem on Ubuntu 16.04 and Kernel 4.10.0-38-generic .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526537
Title:
blk_update_request: I/O error
To manage notifications about this
D. Charles Pyle / hakuna_matata, it will help immensely if you filed a new
report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
I can confirm that the error messages on Ubuntu 16.04 (daily) still
exist but it seems that it is not as bad as it looks.
I followed the steps which Marcin described in comment #16. Instead of
> Write some data on backing file via loop device
> dd if=/dev/zero of=/mnt/Test.file bs=1M count=512
I
Still seeing this in 4.4.0 kernels on Ubuntu 16.04.
$ dmesg | grep -i blk
[5.660121] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[ 60.473635] b
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526537
T
Marcin, the next step is to fully commit bisect from kernel 3.13 to 4.2
in order to identify the last good kernel commit, followed immediately
by the first bad one. This will allow for a more expedited analysis of
the root cause of your issue. Could you please do this following
https://wiki.ubuntu.
Yes, this issue not reproducible in a release prior to 15.04 [ ex.
14.04.3 ]
** 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/1526537
Marcin, was this issue not reproducible in a release prior to 15.04?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526537
Title:
** Tags removed: kernel-bug-exists-upstream-4.4.0-040400rc5-generic
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.4-rc5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526537
T
** Tags removed: apport-collected kernel-bug-exists-4.3.0-2-generic
latest-bios-1.40 vivid wily xenial
** Tags added: kernel-bug-exists-4.4.0-040400rc5-generic
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: kernel-bug-exists-4.4.0-040400rc5-generic
** Tags
** Tags added: kernel-bug-exists-4.3.0-2-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526537
Title:
blk_update_request: I/O error
To manage notifications about this bug go to:
https://bug
Marcin, at your earliest convenience, could you please test the latest
upstream kernel available from the very top line at the top of the page
from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install
** Tags added: latest-bios-1.40
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526537
Title:
blk_update_request: I/O error
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Joseph, I encounter this problem also in ubuntu 15.04 with a linux-
image-3.19.0-15-generic.
I can append some additional information how to reproduce this issue.
After my analysis I found dependence: drive filesystem vs backing file
filesystem:
Create backing file on a drive that is formatted to
apport information
** Tags added: apport-collected xenial
** Description changed:
On my laptop I am using the ubuntu in persistent mode with a backing files:
casper-rw, home-rw. For some time in the new editions of ubuntu [ 15.04 / 15.10
/ 16.04 daily (15.12) ] I meet with error: blk_upda
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.4 kernel[0
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526537
Title:
blk_update_request: I/O error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
** Package changed: linux-meta (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/1526537
Title:
blk_update_request: I/O error
To manage notifications about this bug go to:
ht
20 matches
Mail list logo
