On Tue, December 23, 2014 10:10 am, Christopher Gregory wrote: > Hello, > > > With systemd-217 they have introduced a nasty flaw/bug that ONLY effects > people who are using GPT partitions, which I am using. > > Before anyone starts and says that it can be configured and over-ridden > think twice or even three times before you say that I am wrong, because > this has been confirmed on the systemd bugzilla by Debian devleopers with > references to a user reporting the same on Arch. > > If you have the following: > > > /boot partition that has kernel images for various installations then > systemd-gpt-auto-generator will actually mount the swap partition for that > first installation, (I just can not think of the perhaps correct term > for this) and then then fail to activate the correct wanted swap partition > that is listed in fstab. > > This is the result that I get when listing the swap files that get > auto-generated: > > > root [ /run/systemd/generator.late ]# ls dev-sdb12.swap dev-sdb6.swap > swap.target.wants > > Deleting the wrong .swap file, in this case dev-sdb6.swap has absolutely > no effect upon re-boot because it is auto-generated each and every time > that the machine is booted. > > From journalctl you get the following: > > > > Dec 23 09:25:12 lfs systemd[1]: Reached target Swap. > Dec 23 09:25:12 lfs systemd[1]: Starting Swap. > Dec 23 09:25:12 lfs systemd[1]: Unit > dev-disk-by\x2duuid-2280a26b\x2d4ff4\x2d4dde\x2d9848\x2d0d9bbc999de5.swap > entered failed state. Dec 23 09:25:12 lfs systemd[1]: > dev-disk-by\x2duuid-2280a26b\x2d4ff4\x2d4dde\x2d9848\x2d0d9bbc999de5.swap > swap process exited, code=exited status=255 Dec 23 09:25:12 lfs > systemd[1]: Mounted /opt. > Dec 23 09:25:12 lfs systemd[1]: Activated swap > /dev/disk/by-uuid/2280a26b-4ff4-4dde-9848-0d9bbc999de5. > Dec 23 09:25:12 lfs systemd[1]: Activated swap Swap Partition. > Dec 23 09:25:12 lfs kernel: Adding 7167996k swap on /dev/sdb12. > Priority:-2 extents:1 across:7167996k > Dec 23 09:25:12 lfs kernel: EXT4-fs (sdb13): mounted filesystem with > ordered data mode. Opts: (null) Dec 23 09:25:12 lfs swapon[219]: swapon: > /dev/disk/by-uuid/2280a26b-4ff4-4dde-9848-0d9bbc999de5: swapon failed: > Device or resource busy > Dec 23 09:25:12 lfs systemd[1]: Activating swap > /dev/disk/by-uuid/2280a26b-4ff4-4dde-9848-0d9bbc999de5... > Dec 23 09:25:12 lfs systemd[1]: Activating swap Swap Partition... > Dec 23 09:25:12 lfs systemd[1]: Found device TOSHIBA_MQ01ABD050 12. > Dec 23 09:25:12 lfs systemd[1]: Found device TOSHIBA_MQ01ABD050 12. > Dec 23 09:25:12 lfs systemd[1]: Activated swap Swap Partition. > Dec 23 09:25:12 lfs kernel: Adding 6143996k swap on /dev/sdb6. > Priority:-1 extents:1 across:6143996k > > > This is really just information for those who do use gpt (GUID Partition > Table). > > > The Debian confirmed report is at: > > > https://bugs.freedesktop.org/show_bug.cgi?id=86930 > > > There is another, which I have replied to at: > > > https://bugs.freedesktop.org/show_bug.cgi?id=87230 > > > I have no idea if the replies are actually from systemd developers or > just others who think that this should be fixed. > > Needless to say that for my next installation, until I know that this has > been fixed I am reverting to a version of systemd that does not have > this bug. > > Regards, > > > Christopher
The only fix for this is to use gptfdisk and set the attribute of the swap partions to 63: do not automount. This totaly turns off systemd-gpt-auto-generator and also corrects the other bug of systemd trying to mount a swap partition that was already mounted by the Kernel and producing an error for failed dependency in journalctl. Regards, Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
