top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

15 min pause during boot - Setting up logical volume management using CentOS

0 votes

I rebooted a server having a 20TB XFS volume under LVM and wait about 15 min to boot.

It stays at;
Setting up logical volume management
For 15 min then proceeds to boot fine.

During this time, I see the 14 disks of the 20TB volume flashing quickly as though being read. Nothing in my logs to indicate bad behavior. I am running the latest 6,4 kernel.

posted Jun 27, 2013 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes

I want to set up dovecot on a CentOS server. I did this before, some time ago, but it seems to have become much more complicated, involving postfix, amavisd-new and clamav (for spamassassin).

What puzzles me is the role, if any, of procmail and .procmailrc in this new system.
Is procmail no longer used/needed?

+1 vote

I was just wondering, is there a "correct" or "preferred" way of setting up the path and other environment variables for Qt 4 development/build using qmake and all - on a CentOS 6 system?

I mean, this does not work out-of-the box, at least if you have build files that assume "qmake" may be executed just like that - as there is no Qt 4 qmake on the path, although "qmake-qt4" is available. Also, if
qt3-devel is installed, and the default path setup is used, "qmake" will point to the Qt 3 version, as the package includes a profile.d file that modify the path in such a way. Which also sets up other Qt related
variables, I believe. There is no such file in qt4-devel, however.

I know ways to set up everything so that this works as expected, of course, but it would be interesting to know how the packagers intended it to be done. Are you expected to edit login files by hand? That's sort
of surprising in this day and age... Or is the thinking that the suffixed ("-qt4") version of commands will always be used? Or that everyone will be using plain make with pkg-config? Or is there some other mechanism that should to be used to select the right Qt version?

+2 votes

I am used to traditional update-rc.d et all.

Now I wonder how to add a a script that used to called by init.d (with start/sop ..) to the new "service start xx" regime.

All the tutorials I found talk about how to use update-rc.d..

0 votes

I am using CentOS 6.0 with Apache 2.2.15, and set up Apache with virtual host. The SSI works fine on the first VH, but ssi on the other virtual hosts does not work. I got the following message in the error log:

mod_include: Options +Includes (or IncludesNoExec) wasnt set, INCLUDES filter removed

Does anyone know how to resolve this problem?

0 votes

I installed today and had some boot issues.

After rebooting, the system locked immediately after the Asus motherboard logo. I thought at first that it was a hardware issue because it didn't appear that grub even loaded. I wasn't even able to get into the BIOS to change the boot order so it appeared that it was a hardware issue. I reset the MB BIOS and rebooted, which allowed me to get into the BIOS. Everything looked normal. I then tried to boot and the same issue. I repeated the BIOS clear and this time got to grub and let it load the latest kernel (2.6.32-358.14.1.el6). It hung again. I repeated the BIOS clear, go to the grub screen, selected the previous kernel and everything was fine.

Once I got to the OS, I removed the "rhgb quiet" from grub.conf from the newest kernel. Rebooted. Hung again immediately after loading. The weird thing is that I couldn't just power down and get back to grub; I
had to clear the BIOS again before I could even load grub to select the previous kernel.

Anyone else experiencing issues with the latest kernel? Any idea why it seems to even corrupt the BIOS?