[Bug 1828712] Re: I/O errors when trying to loop mount an image

2020-04-19 Thread codywohlers
Update: My `print_req_error: I/O error` errors went away after writing
some files to the image, unmounting it and running `e2fsck -f` again.
No errors reported from e2fsck but after I didn't get the print_req
errors anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828712

Title:
  I/O errors when trying to loop mount an image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828712] Re: I/O errors when trying to loop mount an image

2020-04-18 Thread codywohlers
possibly related:

This happened to me too after I resized an ext4 image file from 50G to
99G.  Ever since then when I mount it I get the same error except
starting a higher sector.  If I unmount it and mount it again I get
errors for different sectors.  And `e2fsck -f` didn't find any error on
the image.

`EXT4-fs (loop3): mounted filesystem with ordered data mode. Opts: (null)
print_req_error: I/O error, dev loop3, sector 197148928
print_req_error: I/O error, dev loop3, sector 197153024
...`

system:
`Ubuntu 18.04.4 LTS bionic
Linux 4.15.0-91-generic x86_64
libmount1:amd64 2.31.1-0.4ubuntu3.6`

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828712

Title:
  I/O errors when trying to loop mount an image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828712] Re: I/O errors when trying to loop mount an image

2019-05-17 Thread James Harris
@brian-murray thanks for the suggestion. Have done you suggest but
apport-cli on the system with the GUI does not seem to allow an existing
bug to be updated with the info, so rather than generating a new bug
report am copying the file generated by apport-cli --save below.

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Fri May 17 10:50:14 2019
Dependencies:
 adduser 3.116ubuntu1
 apt 1.6.10
 apt-utils 1.6.10
 busybox-initramfs 1:1.27.2-2ubuntu3.2
 ca-certificates 20180409
 coreutils 8.28-1ubuntu1
 cpio 2.12+dfsg-6
 debconf 1.5.66
 debconf-i18n 1.5.66
 dmsetup 2:1.02.145-4.1ubuntu3
 dpkg 1.19.0.5ubuntu2.1
 fdisk 2.31.1-0.4ubuntu3.3
 gcc-8-base 8.3.0-6ubuntu1~18.04
 gettext-base 0.19.8.1-6ubuntu0.3
 gpgv 2.2.4-1ubuntu1.2
 grub-common 2.02-2ubuntu8.13
 grub-gfxpayload-lists 0.7
 grub-pc 2.02-2ubuntu8.13
 grub-pc-bin 2.02-2ubuntu8.13
 grub2-common 2.02-2ubuntu8.13
 init-system-helpers 1.51
 initramfs-tools 0.130ubuntu3.7
 initramfs-tools-bin 0.130ubuntu3.7
 initramfs-tools-core 0.130ubuntu3.7
 klibc-utils 2.0.4-9ubuntu2
 kmod 24-1ubuntu3.2
 libacl1 2.2.52-3build1
 libapt-inst2.0 1.6.10
 libapt-pkg5.0 1.6.10
 libattr1 1:2.4.47-2build1
 libaudit-common 1:2.8.2-1ubuntu1
 libaudit1 1:2.8.2-1ubuntu1
 libblkid1 2.31.1-0.4ubuntu3.3
 libbz2-1.0 1.0.6-8.1
 libc6 2.27-3ubuntu1
 libcap-ng0 0.7.7-3.1
 libdb5.3 5.3.28-13.1ubuntu1
 libdevmapper1.02.1 2:1.02.145-4.1ubuntu3
 libfdisk1 2.31.1-0.4ubuntu3.3
 libffi6 3.2.1-8
 libfreetype6 2.8.1-2ubuntu2
 libfuse2 2.9.7-1ubuntu1
 libgcc1 1:8.3.0-6ubuntu1~18.04
 libgcrypt20 1.8.1-4ubuntu1.1
 libgmp10 2:6.1.2+dfsg-2
 libgnutls30 3.5.18-1ubuntu1
 libgpg-error0 1.27-6
 libgpm2 1.20.7-5
 libhogweed4 3.4-1
 libidn2-0 2.0.4-1.1build2
 libklibc 2.0.4-9ubuntu2
 libkmod2 24-1ubuntu3.2
 liblocale-gettext-perl 1.07-3build2
 liblz4-1 0.0~r131-2ubuntu3
 liblzma5 5.2.2-1.3
 libmount1 2.31.1-0.4ubuntu3.3
 libncurses5 6.1-1ubuntu1.18.04
 libncursesw5 6.1-1ubuntu1.18.04
 libnettle6 3.4-1
 libp11-kit0 0.23.9-2
 libpam-modules 1.1.8-3.6ubuntu2.18.04.1
 libpam-modules-bin 1.1.8-3.6ubuntu2.18.04.1
 libpam0g 1.1.8-3.6ubuntu2.18.04.1
 libpcre3 2:8.39-9
 libpng16-16 1.6.34-1ubuntu0.18.04.2
 libprocps6 2:3.3.12-3ubuntu1.1
 libseccomp2 2.3.1-2.1ubuntu4.1
 libselinux1 2.7-2build2
 libsemanage-common 2.7-2build2
 libsemanage1 2.7-2build2
 libsepol1 2.7-1
 libsmartcols1 2.31.1-0.4ubuntu3.3
 libssl1.1 1.1.0g-2ubuntu4.3
 libstdc++6 8.3.0-6ubuntu1~18.04
 libsystemd0 237-3ubuntu10.21
 libtasn1-6 4.13-2
 libtext-charwidth-perl 0.04-7.1
 libtext-iconv-perl 1.7-5build6
 libtext-wrapi18n-perl 0.06-7.1
 libtinfo5 6.1-1ubuntu1.18.04
 libudev1 237-3ubuntu10.21
 libunistring2 0.9.9-0ubuntu2
 libuuid1 2.31.1-0.4ubuntu3.3
 libzstd1 1.3.3+dfsg-2ubuntu1
 linux-base 4.5ubuntu1
 linux-modules-4.18.0-18-generic 4.18.0-18.19~18.04.1
 lsb-base 9.20170808ubuntu1
 openssl 1.1.0g-2ubuntu4.3
 os-prober 1.74ubuntu1
 passwd 1:4.5-1ubuntu2
 perl-base 5.26.1-6ubuntu0.3
 procps 2:3.3.12-3ubuntu1.1
 psmisc 23.1-1ubuntu0.1
 sensible-utils 0.0.12
 tar 1.29b-2ubuntu0.1
 ubuntu-keyring 2018.09.18.1~18.04.0
 ucf 3.0038
 udev 237-3ubuntu10.21
 update-motd 3.6-0ubuntu1
 util-linux 2.31.1-0.4ubuntu3.3
 uuid-runtime 2.31.1-0.4ubuntu3.3
 zlib1g 1:1.2.11.dfsg-0ubuntu2
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-25 (1299 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
Package: linux-image-4.18.0-18-generic 4.18.0-18.19~18.04.1
PackageArchitecture: amd64
ProcCpuinfoMinimal:
 processor  : 0
 vendor_id  : GenuineIntel
 cpu family : 6
 model  : 42
 model name : Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz
 stepping   : 7
 cpu MHz: 2494.338
 cache size : 8192 KB
 physical id: 0
 siblings   : 1
 core id: 0
 cpu cores  : 1
 apicid : 0
 initial apicid : 0
 fpu: yes
 fpu_exception  : yes
 cpuid level: 13
 wp : yes
 flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc rep_good 
nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq monitor ssse3 
cx16 sse4_1 sse4_2 popcnt aes xsave avx hypervisor lahf_lm pti
 bugs   : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
 bogomips   : 4988.67
 clflush size   : 64
 cache_alignment: 64
 address sizes  : 36 bits physical, 48 bits virtual
 power management:
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
 TERM=ansi
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
SourcePackage: linux-signed-hwe
Tags:  bionic
Uname: Linux 4.18.0-18-generic x86_64
UpgradeStatus: Upgraded to bionic on 2019-02-08 (97 days ago)
_MarkForUpload: True

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828712

Title:
  I/O errors when trying 

[Bug 1828712] Re: I/O errors when trying to loop mount an image

2019-05-13 Thread Brian Murray
apport-cli contains an option for save the report from another machine.
apport-cli --help says:

  --save=PATH   In bug filing mode, save the collected information
into a file instead of reporting it. This file can
then be reported later on from a different machine.

and:

  -c PATH, --crash-file=PATH
Report the crash from given .apport or .crash file
instead of the pending ones in /var/crash. (Implied if
file is given as only argument.)

However, this doesn't work with apport-collect but if the Ubuntu Kernel
Bot still wants this you could open a new bug report using --save and
the --crash-file.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828712

Title:
  I/O errors when trying to loop mount an image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828712] Re: I/O errors when trying to loop mount an image

2019-05-13 Thread James Harris
Sorry I cannot run apport-collect as the machine has no GUI. I have
tried the command on the console and via ssh but the resulting text-mode
screen seems to prevent me entering my email address to log in.

I also tried apport-cli but it had the same problem with the same
authentication screen.

As for logs, I did include the relevant syslog entries in the original
report, if that helps.


** 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/1828712

Title:
  I/O errors when trying to loop mount an image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828712] Re: I/O errors when trying to loop mount an image

2019-05-13 Thread James Harris
Setting package to linux kernel as advised for a filesystem issue.

Ran apport-collect -p linux 1828712 per the instructions but I don't
know that it worked as machine has no GUI.


** Package changed: 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/1828712

Title:
  I/O errors when trying to loop mount an image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828712] Re: I/O errors when trying to loop mount an image

2019-05-12 Thread Ubuntu Foundations Team Bug Bot
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/1828712/+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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828712

Title:
  I/O errors when trying to loop mount an image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1828712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs