Small fixes done.
** Attachment removed: "script for /etc/initramfs-tools/scripts/local-bottom"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1639500/+attachment/4773061/+files/zfs-boot-snap
** Attachment removed: "zfs-systemd-snap"
Small fixes done.
** Attachment added: "zfs-systemd-snap"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1639500/+attachment/4774848/+files/zfs-systemd-snap
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
** Attachment added: "zfs-mount.service"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1639500/+attachment/4773689/+files/zfs-mount.service
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
For the additional pools one might have, I adapted the script so it
snapshots everything else.
To trigger the script I added a new service zfs-import-scan.service, and
I adapted the existing zfs-mount.service to include it. This way
additional zpools will be snapshotted right after being
** Attachment added: "zfs-import-snap.service"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1639500/+attachment/4773688/+files/zfs-import-snap.service
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
No errors encountered using the PPA.
--
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/1571241
Title:
ZFS initrd script does not import zpool using /dev/disk/by-id device
paths
No errors encountered using the PPA.
--
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/1577057
Title:
zfs initrd script fails when rootdelay boot option is set
Status in zfs-linux
Here are the test results:
- no datasets mounted when it breaks
- A delay of 1 second is not enough: breaks on first try
- Retested with 5 seconds delay: ok
- Retested with new zfs script: notok, again the pool is busy error.
I had a quick look at the script and I found the remaining problem:
Dear
As far as I'm concerned it is ok to close this bug. I indeed upgraded to
14.04 in the meantime.
Kind regards
Sam
--
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/1222197
Title:
I am definitely booting in EFI, as my laptop does not have a Bios
enabled bootloader installed.
Installation from USB will probably bring you in Bios mode though
meaning you will have to fix the EFI afterwards.
--
You received this bug notification because you are a member of Kernel
Packages,
Hi Steve
Thank you for this workaround, I confirm this also works for me!
I _think_ this brings you in USB bios mode per default when installing?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I confirm the bug still exists in latest mainline kernel
3.12.0-031200rc5.
Can we please increase the priority on this? If I would have followed
the 13.04 dist upgrade suggestion, I would have ended up with a non-
functional system. This is an Ubuntu promoted machine!
--
You received this bug
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
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/1234546
Title:
Plymouth screen refresh is bad when Live USB is started
I confirm this bug and I would like to extend it: it is not limited to
the installer LiveUSB. When using the Dell XPS 13 and booting using
UEFI, the screen goes crazy with lots of ghost images etc. as the OP
describes.
I unfortunately use EFI to boot several instances of Ubuntu, making
saucy
Public bug reported:
Since installing the latest kernel 3.8.0-30 on my Dell XPS 13, I can
only use the screen on lowest dim/brightness. Hardware keys as well as
System Settings have no effect on the dim level.
I already had issues with the brightness settings before. To make
hardware keys and
15 matches
Mail list logo