Gragorg
-
Posts
499 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Gragorg
-
-
Did you login to https://www.plex.tv/ or your local ip webgui for your server?
-
If you login to plex.tv website can you select a movie? If so Hit the "..." and select "get info". In the bottom left corner of the window hit "View XML". Take a look in the address bar of your browser and the the token should be at the end. You can copy this for your docker template.
-
You should post your diagnostics. It sounds like you put the 3 drives in the array. Typically SSDs are not recommended for the array as there is no TRIM support. If this is the case I would put the 2TB in the array and use the SSD in a pool for testing.
-
Yes you can remove the trial key and reboot. I would make a copy of it just in case something goes south.
-
Is your docker image showing full on the dashboard? Also post your diagnostics.
-
You can do the parity swap procedure.
-
Currently my parity is by far my largest drive and I agree it should skip the portion after the largest data drive. However there is no way to skip. Would be a good new feature thou.
-
Here is the list of approved controllers. JMB585 and Asmedia are both on the approved list. Just be sure they do not use port multipliers. So a JMB585 should be a 5 port card and an Asmedia ASM 1166 is a 6 port. Both chipsets should work well.
-
So when I did my parity check this month I had an issue with a drive connection resetting so it took longer than normal. When i completed the parity check it send a notification (telegram) that said it took "1 day, 9 hr, 4 min, 14 sec". In reality it took "1 day, 17 hr, 29 min, 10 sec" and I can see that clearly in the history. Yesterday I went to address the drive that was resetting connection but since I had a warm spare already in my machine I just used it to rebuild. The rebuild notification reported "1 day, 17 hr, 29 min, 10 sec" was the completion time. In reality it took "8 hr, 20 min, 35 sec" as it is clearly listed in the history. It seems to be sending the previous time. Is this a known bug?
-
The requirement for an array device is going to be removed in a future release. The ZFS zpool has higher performance but drives do not spin down. The array allows you mix and match hard drive sizes and expand one drive at a time when needed. It also spins down unused drives to save power but performance is limited to the performance of a single drive as data is not striped. If you lose one drive your data is covered in both cases (array and raidz). If you lose two drives the raidz pool you would lose your data while the array would only lose the two failed disks and all remaining data would be intact. You can add a second parity to the array to have a two disk fault tolerance.
-
Update went smoothly. Thanks for all your hard work.
-
1
-
-
I would run an extended smart test on the disk. CRC errors are usually a connection issue. However if the Realocated sector count and Reported uncorrect increase it could be a disk problem and I would change the disk. I believe CRC errors are already corrected.
-
15 hours ago, JorgeB said:
I believe this is normal if you use macvlan with bridging disabled, try ipvlan if it works for you.
This seems to be the case for me I am using macvlan with bridging disabled. What really threw my for a loop is my netgear RAXE 500 actually sees both them for the same ip while my old router did not.
-
Take a peak in your config folder on your usb is pro.key file present there? I assume you followed the email instructions from unraid and rebooted to take effect?
-
I'm not familiar with your controller card but you motherboard won't slow them down. JorgeB did some good testing on controllers you can find here.
-
Typically monthly parity check are non correcting. If you look under settings and scheduler under the parity check section then "Write corrections to parity disk:" is by default set to no. The check mark on the main page is for manual parity checks
-
Your first three parity checks detected the errors but nothing was corrected until you ran the correcting parity check. The follow up parity check should be zero since you ran a correcting parity check.
-
You won't see a performance difference with a LSI card your current board is not capping your drive speed.
-
Unrelated but your appdata backup and unbalance plugins are depreciated. The new version is appdata backup by KluthR and unbalanced is the name of the new unbalance.
-
The drive with problem is Sdc which appears to be your parity drive. There is no point finishing the rebuild of parity until you figure out the cause. I'm no expert but if it was me I would stop the rebuild powerdown and replace/check power and sata cables to your parity drive including any splitter you have on that drive and try again.
-
Any share you setup has primary and secondary storage as well as mover action. So if you set the download share primary as cache and array as secondary with mover action cache-->array it wlll move the download files to the array from the cache. Most use the "arr" dockers to move media files to the media folder when completed. Some setup media folders as array only so when downloads are completed they are moved direct into the array. In this case media is setup as primary as array and secondary and mover action are left blank. Some prefer the media share set to cache as primary and array as secondary with the mover action set cache-->array. In this case files are usable by your media player right away but are protect by the array once the mover runs.
-
You can post your diagnostics here for the pros. The "Anonymize diagnostics" box is usually checked by default.
-
1
-
-
That CPU does not have quicksync so the CPU will get hammered trying to transcode with the cpu. You could look for a used Xeon chip from the Haswell family that has quicksync built in. A Haswell Xeon with quicksync will handle 1080p streams with transcoding all day long. Here are E3 1275 v3 on ebay. Worth mentioning I beleive you need plex pass to use hardware transcoding.
-
Here is the recommended list. Most seem to use LSI cards but there are some inexpensive 6 port options on amazon.
error when trying to update Docker container
in General Support
Posted · Edited by Gragorg
Look like something is filling your docker image. If you hit the "container size" button on docker tab is there anything obvious? Also turn on the advanced view switch on the docker tab and see if you have any orphans at the bottom of the screen.