[Touch-packages] [Bug 1848180] [NEW] LVM initrd fails to activate btrfs multidevice root
Public bug reported: I have two lvm volumes (/dev/mapper/raid-btrfs and /dev/mapper/fast- btrfs) in two different volume groups. I have created a btrfs (raid1) filesystem on top of them and that's my root filesystem. If i define it by UUID in the root= kernel argument, i just hit bug #1574333. Forcing my root to "/dev/mapper/fast-btrfs" by defining GRUB_DEVICE in /etc/default/grub works around that bug. The problem now is that initrd is only activating the device given as root= argument, leaving the other inactive; consequently the btrfs mount fails to find its second device and the system fails to boot giving up at initramfs prompt. Manually adding a line to activate also 2nd device at the bottom of /usr/share/initramfs-tools/scripts/local-top/lvm2 and rebuilding the initramfs works around this issue too, but i suppose my mods will be washed away by next package upgrade. Here is the result: > activate "$ROOT" > activate "$resume" > activate "/dev/mapper/raid-btrfs" Proposed solution: I understand this is an uncommon setup and correctly handling multidevice LVM roots is complicated, please just add a configuration option to manually define/append the list of volume groups to be activated at initrd time. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Description changed: I have two lvm volumes (/dev/mapper/raid-btrfs and /dev/mapper/fast- btrfs) in two different volume groups. I have created a btrfs (raid1) filesystem on top of them and that's my root filesystem. - If i define it bu UUID in the root= kernel argument, i just hit bug + If i define it by UUID in the root= kernel argument, i just hit bug #1574333. Forcing my root to "/dev/mapper/fast-btrfs" by defining GRUB_DEVICE in /etc/default/grub works around that bug. The problem now is that initrd is only activating the device given as root= argument, leaving the other inactive; consequently the btrfs mount fails to find its second device and the system fails to boot giving up at initramfs prompt. Manually adding a line to activate also 2nd device at the bottom of /usr/share/initramfs-tools/scripts/local-top/lvm2 and rebuilding the initramfs works around this issue too, but i suppose my mods will be washed away by next package upgrade. Here is the result: > activate "$ROOT" > activate "$resume" > activate "/dev/mapper/raid-btrfs" Proposed solution: I understand this is an uncommon setup and correctly handling multidevice LVM roots is complicated, please just add a configuration option to manually define/append the list of volume groups to be activated at initrd time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1848180 Title: LVM initrd fails to activate btrfs multidevice root Status in lvm2 package in Ubuntu: New Bug description: I have two lvm volumes (/dev/mapper/raid-btrfs and /dev/mapper/fast- btrfs) in two different volume groups. I have created a btrfs (raid1) filesystem on top of them and that's my root filesystem. If i define it by UUID in the root= kernel argument, i just hit bug #1574333. Forcing my root to "/dev/mapper/fast-btrfs" by defining GRUB_DEVICE in /etc/default/grub works around that bug. The problem now is that initrd is only activating the device given as root= argument, leaving the other inactive; consequently the btrfs mount fails to find its second device and the system fails to boot giving up at initramfs prompt. Manually adding a line to activate also 2nd device at the bottom of /usr/share/initramfs-tools/scripts/local-top/lvm2 and rebuilding the initramfs works around this issue too, but i suppose my mods will be washed away by next package upgrade. Here is the result: > activate "$ROOT" > activate "$resume" > activate "/dev/mapper/raid-btrfs" Proposed solution: I understand this is an uncommon setup and correctly handling multidevice LVM roots is complicated, please just add a configuration option to manually define/append the list of volume groups to be activated at initrd time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565367] [NEW] Lightdm fails to show login screen
Public bug reported: Hello, there! When I start the PC, it boots correctly. Lightdm starts and shows the login prompt for about 1-2 seconds, then the screen goes black, like lightdm just crashed. If i CTRL+ALT+F5-F9, lightdm is gone, there is no more graphical screen prompting for login. If i CTRL+ALT+F1, i can login into the terminal and inspect the problem: - "service lightdm status" still reports lightdm as "active (running)", even if no lightdm screen can be found - "ps aux | grep lightm" shows many lightdm-related processes still running The log (attached) complains about being unable to autologin, but i have automatic login disabled. I suspect this is somewhat related to suspension/resume, because it started to happen after I've tried to use it. When I issue a "service lightdm restart", lightdm restarts and this time it works correctly (it shows the login screen, then "blinks" the screen to black after 1-2 secs like it is about to get stuck again, but this time it recovers back to the login prompt and allows me to login). Here is my lightdm.conf: " [SeatDefaults] allow-guest=false autologin-guest=false #autologin-user= #greeter-session=lightdm-kde-greeter greeter-session=lightdm-gtk-greeter #user-session=kde-plasma user-session=xfce4-session [VNCServer] enabled=false [XDMCPServer] enabled=false " Thank you for reading. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 3 00:10:26 2016 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to wily on 2015-10-31 (154 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1565367 Title: Lightdm fails to show login screen Status in lightdm package in Ubuntu: New Bug description: Hello, there! When I start the PC, it boots correctly. Lightdm starts and shows the login prompt for about 1-2 seconds, then the screen goes black, like lightdm just crashed. If i CTRL+ALT+F5-F9, lightdm is gone, there is no more graphical screen prompting for login. If i CTRL+ALT+F1, i can login into the terminal and inspect the problem: - "service lightdm status" still reports lightdm as "active (running)", even if no lightdm screen can be found - "ps aux | grep lightm" shows many lightdm-related processes still running The log (attached) complains about being unable to autologin, but i have automatic login disabled. I suspect this is somewhat related to suspension/resume, because it started to happen after I've tried to use it. When I issue a "service lightdm restart", lightdm restarts and this time it works correctly (it shows the login screen, then "blinks" the screen to black after 1-2 secs like it is about to get stuck again, but this time it recovers back to the login prompt and allows me to login). Here is my lightdm.conf: " [SeatDefaults] allow-guest=false autologin-guest=false #autologin-user= #greeter-session=lightdm-kde-greeter greeter-session=lightdm-gtk-greeter #user-session=kde-plasma user-session=xfce4-session [VNCServer] enabled=false [XDMCPServer] enabled=false " Thank you for reading. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 3 00:10:26 2016 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to wily on 2015-10-31 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1565367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553907] [NEW] fsck man page refers to missing -p option
Public bug reported: Hello there, in the fsck man mage there are references to a '-p' option: -s says it must be used in conjunction with -a or p -a suggests -p is probably better to use instead of -a Anyway, there is no -p option in the man page. There is -P but, for what I know, options are case-sensitive so it's not related. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: util-linux 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 7 08:24:33 2016 SourcePackage: util-linux UpgradeStatus: Upgraded to wily on 2015-10-31 (128 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1553907 Title: fsck man page refers to missing -p option Status in util-linux package in Ubuntu: New Bug description: Hello there, in the fsck man mage there are references to a '-p' option: -s says it must be used in conjunction with -a or p -a suggests -p is probably better to use instead of -a Anyway, there is no -p option in the man page. There is -P but, for what I know, options are case-sensitive so it's not related. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: util-linux 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 7 08:24:33 2016 SourcePackage: util-linux UpgradeStatus: Upgraded to wily on 2015-10-31 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1553907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 104190] Re: df does not list root directory
I have same problem un lastest ubuntu: # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.10 DISTRIB_CODENAME=utopic DISTRIB_DESCRIPTION=Ubuntu 14.10 # uname -a Linux hostname 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:27:29 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/fstab | grep -v '^#' proc /proc proc nodev,noexec,nosuid0 0 UUID=a0e530b0-5fa6-4042-aefc-18c5cc2e2263 / ext4 discard,errors=remount-ro 0 1 UUID=6572056d-e925-40df-8408-fcfa572521df /home jfs defaults 0 2 UUID=d5234c1a-ee6a-4acd-97b2-bfe7c09e8123 /varreiserfs defaults 0 2 UUID=7eb9e3dd-e7c5-4141-8849-ba32cbdc4daf /var/logext4 defaults 0 2 /dev/mapper/swap noneswap sw 0 0 tmpfs /tmptmpfs nodev,nosuid,mode=1777 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0 # cat /etc/mtab /dev/sda1 / ext4 rw,discard,errors=remount-ro 0 0 proc /proc proc rw,nodev,noexec,nosuid 0 0 sysfs /sys sysfs rw,nodev,noexec,nosuid 0 0 none /sys/fs/cgroup tmpfs rw,uid=0,gid=0,mode=0755,size=1024 0 0 none /sys/fs/fuse/connections fusectl rw 0 0 none /sys/kernel/debug debugfs rw 0 0 none /sys/kernel/security securityfs rw 0 0 udev /dev devtmpfs rw,mode=0755 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0 tmpfs /tmp tmpfs rw,nodev,nosuid,mode=1777 0 0 tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0 none /run/lock tmpfs rw,nodev,noexec,nosuid,size=5242880 0 0 none /run/shm tmpfs rw,nosuid,nodev 0 0 none /run/user tmpfs rw,nodev,noexec,nosuid,size=104857600,mode=0755 0 0 none /sys/fs/pstore pstore rw 0 0 /dev/md3 /var reiserfs rw 0 0 /dev/md4 /var/log ext4 rw 0 0 /dev/md7 /home jfs rw 0 0 /etc/hylafax /var/spool/hylafax/etc none rw,bind 0 0 # df Filesystem 1K-blocks Used Available Use% Mounted on /etc/hylafax 709375250041721706196 75% /var/spool/hylafax/etc none 4 0 4 0% /sys/fs/cgroup udev 1526692 41526688 1% /dev tmpfs1540660 286001512060 2% /tmp tmpfs 308136 14352 293784 5% /run none5120 8 5112 1% /run/lock none 1540660 01540660 0% /run/shm none 102400 0 102400 0% /run/user /dev/md324412368 14240640 10171728 59% /var /dev/md4 281699212387721415408 47% /var/log /dev/md7 939391028 799602024 139789004 86% /home # df -a Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 - - -- / proc 0 0 0- /proc sysfs 0 0 0- /sys none 4 0 4 0% /sys/fs/cgroup none 0 0 0- /sys/fs/fuse/connections none 0 0 0- /sys/kernel/debug none 0 0 0- /sys/kernel/security udev 1526692 41526688 1% /dev devpts 0 0 0- /dev/pts tmpfs1540660 286001512060 2% /tmp tmpfs 308136 14356 293780 5% /run none5120 8 5112 1% /run/lock none 1540660 01540660 0% /run/shm none 102400 0 102400 0% /run/user none 0 0 0- /sys/fs/pstore /dev/md324412368 14240652 10171716 59% /var /dev/md4 281699212388281415352 47% /var/log /dev/md7 939391028 799602024 139789004 86% /home /etc/hylafax 709375250041721706196 75% /var/spool/hylafax/etc # df /dev/sda1 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/sda17093752 5004172 1706196 75% / ** Changed in: coreutils (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/104190 Title: df does
