FSCK pada partisi LVM

setelah masuk ke server berikan perintah

#smartctl -t short /dev/sda

cek lvm

#lvdisplay

menampilkan partisi
  --- Logical volume ---
  LV Path                /dev/VolGroup00/LogVol00
  LV Name                LogVol00
  VG Name                VolGroup00
  LV UUID                dyi31m-U6qv-zUzE-nvGd-P2zd-KZ2r-I6Ec7d
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 0
  LV Size                926,28 GiB
  Current LE             29641
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:2
  
  --- Logical volume ---
  LV Path                /dev/VolGroup00/LogVol01
  LV Name                LogVol01
  VG Name                VolGroup00
  LV UUID                I3mQHd-xjr1-FUqD-c9xR-eg5V-Ki4w-Zf0pwh
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 2
  LV Size                5,12 GiB
  Current LE             164
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

Catatan:
pvscan :Physical scanning of particular disk

vgscan :Volume group scanning

lvscan :Logical volume scanning

# lvscan

  hasil:

 ACTIVE            '/dev/VolGroup00/LogVol00' [926,28 GiB] inherit
 ACTIVE            '/dev/VolGroup00/LogVol01' [5,12 GiB] inherit

#lvchange -ay "yourLogicalVolume"

# lvchange -ay /dev/VolGroup00/LogVol00

Then run "fdisk -l" and verify the LVM device is showing there







# fdisk -l

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  1953520064   976760032   83  Linux

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00049f60

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63      208844      104391   83  Linux
/dev/sda2          208845  1953520064   976655610   8e  Linux LVM

Disk /dev/mapper/live-rw: 4294 MB, 4294967296 bytes, 8388608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/live-osimg-min: 4294 MB, 4294967296 bytes, 8388608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/VolGroup00-LogVol00: 994.6 GB, 994586918912 bytes, 1942552576 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/VolGroup00-LogVol01: 5502 MB, 5502926848 bytes, 10747904 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes



langka terakhir fsck pada logical volume:


#e2fsck -y /YourLogicalVolume

# e2fsck -y /dev/VolGroup00/LogVol00
e2fsck 1.42.9 (28-Dec-2013)
Adding dirhash hint to filesystem.

/dev/VolGroup00/LogVol00 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 23560195 was part of the orphaned inode list.  FIXED.
Inode 23560207 was part of the orphaned inode list.  FIXED.
Inode 23560209 was part of the orphaned inode list.  FIXED.
Inode 23560214 was part of the orphaned inode list.  FIXED.
Inode 23560218 was part of the orphaned inode list.  FIXED.
Deleted inode 23560224 has zero dtime.  Fix? yes