lars

Members
  • Posts

    143
  • Joined

  • Last visited

Posts posted by lars

  1. Out of curiosity, has anyone upgraded to Beta21 from 6.1.9 ?  Just curious how the process went for you, trying to get a feel if some of the subsequent betas have smoothed this over or not.

     

    Thanks.

     

    i actually just did about 2hrs ago on my back-up server. the install/ update went generally smooth. nearly everything is working... my docker apps seem to be all disappeared (wasn't much to start with, just madsonic, calibre and plex. what i get instead of the apps is a grayed-out pic saying 'orphaned image'. did not yet really figured out the solution. updating (as said in thread) is not an option - just not happen, new install to old directory ends with failure. will work on that later or roll back to 6.1.9... we will see. all else seems to work fine. what interested me most was the 2nd parity disk option - tossed in a drive i had sitting around, which fits the specs and got that process going. it is going, but i seem to have a huge performance loss for the parity check speed, while under 6.1.9 it was bumbling along at around 120-125MBs for the last 2hrs it is snailing even more at about 80-85MBs. i thought there where supposedly nice improvements. we will see - as it is, i am looking at another (gui estimated) 9hrs to see if it suddenly 'turbos up'.

    can update that later, if you are interested...

    ohh, btw... thats what i get on the dashboard screen under parity status:

    Last checked on Friday, 08-04-2016, 23:25 (today), finding 0 errors.

    Duration: unavailable (no parity-check entries logged)

     

    seems not exactly rite - at the moment i just let it run and see 2morrow pm what happen ;)

     

    cheers, L

     

    ps: the verification system s*cks majorly!!! i am not into movies at all! wonder how ppl would feel if they suddenly have to figure out what the 2nd official live album of Sham 69 was??? i am sure that could be solved in a more common way!

     

    i quote here on myself - i couldn't remember the password for my old account, don't have the email account it was linked to anymore.... yadayadayada... anyway, after being able to look up my own profile i figured it out again and now i am back as me LOL.

    i will get rid of the 'one post account'.

     

    anyway, i like the new beta so far. still try to wrap my head around the docker issue.

    otherwise, the parity check is roughly going as fast as molasses flows uphill on a reaaaaally cold winter day! it did not turbo up, but nearly halfed in speed since my last post - how can that be, considering no hardware changes etc. - just upgrading 6.1.9 to b6.2-21???

     

    cheers, L

  2. have to say, after running rc4 over rc3 now for about 2 1/2 days, the average gui displayed hdd temp is about 3-5°C hotter than before upgrade. still not getting alarming, but considering nothing else changed it is kinda strange.

     

    cheers, L

  3. If you're on a static IP and have had the ISP set up a reverse DNS record for your mail server, running one at home can work.  But on a dynamic IP (most residential connections) where reverse DNS records are impossible, most of your mail will get rejected and/or tagged as spam as NAS states.  In addition, most residential IP blocks are blacklisted by spam filters.

     

    So yes, it can be done, but it's an uphill battle.

     

    i wasn't trying to encourage ppl to set up their own mail servers, it's way beyond the needs of most of us. i was just saying that nobody should recommend email services like gmail and the likes this days. i listed 3 alternatives above that offer encryption (which you can 'super enforce by encrypting in top of it beforehand with sth like pgp), no ip logging etc. there are more than this examples around. so, no need to set that up at home, reasonable save options are out there, same for other stuff.

    i just tried to call to mind, we are not living in 1990 anymore, not even wanna really mention snowden... just saying we all (law abiding, upright citizens as we are) should take it in our own hands to see that basic constitutional rights of us are still taken care of, even with patriot acts +++ in use. i even love the idea to say 'hi dad, happy birthday' and have it heavily encrypted. because even that simple line is something between me and my dad. i don't need google to analyze it and offer flower shops online as a result and it is nobody else's business along the line that my dad has his birthday and i like him enough to congratulate.

     

    nobody should go completely over-board here, but reasonable measures should be taken by everybody this days. that includes not to recommend services, software etc. with a more than question-worthy background. if i want my information out there, i will sell it to the highest bidder - i am not offering it on the silver tray.

     

    anyway, all that was just meant as a friendly advise and we don't need to argue that any further. each to his own ;)

     

    cheers, L

  4. The general rule of thumb is dont run a mail server at home as most of you mail will be marked as spam or rejected upstream.

     

    Definitely gmail

     

    don't run it at your home server i can follow, gmail as recommendation is beyond me! maybe i am paranoid, don't like ppl to have semi-easy access to my mail (may it be big brother, or just small brother google)...

    to recommend anything like gmail, yahoo. aol etc... this days is just WRONG! we all should be a little more conscious about our data, mails, communication in general online!

    so let me suggest some alternatives with a reasonable security expection:

    for email: OpenMailBox.org, ProtonMail.ch, Tutanota.com (btw, i also don't really agree with your argument about not having own mailservers, but we don't need to push that here)

     

    generally i recommend this days as starter reading https://www.privacytools.io/ about security for your own hardware, how far you want to push that is a personal decision. i have not really anything to hide (yeah rite haha, who has no skeletons in the closet somewhere...?), but i don't see a reason to make it easy to find them.

     

    cheers, L

  5. well updated a couple hrs ago. got rid of my old apcups  plugin before. update worked flawless, did the docker img thingy - also no prob. so far so good. beside the one or other little cosmetic issue (some might be even intentionally) and the highly annoying 'hdd not spin down' issue after first check all seems to be a-ok. time for a spliff and some more checking  8)

     

    cheers, L

  6. Another nit-picking item.  On the GUI, if you go the the 'Settings', 'Global Share Setting', 'Cache Settings' and (I do not have a cache drive installed), the 'Done' button is inactive.  It does not return to the 'Settings' page as all of the other 'Done' buttons do.

     

    i would guess it's a minor oversight - since the array has to be stopped to make changes there, it actually works for me with stopped array. so, yep nit-picking  ;). but should be fixed at one point.

     

    cheers, L

  7. Just updated to beta 14 from beta 12. Noticed this in my syslog.

     

    Feb 21 07:27:22 Dirge kernel: ------------[ cut here ]------------
    Feb 21 07:27:22 Dirge kernel: kernel BUG at fs/btrfs/inode.c:3123!
    Feb 21 07:27:22 Dirge kernel: invalid opcode: 0000 [#1] SMP
    Feb 21 07:27:22 Dirge kernel: Modules linked in: md_mod it87 hwmon_vid k10temp r8169 mii sata_sil i2c_piix4 ahci libahci
    Feb 21 07:27:22 Dirge kernel: CPU: 2 PID: 7466 Comm: btrfs-cleaner Not tainted 3.18.5-unRAID #3
    Feb 21 07:27:22 Dirge kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./SABERTOOTH 990FX R2.0, BIOS 2103 11/06/2013
    Feb 21 07:27:22 Dirge kernel: task: ffff8803f8064890 ti: ffff880007e14000 task.ti: ffff880007e14000
    Feb 21 07:27:22 Dirge kernel: RIP: e030:[<ffffffff812cce1e>]  [<ffffffff812cce1e>] btrfs_orphan_add+0xc8/0x15d
    Feb 21 07:27:22 Dirge kernel: RSP: e02b:ffff880007e17c58  EFLAGS: 00010286
    Feb 21 07:27:22 Dirge kernel: RAX: 00000000ffffffe4 RBX: ffff8803f80a4800 RCX: 0000000000000000
    Feb 21 07:27:22 Dirge kernel: RDX: 0000000001400140 RSI: 0000000016861684 RDI: ffff8803fb87a138
    Feb 21 07:27:22 Dirge kernel: RBP: ffff880007e17c98 R08: 0000000000019cd0 R09: 0000000000000000
    Feb 21 07:27:22 Dirge kernel: R10: 0000000000000000 R11: ffff880007e17c28 R12: ffff8803f89863f0
    Feb 21 07:27:22 Dirge kernel: R13: ffff8803f8899160 R14: 0000000000000001 R15: 0000000000000001
    Feb 21 07:27:22 Dirge kernel: FS:  00002adc4ef9cf40(0000) GS:ffff880418300000(0000) knlGS:0000000000000000
    Feb 21 07:27:22 Dirge kernel: CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
    Feb 21 07:27:22 Dirge kernel: CR2: 00002adc4fd6e488 CR3: 0000000001807000 CR4: 0000000000000660
    Feb 21 07:27:22 Dirge kernel: Stack:
    Feb 21 07:27:22 Dirge kernel: ffff880007e17c98 ffff8803f80a4c58 0000000000000000 ffff8803f81b0e00
    Feb 21 07:27:22 Dirge kernel: ffff8803f80a1800 ffff8803f889d630 ffff8803f89863f0 ffff8803f8899160
    Feb 21 07:27:22 Dirge kernel: ffff880007e17d28 ffffffff812ba667 ffff8803f889d630 ffff8803f889d630
    Feb 21 07:27:22 Dirge kernel: Call Trace:
    Feb 21 07:27:22 Dirge kernel: [<ffffffff812ba667>] btrfs_remove_block_group+0x11b/0x484
    Feb 21 07:27:22 Dirge kernel: [<ffffffff812e8e33>] btrfs_remove_chunk+0x589/0x600
    Feb 21 07:27:22 Dirge kernel: [<ffffffff812dec20>] ? free_extent_state.part.26+0x34/0x38
    Feb 21 07:27:22 Dirge kernel: [<ffffffff812defe4>] ? free_extent_state+0x15/0x17
    Feb 21 07:27:22 Dirge kernel: [<ffffffff812bab9b>] btrfs_delete_unused_bgs+0x1cb/0x207
    Feb 21 07:27:22 Dirge kernel: [<ffffffff812c09a2>] cleaner_kthread+0x11b/0x14a
    Feb 21 07:27:22 Dirge kernel: [<ffffffff815fcb91>] ? _raw_spin_unlock_irqrestore+0x50/0x60
    Feb 21 07:27:22 Dirge kernel: [<ffffffff812c0887>] ? btrfs_destroy_pinned_extent+0x9a/0x9a
    Feb 21 07:27:22 Dirge kernel: [<ffffffff81057486>] kthread+0xd6/0xde
    Feb 21 07:27:22 Dirge kernel: [<ffffffff810573b0>] ? kthread_create_on_node+0x172/0x172
    Feb 21 07:27:22 Dirge kernel: [<ffffffff815fd0fc>] ret_from_fork+0x7c/0xb0
    Feb 21 07:27:22 Dirge kernel: [<ffffffff810573b0>] ? kthread_create_on_node+0x172/0x172
    Feb 21 07:27:22 Dirge kernel: Code: 01 72 08 41 be 01 00 00 00 eb 03 45 31 f6 48 8b 7d c8 e8 eb fc 32 00 45 85 f6 74 11 4c 89 e6 4c 89 ef e8 6c 7e fe ff 85 c0 74 02 <0f> 0b 41 ff cf 75 76 49 8b 94 24 68 fe ff ff 48 85 d2 74 0b 41
    Feb 21 07:27:22 Dirge kernel: RIP  [<ffffffff812cce1e>] btrfs_orphan_add+0xc8/0x15d
    Feb 21 07:27:22 Dirge kernel: RSP <ffff880007e17c58>
    Feb 21 07:27:22 Dirge kernel: ---[ end trace 6f663e95f806acc6 ]---
    

     

    Just wondering what it is.

     

    you must have hit the the "start auto self destruct sequence" button sparklyballs just mentioned!!!! ;D

     

    cheers, L

  8. Since we are telling everyone to recreate their docker image we really should provide a procedure how to do so in the least amount of steps whilst preserving container settings etc.

     

    +1

    sounds like the sensible thing to do! kinda good customer relation & pr-work , instead of telling ppl '...btw you will have to do this and that afterwards (and now go figure it out in the forum)...' many here poss. have little or none probs to deal with it, but many others looking at a potential scary and disastrous adventure  ;D

     

    cheers, L

  9. just to chime in here on the complaints. it is a beta release, as others pointed out as well. so please stop bit**ing! i don"t have the luxury of a test-server this days myself. so, as much as it itches to upgrade.... on a production server it is a NONO! or you don"t care about your data. i have to wait this days also for a couple days and see what pops up, after that make a decision if it is reasonably safe to upgrade. it is BETA, means bug prone. usually LT does a fine job to release working beta"s with few problems, BUT shit happens! if you want to be on the cutting edge you accept that risk and use the chance to help fix initial problems, or you play it conservative and wait a little, analyze existing probs and how they might affect your system.

    you def are not pissed off, because....!!!!

     

    just had to say that for once.

     

    cheers, L

  10. The intent was for apcupsd webGui plugin to be included in the build, but we removed because we haven't completed it's testing and we didn't want to delay this release even more.

     

    I'm not sure I understand the reluctance to include the apcupsd plugin.  It is a webgui that adjusts the apcupsd.conf file for the desired operation and starts and stops the apcupsd daemon that is in the apcupsd package.  There are many using the apcupsd plugin and of all the plugins, it has probably been tested more thoroughly than any others.  If has been tested thoroughly by PeterB with his constant power black and brown outs.

     

    What do you think LT needs to test?

     

    Including the apcupsd plugin in b13 would have prevented a lot of the update issues and not introduced any new issues and prevented a lot of headaches.  Any adjustments in the operation you felt needed to be done could have been done at a later release.

     

    same as PeterB, i live in a country (jamaica) with constant power outages, brown outs and spikes. my house is generally set up with a surge protector, the computers with extra apc power filters and apc ups. your little plugin saved my ass more than once.anyway, what i do not really understand at this point is the decision to integrate part of the apc plugin, but not the rest. seems to me to create more probs than it solves. either you take it in the core unraid all the way, or you leave it as a separate plugin. as is at the moment it"s a half-assed solution and a step back.

    i hope with b14 we will see either, full integration or back to plugin which was stable, well developed and without major issues.

    personally i think it is not necessary to integrate everything with brute force. keep developing the core and add more features over time and fully.

     

    cheers, L

     

  11. yep well, maybe it would be not a bad idea to have sth like a beta12b version. which actually just focuses on fixing the most common encountered bugs in beta12, instead of introducing new features which may work flawless or not. don't get me wrong, i am pretty happy with b12! only real issue i have is drives not spinning down when they should (i guess thats better than not spinning up, but still annoying).  but there seem to be more probs for other users. so why not take a breath, stop introducing all kind of new and improved features, get a grip on the existing probs and try to solve them... than go with new steam on b13 (or rc1).

    i am easy going using only one plugin and one docker-app. i would think for others the issues are a lot worse.

     

    cheers, L

  12. Hi Lars I think you need to better understand the v switch in docker, basically it's split into host part, this is the path on the left of the colon, then there is the docker side which is the path on the right. The path on the left is easy, this is simply the path to what you wish to share with the docker container e.g. /mnt/user/Music. The right hand side is the root folder created within the docker that you use with the app to access the media from your host e.g. /Music

     

    So the whole thing would look like this -v /mnt/user/Music:/Music

     

    You can of course be lazy and simply share the whole of your array by simply specifying /mnt:/mnt I hope this helps.

     

    sorry wasn't really clear there before. what i used initially was:

     

    docker run -d -p 4041:4040 -p 4051:4050 --name=madsonic-binhex -v /mnt/user/LFI/Music:/Music -v /mnt/cache/appdata/madsonic-binhex/:/config -v /etc/localtime:/etc/localtime:ro binhex/arch-madsonic

     

    that led for whatever reason in madsonic with any variation to media folder not found, next i went up one level to just /mnt/user/LFI:/Music same result with all kind of tries... and so on.

    now i went for the /mnt:/mnt and it works. not my favorite solution, but hey suddenly madsonic can find my media folders, just had to adjust the path in madsonic accordingly.

     

    thx for the help!!! didnt even came to my mind before to try that!

    having a happy Lars now  ;)

    still wondering what the issue was with the other path variations....

     

    anyway, it is working

     

    cheers, L

     

     

    Working off your first example (-v /mnt/user/LFI/Music:/Music)

     

    if under /mnt/user/LFI/Music you had:

    /mnt/user/LFI/Music/artist1
    /mnt/user/LFI/Music/artist2
    /mnt/user/LFI/Music/artist3

     

    Within the madsonic docker what madsonic will think the directory structure is like is:

    /Music/artist1
    /Music/artist2
    /Music/artist3
    

     

    So in this case in the gui you'd just share /Music to madsonic and it should pick up everything.

     

    Also, I hope you're changing your config directory for each different version you're trying to run or they will all step on each others toes.

    that was my thought as well, but it didn't. don't ask me why! right now i have it running with /mnt:/mnt - fine for the moment. it bothers me as well, why it wont see the other options. i will investigate further on that with a new container. so far i established that 5.1 is running a lot faster in the gui daily use events (i assume it's based on additional/ optimized caches for the gui) and also a full database scan went down from about 40hrs to roughly 12hrs. that is still insane compared to my old scan times of about 3hrs running subsonic as .plg - but it is doable, considering i do that once a week.

    thx anyway for the knowledge sharing. i will take your advice as a guideline again for the next experiments!  ;D

    hope i get that to work at one point as well. /mnt:/mnt does not strike me as an outrageously clever idea to begin with + i could see (just the layman's way of thinking!) that shorter path leads to shorter scan times  ::) - i do not wanna go into my logic behind that rite now, fearing to get a digital beating  ;D

     

    cheers, L

  13. Hi Lars I think you need to better understand the v switch in docker, basically it's split into host part, this is the path on the left of the colon, then there is the docker side which is the path on the right. The path on the left is easy, this is simply the path to what you wish to share with the docker container e.g. /mnt/user/Music. The right hand side is the root folder created within the docker that you use with the app to access the media from your host e.g. /Music

     

    So the whole thing would look like this -v /mnt/user/Music:/Music

     

    You can of course be lazy and simply share the whole of your array by simply specifying /mnt:/mnt I hope this helps.

     

    sorry wasn't really clear there before. what i used initially was:

     

    docker run -d -p 4041:4040 -p 4051:4050 --name=madsonic-binhex -v /mnt/user/LFI/Music:/Music -v /mnt/cache/appdata/madsonic-binhex/:/config -v /etc/localtime:/etc/localtime:ro binhex/arch-madsonic

     

    that led for whatever reason in madsonic with any variation to media folder not found, next i went up one level to just /mnt/user/LFI:/Music same result with all kind of tries... and so on.

    now i went for the /mnt:/mnt and it works. not my favorite solution, but hey suddenly madsonic can find my media folders, just had to adjust the path in madsonic accordingly.

     

    thx for the help!!! didnt even came to my mind before to try that!

    having a happy Lars now  ;)

    still wondering what the issue was with the other path variations....

     

    anyway, it is working

     

    cheers, L

  14. to bring it down to my main issues at this point - the response of the gui is sub-optimal and what sucks even more is the time of a rescan. my last folder rescan took just under 39hrs! that's unacceptable!

    i am looking for improvements.

    considering my issue with with media folders not found in binhex and pinion options... i need the working botez option still, don't I? ;)

    i actually tried  in the meantime the deactivate botez-madsonic completely and just run unmodified binhex-madsonic. same friggin result! "No media folders found.

    Please change the settings." in the header bar, behind every folder i try to create in settings i get a "folder not found" comment. kinda on the end of my (limited) knowledge here. it was/ still is all fine with 5.1.4800.beta2. i was really hyped about 5.1final. especially reading stuff like faster, smoother, better. at the moment it is faster (yes, but i cant get media running), smoother, yep... with 2.5promille in my head i can enjoy a system without media :/ , better... might be - still to be seen.

    as i said, i tried 'unmodified' in the meantime - same result. i get the actual madsonic up and running. all good, i can change/ adjust/ modify everything - no prob. i just get this folder not found issue.

    let me ask you a question here - being the semi-noob idiot.

    i tried all kind of variations at this point for the /media setting - from /mnt/user over /mnt/user/<sharename>, ... deeper drilling down the tree - all to the same result. tried the same with settings like boohbah's - to music and movie instead of media.... all leading to the same result. considering that i had to mkdir .last.fm-cache/ and thumbs/ manually anyway in order to get madsonic up and running in the first place... do i have to create /media as well somewhere???? i tried a couple places allready, with no positive result. got rid of them as well again, since it was a no go.

     

    basically my /mnt/user goes /mnt/user/<sharename>/music/A ... /B... /C... -... /movies/A... /B ... /C - i tried all kind of path options so far, even outlandish ones with no go. basically i would think when /mnt/user:/media it should be /<sharename>/music/folder in settings-madsonic. i tried also there all kind of unlikely stuff - always leading to 'folder not found'

    what do i do wrong? :(

    is there a rw setting i miss?.....

     

    any help would be appreciated!

     

    cheers, L

  15. Why do you need them both running?

     

    i don't need them both running - just one at the time and figure out which one works better ;)

     

    at the moment it does not matter - like the botez version is working. none of the others does!

    i am going slowly up the wall here. trying to figure out why the folders are not seen.

    just getting majorly pissed. i need the botez install running at the moment - because it works  8)

    i like to get yours or binhex's to work - cause i have issues with botez' - which might be solved by yours or binhex's version.

    i wanna see that before i switch.

    at the moment it seems like whatever version i try - it will not see my folders.

    i am kinda cautious this days - having friends on the server. just dont want a 'upgrade' - leading to a 3 day downtime due to a folderscan. which wouldn't be happen at the moment anyway - since the media folders are not recognized...

     

     

  16. No media folders found.

    Please change the settings.

     

    is what i get now in the binhex-madsonic gui. everything else is working fine  ::)

    guess i have to play a little more with the media folder settings  :'(

    so far i just took them from botez version over to it.

    well, that will be solved also, at least madsonic itself is running for now :)

     

    cheers, L

  17. I too updated last night 6.0~beta10-x1 and everything seems to be running really well.  No issues yet.

    I wonder why it appears several people can see the beta 10 update, but others (e.g. myself) cannot.  Are you perhaps running a version of the GUI that has been updated past that supplied with beta 9?

     

    i am running stock 6b9.

    i remember there was sth to change on flashdrive in regards to the dockerman integration, which i did at the time. but i can't see that would affect the unraid-update function really.

  18. ok the release notes can be found under tools - release notes:

     

    Summary of changes from 6.0-beta9 to 6.0-beta10

    -----------------------------------------------

    - avahi: fix issue with OSX causing "Invalid response packet from host" messages.

    - dhcpcd: use the hardware address of the interface for the Client ID.

    - emhttp: improve http connection handling

    - emhttp: when cache device re-assigned set file system type to 'auto'

    - emhttp: fix issue creating cache-only share following cache device format completion

    - linux: update to 3.16.3 (reiserfs corruption patch built-in)

    - linux: support all Winbond h/w monitor chips

    - netatalk: update to 3.1.6

    - slack: fixed rsyslog syslog rotation

    - slack: fixed acpi power-button event

    - slack: don't start AFP in rc.M

    - slack: inetd.conf: comment out unused comsat and auth services

    - slack: update bash to 4.2.048 (shellshock bug fix)

    - plgMan: version 2014.09.12

    - webGui: added 'Default file system' on Disk Settings page (default is XFS)

     

    it would be great to see them before updating!

     

    cheers, L

  19. i just bit the bullet and installed it - immediate changes i noticed are in the layout of the gui dockerman and linux is updated to 3.16.3

    there might be more. as i said, couldn't find a changelog.

     

    also, it might be useful to give ppl some guidance how to proceed with this way of updating. i just stopped my array, did the update and rebooted my server. looks like that did it. and running now 6.0beta10-x1

     

     

    cheers, L

     

    ps: plugins and docker have now separate tabs as well, forgot to mention that.