batt01
-
Posts
235 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by batt01
-
-
Working on getting this working with my HdHomerun Prime. I can get it recognized and it scans. However I cant connect with the backend. I have a Hdhomerun ATSC, Prime and a Genpix Skywalker usb. The Skywalker is supported but it requires some addition modules.
GENPIX 8pks/qpsk/DCII USB2.0 - DVB-S
The following modules are necessary in order to get this device running:
- dvb-usb.ko
- gp8psk.ko
I have no Idea how to install these. Could this be included in a upcomming release?
-
What exactly do you have to do after installing this template. In the form /hdhomerun is there. What goes in the other box?
You mean in the "Host path:" box for /hdhomerun? That would be the location of where you want the recordings and log files to go. As an example, mine is set to /mnt/user/Media/Recorded.
I get it now, I think I was having some brain flatulence. Thanks
-
What exactly do you have to do after installing this template. In the form /hdhomerun is there. What goes in the other box?
-
I looks like the cable was the issue. Parity sync is in progress for a couple of hours. Before with the other cable, it would disable the disk after a half hour or so. This is what you get when you buy the cheapest cables you can fine. These were 15 bucks. Saved a few buck in exchange for hours of aggravation. Thanks very much for your attention and help.
-
You have a plugin, Aesir, which to my understanding is an incomplete work in progress. Probably not the issue but you might try removing it.
I put that on just to take a look. After I replace the cable, im starting clean without plugins.
-
I see that sdb has only negotiated a 1.5 Gb/s link with its controller, ata3, while other disks have full 6 Gb/s SATA links. Perhaps you have a cable problem?
Mar 9 18:36:32 Loopcerv kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
I am using reverse breakout cables in a 12bay NAS case. I have 3 cables and all bays are connected. Only tow cables are in use. So I think good test would be to pull the cable attached to Sdb and swap it for the one attached to the empty bays. I think the cable is the likely culprit. I put another new drive in the same bay today, and it also went device disabled om the UI. Its gonna be a PITA tho. I have remove the fan wall the Norco to get to the cables. Will do tonight or tomorrow.
-
All the drives appearing in your diagnostics appear to be drives you have already assigned so the drive you are talking about seems to be missing. Can you access its SMART attributes and post them?
Tje drive is the parity drive. I unassigned to run Preclear.
-
You need to take a SMART report of the disk in question. If that doesn't reveal anything, try running the long self-test.
I ran the Long smart test and it completed without errors.
-
I have attempted to preclear a 4tb Toshiba drive. twice. It has failed twice at the exact same stopt. The drive is brand new. Installed it as parity, without preclearing first. After a few hours of parity sync, I would find the disk with a Red X, disabled. It get no useful info in the putty/preclear screen. It just froze, text pasted below.
Also the web ui is inaccessible after the preclear failure, reboot is required to restore. This is anew build with all brand new parts. Log attached device in question is Y5OAKE1QFSAA (sdb) 3907018584.
Disk Temperature: 36C, Elapsed Time: 30:57:43
1907719+10 records in
1907718+10 records out
4000784932864 bytes (4.0 TB) copied, 62088.4 s, 64.4 MB/s
Wrote 4,000,784,932,864 bytes out of 4,000,787,030,016 bytes (99% Done)
unRAID server Pre-Clear disk /dev/sdb
= cycle 1 of 1, partition start on sector 1
= Disk Pre-Clear-Read completed DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it
= **** This will take a while... you can follow progress below:
=
Disk Temperature: 36C, Elapsed Time: 30:57:43
1907719+10 records in
1907718+10 records out
4000784932864 bytes (4.0 TB) copied, 62088.4 s, 64.4 MB/s
Wrote 4,000,784,932,864 bytes out of 4,000,787,030,016 bytes (99% Done)
-
I think the trend now to go with Intel CPUs. I just moved from a TriCore AMD to a Intel Core I5. I think the reason is they perform better and comsume less power.
-
Some simple modding my be needed to get the norco cage in. I used a c clamp to press down the tabs that would be used to hold optical drives. My next build wil be in this. The way the drives are mounted you can forgo the norcos and how at least 8 drives.
-
I moved my server to a new location and serverely bent my usb thumb drive. It still works, but it silver part is attached by a thread. I am afraid to remove it, for fear of breaking it completely. How do I go about getting Unraid on a new thumb drive?
-
I picked up a old Dell Optiplex 755 without a hard drive for 20 bucks at Goodwill. I ran the trial version of unraid and it worked fine. I see no reason why your Dell wouldnt work. You could load the Unraid trial and boot from it, just to be sure before ou commit to buy.
-
No sure about how will it working in unraid, but the Genpix Skywalker is a great piece of hardware. I bought mine in 03 and use it with DVBlink for DVBDream and WMC.
-
Not meaning to hijack, but can the onboard video be used for passthrough.?
-
I replaced my Norco SS500 fain with Coolink SWiF2 80mm, they are very quiet. I have to Norco SS500s in my case and you cant hear them.
http://www.amazon.com/gp/product/B002IGC8OU?psc=1&redirect=true&ref_=oh_aui_detailpage_o03_s00
-
Im a docker noob, could someone post a screenshot or just plain text, of the follder mappings. I cant get it runninng and that is probably why.
-
Thanks for the reply, it seem to have been a problem iwth my password. I appeard I was logged into to plex and I was not.
-
Switching from plugin to docker. Got it running but Plex is available only on the local network. I have it running in Host mode asp per a guide I saw somewhere in he forum. Is the port forwarding different in some way?
-
I pulled and replaced the drive, thanks.
-
You should post your diagnostics (Tools - Diagnostics)
I have attached the Diagnostics file below.
-
I had been noticing slow performance for several weeks, and high cpu usage. I checked the data and cache drive in maintenance mode and the appear to be ok. There does not seem to be an option to check the parity drive. The log is full of errors on Disk 0. I am assuming that disk 0 is the parity drive. I am posting the log below.
[/Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514136 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514144 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514152 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514160 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514168 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514176 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514184 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514192 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514200 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514208 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514216 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514224 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514232 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514240 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514248 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514256 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514264 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514272 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514280 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514288 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514296 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514304 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514312 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514320 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514328 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514336 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514344 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514352 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514360 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514368 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514376 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514384 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514392 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514400 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514408 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514416 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514424 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514432 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514440 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514448 Dec 22 16:06:27 Tower kernel: md: disk0 read error, sector=25514456 Dec 22 16:07:54 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslogcode]
-
I found the Hardware list after post my message. I have ordered a 4 port from the list. Thanks.
-
Looking to add more drive and would like to by one or two 4 port sata cards. The recommended one daptec 2241000-R PCI Express x4 SATA II is not availabe new. The recommended SuperMicro is a bit expensive. I see a 17.00 4port on Monoprice, that in the review section, app pears to be plug and play.
[DOCKER] Mythtv
in Docker Containers
Posted
Thanks very much. I will give it try once I get my Hdhome/Hdhomerun Prime boxes sorted.