Beiträge von wyleekiot

figured it out...somewhere in my unraid, freenas, windows, omv testing the drives had gotten corrupt gpt tables. they showed to all OS's as 3tb but there were two partitions one of 2tb and one of 746 like it was a mbr disk. omv nor windows could fix the drives, nor any of the free "disk fixing" utilities. finally i grabbed a mint bootable thumbdrive and tried gparted. Viola! it prompted me to fix them all as soon as i entered gparted and with just a couple mouse clicks each they were back up to 3tb and i formatted them with ext4. unfortunately in my diagnosing stage i reloaded omv so back to square one again! now my question is this. should i wipe the drives when i put them back in omv or just try to build the array and sync it?

so after getting docker working i decided it was time to transfer over all my media, the media folder is a touch over 2tb. I started it before i left for work yesterday and noticed it was real slow but after looking on the forums i wasnt concerned as i saw some fixes for that. however when i got home it had only copied 189.1Gb and said disk was full. Ive looked at all the settings i could think of that might be related. should i remove reinstall the array and do the slow wipe? ive always done the quick wipe and this is the third time ive set it up from scratch with this same hardware but didnt get this error the first two times. the first time i might not have moved the whole media folder but i know on the second install i did.

If i were capable of having another child and i did in fact have another i would name him that0n3guy in honor of you sir!! i didnt know to put the variables in bottom so i copied your settings and tada! im forever in your debt!

no timezone errors but still couldnt get a rdp connection and the following was in syslog...though i dont know if all of it is pertinent

Dec 24 20:20:01 omv1 /usr/sbin/cron[2541]: (*system*) RELOAD (/etc/crontab)

Dec 24 20:20:05 omv1 kernel: [15526.423609] aufs au_opts_parse:1133:docker[15624]: unknown option dirperm1

Dec 24 20:20:06 omv1 kernel: [15526.969891] device veth0274c6f entered promiscuous mode

Dec 24 20:20:06 omv1 kernel: [15526.976625] ADDRCONF(NETDEV_UP): veth0274c6f: link is not ready

Dec 24 20:20:06 omv1 avahi-daemon[2607]: Withdrawing workstation service for vethef964d1.

Dec 24 20:20:06 omv1 kernel: [15527.612685] ADDRCONF(NETDEV_CHANGE): veth0274c6f: link becomes ready

Dec 24 20:20:06 omv1 kernel: [15527.612698] docker0: port 1(veth0274c6f) entering forwarding state

Dec 24 20:20:06 omv1 kernel: [15527.612703] docker0: port 1(veth0274c6f) entering forwarding state

Dec 24 20:20:17 omv1 kernel: [15538.512008] eth0: no IPv6 routers present

Dec 24 20:20:21 omv1 kernel: [15542.624011] docker0: port 1(veth0274c6f) entering forwarding state

Dec 24 20:22:00 omv1 kernel: [15641.538866] docker0: port 1(veth0274c6f) entering forwarding state

Dec 24 20:22:01 omv1 avahi-daemon[2607]: Withdrawing workstation service for vethef964d1.

Dec 24 20:22:01 omv1 kernel: [15641.865747] docker0: port 1(veth0274c6f) entering disabled state

Dec 24 20:22:01 omv1 kernel: [15641.866406] device veth0274c6f left promiscuous mode

Dec 24 20:22:01 omv1 kernel: [15641.866410] docker0: port 1(veth0274c6f) entering disabled state

Dec 24 20:22:01 omv1 avahi-daemon[2607]: Withdrawing workstation service for veth0274c6f.

Dec 24 20:22:01 omv1 kernel: [15642.141731] device veth39f7a0a entered promiscuous mode

Dec 24 20:22:01 omv1 kernel: [15642.148591] ADDRCONF(NETDEV_UP): veth39f7a0a: link is not ready

Dec 24 20:22:01 omv1 avahi-daemon[2607]: Withdrawing workstation service for veth15c29bb.

Dec 24 20:22:01 omv1 kernel: [15642.641759] ADDRCONF(NETDEV_CHANGE): veth39f7a0a: link becomes ready

Dec 24 20:22:01 omv1 kernel: [15642.641772] docker0: port 1(veth39f7a0a) entering forwarding state

Dec 24 20:22:01 omv1 kernel: [15642.641782] docker0: port 1(veth39f7a0a) entering forwarding state

Dec 24 20:22:12 omv1 kernel: [15652.912007] eth0: no IPv6 routers present

Dec 24 20:22:16 omv1 kernel: [15657.696011] docker0: port 1(veth39f7a0a) entering forwarding state

would that be just the --timezone=$ENV_TZ part?

i edited the file listed above and i believe i did it properly....but now im getting the following in log as the container runs

Dec 24 11:16:50 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:16:50 omv1 omv-engined[31971]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:16:53 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:16:53 omv1 omv-engined[31972]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:16:58 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:16:58 omv1 omv-engined[31974]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:02 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:03 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:03 omv1 omv-engined[31983]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:08 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:08 omv1 omv-engined[31984]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:13 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:13 omv1 omv-engined[31985]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:18 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:18 omv1 omv-engined[31986]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:23 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:23 omv1 omv-engined[31987]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:24 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:24 omv1 omv-engined[31988]: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:28 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

Dec 24 11:17:28 omv1 ool openmediavault-webgui: Unknown or unsupported timezone [tz=US/Eastern]

I reloaded the unedited container to see if it would do the same...i got the same error messages but they didnt repeat...just logged one time

some googling showed that same command --timezone=$ENV_TZ being used without the _ so i removed that and then upon restart i still couldnt rdp into container but the syslog changed to:
Dec 24 12:04:40 omv1 kernel: [56491.901171] docker0: port 1(veth247a58d) entering forwarding state

Dec 24 12:04:40 omv1 avahi-daemon[2234]: Withdrawing workstation service for vethb3713c5.

Dec 24 12:04:40 omv1 kernel: [56492.222217] docker0: port 1(veth247a58d) entering disabled state

Dec 24 12:04:40 omv1 kernel: [56492.222614] device veth247a58d left promiscuous mode

Dec 24 12:04:40 omv1 kernel: [56492.222617] docker0: port 1(veth247a58d) entering disabled state

Dec 24 12:04:40 omv1 avahi-daemon[2234]: Withdrawing workstation service for veth247a58d.

Dec 24 12:04:41 omv1 kernel: [56492.605954] device veth4a7bb52 entered promiscuous mode

Dec 24 12:04:41 omv1 kernel: [56492.611517] ADDRCONF(NETDEV_UP): veth4a7bb52: link is not ready

Dec 24 12:04:41 omv1 avahi-daemon[2234]: Withdrawing workstation service for vethc978113.

Dec 24 12:04:41 omv1 kernel: [56493.292996] ADDRCONF(NETDEV_CHANGE): veth4a7bb52: link becomes ready

Dec 24 12:04:41 omv1 kernel: [56493.293012] docker0: port 1(veth4a7bb52) entering forwarding state

Dec 24 12:04:41 omv1 kernel: [56493.293021] docker0: port 1(veth4a7bb52) entering forwarding state

Dec 24 12:04:52 omv1 kernel: [56503.504014] eth0: no IPv6 routers present

Dec 24 12:04:56 omv1 kernel: [56508.320010] docker0: port 1(veth4a7bb52) entering forwarding state

got my gentle typhoons and last of my drives for my array so im itching to get my new box up and running...i hope this works...i much prefer omv over freenas and the prebuilt images for the odroid xu4 are a huge bonus. i run odroids for my front ends and next project will be taking my old drives and try to run them in a usb3 array on a xu4...a whole back end running <10 watts would be pretty sweet imo

i tried forwarding port 3389 to itself, random port to 3389, random port to itself, random port to 3389, not entering ports at all, using host instead of bridge, using none instead of bridge. the container seems to start and run but when i try to rdp into it wether i use the machine name or ip the rdp times out.

sorry it wont let me edit the above reply...says im not authorized to view that page..i bolded and underlined the edit i was trying to make

i tried forwarding port 3389 to itself, random port to 3389, random port to itself, 3389 to random port, not entering ports at all, using host instead of bridge, using none instead of bridge. the container seems to start and run but when i try to rdp into it wether i use the machine name or ip the rdp times out.

Seems we had to roll back forums. I think we were about to determine sparklyballs docker wasn't going to work with OMV. I really want to stick with omv but a dvr that supports hdhomeruns, comskipping of some sort, and .264 or .265 encoding is make or break, hence mythtv docker. Are there any other alternatives im overlooking?
Right now im using a windows based system which works well but requires too much interaction to keep everything moving seamlessly. I had a freenas before that which was rock solid but could never get mythtv running in a jail.
Anyway im up for suggestions and am not in an extreme hurry

has anyone tried to run this yet? i pull the image fine and run it however when i try to rdp to it as sparklyballs does in his video the rdp fails. he mentions nothing about the networking section of the plugin so im assuming thats my error. im not running omv firewall. its a fairly vanilla install only 12 hrs old with some general mucking about in plugins but nothing done to omv's settings yet

I have 2 of the hdhr3-us network capture cards that im using on a windows box with nextpvr. both work fine under windows but when i try to channel scan on vdr plugin i am told it cant find any atsc capture cards. Also is there anything like mcebuddy for linux? it might be helpful if i explain my current setup.

i currently run from attic mount antenna to dual hdhr3 to nextpvr backend, which records to "dvr" folder, mcebuddy monitors that folder and anything that is placed there it removes commercials and transcodes to mp4. Mcebuddy then places the transcoded file into the "tvshows" folder which is a plex source folder.

Sickbeard also has a "nzb" folder which is monitored by sabnzbd, nzb's placed into this folder are downloaded by sabnzbd and the completed files are placed in the same "dvr" folder for mcebuddy to transcode and pass to the "tvshows" folder where it is picked up by plex

my front ends are odroid xu3's running openelec with the nextpvr front end for live tv and plex app for the previously recorded and downloaded files.

OMV seems to be able to do all this in one nifty little box with the added benefit of zfs filesystem! i cant however get the hdhomeruns to be recognized by vdr.... has anyone been able to acomplish this?