Server fails to boot with lvm error : “Invalid argument for –available: ay Error during parsing of command line.”
November 28, 2015

Server fails to boot with lvm error : “Invalid argument for –available: ay Error during parsing of command line.”

Posted on November 28, 2015  •  4 minutes  • 744 words  •  Suggest Changes

One of our servers had problems with nfs service (network file system), considering it was a storage server mainly used for nfs, that’s a problem. We where monitoring it before and after and strangely -for a Linux achine- nothing really popped up. Last week the same server had a out of memory state that pretty much locked up the kernel and as such the server. A reboot “fixed” it, but I assumed a new kernel had been pushed and was now being a pain in the ass. Like any production machine it could not be rebooted during the day until, -after some discussion- we noticed that the jobs running for a few weeks where in fact not doing anything. I checked the updates and to my surprise this machine had not been updated for a long while, by default I install yum-cron (unattended-upgrades for debian), on any system I install, but this one was before my time. There where around 1gb of updates ready, and that’s allot that can go wrong. Considering the OOM we decided quickly that installing the latest kernel would be the best thing to do, as clearly this OOM was fixed in the latest version. Since allot some tools depend on that kernel, we decided to take all the updates. During the updates however the machine locked up, active ssh connections got unresponsive, the monitor on the machine was not getting any signal and the worst : the USB keyboard & mouse did not get any power.

Clearly the machine was not functioning and we had to reset the machine. We where welcomed on the reboot with this error :

Server fails to boot with lvm error : "Invalid argument for --available: ay Error during parsing of command line."

That exact error gives back one result on google, a redhat article (I wrongly assumed was behind a paywall, in fact its just behind a login/registration wall) In fact there is not really an article behind. The only thing they give is the “Environment” it can occur in :

Normally yum will protect you from these kind of problems, so by breaking the transaction on yum (server reset) I assume on of those two got on the bad version and gave me the trouble. I used a rescue USB stick and checked the ext4 (root and home) for errors, both where ok. Then I rebooted the machine since installing a new version of lvm, lvm-libs and initscripts looked very difficult from inside a debian distro. The root partition however remained read-only. There is this tiny hack to fix that :

mount -o remount,rw /lvm_root /

Which will remount the root partion in read/write mode. Most people would now be able to finish yum with :


To bad for me that failed.  The advice given then is to check for dupes package-cleanup –dupes, (since that was one of the problems) However checking for dupes and cleaning them, can -in my case- be dangerous: it wanted to remove glibc and 2.1 Gb of system application, that really bad news, so don’t let it do that!

The thing that got me on track was : yum-complete-transaction –cleanup-only this removed the constant error telling me to finish the transaction. After that I wanted to remove the duplicates, you cannot use yum, cause yum will remove dependencies :

rpm --nodeps --noscript -e package

If you like me had around 1gb of updates, this is a easy hack :

# Store duplicate-list in a file.
package-cleanup --dupes > duplicates.txt

# Remove odd lines.
awk 'NR%2==0' duplicates.txt > single-duplicates.txt

# Replace new lines with spaces.
awk '{ printf "%s ", $0 }' single-duplicates.txt > duplicates.txt

# Copy-paste content of duplicates after command.
rpm --nodeps --noscripts -e [paste here]

source, also works for Centos 6X. After that I reinstalled allot of the packages. I tried to recall the problematic (initscripts, lvm, glibc, kernel, kernel-headers,…) and made sure those where done.

Later I also found yum check all that did not help too much as most was already fixed, but still worth the look!

After yum and rpm where both happy (updated) I rebooted the machine and until now its holding up like a champ. Also _to hell _ with the last sysadmin that got me in this mess! Install yum-cron if you are to lazy to update regularly!

Also usefull :


If you enjoyed this website, consider buying me a Dr. Pepper

Buy me a Dr PepperBuy me a Dr Pepper