omv-extras.org plugin.
After installing the plugin it seems to change my web interface login details on version 2.0.13. So i can't uninstall the plugin.
Is the extras plugin compatible with version 1.9 hopefully this wont have effected my completion of a resync of my Raid 10 array.
Thanks for any help.
Yes, it works just fine on OMV 2.x. It definitely did not change your login details though. Did you try omv-firstaid to reset your login?
I have tried logging in on my Mac using ssh to use omv-firstaid yet it rejects my root password and any of the default passwords i could find online for OMV.
This only happened since installing the plugin which is strange, It hasn't installed any other packages from its collection yet.
Do you have root login over ssh disabled? Try logging locally. omv-extras definitely does not change your root password. There is no default root password. It has to be what you set it to when installing.
I tried locally (ssh might not have been enabled yet, have to check) and it worked thank you. I would like to know what caused this error though. Also is the wordpress and minidlna plugin no longer available?
I have no idea what caused that error. First I have ever heard about something like that. omv-extras doesn't do anything other than enable a repo and add some gpg keys on installation.
Nope, they are available. Did you click check? Are you sure you don't have this problem affecting you?
reprepro ls openmediavault-minidlna
openmediavault-minidlna | 0.5.9 | sardaukar | i386, amd64, armel, armhf
openmediavault-minidlna | 1.0.11 | kralizec | i386, amd64, armel, armhf
openmediavault-minidlna | 1.0.11 | stoneburner | i386, amd64, armel, armhfJust wait a little longer to upgrade to 2.0
I'm still going to wait at least another month and ensure all plugins are working correctly before doing anything...
They appear to be showing now, Strange. Regardless great little extendable NAS OS. Hopefully I won't find to many more hiccups with our new setup. Thanks for your help.
I wasn't so lucky after the FAKERaid 10 array finished cleaning it won't let me create a partition or even a local volume. This is likely my inexperience in moving from NAS4Free to OMV for our new system. Will I have to create a software RAID volume instead on relying on FAKERaid. Or purchase another hardware RAID controller with RAID 10. Our other SSD hardware RAID volume works fine in OMV. Sorry for going off topic.
Linux SLSZ-SERVER 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jun 19 12:29:15 2015
root@SLSZ-SERVER:~# cat /proc/mdstat
Personalities : [raid10]
md127 : active raid10 sdc[0] sdf[3] sde[2] sdd[1]
3906765824 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
unused devices: <none>
root@SLSZ-SERVER:~# fdisk -l
Disk /dev/sdb: 250.0 GB, 250014072832 bytes
255 heads, 63 sectors/track, 30395 cylinders, total 488308736 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 identifier: 0x000bc012
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 468469759 234233856 83 Linux
/dev/sdb2 468471806 488306687 9917441 5 Extended
/dev/sdb5 468471808 488306687 9917440 82 Linux swap / Solaris
Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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 identifier: 0x00000000
Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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 identifier: 0x00000000
Disk /dev/sdc doesn't contain a valid partition table
Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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 identifier: 0x00000000
Disk /dev/sde doesn't contain a valid partition table
Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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 identifier: 0x00000000
Disk /dev/sdf doesn't contain a valid partition table
Note: sector size is 4096 (not 512)
Disk /dev/sda: 2000.4 GB, 2000398929920 bytes
255 heads, 63 sectors/track, 30400 cylinders, total 488378645 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x9a8b45ec
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 488378644 1953506388 7 HPFS/NTFS/exFAT
Disk /dev/md127: 4000.5 GB, 4000528203776 bytes
2 heads, 4 sectors/track, 976691456 cylinders, total 7813531648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000
Disk /dev/md127 doesn't contain a valid partition table
root@SLSZ-SERVER:~#
You created a software raid array (mdadm). Most people call the "hardware" raid on cheap motherboards fakeraid.
Now, you just need to create a filesystem on the array. Then create shared folders using that filesystem.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!