Beiträge von chriz77

Hi,
will this nic work with OMV4.x?
Thx!
Chris

Zitat von ryecoaaron

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!

Zitat von ryecoaaron

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

Sorry, I am a noob What you would recommend? What shoult I do?

Unfortunately the volume is still not extended to its real size

root@nas:~# lvresize --extents +100%FREE -r /dev/mapper/vg1000-lv
Extending logical volume lv to 7,27 TiB
Logical volume lv successfully resized
resize2fs 1.42.5 (29-Jul-2012)
Das Dateisystem ist schon 1951140864 Blöcke groß. Nichts zu tun!


root@nas:~# lvs
LV   VG     Attr     LSize Pool Origin Data%  Move Log Copy%  Convert
lv   vg1000 -wi-ao-- 7,27t

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 : Wed Aug 17 13:45:52 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 : 26527


    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

Cheers,

Chris

Zitat von Trickreich

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.

Alles anzeigen

root@nas:~# lvs
LV   VG     Attr     LSize Pool Origin Data%  Move Log Copy%  Convert
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

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

Ich habe gparted ausprobiert. Aber das Raid Volume wurde mir nicht angezeigt, nur die einzelnen Disks. Das Problem haben anscheinend mehr?

Zitat von Trickreich

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.

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

Zitat von diskman

apt-get remove openmediavault- and hit tab....it will show you all installed plugins. select one and deinstall it. after all deinstalled deinstall omvextras too....done

Thx dude, you saved my day. After removing all installed components my GUI is back to life.

Finally I managed installing OMV2.x. I used an temporary USB network adapter (Apple) for the installation. Aber the installation was done I installed the 3.16 backport kernel, which brings the drivers for my Intel NIC.
Thank you for your help guys!

That sounds not that easy. I tried to run the make install from a usb thumb. But it failed, make was not available. Now I'm running 3.0.4 w/out problems.

Thanks for the quick response! I'll give it a try tomorrow. Now I'll have some sleep

Hi,
I have problems installing OMV2.x on my new MSI B150M Eco with Intel I219V NIC. Maybe someone can help me with installing/compiling a suited driver? Unfortunately Google wasn't my friend so far
Thx,
Chris

Zitat

CPU : 6600T.

I wouldn't buy with the T model, except you have a good reason to buy it. You have more cons than pros on this model. If you speak german, you can have a look here:
http://www.technikaffe.de/anle…under_oder_ueberschaetzt_
Otherwise just google for a test/comparison between the t model and the standard model.

I downloaded the Media Built Driver media_build-bst-14-141106

When I try to compile I get this error:

root@nas:~/media_build-bst-14# ./v4l/build_x64.sh if build for 64 bit system os to support multi-standard, include DVB-T,DVB-T2 and DVB-C
root@nas:~/media_build-bst-14# make
make -C /root/media_build-bst-14/v4l
make[1]: Entering directory `/root/media_build-bst-14/v4l'
No version yet, using 3.16.0-0.bpo.4-amd64
make[1]: Leaving directory `/root/media_build-bst-14/v4l'
make[1]: Entering directory `/root/media_build-bst-14/v4l'
scripts/make_makefile.pl
Updating/Creating .config
Preparing to compile for kernel version 3.16.0
File not found: /lib/modules/3.16.0-0.bpo.4-amd64/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4.
make[1]: Leaving directory `/root/media_build-bst-14/v4l'
make[1]: Entering directory `/root/media_build-bst-14/v4l'
Updating/Creating .config
Preparing to compile for kernel version 3.16.0
File not found: /lib/modules/3.16.0-0.bpo.4-amd64/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4.
make[1]: *** Keine Regel vorhanden, um das Target ».myconfig«,
  benötigt von »config-compat.h«, zu erstellen.  Schluss.
make[1]: Leaving directory `/root/media_build-bst-14/v4l'
make: *** [all] Fehler 2

BTW: The card works fine with OMW 3 beta(4.3.0 BPO).

Zitat von fubz

I have finished the plugin for Let's Encrypt and it will be coming to OpenMediaVault very soon

Sounds great! Looking forward installing it

Excellent work, thank you very much!

Works fine on OMV 2.1 (3.16) with my TeVii S660 DVB-S2 USB. But I have problems to bring my DVBSKY S952 v3 to life I did exactly as decribed in this install guide:
http://www.linuxtv.org/wiki/index.php/DVBSky

dmesg | grep -i dvb
[ 2.892753] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 2.895430] usb 1-1.5: firmware: direct-loading firmware dvb-usb-s660.fw
[ 3.018265] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 3.018295] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3.022318] DVB: registering new adapter (TeVii S660 USB)
[ 3.039414] dvb-usb: MAC address: 01:01:01:01:01:01
[ 3.041610] dvb-usb: no frontend was attached by 'TeVii S660 USB'
[ 3.066338] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/rc/rc0/input15
[ 3.066445] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/rc/rc0
[ 3.066447] dvb-usb: schedule remote query interval to 150 msecs.
[ 3.066448] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 3.134578] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
[ 4.775229] usb 1-1.5: Product: DVBS2BOX
[ 4.775526] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 4.782008] usb 1-1.5: firmware: direct-loading firmware dvb-usb-s660.fw
[ 4.902211] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 4.902257] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 4.902484] DVB: registering new adapter (TeVii S660 USB)
[ 5.033210] dvb-usb: MAC address: 00:18:bd:5b:c7:58
[ 5.055628] usb 1-1.5: DVB: registering adapter 0 frontend 0 (Montage Technology DS3000)...
[ 5.056070] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/rc/rc0/input16
[ 5.056099] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/rc/rc0
[ 5.056101] dvb-usb: schedule remote query interval to 150 msecs.
[ 5.056102] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 5.486731] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
[ 5.487072] usb 1-1.5: firmware: direct-loading firmware dvb-fe-ds3000.fw

But the card is not shown in TVH.

Any ideas or anybody who runs the S952 successfully?

Cheers,

Chris