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 Kernel
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
@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
ApportV
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 fr
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
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 Kern
6 matches
Mail list logo
