Arief Yudhawarman

Masih belajar buat blog

Installing Proxmox VE 2.3 With Software Raid

with one comment

Overview

Proxmox Virtual Environment is an easy to use Open Source virtualization platform for running Virtual Appliances and Virtual Machines. Proxmox does not officially support software raid but the software raid to be very stable and in some cases have had better luck with it than hardware raid.

First, install Proxmox V2 the normal way with the CD downloaded from Proxmox. Installation instructions here:
Proxmox Quick Installation

Then follow the procedures below to setup software raid.

  1. After installing proxmox, login to console as root then run fdisk -l to list the current partitioning:
    root@proxmox1:~# fdisk -l
    Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 
    255 heads, 63 sectors/track, 243201 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x0003f97f 
    
       Device Boot      Start         End      Blocks   Id  System 
    /dev/sda1   *           1          66      523264   83  Linux 
    Partition 1 does not end on cylinder boundary. 
    /dev/sda2              66      243202  1952990208   8e  Linux LVM 
    
    Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes 
    255 heads, 63 sectors/track, 243201 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x000e49a7 
    
       Device Boot      Start         End      Blocks   Id  System 
    
    Disk /dev/dm-0: 103.1 GB, 103079215104 bytes 
    255 heads, 63 sectors/track, 12532 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x00000000 
    
    Disk /dev/dm-0 doesn't contain a valid partition table 
    
    Disk /dev/dm-1: 7516 MB, 7516192768 bytes 
    255 heads, 63 sectors/track, 913 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x00000000 
    
    Disk /dev/dm-1 doesn't contain a valid partition table 
    
    Disk /dev/dm-2: 1872.1 GB, 1872089841664 bytes 
    255 heads, 63 sectors/track, 227601 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x00000000 
    
    Disk /dev/dm-2 doesn't contain a valid partition table

  2. Do update and upgrade proxmox.

    apt-get update apt-get upgrade

  3. We have to make sure to clear any partition from /dev/sdb.
    root@proxmox1:~# fdisk -l /dev/sdb
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 
    255 heads, 63 sectors/track, 121601 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x07259175 
    
    Device Boot Start End Blocks Id System 
    /dev/sdb1 * 1 66 523264 83 Linux 
    Partition 1 does not end on cylinder boundary. 
    /dev/sdb2 66 121602 976237568 8e Linux LVM


    There are 2 partitions, eg. /dev/sdb1 and /dev/sdb2. Remove them all.

    root@proxmox1:~# fdisk /dev/sdb
    The device presents a logical sector size that is smaller than 
    the physical sector size. Aligning to a physical sector (or optimal 
    I/O) size boundary is recommended, or performance may be impacted. 
    
    WARNING: DOS-compatible mode is deprecated. It's strongly recommended to 
    switch off the mode (command 'c') and change display units to 
    sectors (command 'u'). 
    
    Command (m for help): d 
    Partition number (1-4): 2 
    
    Command (m for help): p 
    
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 
    255 heads, 63 sectors/track, 121601 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x07259175 
    
    Device Boot Start End Blocks Id System 
    /dev/sdb1 * 1 66 523264 fd Linux raid autodetect 
    Partition 1 does not end on cylinder boundary. 
    
    Command (m for help): d 
    Selected partition 1 
    
    Command (m for help): p 
    
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 
    255 heads, 63 sectors/track, 121601 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x07259175 
    
    Device Boot Start End Blocks Id System 
    
    Command (m for help): w 
    The partition table has been altered! 
    
    Calling ioctl() to re-read partition table. 
    
    WARNING: Re-reading the partition table failed with error 16: Device or resource busy. 
    The kernel still uses the old table. The new table will be used at 
    the next reboot or after you run partprobe(8) or kpartx(8) 
    Syncing disks.

    Because the system (kernel) still uses the old table partitions of sdb we should reboot the system.

  4. Install mdadm.

    apt-get install mdadm

    mdadm configuration

    mdadm configuration


    In the package configuration window choose all then ok.
  5. Now run
    root@proxmox1:~# cat /proc/mdstat
    Personalities : 
    unused devices: 
    

  6. After reboot copy the partition table from sda to sdb.
    root@proxmox1:~# sfdisk -d /dev/sda | sfdisk --force /dev/sdb
    Checking that no-one is using this disk right now ... 
    OK 
    
    Disk /dev/sdb: 243201 cylinders, 255 heads, 63 sectors/track 
    Old situation: 
    Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 
    
       Device Boot Start     End   #cyls    #blocks   Id  System 
    /dev/sdb1          0       -       0          0    0  Empty 
    /dev/sdb2          0       -       0          0    0  Empty 
    /dev/sdb3          0       -       0          0    0  Empty 
    /dev/sdb4          0       -       0          0    0  Empty 
    New situation: 
    Units = sectors of 512 bytes, counting from 0 
    
       Device Boot    Start       End   #sectors  Id  System 
    /dev/sdb1   *      2048   1048575    1046528  83  Linux 
    /dev/sdb2       1048576 3907028991 3905980416  8e  Linux LVM 
    /dev/sdb3             0         -          0   0  Empty 
    /dev/sdb4             0         -          0   0  Empty 
    Warning: partition 1 does not end at a cylinder boundary 
    Successfully wrote the new partition table 
    
    Re-reading the partition table ... 
    
    If you created or changed a DOS partition, /dev/foo7, say, then use dd(1) 
    to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1 
    (See fdisk(8).)
    

  7. The new list partitioning table of sdb:
    root@proxmox1:~# fdisk -l /dev/sdb
    Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes 
    255 heads, 63 sectors/track, 243201 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x000e49a7 
    
       Device Boot      Start         End      Blocks   Id  System 
    /dev/sdb1   *           1          66      523264   83  Linux 
    Partition 1 does not end on cylinder boundary. 
    /dev/sdb2              66      243202  1952990208   8e  Linux LVM
    

  8. Change the partition types of sdb to linux raid autodetect:


    sfdisk -c /dev/sdb 1 fd sfdisk -c /dev/sdb 2 fd

  9. The new list partitioning table of sdb:
    root@proxmox1:~# fdisk -l /dev/sdb
    Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes 
    255 heads, 63 sectors/track, 243201 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x000e49a7 
    
       Device Boot      Start         End      Blocks   Id  System 
    /dev/sdb1   *           1          66      523264   83  Linux 
    Partition 1 does not end on cylinder boundary. 
    /dev/sdb2              66      243202  1952990208   fd  Linux raid autodetect
    

  10. To make sure that there are no remains from previous RAID installations on /dev/sdb, we run the following commands:

    mdadm --zero-superblock /dev/sdb1 mdadm --zero-superblock /dev/sdb2

    The normal result will show empty response to the console. But it’s ok when the result like this:


    mdadm: Couldn't open /dev/sdb1 for write - not zeroing mdadm: Couldn't open /dev/sdb2 for write - not zeroing

  11. Now we need to create our new raid arrays:
    root@proxmox1:~# mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/sdb1
    mdadm: /dev/sdb1 appears to contain an ext2fs file system 
        size=1953513560K  mtime=Thu Jan  1 07:00:00 1970 
    mdadm: Note: this array has metadata at the start and 
        may not be suitable as a boot device.  If you plan to 
        store '/boot' on this device please ensure that 
        your boot-loader understands md/v1.x metadata, or use 
        --metadata=0.90 
    Continue creating array? y 
    mdadm: Defaulting to version 1.2 metadata 
    mdadm: array /dev/md0 started.
    

    root@proxmox1:~# mdadm --create /dev/md1 --level=1 --raid-disks=2 missing /dev/sdb2
    mdadm: Note: this array has metadata at the start and 
        may not be suitable as a boot device.  If you plan to 
        store '/boot' on this device please ensure that 
        your boot-loader understands md/v1.x metadata, or use 
        --metadata=0.90 
    Continue creating array? y 
    mdadm: Defaulting to version 1.2 metadata 
    mdadm: array /dev/md1 started.
    

  12. Now run
    root@proxmox1:~# cat /proc/mdstat
    Personalities : [raid1] 
    md1 : active raid1 sdb2[1] 
          1952989048 blocks super 1.2 [2/1] [_U] 
          
    md0 : active raid1 sdb1[1] 
          523252 blocks super 1.2 [2/1] [_U] 
          
    unused devices: 
    

  13. Next we must adjust /etc/mdadm/mdadm.conf (which doesn’t contain any information about our new RAID arrays yet) to the new situation:

    cp /etc/mdadm/mdadm.conf /etc/mdadm/mdadm.conf_orig mdadm --examine --scan >> /etc/mdadm/mdadm.conf

  14. To see the lvm partitions use the command:
    root@proxmox1:~# lvscan
      ACTIVE            '/dev/pve/swap' [7.00 GiB] inherit 
      ACTIVE            '/dev/pve/root' [96.00 GiB] inherit 
      ACTIVE            '/dev/pve/data' [1.70 TiB] inherit
    

  15. Now we will create a new volume group named pve1 and matching logical volumes for swap, root, and data.
    root@proxmox1:~# pvcreate /dev/md1
      Writing physical volume data to disk "/dev/md1" 
      Physical volume "/dev/md1" successfully created
    

  16. Now run
    root@proxmox1:~# pvscan
      PV /dev/sda2   VG pve             lvm2 [1.82 TiB / 16.00 GiB free] 
      PV /dev/md1                       lvm2 [1.82 TiB] 
      Total: 2 [3.64 TiB] / in use: 1 [1.82 TiB] / in no VG: 1 [1.82 TiB]
    

  17. Now let’s create our volume group pve1 and add /dev/md1 to it:

    vgcreate pve1 /dev/md1

  18. Now we need to create our logical volumes. We will use the same sizes and names as the volumes from the lvscan command above.

    lvcreate --name swap --size 7G pve1 lvcreate --name root --size 96G pve1 lvcreate --name data --size 812.02G pve1

  19. Now run
    root@proxmox1:~# lvscan
      ACTIVE            '/dev/pve/swap' [7.00 GiB] inherit 
      ACTIVE            '/dev/pve/root' [96.00 GiB] inherit 
      ACTIVE            '/dev/pve/data' [1.70 TiB] inherit 
      ACTIVE            '/dev/pve1/swap' [7.00 GiB] inherit 
      ACTIVE            '/dev/pve1/root' [96.00 GiB] inherit 
      ACTIVE            '/dev/pve1/data' [1.70 TiB] inherit
    

  20. Now we need to create the filesystems:

    mkfs.ext3 /dev/md0 mkswap /dev/pve1/swap -f mkfs.ext3 /dev/pve1/root mkfs.ext3 /dev/pve1/data

  21. If that was successful then it is time to copy the files to the new raid array. First we mount the new partitions:

    mkdir /mnt/boot mkdir /mnt/root mkdir /mnt/data mount /dev/md0 /mnt/boot mount /dev/pve1/root /mnt/root mount /dev/pve1/data /mnt/data

  22. Edit /etc/fstab.

    cp /etc/fstab /etc/fstab.orig cat /etc/fstab


    This the original /etc/fstab.

    #       
    /dev/pve/root / ext3 errors=remount-ro 0 1 
    /dev/pve/data /var/lib/vz ext3 defaults 0 1 
    UUID=aa20c3e8-5008-46ea-99af-f2a07d7d2542 /boot ext3 defaults 0 1 
    /dev/pve/swap none swap sw 0 0 
    proc /proc proc defaults 0 0
    


    Edit /etc/fstab with vi or nano like this:

    #       
    /dev/pve1/root / ext3 errors=remount-ro 0 1 
    /dev/pve1/data /var/lib/vz ext3 defaults 0 1 
    /dev/md0 /boot ext3 defaults 0 1 
    /dev/pve1/swap none swap sw 0 0 
    proc /proc proc defaults 0 0
    

  23. Now up to the GRUB2 boot loader. Create the file /etc/grub.d/09_swraid1_setup as follows:

    cp /etc/grub.d/40_custom /etc/grub.d/09_swraid1_setup


    Edit file /etc/grub.d/09_swraid1_setup like this:

    #!/bin/sh 
    exec tail -n +3 $0 
    # This file provides an easy way to add custom menu entries.  Simply type the 
    # menu entries you want to add after this comment.  Be careful not to change 
    # the 'exec tail' line above. 
    menuentry 'Proxmox, with RAID1' --class proxmox --class gnu-linux --class gnu --class os { 
        insmod raid 
        insmod mdraid 
        insmod part_msdos 
        insmod ext2 
        set root='(md/0)' 
        echo    'Loading Proxmox with RAID ...' 
        linux   /vmlinuz-2.6.32-18-pve root=/dev/mapper/pve1-root ro quiet 
        echo    'Loading initial ramdisk ...' 
        initrd  /initrd.img-2.6.32-18-pve 
    }
    

  24. Because we don’t use UUIDs anymore for our block devices, edit /etc/default/grub.

    echo 'GRUB_DISABLE_LINUX_UUID=true' >> /etc/default/grub

  25. Then update-grub.
    root@proxmox1:~# update grub
    Generating grub.cfg ... 
    Found linux image: /boot/vmlinuz-2.6.32-18-pve 
    Found initrd image: /boot/initrd.img-2.6.32-18-pve 
    Found memtest86+ image: /memtest86+.bin 
    Found memtest86+ multiboot image: /memtest86+_multiboot.bin 
    done
    

  26. Next we adjust our ramdisk to the new situation:
    root@proxmox1:~# update-initramfs -u
    update-initramfs: Generating /boot/initrd.img-2.6.32-18-pve
    

  27. Next we copy the files:

    cp -dpRx / /mnt/root cp -dpRx /boot/* /mnt/boot cp -dbRx /var/lib/vz/* /mnt/data

  28. Check the raid:
    root@proxmox1:~# cat /proc/mdstat
    Personalities : [raid1] 
    md1 : active raid1 sdb2[1] 
          1952989048 blocks super 1.2 [2/1] [_U] 
          
    md0 : active raid1 sdb1[1] 
          523252 blocks super 1.2 [2/1] [_U] 
          
    unused devices: 
    

    root@proxmox1:~# mdadm --detail /dev/md0
    /dev/md0: 
            Version : 1.2 
      Creation Time : Wed Jul 31 20:49:38 2013 
         Raid Level : raid1 
         Array Size : 523252 (511.07 MiB 535.81 MB) 
      Used Dev Size : 523252 (511.07 MiB 535.81 MB) 
       Raid Devices : 2 
      Total Devices : 1 
        Persistence : Superblock is persistent 
    
        Update Time : Wed Jul 31 21:46:32 2013 
              State : clean, degraded 
     Active Devices : 1 
    Working Devices : 1 
     Failed Devices : 0 
      Spare Devices : 0 
    
               Name : proxmox1:0  (local to host proxmox1) 
               UUID : 7a789bd2:7c5593ba:3506797c:9b4d38d3 
             Events : 14 
    
        Number   Major   Minor   RaidDevice State 
           0       0        0        0      removed 
           1       8       17        1      active sync   /dev/sdb1
    

    root@proxmox1:~# mdadm --detail /dev/md1
    /dev/md1: 
            Version : 1.2 
      Creation Time : Wed Jul 31 20:49:55 2013 
         Raid Level : raid1 
         Array Size : 1952989048 (1862.52 GiB 1999.86 GB) 
      Used Dev Size : 1952989048 (1862.52 GiB 1999.86 GB) 
       Raid Devices : 2 
      Total Devices : 1 
        Persistence : Superblock is persistent 
    
        Update Time : Wed Jul 31 21:46:47 2013 
              State : clean, degraded 
     Active Devices : 1 
    Working Devices : 1 
     Failed Devices : 0 
      Spare Devices : 0 
    
               Name : proxmox1:1  (local to host proxmox1) 
               UUID : 2ad8865c:f153a84b:0a74eb8d:e36ea60b 
             Events : 56 
    
        Number   Major   Minor   RaidDevice State 
           0       0        0        0      removed 
           1       8       18        1      active sync   /dev/sdb2
    

  29. Then reboot the system.

    reboot


After Booting

  1. If all goes well you should be able to see our new logical volumes root and data and /dev/md0 mounted:
    root@proxmox1:~# mount
    /dev/mapper/pve1-root on / type ext3 (rw,errors=remount-ro) 
    tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) 
    proc on /proc type proc (rw,noexec,nosuid,nodev) 
    sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) 
    udev on /dev type tmpfs (rw,mode=0755) 
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) 
    devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) 
    /dev/mapper/pve1-data on /var/lib/vz type ext3 (rw) 
    /dev/md0 on /boot type ext3 (rw) 
    fusectl on /sys/fs/fuse/connections type fusectl (rw) 
    /dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,default_permissions,allow_other) 
    beancounter on /proc/vz/beancounter type cgroup (rw,name=beancounter) 
    container on /proc/vz/container type cgroup (rw,name=container) 
    fairsched on /proc/vz/fairsched type cgroup (rw,name=fairsched)
    

  2. Now we need to remove the volume group pve:
    root@proxmox1:~# lvremove /dev/pve/root
    Do you really want to remove active logical volume root? [y/n]: y 
      Logical volume "root" successfully removed
    
    root@proxmox1:~# lvremove /dev/pve/swap
    Do you really want to remove active logical volume swap? [y/n]: y 
      Logical volume "swap" successfully removed
    
    root@proxmox1:~# lvremove /dev/pve/data
    Do you really want to remove active logical volume data? [y/n]: y 
      Logical volume "data" successfully removed
    
    root@proxmox1:~# vgremove /dev/pve
    root@proxmox1:~# pvremove /dev/sda2
    

  3. Now we must change the partition types of our three partitions on /dev/sda to Linux raid autodetect as well:

    sfdisk -c /dev/sda 1 fd sfdisk -c /dev/sda 2 fd

  4. The new list partitioning table of sda:
    root@proxmox1:~# fdisk -l /dev/sda
    Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 
    255 heads, 63 sectors/track, 243201 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 4096 bytes 
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
    Disk identifier: 0x0003f97f 
    
       Device Boot      Start         End      Blocks   Id  System 
    /dev/sda1   *           1          66      523264   fd  Linux raid autodetect 
    Partition 1 does not end on cylinder boundary. 
    /dev/sda2              66      243202  1952990208   fd  Linux raid autodetect
    

  5. Now we can add /dev/sda1 and /dev/sda2 to /dev/md0 and /dev/md1:
    root@proxmox1:~# mdadm --add /dev/md0 /dev/sda1
    mdadm: added /dev/sda1
    
    root@proxmox1:~# mdadm --add /dev/md1 /dev/sda2
    mdadm: added /dev/sda2
    

  6. Now take a look at:
    root@proxmox1:~# cat /proc/mdstat
    Personalities : [raid1] 
    md1 : active raid1 sda2[2] sdb2[1] 
          1952989048 blocks super 1.2 [2/1] [_U] 
          [>....................]  recovery =  0.0% (1473152/1952989048) finish=220.7min speed=147315K/sec 
          
    md0 : active raid1 sda1[2] sdb1[1] 
          523252 blocks super 1.2 [2/2] [UU] 
          
    unused devices: 
    

  7. Then adjust /etc/mdadm/mdadm.conf to the new situation:

    cp /etc/mdadm/mdadm.conf_orig /etc/mdadm/mdadm.conf mdadm --examine --scan >> /etc/mdadm/mdadm.conf

  8. Now we delete /etc/grub.d/09_swraid1_setup.

    rm -f /etc/grub.d/09_swraid1_setup

  9. And update our GRUB2 bootloader configuration:

    update-grub update-initramfs -u

  10. Afterwards we must make sure that the GRUB2 bootloader is installed on both hard drives, /dev/sda and /dev/sdb:
    root@proxmox1:~# grub-install /dev/sda
    Installation finished. No error reported.
    
    root@proxmox1:~# grub-install /dev/sdb
    Installation finished. No error reported.
    

  11. Reboot the system:

    reboot


Smart Daemon

Do no forget to install smartd. smartd is a daemon that monitors the Self-Monitoring, Analysis and Reporting Technology (SMART) system built into most ATA/SATA and SCSI/SAS hard drives and solid-state drives. The purpose of SMART is to monitor the reliability of the hard drive and predict drive failures, and to carry out different types of drive self-tests.


apt-get install smartmontools


Then make sure that the email of the root is redirect to the System Administrator.

root@proxmox1:~# cat /etc/pve/user.cfg 
user:root@pam:1:0:::sysadmin@server.org::


Edit file /etc/default/smartmontools and remove comment before start_smartd=yes.

# Defaults for smartmontools initscript (/etc/init.d/smartmontools)
# This is a POSIX shell fragment

# List of devices you want to explicitly enable S.M.A.R.T. for
# Not needed (and not recommended) if the device is monitored by smartd
#enable_smart="/dev/hda /dev/hdb"

# uncomment to start smartd on system startup
start_smartd=yes

# uncomment to pass additional options to smartd on startup
#smartd_opts="--interval=1800"


Activate the smartd by executing the init script.

root@proxmox1:~# /etc/init.d/smartmontools start
Starting S.M.A.R.T. daemon: smartd.
root@proxmox1:~# /etc/init.d/smartmontools status
smartd is running.


The smartd log is located at /var/log/daemon.log

...
Jan 25 17:09:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 73
Jan 25 17:09:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 26 to 27
Jan 25 17:09:50 proxmox1 smartd[1481]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 75 to 74
Jan 25 17:09:50 proxmox1 smartd[1481]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 25 to 26
Jan 25 17:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 73 to 72
Jan 25 17:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 27 to 28
Jan 25 17:39:49 proxmox1 smartd[1481]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 73
Jan 25 17:39:49 proxmox1 smartd[1481]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 26 to 27
Jan 26 04:09:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 117 to 108
Jan 26 04:09:49 proxmox1 smartd[1481]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 108 to 111
Jan 26 04:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 108 to 113
Jan 26 04:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 72 to 73
Jan 26 04:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 28 to 27
Jan 26 04:39:50 proxmox1 smartd[1481]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 111 to 114
Jan 26 05:09:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 113 to 116
Jan 26 05:09:49 proxmox1 smartd[1481]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 114 to 117
Jan 26 05:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 73 to 72
Jan 26 05:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 27 to 28
...


In the case of sh*t happens the error will be emailed to root.

...
Jan 26 08:09:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], 16 Currently unreadable (pending) sectors
Jan 26 08:09:49 proxmox1 smartd[1481]: Sending warning via /usr/share/smartmontools/smartd-runner to root ...
Jan 26 08:09:49 proxmox1 smartd[1481]: Warning via /usr/share/smartmontools/smartd-runner to root: successful
Jan 26 08:09:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], 16 Offline uncorrectable sectors
Jan 26 08:09:49 proxmox1 smartd[1481]: Sending warning via /usr/share/smartmontools/smartd-runner to root ...
Jan 26 08:09:49 proxmox1 smartd[1481]: Warning via /usr/share/smartmontools/smartd-runner to root: successful
Jan 26 08:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], 16 Currently unreadable (pending) sectors
Jan 26 08:39:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], 16 Offline uncorrectable sectors
Jan 26 09:09:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], 16 Currently unreadable (pending) sectors
Jan 26 09:09:49 proxmox1 smartd[1481]: Device: /dev/sda [SAT], 16 Offline uncorrectable sectors


References:

  1. Proxmox VE 2.x With Software Raid
  2. Proxmox VE 2.x With Software Raid – Page 2


Last update: 2014-01-26 21:00 +07:00

Written by awarmanf

January 26, 2014 at 1:18 am

Posted in Linux, proxmox, raid

Tagged with ,

One Response

Subscribe to comments with RSS.

  1. I tilted myself that will where I’d been leaning just a bit
    away from the part, enough to kick advertising as hard as I
    could possibly. If I can make one person smile and feel good I did my
    job. How this girl could keep this cutter spunk in her backpack.

    phentermine

    October 4, 2014 at 3:08 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: