kurulum icin elimizde uygun bir makinamiz var.<\/p>\n
bu makinamizda 4 adet 2tb data diskimiz mevcut,<\/p>\n
biz bu disklerimizi software raid 10 olarak proxmox altinda calistirmak istiyoruz<\/p>\n
daha onceki bir yazimda once debian wheezy kurmus \u00a0daha sonra onun uzerine lvm raid yapip isi hallettmistim<\/p>\n
fakat bu bana cazip gelmiyor, bu tur raid kurulumu guncellemelerde sorun cikartiyor.<\/p>\n
O yuzden bu kez yapmak istedigim oncelikle 4 diskimizin 1.cisine normal sekilde proxmox kurduktan sonra sistemi proxmox calisirken raid 10 haline getirmek<\/p>\n
adimlar su sekildedir:<\/p>\n
1- guncel proxmox isosu download edilir apt-get update apt-get install mdadm<\/p>\n 5-bu asamada partition tablolarimizi disk1 den disk2,3,ve 4 e kopyalayacagiz NOT NOT NOT \/\/ GUNCELLEME GUNCELLEME<\/p>\n EGER PARTITIONLARIMIZ OLDUDA GPT OLDU ISE<\/p>\n gdisk kur<\/p>\n Copy the partition scheme from \/dev\/sda<\/i> to \/dev\/sdb<\/i>:<\/p>\n buda zorunlu Now randomizes the GUID:<\/p>\n <\/p>\n 6- 3 diskimizdeki partition formatini RAID olarak belirleyelim NOT NOT NOT \/\/ GUNCELLEME GUNCELLEME<\/p>\n GPT icin soyle yaptim gdisk \/dev\/sdb tum disklerdeki tum partititonlara yapinca w kaydet q cik<\/p>\n 7- Raid yapilandirmamizi INITIALIZE edelim 8- \/boot dizinimizi \/dev\/md0 uzerine tasiyalim ve fstab dosyamizi \/dev\/md0 dan boot edecek hale getirelim 9- sistemi reboot ediyoruz. sistem acildikdan sonra gerekli kontrolleri yapalim 10- simdi gruba \/dev\/md0 dan boot etmek istedigimizi soyleyelim kisaca asagidaki komutlari girelim<\/p>\n 11- simdi \/dev\/sda1 i raid arrayimiz icine katmaliyiz 12- simdiki adimdan once burada cok uzun vakit alacak bir lvm tasima islemi yapacagimizdan LVM yi \/dev\/md1 uzerine tasiyacagiz<\/p>\n pvmove cok uzun surecek. bu arada yatip uyumak en iyisi, ya da disari cikip hava alin. 2tb disk ve guncel bir islemci ile en az 2-3 saat surecektir \ud83d\ude42<\/p>\n islem bittikten sonra sda2 uzerindeki pveyi reduce edip remove edecegiz 13- en son asamada \/dev\/sda2 yide raid yapimiz icine katacagiz 14- bundan sonra raidimizin rebuild edisini guzel guzel izleyebiliriz \ud83d\ude42 gule gule kullaniniz. EK: Pek Guzel, ne yapmamiz lazim? Bu bos alanimizi mevcut LVM alanimiza dahil edip \/var\/lib\/vz\/ altinda kullanilabilir hale getirmeliyiz. once standart komutlar ile duruma bakalim:<\/p>\n lvdisplay sonra cok guzel mi oldu ne oldu ? ————————————-<\/p>\n EK – GPT alamanca<\/p>\n ————————————-<\/p>\n Proxmox<\/a> unterst\u00fctzt offiziell kein Softraid<\/a>, man kann es aber nach der Installation in ein Softraid<\/a> verwandeln: Bei gro\u00dfen Festplatten verwendet proxmox aber GPT<\/a> zur Partitionierung. Daher erh\u00e4lt man schon beim kopieren der Partitionstabelle eine Fehlermeldung: <\/p>\n <\/p>\n GUNCELLEME 23 MAYIS 2014<\/p>\n Bu is cok Kabak Tadi verdi<\/p>\n Ama ne kadar ugrastigimi ben biliyorum \ud83d\ude42<\/p>\n Bildigim seyi o yuzden yeni yine yeniden bir daha yazayim<\/p>\n bu kez gene 8 disk ile .bash_history dosyam uzerinden gidecegim<\/p>\n Yukaridaki hersey burada var kisa minik aciklamalar ile<\/p>\n Bir iki puf noktasida var<\/p>\n Bunu goz onune almak son olarak ve ileride uygulamak yerinde bir karar olacaktir.<\/p>\n Yazmamaya karar verdim.<\/p>\n Cok daraltti cunku beni<\/p>\n bir daha ugrasip bir daha yaparim sonra…<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" kurulum icin elimizde uygun bir makinamiz var. bu makinamizda 4 adet 2tb data diskimiz mevcut, biz bu disklerimizi software raid 10 olarak proxmox altinda calistirmak istiyoruz daha onceki bir yazimda once debian wheezy kurmus \u00a0daha sonra onun uzerine lvm raid yapip isi hallettmistim fakat bu bana cazip gelmiyor, bu tur raid kurulumu guncellemelerde sorun cikartiyor. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-833","post","type-post","status-publish","format-standard","hentry","category-kategerisiz"],"_links":{"self":[{"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/posts\/833","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/comments?post=833"}],"version-history":[{"count":10,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/posts\/833\/revisions"}],"predecessor-version":[{"id":907,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/posts\/833\/revisions\/907"}],"wp:attachment":[{"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/media?parent=833"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/categories?post=833"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/tags?post=833"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n2- \/dev\/sda uzerine normal proxmox kurulumu yapilir
\n3- hersey calisir hale geldikden sonra ssh ile sisteme baglanilir
\n4- proxmox icin gerekli repo ayarlari yapilir ve sistem guncellenir son olarak mdadm paketleri sisteme yuklenir
\n
\nnano \/etc\/apt\/sources.list
\n------------
\ndeb http:\/\/ftp.de.debian.org\/debian wheezy main contrib
\n# security updates
\ndeb http:\/\/security.debian.org\/ wheezy\/updates main contrib
\n# PVE pve-no-subscription repository provided by proxmox.com, NOT recommended for production use
\ndeb http:\/\/download.proxmox.com\/debian wheezy pve-no-subscription
\n-------------<\/code><\/p>\n
\napt-get dist-upgrade<\/p>\n
\nancak bundan once eger sistemde olurda daha onceden bir mdadm yapilandirmasi varsa eski disklerde bunu halletmek icin diskleri sifirlayalim, bu komut disklerde eski partitionlari ve mbr yi silecek
\n
\n# dd if=\/dev\/zero of=\/dev\/sdx bs=512 count=1
\n<\/code>
\nbundan sonra partition tablolarimizi kopyalayalim 4disk icin su sekilde
\n
\nsfdisk -d \/dev\/sda | sfdisk -f \/dev\/sdb
\nsfdisk -d \/dev\/sda | sfdisk -f \/dev\/sdc
\nsfdisk -d \/dev\/sda | sfdisk -f \/dev\/sdd
\n<\/code><\/p>\nsgdisk -R=\/dev\/sdb \/dev\/sda\r\n<\/code><\/pre>\n<\/div>\ngdisk -G \/dev\/sdb\r\n<\/code><\/pre>\n<\/div>\n
\n
\nsfdisk -c \/dev\/sdb 1 fd
\nsfdisk -c \/dev\/sdb 2 fd
\nsfdisk -c \/dev\/sdc 1 fd
\nsfdisk -c \/dev\/sdc 2 fd
\nsfdisk -c \/dev\/sdd 1 fd
\nsfdisk -c \/dev\/sdd 2 fd
\n<\/code><\/p>\n
\nBelki baska kolay yolu vardir , bulamadim noobum.<\/p>\n
\nt ye bas
\npartition sec 1 > FD00 yap<\/p>\n
\nONEMLI NOT: eger daha onceden disk yapilandirmamizda raid kullanmis isek
\nmdadm yi sisteme entegre ettigimizde bunlar mdadm.conf dosyamiz icine otomatik olarak yazilmis olabilir, o yuzden raid yapimizi initialize ettikten sonra \/etc\/mdadm\/mdadm.conf dosyamizi incelememiz gerek
\neger gereksiz eski raid array uuid bilgisi var ise bunlari silmeli ve yeni yapiyi icine olusturmaliyiz.
\n
\nmdadm --create \/dev\/md0 --level=1 --raid-disks=4 missing \/dev\/sdb1 \/dev\/sdc1 \/dev\/sdd1
\nmdadm --create \/dev\/md1 --level=10 --raid-disks=4 missing \/dev\/sdb2 \/dev\/sdc2 \/dev\/sdd2
\n<\/code>
\nconf dosyamiza goz atalim eski yapilar varsa silelim, yeni yapimizi kayit etmek icin
\n
\nmdadm --examine --scan >> \/etc\/mdadm\/mdadm.conf
\n<\/code>
\nislem tamamdir<\/p>\n
\n
\nmkfs.ext3 \/dev\/md0
\nmkdir \/mnt\/md0
\nmount \/dev\/md0 \/mnt\/md0
\ncp -ax \/boot\/* \/mnt\/md0
\n<\/code>
\nsonra
\n
\nnano \/etc\/fstab su sekilde olmasi gerek, basitce UUID satirimizi devre disi birakiyoruz
\n-----------------
\n# \/dev\/pve\/root \/ ext3 errors=remount-ro 0 1
\n\/dev\/pve\/data \/var\/lib\/vz ext3 defaults 0 1
\n#UUID=cc425576-edf6-4895-9aed-ccfd89aeb0fb \/boot ext3 defaults 0 1
\n\/dev\/md0 \/boot ext3 defaults 0 1
\n\/dev\/pve\/swap none swap sw 0 0
\nproc \/proc proc defaults 0 0
\n-------------------
\n<\/code><\/p>\n
\neger hersey yolunda giderse sistemimiz \/dev\/md0 uzerinden boot edecek demektir.
\nbravo ciddi bir asamayi hallettik |:)<\/p>\n
\n
\nmount | grep boot
\ndedigimizde asagidaki gibi bir satir cikmasi gerek
\n\/dev\/md0 on \/boot type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)
\n<\/code>
\nbunu gorduysek islem tamam demektir.<\/p>\n
\necho '# customizations' >> \/etc\/default\/grub
\necho 'GRUB_DISABLE_LINUX_UUID=true' >> \/etc\/default\/grub
\necho 'GRUB_PRELOAD_MODULES=\"raid dmraid\"' >> \/etc\/default\/grub
\necho raid1 >> \/etc\/modules
\necho raid10 >> \/etc\/modules
\necho raid1 >> \/etc\/initramfs-tools\/modules
\necho raid10 >> \/etc\/initramfs-tools\/modules
\ngrub-install \/dev\/sda
\ngrub-install \/dev\/sdb
\ngrub-install \/dev\/sdc
\ngrub-install \/dev\/sdd
\nupdate-grub
\nupdate-initramfs -u
\n<\/code>
\nislem tamam<\/p>\n
\n
\nsfdisk -c \/dev\/sda 1 fd
\nmdadm \u2013add \/dev\/md0 \/dev\/sda1
\n<\/code><\/p>\n
\nscreen
\nkurup calistirip bunun altinda islemleri yapmakta fayda var.<\/p>\n
\npvcreate \/dev\/md1
\nvgextend pve \/dev\/md1
\npvmove \/dev\/sda2 \/dev\/md1
\n<\/code><\/p>\n
\n
\nvgreduce pve \/dev\/sda2
\npvremove \/dev\/sda2
\n<\/code><\/p>\n
\n
\nsfdisk --change-id \/dev\/sda 2 fd
\nmdadm --add \/dev\/md1 \/dev\/sda2
\n<\/code><\/p>\n
\n
\nwatch -n 5 cat \/proc\/mdstat
\n<\/code>
\nhatta dilersek bunu biraz hizlandirabiliriz
\n
\necho 800000 > \/proc\/sys\/dev\/raid\/speed_limit_min
\necho 1600000 > \/proc\/sys\/dev\/raid\/speed_limit_max
\n<\/code><\/p>\n
\nPROXMOX SOFTWARE RAID 10 KURULUMUNUZ KULLANIMA HAZIRDIR<\/p>\n
\n15– bu islemleri yaptiktan sonra df -h komutumuza makinamiz su sekilde yanit veriyor
\n
\nFilesystem Size Used Avail Use% Mounted on
\nudev 10M 0 10M 0% \/dev
\ntmpfs 3.2G 416K 3.2G 1% \/run
\n\/dev\/mapper\/pve-root 20G 1.2G 18G 7% \/
\ntmpfs 5.0M 0 5.0M 0% \/run\/lock
\ntmpfs 6.3G 3.1M 6.3G 1% \/run\/shm
\n\/dev\/mapper\/pve-data 1.8T 196M 1.8T 1% \/var\/lib\/vz
\n\/dev\/md0 495M 58M 412M 13% \/boot
\n\/dev\/fuse 30M 12K 30M 1% \/etc\/pve
\n<\/code>
\n\/var\/lib\/vz\/ 2TB mi? bir yerde yanlislik var 4 TB olmali idi \ud83d\ude42
\nEh normal, Kalan raid 10 diskimiz bos vg alani olarak duruyor. BKNZ:
\n
\nvgdisplay
\n--- Volume group ---
\nVG Name pve
\nSystem ID
\nFormat lvm2
\nMetadata Areas 1
\nMetadata Sequence No 11
\nVG Access read\/write
\nVG Status resizable
\nMAX LV 0
\nCur LV 3
\nOpen LV 3
\nMax PV 0
\nCur PV 1
\nAct PV 1
\nVG Size 3.64 TiB
\nPE Size 4.00 MiB
\nTotal PE 953544
\nAlloc PE \/ Size 472709 \/ 1.80 TiB
\nFree PE \/ Size 480835 \/ 1.83 TiB
\nVG UUID 16k1ou-8jQ7-OB63-Jesb-s7p4-SOPW-deKGGc
\n<\/code><\/p>\n
\nBu asamada linux LVM engin tecrubelerimizden faydalanacagiz.<\/p>\n
\npvdisplay
\nvgdisplay<\/p>\n
\nroot@pmd04:~# vgs
\nVG #PV #LV #SN Attr VSize VFree
\npve 1 3 0 wz--n- 3.64t 1.83t
\nroot@pmd04:~# pvs
\nPV VG Fmt Attr PSize PFree
\n\/dev\/md1 pve lvm2 a-- 3.64t 1.83t
\nroot@pmd04:~# lvs
\nLV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
\ndata pve -wi-ao--- 1.78t
\nroot pve -wi-ao--- 20.00g
\nswap pve -wi-ao--- 8.00g
\n<\/code><\/p>\n
\nVG bos alanimizi extend edelim ve daha sonra LV mize dahil edelim
\n
\nroot@pmd04:~# lvextend -l +100%FREE \/dev\/pve\/data
\nExtending logical volume data to 3.61 TiB
\nLogical volume data successfully resized
\nroot@pmd04:~# resize2fs \/dev\/pve\/data
\nresize2fs 1.42.5 (29-Jul-2012)
\nFilesystem at \/dev\/pve\/data is mounted on \/var\/lib\/vz; on-line resizing required
\nold_desc_blocks = 118, new_desc_blocks = 232
\nPerforming an on-line resize of \/dev\/pve\/data to 969089024 (4k) blocks.
\nThe filesystem on \/dev\/pve\/data is now 969089024 blocks long.
\nroot@pmd04:~# df -h
\nFilesystem Size Used Avail Use% Mounted on
\nudev 10M 0 10M 0% \/dev
\ntmpfs 3.2G 416K 3.2G 1% \/run
\n\/dev\/mapper\/pve-root 20G 1.2G 18G 7% \/
\ntmpfs 5.0M 0 5.0M 0% \/run\/lock
\ntmpfs 6.3G 3.1M 6.3G 1% \/run\/shm
\n\/dev\/mapper\/pve-data 3.6T 197M 3.6T 1% \/var\/lib\/vz
\n\/dev\/md0 495M 58M 412M 13% \/boot
\n\/dev\/fuse 30M 12K 30M 1% \/etc\/pve
\nroot@pmd04:~#
\n<\/code><\/p>\n
\nevet oldu
\ntamam o zaman |:)<\/p>\nProxmox 3.1 auf Softraid mit GPT<\/h2>\n
\nhttp:\/\/boffblog.wordpress.com\/2013\/08\/22\/how-to-install-proxmox-ve-3-0-on-software-raid\/<\/a><\/p>\n
\n\u201cWARNING: GPT<\/a> (GUID Partition Table<\/a>) detected on \u2018\/dev\/sda\u2019! The util sfdisk doesn\u2019t support GPT<\/a>. Use GNU Parted.\u201d
\nAbhilfe schafft die Verwendung von gdisk. F\u00fcr was genau die 1. Partition belegt ist weiss ich nicht. Boot lag bei mir auf \/dev\/sda2 und die lvm-Volumes lagen auf \/dev\/sda3
\nSomit habe ich folgende Befehle verwendet:<\/p>\napt-get update
\napt-get dist-upgrade
\napt-get install mdadm gdisk
\nsgdisk -R \/dev\/sdb \/dev\/sda <\/code>!!!ACHTUNG Reihenfolge beachten, wird in dem Fall von recht nach links kopiert
\nsgdisk -G \/dev\/sdb
\ndd if=\/dev\/sda1 of=\/dev\/sdb1 <\/code>NOTWENDIG?
\nsgdisk -t 2:fd00 \/dev\/sdb
\nsgdisk -t 3:fd00 \/dev\/sdb<\/code>
\nReboot notwendig?
\n
\nmdadm --create \/dev\/md0 --level=1 --raid-disks=2 missing \/dev\/sdb2
\nmdadm --create \/dev\/md1 --level=1 --raid-disks=2 missing \/dev\/sdb3
\nmkfs.ext3 \/dev\/md0
\nmkdir \/mnt\/md0
\nmount \/dev\/md0 \/mnt\/md0
\ncp -ax \/boot\/* \/mnt\/md0<\/code>
\n\/etc\/fstab editieren und die UUID vor \/boot durch \/dev\/md0 ersetzen
\nund nochmal booten!
\n
\necho \u2018GRUB_DISABLE_LINUX_UUID=true\u2019 >> \/etc\/default\/grub
\necho \u2018GRUB_PRELOAD_MODULES=\"raid dmraid\"\u2018 >> \/etc\/default\/grub
\necho raid1 >> \/etc\/modules
\necho raid1 >> \/etc\/initramfs-tools\/modules
\ngrub-install \/dev\/sda
\ngrub-install \/dev\/sdb
\nupdate-grub
\nupdate-initramfs -u
\nmdadm --add \/dev\/md0 \/dev\/sda2
\npvcreate \/dev\/md1
\nvgextend pve \/dev\/md1
\npvmove \/dev\/sda3 \/dev\/md1
\nvgreduce pve \/dev\/sda3
\npvremove \/dev\/sda3
\nsgdisk -t 3:fd00 \/dev\/sda
\nmdadm --add \/dev\/md1 \/dev\/sda3
\ncat \/proc\/mdstat<\/code><\/p>\n
\n
\n