sacretagent
-
Posts
943 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by sacretagent
-
-
adding a 4th to be able to shut down the other 3 at night
having now 2 running 24/7
-
Hi guys,
moving soon to my new home and i was wanting to make some changes to my setup but without spending too much money
for the moment i have a w7 desktop and 1 unraid (TVRAID in my sig) running 24/7 and would like to reduce that to one machine
i know already some of you guys going to say replace your hdd with 4 or 6TB ones and only use one unraid server but that is simply to costly for the moment ... would also need new case for that
and waf would be around zero LOL
so basically what i was thinking is to use a server i got for free (dl380 g8 with 2 x Xeons and 32 GB of ram) as the workhorse in the setup
to run all applications, so that during the night i can shut down my 2 unraid servers and my desktop
and use the 2 unraid servers for what they were meant to be without any other fuss.... the current setups have no processor power to much as i am running them already to the max (specs see sig)
the dl380 would be running plex / sickbeard/ sabnzbd/ couchpotato / headphones / lazylibrarian and whatever else i would need
he would download things which i would like to move to my unraids like every day at noon and 19.00 hours
i would also like to run some vpn software on the dl380 so i can get rid of hamachi since this server has 4 x 1gb nics
now what i am unclear about is what OS i should run ... LOL
i am reasonably versed in linux with unraid and ubuntu / debian / rhel and there is windows LOL
i was thinking/hoping there was some special version of a distro that would maybe make things easier
something that would automount unraid shares
something with vpn software build in
something that would make rsync easy
something that would check the unraid boxes if they were up or down to mount the shares
something with a GUI lol
but i guess i am dreaming here .. hoping for the easy way out without all the hassle
i know if i install ubuntu desktop on the dl380 that i can apt-get everything above here but every time i ran some setup outside of unraid (tried Xen for a month or two) i always get into issues it seems with mounting shares
i tried over time nfs and smb shares and there is always some hassle it seems ... never tried this automount yet though so that might improve things....
but still anybody running something similar?
what os are you running? any advice on this automount thing? (autofs)
i know windows can run all above programs and with gui but i seem to worry about auto syncing things to the unraid servers from a windows machine .... there doesn't seem to be a real good program out there to do that ?
been using freefilesync now for a while now to move things from my w7 desktop to bitcasa.... but that is not really automatic .... i mean it will not autosync at noon and 19:00....
so i am kind of looking for ideas .... any suggestions welcome but like i said upgrading unraid hardware and selling the dl380 is not an option ....
need to work with the things i have ..... and i would continue running like i am now, but i am really abusing this i5-760 cpu already with all i am running in dockers
so adding a torrent client to this unraid would not be possible so i still need my desktop to run 24/7 too
-
Plugin itself is not updating and the update detection is showing I need to update plexwatch and I do it and it still shows i need to update it.
Got same issue ....
multiple blue arrows...
upgrade it but blue arrows don't go away
examples Mariadb, Dropbox, on one server crashplan and plex but on the other server both have green checks.... plex version is same on both servers though... crashplan too
-
squid and everybody else who uses md5 or any other kind of checksum
what are you using to make these?
how automated is this?
as i have like a million files on these servers.. would hate to do this one by one
i thought i sawsome script but didn't have the time to try it yet but this would be my first priority after upgrading to beta9
seems that script was to find duplicates ...
-
automated update in extensions not ready yet ?
just asking
tried to click check update but nothing found
-
Quoting jonp:
I would suggest migrating away from reiserfs as users find the opportunity to do so. Its not a rush... Its not going to break... Its been very stable...
Hmmm ......
Maybe I should go update that thread... 
You jinxed it ... see what happens when you wake the death
jonp has strong voodoo....
-
Are you seeing those same error messages in your syslog as the person who reported the issue with unMENU??
(are you running loop-back devices?? with docker images??)
I am the one who first reported it
see also this -> http://lime-technology.com/forum/index.php?topic=27051.msg326217#msg326217
so yeah i am running beta 8 with the loopback loop 8 for the dockerimage
-
not wanting to piss anybody off ... especially not NAS or Needo or GFJardim
but was just wondering when we are going to upgrade the baseimage?
0.9.13 was released end of August
and although nothing in the release notes make me want to jump to a new image
see -> http://blog.phusion.nl/2014/08/22/baseimage-docker-0-9-13-released/
i was just wanting to know what our criteria would be to change to a newer image?
-
hi Joe
server r2d2
root@R2D2:/# /root/mdcmd status | strings | grep loo
root@R2D2:/#
server p8h67
root@P8H67:/# /root/mdcmd status | strings | grep loo
root@P8H67:/#
r2d2 without the grep
root@R2D2:/# /root/mdcmd status | strings
sbName=/boot/config/super.dat
sbVersion=2.2.0
sbCreated=1406786502
sbUpdated=1409912139
sbEvents=24
sbState=0
sbNumDisks=14
sbSynced=0
sbSyncErrs=0
mdVersion=2.3.0
mdState=STARTED
mdNumProtected=14
mdNumDisabled=1
mdDisabledDisk=0
mdNumInvalid=1
mdInvalidDisk=0
mdNumMissing=0
mdMissingDisk=0
mdNumNew=0
mdResync=0
mdResyncCorr=0
mdResyncPos=0
mdResyncDt=0
mdResyncDb=0
diskNumber.0=0
diskName.0=
diskSize.0=0
diskState.0=4
diskId.0=
rdevNumber.0=0
rdevStatus.0=DISK_DSBL_NP
rdevName.0=
rdevSize.0=0
rdevId.0=
rdevNumErrors.0=0
rdevLastIO.0=0
rdevSpinupGroup.0=0
diskNumber.1=1
diskName.1=md1
diskSize.1=1953514552
diskState.1=7
diskId.1=SAMSUNG_HD204UI_S2H7J9JB614304
rdevNumber.1=1
rdevStatus.1=DISK_OK
rdevName.1=sdn
rdevSize.1=1953514552
rdevId.1=SAMSUNG_HD204UI_S2H7J9JB614304
rdevNumErrors.1=0
rdevLastIO.1=0
rdevSpinupGroup.1=0
diskNumber.2=2
diskName.2=md2
diskSize.2=1953514552
diskState.2=7
diskId.2=WDC_WD20EARX-00PASB0_WD-WMAZA8611843
rdevNumber.2=2
rdevStatus.2=DISK_OK
rdevName.2=sdm
rdevSize.2=1953514552
rdevId.2=WDC_WD20EARX-00PASB0_WD-WMAZA8611843
rdevNumErrors.2=0
rdevLastIO.2=0
rdevSpinupGroup.2=0
diskNumber.3=3
diskName.3=md3
diskSize.3=976762552
diskState.3=7
diskId.3=Hitachi_HDT721010SLA360_STF607MH3N350K
rdevNumber.3=3
rdevStatus.3=DISK_OK
rdevName.3=sdc
rdevSize.3=976762552
rdevId.3=Hitachi_HDT721010SLA360_STF607MH3N350K
rdevNumErrors.3=0
rdevLastIO.3=1410097247
rdevSpinupGroup.3=0
diskNumber.4=4
diskName.4=md4
diskSize.4=1953514552
diskState.4=7
diskId.4=WDC_WD20EARX-00PASB0_WD-WCAZAC672415
rdevNumber.4=4
rdevStatus.4=DISK_OK
rdevName.4=sdg
rdevSize.4=1953514552
rdevId.4=WDC_WD20EARX-00PASB0_WD-WCAZAC672415
rdevNumErrors.4=0
rdevLastIO.4=0
rdevSpinupGroup.4=0
diskNumber.5=5
diskName.5=md5
diskSize.5=976762552
diskState.5=7
diskId.5=WDC_WD10EARS-00Y5B1_WD-WCAV5M103508
rdevNumber.5=5
rdevStatus.5=DISK_OK
rdevName.5=sdd
rdevSize.5=976762552
rdevId.5=WDC_WD10EARS-00Y5B1_WD-WCAV5M103508
rdevNumErrors.5=0
rdevLastIO.5=1410097657
rdevSpinupGroup.5=0
diskNumber.6=6
diskName.6=md6
diskSize.6=1953514552
diskState.6=7
diskId.6=ST2000DM001-1CH164_Z1E4BSSC
rdevNumber.6=6
rdevStatus.6=DISK_OK
rdevName.6=sdh
rdevSize.6=1953514552
rdevId.6=ST2000DM001-1CH164_Z1E4BSSC
rdevNumErrors.6=0
rdevLastIO.6=1410097534
rdevSpinupGroup.6=0
diskNumber.7=7
diskName.7=md7
diskSize.7=976762552
diskState.7=7
diskId.7=WDC_WD10EACS-00D6B0_WD-WCAU45503540
rdevNumber.7=7
rdevStatus.7=DISK_OK
rdevName.7=sdi
rdevSize.7=976762552
rdevId.7=WDC_WD10EACS-00D6B0_WD-WCAU45503540
rdevNumErrors.7=0
rdevLastIO.7=1410096902
rdevSpinupGroup.7=0
diskNumber.8=8
diskName.8=md8
diskSize.8=976762552
diskState.8=7
diskId.8=WDC_WD10EARS-00MVWB0_WD-WCAZA0747326
rdevNumber.8=8
rdevStatus.8=DISK_OK
rdevName.8=sdj
rdevSize.8=976762552
rdevId.8=WDC_WD10EARS-00MVWB0_WD-WCAZA0747326
rdevNumErrors.8=0
rdevLastIO.8=1410097247
rdevSpinupGroup.8=0
diskNumber.9=9
diskName.9=md9
diskSize.9=976762552
diskState.9=7
diskId.9=WDC_WD10EADS-00L5B1_WD-WCAU4D176083
rdevNumber.9=9
rdevStatus.9=DISK_OK
rdevName.9=sdk
rdevSize.9=976762552
rdevId.9=WDC_WD10EADS-00L5B1_WD-WCAU4D176083
rdevNumErrors.9=0
rdevLastIO.9=0
rdevSpinupGroup.9=0
diskNumber.10=10
diskName.10=md10
diskSize.10=976762552
diskState.10=7
diskId.10=WDC_WD10EADS-11M2B2_WD-WCAV5A500947
rdevNumber.10=10
rdevStatus.10=DISK_OK
rdevName.10=sdb
rdevSize.10=976762552
rdevId.10=WDC_WD10EADS-11M2B2_WD-WCAV5A500947
rdevNumErrors.10=0
rdevLastIO.10=0
rdevSpinupGroup.10=0
diskNumber.11=11
diskName.11=md11
diskSize.11=1953514552
diskState.11=7
diskId.11=TOSHIBA_DT01ACA200_83PZV9LKS
rdevNumber.11=11
rdevStatus.11=DISK_OK
rdevName.11=sdf
rdevSize.11=1953514552
rdevId.11=TOSHIBA_DT01ACA200_83PZV9LKS
rdevNumErrors.11=0
rdevLastIO.11=1410096900
rdevSpinupGroup.11=0
diskNumber.12=12
diskName.12=md12
diskSize.12=976762552
diskState.12=7
diskId.12=WDC_WD10EARS-00Y5B1_WD-WCAV5W578010
rdevNumber.12=12
rdevStatus.12=DISK_OK
rdevName.12=sde
rdevSize.12=976762552
rdevId.12=WDC_WD10EARS-00Y5B1_WD-WCAV5W578010
rdevNumErrors.12=0
rdevLastIO.12=0
rdevSpinupGroup.12=0
diskNumber.13=13
diskName.13=md13
diskSize.13=1953514552
diskState.13=7
diskId.13=WDC_WD20EARX-00PASB0_WD-WMAZA8131647
rdevNumber.13=13
rdevStatus.13=DISK_OK
rdevName.13=sdl
rdevSize.13=1953514552
rdevId.13=WDC_WD20EARX-00PASB0_WD-WMAZA8131647
rdevNumErrors.13=0
rdevLastIO.13=1410097689
rdevSpinupGroup.13=0
diskNumber.14=14
diskName.14=
diskSize.14=0
diskState.14=0
diskId.14=
rdevNumber.14=14
rdevStatus.14=DISK_NP
rdevName.14=
rdevSize.14=0
rdevId.14=
rdevNumErrors.14=0
rdevLastIO.14=0
rdevSpinupGroup.14=0
diskNumber.15=15
diskName.15=
diskSize.15=0
diskState.15=0
diskId.15=
rdevNumber.15=15
rdevStatus.15=DISK_NP
rdevName.15=
rdevSize.15=0
rdevId.15=
rdevNumErrors.15=0
rdevLastIO.15=0
rdevSpinupGroup.15=0
diskNumber.16=16
diskName.16=
diskSize.16=0
diskState.16=0
diskId.16=
rdevNumber.16=16
rdevStatus.16=DISK_NP
rdevName.16=
rdevSize.16=0
rdevId.16=
rdevNumErrors.16=0
rdevLastIO.16=0
rdevSpinupGroup.16=0
diskNumber.17=17
diskName.17=
diskSize.17=0
diskState.17=0
diskId.17=
rdevNumber.17=17
rdevStatus.17=DISK_NP
rdevName.17=
rdevSize.17=0
rdevId.17=
rdevNumErrors.17=0
rdevLastIO.17=0
rdevSpinupGroup.17=0
diskNumber.18=18
diskName.18=
diskSize.18=0
diskState.18=0
diskId.18=
rdevNumber.18=18
rdevStatus.18=DISK_NP
rdevName.18=
rdevSize.18=0
rdevId.18=
rdevNumErrors.18=0
rdevLastIO.18=0
rdevSpinupGroup.18=0
diskNumber.19=19
diskName.19=
diskSize.19=0
diskState.19=0
diskId.19=
rdevNumber.19=19
rdevStatus.19=DISK_NP
rdevName.19=
rdevSize.19=0
rdevId.19=
rdevNumErrors.19=0
rdevLastIO.19=0
rdevSpinupGroup.19=0
diskNumber.20=20
diskName.20=
diskSize.20=0
diskState.20=0
diskId.20=
rdevNumber.20=20
rdevStatus.20=DISK_NP
rdevName.20=
rdevSize.20=0
rdevId.20=
rdevNumErrors.20=0
rdevLastIO.20=0
rdevSpinupGroup.20=0
diskNumber.21=21
diskName.21=
diskSize.21=0
diskState.21=0
diskId.21=
rdevNumber.21=21
rdevStatus.21=DISK_NP
rdevName.21=
rdevSize.21=0
rdevId.21=
rdevNumErrors.21=0
rdevLastIO.21=0
rdevSpinupGroup.21=0
diskNumber.22=22
diskName.22=
diskSize.22=0
diskState.22=0
diskId.22=
rdevNumber.22=22
rdevStatus.22=DISK_NP
rdevName.22=
rdevSize.22=0
rdevId.22=
rdevNumErrors.22=0
rdevLastIO.22=0
rdevSpinupGroup.22=0
diskNumber.23=23
diskName.23=
diskSize.23=0
diskState.23=0
diskId.23=
rdevNumber.23=23
rdevStatus.23=DISK_NP
rdevName.23=
rdevSize.23=0
rdevId.23=
rdevNumErrors.23=0
rdevLastIO.23=0
rdevSpinupGroup.23=0
root@R2D2:/#
no parity running on that one for the moment (need to get salary to buy one.. just bought a house and other costs get priority
-
you ave to add the templates to get these banners back
https://github.com/gfjardim/docker-containers/tree/templates
see gfjardims post here
Version 2014.09.06-1:- Loads of mods
.Ok, guys, I will explain what has been done in this release.
Tom approached me about two weeks ago, informing that this plugin would be a part of the unRAID core (he asked, I said yes!, etc...).
Then he explained to me that, in his vision, apps should have an icon, and that the templates must be treated as add-ons. No templates should be distributed with unRAID. But the time was short, and beta8 was released without icons and with a limited set of templates.
Well, a lot o development was done this week, the plugin has being broken and fixed all the time (thanks for the patience), but here we stand. Now the plugin have both icons and banners (I don't know if Tom will retain the banners, tho). But the templates issue hasn't being addressed until now.
From now on, No templates will be distributed with this plugin or unRAID by default. What does this mean?
1) Template repositories must be added by the user;
2) Users can add template repositories on the proper field;
To help the transition, I've created a template repository here:
https://github.com/gfjardim/docker-containers/tree/templates
After update the plugin, a new field will appear on the Docker extension page. Add this address there and click Save.
Developers are asked to create their own template repositores. Other way of distributing templates is to host a [conteiner-name].xml file with the container itself and distribute the GitHub address, assuming that it's the only .xml file in there.
Be advised that this is all very new, so expect some hiccups.
Thanks for your support.
-
just wanted to say it is a harmless error
it is looking for the info in /sys/block/loop8/stat
normally this file contains reads/writes and other info....
but since the drive assignation is deprecated to 3 digits is this messing up
now if you go look for this real file you will see that it contains all zeroes so the outcome is not really helpful i guess
but the error is annoying and it fills up the syslog
-
it is definately a unmenu issue....
i narrowed it down to a line in unmenu.awk
but my coding fu is not strong enough to figure out where the drive designation gets deprecated to 3 letters
normal drive assignment in unraid is 3 letters (MD1/ SDA)
so this deprecation is happening to loop8 to which makes it appear as loo...
i put it in the unmenu thread in the hope Joe will have a look at it
-
any way of solving this
Sep 6 12:26:34 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directorySep 6 12:28:39 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
Sep 6 12:30:44 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
Sep 6 12:32:58 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
Sep 6 12:35:04 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
Sep 6 12:37:18 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
Sep 6 12:39:28 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
Sep 6 12:41:43 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
Sep 6 12:43:48 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
Sep 6 12:45:54 R2D2 unmenu[29425]: cat: /sys/block/loo/stat: No such file or directory
this is supposed to be loop8 i guess ...
as it started after upgrading to beta8 with the looped docker image...
been looking around myself a bit and i guess it comes from unmenu.awk line 2275
function GetReadWriteStats(theDevIndex, cmd) {
cmd="cat /sys/block/" disk_device[theDevIndex] "/stat 2>/dev/null"
cmd | getline
disk_reads[theDevIndex] = $1
disk_writes[theDevIndex] = $5
close(cmd)
i assume somebody limited the drive assignment to 3 digits (SDA,SDB, and so on) whic explains the error for loop8 to be deprecated to loo
just not sure where in this script to find that
-
seems unmenu is not very happy with that loop thing
Sep 5 19:38:20 R2D2 unmenu[2584]: cat: /sys/block/loo/stat: No such file or directory Sep 5 19:40:34 R2D2 unmenu[2584]: cat: /sys/block/loo/stat: No such file or directory Sep 5 19:42:37 R2D2 unmenu[2584]: cat: /sys/block/loo/stat: No such file or directory Sep 5 19:44:58 R2D2 unmenu[2584]: cat: /sys/block/loo/stat: No such file or directory Sep 5 19:47:02 R2D2 unmenu[2584]: cat: /sys/block/loo/stat: No such file or directory Sep 5 19:49:04 R2D2 unmenu[2584]: cat: /sys/block/loo/stat: No such file or directory Sep 5 19:51:08 R2D2 unmenu[2584]: cat: /sys/block/loo/stat: No such file or directory
Joe will have to take a look
-
ok bare with me
i am just thinking in the wild here
so i update to beta 8
point the img to /mnt/cache/dock/docker.img
set it to 20 gb
what prevents me from doing a cp /mnt/cache/docker/*.* /var/lib/docker/ ?
basically everything would be copied over? containers and images ?
-
well limetech
unraid is for media files...
i have 45000 + tv episodes
which brings my plex database up to about 1500000 small files which are a pita to transfer ....
takes about 1 day to just move these .....
now i know with just having to rebuild my containers i don't need to move my data
but still it is a lot of work ... download the docker zip.... make changes to the docker file.... then do a docker build and then make the container ....
i know in your testing environment there is not such an abundance on files so i seems all easy to you
but for us in the real world it is a lot of work especially when you change ideas a lot
and the main reason why i updated is because beta 6 btfs version was SLOOOOOW
now beta 7 is much quicker ....
i hope beta 8 is also an improvement ... but i will have to work hard to get there
so i was waiting for beta 9 where i saw already a hint for in one of the posts Tom made to see what changed in that one
-
mmm that will require a lot of work
and i was waiting if limetech would stick with this half assed solution by mounting this docker image
he first lets us go through the trouble of converting our reiserfs cache disks to btrfs without a converting tool ... so moving off cache drive ... reformat ... putting on cache drive again
and now he changes idea again and we need to docker build all our containers again ...
cause i have custom containers which are not in your templates...
if he can tell me how to copy my containers into this new image that would make things MUCH easier ....
-
Please, update to the last version please. I modified so many things that's impossible to keep track them.
well like i said .. when i click check it says it is up to date ...
no new versions show up...
can i stop docker ... remove the plugin
and install extension again ?
or will i loose my templates like this?
running beta 7 fyi
-
gfjardim,
version 2014.08.31 has a small bug ...
when you try to update the docker from the docker page (not app page) then the popup is not showing... you get the text are you sure on top of the field with all containers
but nowhere can you confirm.....
it works though from the app page .....
also when i just did a check update to upgrade to new versions above it said it was up to date ... no new updates ...
Just FYI
oh yeah forgot to tell in both Chrome and Firefox i had the issue as i first thought it might have been a chrome quirk
-
Don't let grumpy see that LOL
he will yell blasphemy
-
10 points an a kiss of the female actress of his choice for Itimpi
will wait for the parity check though .... :0
Tom Might need to add a error message for that .. would make things easier to spot
-
oops here you go
this should be boot from beta 7...
2 start attempts ... 1 start attempt with maintenance
reboot
same start attempts
clean shutdown
-
mmm we can still do docker builds ourselves i hope?
cuase i read templates and then my heart jumps....
i have a few customized dockers that i download the zip from but build on my own unraid .....
-
bug or normal expected behavior?
ok while i was away my home got one of these one in a 3 months power outages and my servers where not shutdown cleanly
yesterday i come back home see that beta 7 is release and since i did a parity check last week sunday i think ok since he is down now i take the flash drive and upgrade
he can start with beta 7 and do a parity check with beta7
but he didn't want to start the array
booted fine
but when i push start the array didn't start not even in maintenance mode
so changed 4 files back to beta6 and now he is running a parity check
guess can upgrade to beta 8 once he completed that LOL
just wanted to know if this is a bug or a sort of protection ?
Maybe I should go update that thread... 
increase docker img space ?
in General Support
Posted
Have 15 gb made from the beginning but now sab doesn't want to start cause i am out of space
the thingie says i am using 15 gb from the 15 gb available
so i would like to increase the space with 5gb ...
searched all over but can't figure out how to do this ....
so please how is this done ?