Dale <rdalek1...@gmail.com> wrote: > Howdy, > > I had a drive to fail and removed it. When booting back up, I noticed > these errors flying by at close to warp speed. I dug in the log to see > what they were about. I hope this pastes in a readable way. > > /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8) > * Starting lvmetad ... [ ok ] > /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8) > * Setting up the Logical Volume Manager ... > /run/lvm/lvmetad.socket: connect failed: No such file or directory > WARNING: Failed to connect to lvmetad. Falling back to internal scanning. > [ ok ] > /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8) > /etc/init.d/device-mapper: line 64: awk: command not found > /etc/init.d/device-mapper: line 65: uniq: command not found > /etc/init.d/device-mapper: line 64: awk: command not found > /etc/init.d/device-mapper: line 65: uniq: command not found > /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8) > > << SNIP >> > > /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8) > /etc/init.d/chronyd: line 30: awk: command not found > * Starting chronyd ... > * start-stop-daemon: /usr/sbin/chronyd does not exist > * Failed to start chronyd > [ !! ] > * ERROR: chronyd failed to start > /bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8) > > > I had it set to run fsck on all file systems so I snipped that part > out. It's just clutter for what I am needing to know. Anyway, when I > got booted up, the chrony process did not start. The LVM stuff did > retry later but who knows how long it will be before that changes. LVM > and chrony seems to be having a issue with not having awk, uniq and > such. The setlocale error has been around since like forever. I don't > guess it matters to much. :-D > > Does it appear that LVM is going to require a init thingy to get a clean > boot or is it something else? I sorta hope it is something else. That > init thingy is not a path I want to go down again. May switch away from > LVM and try something else. > > Oh, I am using evdev. > > Thoughts??
Are you sure /usr was mounted? If its on a separate lvm volume, I would definitely use an initrd, as various tools assume /usr is mounted these days -- the init thingy can do that for you. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com