LV cannot be automatically activated after the system is restarted (boot. lvm & amp; after. loca)

Source: Internet
Author: User

LV cannot be automatically activated after the system is restarted (boot. lvm & after. loca) We recently discovered that the suse11sp2 system solved the problem of abnormal crashes and introduced another problem. For example, this lv cannot be automatically activated, and the problem is solved one by one. 1. lv can be manually activated, but dcoadbpro cannot be automatically activated :~ # Lvdisplay --- Logical volume --- LV Name/dev/dcoadbpro_lv/lvol0 VG Name dcoadbpro_lv UUID XejtSI-ifla-NJgl-SfkO-KKlq-jRme-eI5Ivt LV Write Access read/write LV Status NOT available LV Size 990.00 GiB Current LE 253440 Segments 1 Allocation inherit Read ahead sectors auto dcoadbpro: ~ # Vgchange-ay dcoa_lv dcoadbpro :~ # Lvdisplay --- Logical volume --- LV Name/dev/dcoadbpro_lv/lvol0 VG Name dcoadbpro_lv UUID XejtSI-ifla-NJgl-SfkO-KKlq-jRme-eI5Ivt LV Write Access read/write LV Status available LV Size 990.00 GiB Current LE 253440 Segments 1 Allocation inherit read ahead sectors auto dcoadbpro: ~ # Dcoadbpro :~ # Dcoadbpro :~ # Reboot Broadcast message from root (pts/0) (Thu Aug 22 08:56:00 2013): The system is going down for reboot NOW! Dcoadbpro :~ # Login as: rootUsing keyboard-interactive authentication. Password: Last login: Thu Aug 22 08:48:30 2013 from dengweie-2.digitalchina.comdcoadbpro :~ # Dcoadbpro :~ # Dcoadbpro :~ # Dcoadbpro :~ # Lvdisplay --- Logical volume --- LV Name/dev/dcoadbpro_lv/lvol0 VG Name dcoadbpro_lv UUID XejtSI-ifla-NJgl-SfkO-KKlq-jRme-eI5Ivt LV Write Access read/write LV Status NOT available LV Size 990.00 GiB Current LE 253440 Segments 1 Allocation inherit Read ahead sectors auto 2. Check the boot. whether to enable dcoadbpro when lvm is started :~ # Dcoadbpro :~ # Dcoadbpro :~ # Chkconfig-A | grep boot. lvmboot. lvm offboot. lvm_monitor ondcoadbpro :~ # Chkconfig boot. lvm ondcoadbpro :~ # Chkconfig-A | grep boot. lvmboot. lvm onboot. lvm_monitor ondcoadbpro :~ # Reboot dcoadbpro :~ # Lvdisplay --- Logical volume --- LV Name/dev/dcoadbpro_lv/lvol0 VG Name dcoadbpro_lv UUID XejtSI-ifla-NJgl-SfkO-KKlq-jRme-eI5Ivt LV Write Access read/write LV Status NOT available LV Size 990.00 GiB Current LE 253440 Segments 1 Allocation inherit Read ahead sectors auto 3, in/etc/init. d/Add a new after. the local script is as follows: 1 ). if/etc/init. d/after. the local file does not exist. Run cp/etc/init. d/boot. local/etc/init. d/af Ter. local Command to create. 2 ). vi after. local: edit the file, delete all non-annotation statements, and add/etc/init to the file. d/boot. lvm start statement, save and exit 3 ). restart the operating system, check the lv status, and find that the lv has been automatically activated. At this point, the problem is solved.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.