Am 26.07.2014 21:33, schrieb Brian Julin: > > Michael Biebl wrote: >> Am 26.07.2014 20:10, schrieb Brian Julin: >>> 3) If you enable "quiet" and run the recovery mode, you will get login >>> prompts >>> within a minute or two. You will get two login prompts running >>> simultaneously. >>> Once you have provided a password to one of the prompts, the other will >>> start >>> stealing every other character you type. To get out of this you can type a >>> sleep >>> command to the first shell by hitting enter after every character, then >>> after >>> you have successfully put that shell to sleep, you can provide the password >>> again >>> and get a mostly usable shell. 50/50 chance the shell will have echo on, >>> so you >>> may not be able to see what you are typing. >> >> If I use "emergency" on the kernel command line, I can boot into >> emergency mode without any issues, no matter if I have enabled quiet or not. > > You may need to have a dependency failure for the boot target to see this > behavior. > >> Since you are able to reproduce this issue, are you open for further >> debugging? > > Sure, what's needed? To start: > > root@charon:/home/bri# blkid > /dev/sda1: TYPE="swap" UUID="62d7daa5-5064-4b07-b06a-479722490aea" > /dev/sda2: UUID="fb01de48-f1fc-480a-90fc-15d6f858ec0e" TYPE="ext2" > /dev/sda3: UUID="aa676cc9-5f75-45f2-b039-c44283df8c4b" TYPE="ext3" > SEC_TYPE="ext2" > > And here are some random junk from the logs that might serve as starting > clues: > > Jul 26 13:38:51 charon systemd-udevd[330]: specified group 'nvram' unknown > Jul 26 13:38:51 charon systemd-udevd[330]: specified user 'tss' unknown > Jul 26 13:38:51 charon systemd-udevd[330]: specified group 'tss' unknown > Jul 26 13:38:51 charon systemd-udevd[330]: specified group 'kvm' unknown > Jul 26 13:38:51 charon systemd-udevd[330]: specified group 'rdma' unknown > Jul 26 13:38:49 charon systemd-udevd[330]: invalid ENV attribute, 'DEVTYPE' > can > not be set /etc/udev/rules.d/60-persistent-storage.rules:27
You have a broken/outdated 60-persistent-storage.rules in /etc/udev/rules.d. Why? Please delete that file. > Jul 26 13:38:49 charon systemd-udevd[330]: invalid rule > '/etc/udev/rules.d/60-persistent-storage.rules:27' > ul 26 13:19:09 localhost systemd[1]: Job > dev-disk-by\x2duuid-62d7daa5\x2d5064\x2d4b07\x2db06a\x2d479722490aea.device/start > timed out. You have a device listed in /etc/fstab which doesn't exist during boot, Please double check if your swap partition actually has UUID "62d7daa5-5064-4b07-b06a-479722490aea". Maybe you (or some other installer) has reformatted your swap partition. > /var/log/syslog:Jul 26 13:19:09 localhost systemd[1]: Dependency failed for > /dev/disk/by-uuid/62d7daa5-5064-4b07-b06a-479722490aea. > Jul 26 13:38:52 charon systemd-udevd[468]: failed to execute > '/lib/udev/socket:@/org/kernel/udev/monitor' > 'socket:@/org/kernel/udev/monitor': No such file or directory Can you check your udev rules for this, i.e. which one is using "socket:@/org/kernel/udev/monitor". That interface is long gone. > Jul 26 13:38:59 charon systemd-udevd[2031]: failed to execute > '/lib/udev/vol_id' 'vol_id --export /dev/sda3': No such file or directory vol_id is long gone. Do you have any outdated udev rules besides /etc/udev/rules.d/60-persistent-storage.rules? > Jul 26 13:39:12 charon systemd[1]: Cannot add dependency job for unit > systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service > failed to load: No such file or directory. That can be safely ignored. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
