I boot from ZFS so that datapool will be root mounted. That same
datapool has been used in the past exclusively for Virtual Machines,
later I added the datasets for the host OSes to the same datapool,
because they were at the begin of my SSHD. So that datapool contains
datasets with Virtualbox VMs
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846424
Title:
19.10 ZFS Update failed on 2019-10-02
Status
I think we have two bugs:
- one is about dmesg is reporting the wrong versions
- the other is about a failing zfs upgrade, if we boot from ZFS. Why mount the
system again? It has already been mounted during the boot and all other non-zfs
package updates have been completed without problems.
--
I have done a fresh install of zfsutils-linux on another system booted
from ext4. Ubuntu Mate 19.10. Also there the system is confused about
the module installed. See install and the result of dmesg.
** Attachment added: "zfs-update-bug3"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bu
ON the system that I boot from ext4, the system is confused about which
zfs module is loaded, see attachment.
** Attachment added: "zfs-update-bug2"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+attachment/5293869/+files/zfs-update-bug2
--
You received this bug notificati
I tried removing zfs-dkms, but in the VM with Ubuntu 19.10, it said module not
installed. In that system I boot from ext4.
On my laptop with Ubuntu Mate I boot from ZFS and there, it produced the
following errors, see attachment.
** Attachment added: "zfs-update-bug"
https://bugs.launchpad.
Public bug reported:
On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb failed
the same is true for zfs-zed and zfsutils-linux.
The system still runs on 0.8.1-1ubuntu11_amd64.
The first error message was about a failing mount and at the end it announced
that all 3 modules w
Some additional info from conky about the configuration:
** Attachment added: "Screenshot from 2019-09-26 12-09-32.png"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843222/+attachment/5291518/+files/Screenshot%20from%202019-09-26%2012-09-32.png
--
You received this bug notificat
Note that I only can use the datapools after I exported and re-imported
them again. But I have to do that on all boots, so I wrote a small
script for it. I did not upgrade the datapool itself, because 2 of the 3
systems still run Ubuntu 19.04 one also from the zfs systems datapool
and the other fro
OK I did upgrade one of my desktop OSes (ubuntu Mate 19.04). It has been
running on a Ryzen 3 2200G, but initially it has been installed on a
Phenom II X4 B97 with a GeForce 8400GS. So maybe you see some nvidea
related error too, I did not purge that module, I did forget all about
it. This syst
My laptop has been completely upgraded. I will try it on one of the two
systems on my Ryzen desktop both still running 19.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1843222
Tit
I have two datapools one in the begin of the HDD for the Host OSes and
Virtual Machines and one at the end for data, music, family videos and
relatively large old archives. The throughput at the begin of the HDD is
often twice the throughput at the end of the HDD, so I have a very good
reason to pu
I did add an entry with two /boot/grub/grub.cfg files and one did
include my 40_custom file. That file did include "This" but in the first
comment line as shown below:
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries y
It has been an error during the upgrade itself, since a fresh install
solved my problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1843222
Title:
Old Linux version booted after
Public bug reported:
I have 2 systems installed on ZFS
- Ubuntu Mate 18.04.3
- Xubuntu 19.10
For the coming period I like to keep one ext4 installation, so I did do
a fresh install of Ubuntu 19.10 on the ext4 sda1 partition. I installed
zfsutils-linux and rebooted. Afterwards I did run "update-gr
Two other relevant files from /boot/grub.
"grub.cfg" the one used with 5.0 and "grub.cfg.new" NOT used and with Linux 5.2.
** Attachment added: "grub.zip"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843222/+attachment/5287546/+files/grub.zip
--
You received this bug notificati
Public bug reported:
I have upgraded my dual boot laptop (Xubuntu 19.04 on ZFS) to 19.10, I
only had a minor problems:
The system started scrubbing the exisisting datapools.
In the scrub I have been notified, that my datapool did not support all new
features and that I had to upgrade the datapoo
Public bug reported:
I have upgraded my dual boot laptop (Xubuntu 19.04 on ZFS) to 19.10, I
only had a minor problem:
The system on boot did start scrub of all datapools automatically, that was
unexpected and it took a couple of minutes before I realized, why the system
was that effing slow
I did see a number of red error messages, but I did see the same or
almost the same error messages in the upgrade of my zfs based Xubuntu
and that one worked afterwards without any problem. So I probably
ignored those error messages.
On 9/9/19 2:35 a. m., Didier Roche wrote:
> Thanks for test
Public bug reported:
I have a triple boot with the following systems:
- Xubuntu 19.10 from zfs 0.8.1
- Ubuntu Mate 18.04.3 from zfs 0.7.12
- Ubuntu 19.10 from ext4
Upgrading the first system Xubuntu to 19.10 worked fine and I was very happy
with the almost perfect result and the nice grub-menu.
Public bug reported:
Happened during an upgrade from Xubuntu 18.04 to Xubuntu 18.10. But ZFS
did work OK after upgrade.
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: zfs-dkms 0.7.9-3ubuntu6
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
I can't reproduce the problem on Linux 4.15.0-13. I reinstalled
Lollypop, but no crashes. Only a completely other crash of Lollypop
itself, every time I change the album art.
I think, it might be one of those crashes, that occur once a week or so.
Sorry, I keep looking.
On 12/04/18 16:14, Jos
Public bug reported:
Playing lollypop while lollypop is scanning its library for the first
time
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
A
I update the system each day, so I assume it has been introduced this
week.
On 27-03-18 17:39, Joseph Salisbury wrote:
> 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
Yes, I update the system each day, so it has been introduced this week.
On 27-03-18 17:16, Joseph Salisbury wrote:
> 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 t
Public bug reported:
Crash happened after booting the system
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
Annotation: Your system might become
Public bug reported:
Crash occured after reboot of the Saturday update.
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
Annotation: Your system mi
Up to now it has been a one time event.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1749329
Title:
BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1
Status in linux package
Public bug reported:
No additional information.
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
Annotation: Your system might become unstable now
Public bug reported:
Trying to play music using Rhytmbox
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-17-generic 4.13.0-17.20 [modified:
boot/vmlinuz-4.13.0-17-generic]
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_
Forgot to mention the other Ubuntu Betas (L-, X- and Mate) have no
problem and work normally.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1718713
Title:
upon reboot monitor came up wi
I have the same problem running the Ubuntu Beta in Virtualbox with as far as I
remember 4.13.0.11. All other Ubuntu Betas (L-, X- and Mate) did use that Linux
version too. I tried a fresh install from the latest second daily build of 26-9
with the same result. The symptom is a VM-screen that swi
Public bug reported:
I have 12,000 files in my music library, the scanning of the library
stopped after # 3,085. It stayed on that number for say 1 minute and
afterwards this crash happened.
ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-11-generic 4.13.0-11.12
Pr
Public bug reported:
Spontaneous after boot
ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-13-generic 4.12.0-13.14
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
Annotation: Your system might become unstable now and
Forget to mention, it is all happening in a Virtual Machine of
Virtualbox 5.1.26 r117224 (Qt5.5.1) with 3D enabled for this Guest.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1717132
Ti
Public bug reported:
I just started firefox 56.0b3, but it opened normally;
ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-13-generic 4.12.0-13.14
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
Annotation: Your syst
101 - 136 of 136 matches
Mail list logo
