Add Disk to Raid5

    • OMV 2.x
    • Add Disk to Raid5

      Hi all,

      I have added a new harddisk (4th) to my existing Raid5. The array looks fine, with 10.90 TiB in total. But only 7.12TiB are accessible in the filesystem. If I click on resize the confirmation message appears. If I hit 'yes' nothing else happens.

      Version : 1.2
      Creation Time : Sun Sep 7 20:06:10 2014
      Raid Level : raid5
      Array Size : 11706850944 (11164.52 GiB 11987.82 GB)
      Used Dev Size : 3902283648 (3721.51 GiB 3995.94 GB)
      Raid Devices : 4
      Total Devices : 4
      Persistence : Superblock is persistent

      Update Time : Mon Aug 8 20:08:20 2016
      State : clean
      Active Devices : 4
      Working Devices : 4
      Failed Devices : 0
      Spare Devices : 0

      Layout : left-symmetric
      Chunk Size : 64K

      Name : DiskStation:2
      UUID : bddbfff8:e52d00ba:dd8e1663:bf60cf48
      Events : 26306

      Number Major Minor RaidDevice State
      0 8 37 0 active sync /dev/sdc5
      1 8 21 1 active sync /dev/sdb5
      2 8 53 2 active sync /dev/sdd5
      4 8 64 3 active sync /dev/sde






      Any ideas what to do?
      Thanks a lot!
      Regards,

      Chris
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x
    • Trickreich wrote:

      Das schon mal probiert, via Putty?

      try this

      resize2fs /dev/md2

      resize2fs 1.42.5 (29-Jul-2012)
      resize2fs: Das Gerät oder die Ressource ist belegt beim Versuch, /dev/md2 zu öffnen
      Kann keinen gültigen Dateisystem-Superblock finden.
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x
    • Ich habe gparted ausprobiert. Aber das Raid Volume wurde mir nicht angezeigt, nur die einzelnen Disks. Das Problem haben anscheinend mehr?
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x
    • Hi Trickreich,

      danke für den Tipp, aber das war leider auch nicht der Durchbruch :(

      resize2fs 1.42.5 (29-Jul-2012)
      Das Dateisystem ist schon 1951140864 Blöcke groß. Nichts zu tun!

      Das Volume wurde ursprünglich auf meiner Synology NAS generiert. Vielleicht liegt es daran.

      Gruß

      Chris
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x
    • Hallo,

      was kommt denn als Antwort wenn Du bei Putty oder einem Terminal

      lvs

      eingibst?

      Ich denke die Synology hat LVM benutzt um das Raid zu erstellen. Dann mußt Du als zwischenschritt das Logische Laufwerk vergrößern und dann erst das Dateisystem.

      lvresize --extents +100%FREE /dev/mapper/vg1000-lv

      und dann erst

      resize2fs /dev/mapper/vg1000-lv


      Aber eigentlich kenne ich mich zu wenig aus als das ich mir da selber vertrauen würde.Ich will nicht schuld sein wenn dann alle Daten weg sind.

      In diesem Sinne einen schönen Abend.

      The post was edited 1 time, last by Trickreich ().

    • Trickreich wrote:

      Ich denke die Synology hat LVM benutzt um das Raid zu erstellen. Dann mußt Du als zwischenschritt das Logische Laufwerk vergrößern und dann erst das Dateisystem.


      lvresize --extents +100%FREE /dev/mapper/vg1000-lv

      und dann erst

      resize2fs /dev/mapper/vg1000-lv


      Aber eigentlich kenne ich mich zu wenig aus als das ich mir da selber vertrauen würde.Ich will nicht schuld sein wenn dann alle Daten weg sind.


      Source Code

      1. root@nas:~# lvs
      2. LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
      3. lv vg1000 -wi-ao-- 7,27t
      lvresize --extents +100%FREE /dev/mapper/vg1000-lv
      resize2fs /dev/mapper/vg1000-lv

      Can someone confirm please, that this will NOT delete all my data?

      Cheers!

      Chris
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x

      The post was edited 1 time, last by chriz77 ().

    • It won't delete your data but combine the statement into one. That is one of the things LVM is supposed to do (online resize).

      lvresize --extents +100%FREE -r /dev/mapper/vg1000-lv
      omv 4.0.19 arrakis | 64 bit | 4.14 backports kernel | omvextrasorg 4.1.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Unfortunately the volume is still not extended to its real size :(

      Source Code

      1. root@nas:~# lvresize --extents +100%FREE -r /dev/mapper/vg1000-lv
      2. Extending logical volume lv to 7,27 TiB
      3. Logical volume lv successfully resized
      4. resize2fs 1.42.5 (29-Jul-2012)
      5. Das Dateisystem ist schon 1951140864 Blöcke groß. Nichts zu tun!
      6. root@nas:~# lvs
      7. LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
      8. lv vg1000 -wi-ao-- 7,27t


      Source Code

      1. Version : 1.2
      2. Creation Time : Sun Sep 7 20:06:10 2014
      3. Raid Level : raid5
      4. Array Size : 11706850944 (11164.52 GiB 11987.82 GB)
      5. Used Dev Size : 3902283648 (3721.51 GiB 3995.94 GB)
      6. Raid Devices : 4
      7. Total Devices : 4
      8. Persistence : Superblock is persistent
      9. Update Time : Wed Aug 17 13:45:52 2016
      10. State : clean
      11. Active Devices : 4
      12. Working Devices : 4
      13. Failed Devices : 0
      14. Spare Devices : 0
      15. Layout : left-symmetric
      16. Chunk Size : 64K
      17. Name : DiskStation:2
      18. UUID : bddbfff8:e52d00ba:dd8e1663:bf60cf48
      19. Events : 26527
      20. Number Major Minor RaidDevice State
      21. 0 8 37 0 active sync /dev/sdc5
      22. 1 8 21 1 active sync /dev/sdb5
      23. 2 8 53 2 active sync /dev/sdd5
      24. 4 8 64 3 active sync /dev/sde
      Display All



      Cheers,

      Chris
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x
    • Source Code

      1. root@nas:~# vgs
      2. VG #PV #LV #SN Attr VSize VFree
      3. vg1000 1 1 0 wz--n- 7,27t 0
      4. root@nas:~# pvs
      5. PV VG Fmt Attr PSize PFree
      6. /dev/md2 vg1000 lvm2 a-- 7,27t 0
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x
    • You need to resize your physical volume. It doesn't know the array grew.

      pvresize /dev/md2

      then run the other command again.

      Personally, I wouldn't use lvm on top of mdadm raid.
      omv 4.0.19 arrakis | 64 bit | 4.14 backports kernel | omvextrasorg 4.1.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Personally, I wouldn't use lvm on top of mdadm raid.


      Sorry, I am a noob ;) What you would recommend? What shoult I do?
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x
    • You already have it created so keep using it. Just letting you know that mdadm raid is all you need. lvm is just an unnecessary layer.

      Did the resize command work?
      omv 4.0.19 arrakis | 64 bit | 4.14 backports kernel | omvextrasorg 4.1.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      You need to resize your physical volume. It doesn't know the array grew.

      pvresize /dev/md2

      then run the other command again.

      YOU ARE THE MAN! Big thanks that did the trick!
      Hardware: MSI B150M ECO - Intel Pentium G4400 - 16GB Crucial CT2K8G4DFD8213 - Mushkin Chronos SSD 120 GB - 4x WD Red 4TB (RAID5) - DVBSky S952 Dual DVB-S/S2 PCIe (V3)
      Software: OMV 2.1.x (3.16.0-0.bpo.4-amd64), Plex Media Server, Tvheadend 4.1.x