So you're saying I need it on both correct?
Beiträge von kellym
-
-
I may be looking at this wrong, but here is the situation..
Original server runs the original storage in a RAID 5, is almost full. This server also runs my Plex. I just built the new server which can hold a ton more drives. I want to start moving everything over to the new server, then add the original drives to the new server and "grow" the array.
How do I make Plex running on the original server see the new server storage? I know I can see them both through my network browser on my PC. And I can move the files back and forth via this method. But how do I make Plex see storage that is not attached to it's host server?
I am guessing I need to mount the new "NAS" to the original OMV server that runs everything. How?
-
OMV can handle as many drives your power supply+motherboard combination can support.
My max omv disk setup used to be 16 disks in raid6,
8 from onboard sata, 4 from a promise pcie old raid controller
and an extra 4 in an external g-drive sas enclosure + raid controller.
on a non-server gigabyte board with a q6600 quad core.You just don't use hardware raid, tell the controllers to expose single drives
and let mdraid through omv do it's magic.If you have a lot of people streaming off your plex you might want to consider raid10 also.
(raid10 performance is quite nice on COTS (common off the shelf) hardware, if you dont mind the reduced space compared to raid5/6)
For an even greater masterplan, you can use omv inside a proxmox cluster of more than one machines with ceph clustered storage as back-end.
(we can talk about this through pm's if you like)Yes please! Tell me more!
-
I am looking to build a larger full on storage server. My current set up...
Xeon E3-1241V3
Supermicro MB X-10SLL-F or something
SSD for the OS
4 WD Red 3TB drives in a RAID 5I have had so much use of my Plex server people are purchasing me drives. I now have 6 more WD 3TB drives looking for a home. I have a larger master plan, but in the end I am looking to build something that can hold at least 12 drives. I would like to move all the media into this storage server after it is built, then add my original 4 and "grow" the array.
Here is my question...
The drives have to be directly connected correct? No hardware raid controller. Basically a direct to the motherboard attached setup via SATA. Can I use a PCI card that gives me 4 - 8 SATAIII ports and work the same way? I'm familiar with hardware raid. But what would work best for OMV to see all the drives and build an array?
-
The Sonarr plugin has a known dashboard bug in it that shows it isn't running when it really is. I have no idea why this hasn't been solved, but it's only cosmetic anyway.
Radarr is a port of Sonarr, so it's not surprising to me that it shares the same bug.
Once I fixed my resolv.conf file and did the backport, it fixed this issue.
-
Installing the backport kernel installs the headers but you can click on either in any order as many times as you want. They won't keep installing something that is already installed.
Perfect. Basically what I was looking for.
I want to say Thank You to
ryecoaaronYou have always answered all of my questions. Even on my other account I couldn't remember the login info for lol.
-
So do I click both of those buttons or just one? If both, in what order?
I am only putting Radarr, Sonarr, Transmission, and Plex on his. But in the dashboard it shows Radarr and Sonarr as not running. But they are.
-
When do you need to click on "Install Backports Kernel" and "Install Kernel Headers" under OMV-Extras.org > Kernel ?
The only OMV server I have going is my own. And I set it up using a solid guide I found when I did it. I can no longer find that guide. Nor does my searching return anything about these features. So at this point, I am going setting by settings setting up my friends server. And I am noticing some differences with the "Installed Kernels".
Mine : Debian GNU/Linux, with Linux 3.16.0-0.bpo.4-amd64
His : Debian GNU/Linux, with Linux 3.2.0-4-amd64
Any help is greatly appreciated. Thanks in advance!
-
Has Plex remote transcoder been considered? I'm not too sure how that would work. I am currently in the planning stages for an entire new setup. It might work if people are using VM's or something. But I plan on using a dedicated blade server for the transcoding. It would be kinda neat to have OMV on all 3 of my devices. Main server as the head. The remote transcoders, and the storage server.
-
Plex itself is Free, what is not free are the Mobile Client apps. that is you can install and use them but they have limitations when you do not have paid subscription for Plex services. or you can buy the App for like $5 to remove the limitations.
Excerpt from : https://support.plex.tv/hc/en-…2526943-Plex-Free-vs-Paid
The "Free to Use" Parts: The Server and Apps
There are some details to get into, but the summary of "free" is simple:
- The media you own is yours. Of course, we don’t charge you in any way for that.
- The Plex Media Server is free to use and includes the Plex Web App.
- All of our non-mobile, public apps are free. These include Amazon Fire TV, Android TV, Apple TV, Chromecast, Plex Media Player, Roku, Smart TVs, TiVo, and game consoles (PlayStation and Xbox).
- Our mobile apps (Android, iOS, Windows, Windows Phone) can be used for free, but have limitations.
- Until the mobile app is unlocked (through an in-app purchase or a Plex Pass subscription), video and music streamed from a Plex Media Server has a 1 minute limit, and photos will be watermarked.
If you have Plex Pass, all apps are free. Just bite the bullet and get the lifetime membership. I use it a lot lol.
-
Well this is a first. I went in through SSH and ran fdisk with options s, then w, then p, then d for each number, then s and w again. Now in the GUI it shows all is good when I choose the quick wipe feature.
Making a new RAID 5 array and didn't tell me to kick rocks yet. I'll check this after work.
-
-
Code
Alles anzeigenroot@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[bcd] mdadm: looking for devices for /dev/md0 mdadm: no recogniseable superblock on /dev/sdb mdadm: /dev/sdb has no superblock - assembly aborted root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[cd] mdadm: looking for devices for /dev/md0 mdadm: Cannot assemble mbr metadata on /dev/sdc mdadm: /dev/sdc has no superblock - assembly aborted root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sdd mdadm: looking for devices for /dev/md0 mdadm: Cannot assemble mbr metadata on /dev/sdd mdadm: /dev/sdd has no superblock - assembly aborted root@openmediavault:~#
Why do I get the feeling these drives, which I swore I wiped, I not actually wiped...
-
Anything else I can try?
-
-
Code
Alles anzeigenroot@openmediavault:~# fdisk -l | grep "Disk " | grep sd | sort WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 3000.6 GB, 3000592982016 bytes Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes Disk /dev/sde: 480.1 GB, 480103981056 bytes root@openmediavault:~#
-
-
I have OMV 2.1 installed on a machine.
i7-4790
Asus Z series MoBo
16GB Corsair memory
Crucial M.2 SATA3 256GB
4 x 3TB WD Red drives connected straight to the MoBoA couple times in a row now after installing I have lost the RAID array. At first I thought maybe it was me and I clicked a wrong button. After recreating and doing some searching it kept happening. I decided to do a fresh install. Same thing before any updates are applied at all. Here is my outputs from the "Degraded or Missing" thread...
Code
Alles anzeigenroot@openmediavault:~# cat /proc/mdstat Personalities : unused devices: <none> root@openmediavault:~# blkid /dev/sde1: UUID="3ff44633-64cc-4187-a332-297dad2a65c3" TYPE="ext4" /dev/sde5: UUID="610cbe88-0db5-4e68-afa1-8cdf849318d2" TYPE="swap" root@openmediavault:~# fdisk -l | grep sde1 WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. /dev/sde1 * 2048 904658943 452328448 83 Linux root@openmediavault:~# fdisk -l | grep sde5 WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. /dev/sde5 904660992 937701375 16520192 82 Linux swap / Solaris root@openmediavault:~# cat /etc/mdadm/mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays ARRAY /dev/md0 metadata=1.2 name=openmediavault:Storage UUID=2a3b5722:c8e0227d:b5c5dd1f:9e6ea63d root@openmediavault:~# mdadm --detail --scan --verbose root@openmediavault:~#