Jump to content

Roscoe62

Members
  • Posts

    206
  • Joined

  • Last visited

Everything posted by Roscoe62

  1. My UnRAID server is currently running on UnRAID OS version 6.9.2. Although the server is currently working without any issues, I’d like to significantly increase the capacity of the server by increasing the drive size (starting with the parity drive of course. Currently all drives (8 data plus 1 parity) are all 4Tb, and I’d like to increase each one to 12Tb over time). It’s also occurred to me that there are likely benefits, from both a functionality perspective, as well as a general security and support perspective, in updating UnRAID OS to a current/more up-to-date version. However, what concerns me about doing this is that doing so might inadvertently “break” my current system, and I’m thinking primarily from a security perspective. My UnRAID system has a fairly simple use case, which I’ve tried to outline below, and I’m a total noob about network security so when I started reading through the change logs for each of the OS version updates subsequent to 9.6.2 I felt totally out of my depth. What I’m hoping for is for someone to take a look at my use case, and the requirements for each of the different users, and to advise me on the following: · Is it necessary or advisable for me to update to a newer UnRAID OS version? If so, which one? · If I proceed with the update what changes, if any, will need to be made for the different users (media player/WebGUI/Windows user)? Primary use of my UnRAID server – is to act as a repository for my Movie and TV Episode files which are served to 2 media playback devices (currently Zappiti players, but will likely change in the near future). I don’t use my UnRAID server for any virtualization, and I have very few Docker applications (Binhex Plexpass, and Krusader – neither being used any more). I used to use the Plexpass docker application, but found aspects of Plex I didn’t like, so I haven’t used that for years now, and I’m very unlikely to ever pick it up again. USER 1 : Media Playback devices. As alluded to above, providing media for these devices to play is the main reason I built the UnRAID server in the first place. We’re currently only using 2 devices to play back TV Episodes and Movies, but we might add a different player specifically for music playback (I have my CD collection and some multichannel music files also stored on the server), or further media playback devices in the future. Security: Currently, neither of the media players require a username or password to read or play back the files from the Media share on the server. They were able to connect to the UnRAID server, and access the Media share folders I pointed them to when I first set them up. It is a requirement that this level of access remains unchanged OR – if a username and password is required by the media players to support a more recent version of the UnRAID OS – that this change can be made simply with little effort. USER 2 : WebGUI – The UnRAID WebGUI is currently only used to spin the drives up or down, to initiate a parity check, or to shut the server down for maintenance – e.g. – to replace a drive. Security: I currently access the WebGUI from my browser using the ‘root’ user and a password (both stored in LastPass – my password manager). USER 3 : Windows 10 User: From my Windows 10 PC, I have Network Discovery turned on, and I can just select the Server and the user share I need. From here I can easily CRUD my files as required (Create, Reference/Read, Update, Delete). Security: Currently, I don’t require a username or password to perform any of these actions. It is a requirement that this level of access remains unchanged OR – if a username and password is required by me from my Windows 10 PC to support a more recent version of the UnRAID OS – that this change can be made simply with little effort. This is a BIG one, as I’m usually performing these actions regularly (i.e. – almost daily). I’m sorry this is so lengthy. I wanted to make sure I’d provided enough context so any advice given would have the end goal in mind. I’m thankful for any information provided.
  2. UnRAID Support acknowledged and responded to my issue. They confirmed the replacement key did go through, but so far no clues as to why I didn't get the original replacement key email. I did ask the question, and I'll post back here if they respond.
  3. I've ended up contacting support for their help. I'll post back here when I know what's happened, and how the issue has been resolved. It's really only just occurred to me that I don't know anything about the "mechanism" by which the request for a replacement key is sent from my UnRAID server to "UnRAID Central". Maybe that's where the process has fallen over? I don't know - hopefully I'll find out soon. It's not much fun being locked out of the server while I wait...
  4. So, last night I went through the procedure of changing the USB with the UnRAID OS to a new USB drive. I'd been meaning to do this for quite some time as the old USB drive is pretty small (storage space wise - 512Mb), but physically it's large - sticking out the back of the server. This is the first time I've ever done this since buying my license back in 2008. I followed the procedure, and everything worked as per the instructions. When I started the server back up I got the message 'The Registered GUID does not match the USB Flash boot device GUID', I selected 'Replace Key', entered my email address, made sure it was correct. and hit Send. On the instruction page it says 'We strive to manually replace licenses ASAP'. However, it's now just over 14 hours later, and there's no sign of a new key in my email inbox. I've also checked my spam folder locally, and at my ISP - nada. So, have I missed something? How ASAP is ASAP? Should I contact Support for help?
  5. Memory passed memtest without any issues. Successfully backed up UnRaid v6.3.5. Updated to v6.9.2. I then tried the transfer....and it worked. Still large fluctuations with transfer speed, but someone already explained why that was the case. Will keep an eye on it over the next few large transfers I do... Thanks everyone for the support & feedback.
  6. No, there's no reason for not updating to a new version. I will give it a try. However, I'm a little concerned just in case it's a hardware issue, in which case doing the upgrade won't help. Maybe before backing up my flash drive and updating, I'll reboot the server and use the memtest tool to see if there's an issue there. it certainly can't hurt....
  7. No, no VMs, and only 2 dockers - neither are running - don't use them any more.
  8. I took a look at the syslog file under the logs directory. I found the first occurrence of something that looks like an issue matching mine (I really don't know much about this stuff, so I'm just guessing) the incident happened yesterday, and the times the same, or similar incident happens likely lined up with the times I attempted to transfer the file, and failed. The last time was 8:45AM this morning. Here are the 'selected highlights'. To me (again, I'm not an expert so could still be miles off track) it looks like some kind of memory issue, but it would be GREAT to get some expert oversight to confirm or deny, and to (hopefully) advise next steps.... FIRST TIME OBSERVED ISSUE.... Jan 4 09:38:47 Server kernel: cpuload invoked oom-killer: gfp_mask=0x27080c0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOTRACK), nodemask=0, order=0, oom_score_adj=0 Jan 4 09:38:47 Server kernel: cpuload cpuset=/ mems_allowed=0 Jan 4 09:38:47 Server kernel: CPU: 0 PID: 10375 Comm: cpuload Not tainted 4.9.30-unRAID #1 Jan 4 09:38:47 Server kernel: Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0b 05/02/2017 Jan 4 09:38:47 Server kernel: ffffc9002039fb80 ffffffff813a4a1b ffffc9002039fd68 ffffffff8193d255 Jan 4 09:38:47 Server kernel: ffffc9002039fc00 ffffffff8111ef44 0000000000000000 0000000000000000 Jan 4 09:38:47 Server kernel: ffffffff810b2131 0000000000000000 ffffc9002039fbd8 ffffffff8105407d Jan 4 09:38:47 Server kernel: Call Trace: Jan 4 09:38:47 Server kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Jan 4 09:38:47 Server kernel: [<ffffffff8111ef44>] dump_header+0x76/0x20e Jan 4 09:38:47 Server kernel: [<ffffffff810b2131>] ? delayacct_end+0x51/0x5a Jan 4 09:38:47 Server kernel: [<ffffffff8105407d>] ? has_ns_capability_noaudit+0x34/0x3e Jan 4 09:38:47 Server kernel: [<ffffffff810c7ce6>] oom_kill_process+0x81/0x377 Jan 4 09:38:47 Server kernel: [<ffffffff810c84af>] out_of_memory+0x3aa/0x3e5 Jan 4 09:38:47 Server kernel: [<ffffffff810cc181>] __alloc_pages_nodemask+0xb5b/0xc71 Jan 4 09:38:47 Server kernel: [<ffffffff81102d82>] alloc_pages_current+0xbe/0xe8 Jan 4 09:38:47 Server kernel: [<ffffffff81046421>] pte_alloc_one+0x12/0x35 Jan 4 09:38:47 Server kernel: [<ffffffff810ee00a>] handle_mm_fault+0x766/0xf96 Jan 4 09:38:47 Server kernel: [<ffffffff81042252>] __do_page_fault+0x24a/0x3ed Jan 4 09:38:47 Server kernel: [<ffffffff81042438>] do_page_fault+0x22/0x27 Jan 4 09:38:47 Server kernel: [<ffffffff81680f18>] page_fault+0x28/0x30 Jan 4 09:38:47 Server kernel: Mem-Info: Jan 4 09:38:47 Server kernel: active_anon:175370 inactive_anon:4469 isolated_anon:0 Jan 4 09:38:47 Server kernel: active_file:3368827 inactive_file:332778 isolated_file:160 Jan 4 09:38:47 Server kernel: unevictable:0 dirty:331628 writeback:1282 unstable:0 Jan 4 09:38:47 Server kernel: slab_reclaimable:111294 slab_unreclaimable:13733 Jan 4 09:38:47 Server kernel: mapped:17645 shmem:162919 pagetables:2374 bounce:0 Jan 4 09:38:47 Server kernel: free:51705 free_pcp:398 free_cma:0 Jan 4 09:38:47 Server kernel: Node 0 active_anon:701480kB inactive_anon:17876kB active_file:13475308kB inactive_file:1331112kB unevictable:0kB isolated(anon):0kB isolated(file):640kB mapped:70580kB dirty:1326512kB writeback:5128kB shmem:651676kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 6144kB writeback_tmp:0kB unstable:0kB pages_scanned:22529989 all_unreclaimable? yes Jan 4 09:38:47 Server kernel: Node 0 DMA free:15884kB min:132kB low:164kB high:196kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15968kB managed:15884kB mlocked:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Jan 4 17:48:52 Server kernel: Out of memory: Kill process 17308 (smbd) score 1 or sacrifice child Jan 4 17:48:52 Server kernel: Killed process 17308 (smbd) total-vm:402732kB, anon-rss:11096kB, file-rss:4kB, shmem-rss:15988kB Jan 4 17:48:52 Server kernel: oom_reaper: reaped process 17308 (smbd), now anon-rss:0kB, file-rss:0kB, shmem-rss:3324kB Jan 4 17:54:22 Server kernel: cpuload invoked oom-killer: gfp_mask=0x27002c2(GFP_KERNEL_ACCOUNT|__GFP_HIGHMEM|__GFP_NOWARN|__GFP_NOTRACK), nodemask=0, order=0, oom_score_adj=0 Jan 4 17:54:22 Server kernel: Out of memory: Kill process 20368 (smbd) score 1 or sacrifice child Jan 4 17:54:22 Server kernel: Killed process 20368 (smbd) total-vm:400552kB, anon-rss:11024kB, file-rss:4kB, shmem-rss:15920kB Jan 4 17:54:22 Server kernel: oom_reaper: reaped process 20368 (smbd), now anon-rss:0kB, file-rss:0kB, shmem-rss:3328kB Jan 4 17:57:13 Server kernel: awk invoked oom-killer: gfp_mask=0x24280ca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), nodemask=0, order=0, oom_score_adj=0 Jan 4 17:57:13 Server kernel: awk cpuset=/ mems_allowed=0 Jan 4 17:57:13 Server kernel: CPU: 5 PID: 24524 Comm: awk Not tainted 4.9.30-unRAID #1 Jan 4 17:57:13 Server kernel: Out of memory: Kill process 23099 (smbd) score 1 or sacrifice child Jan 4 17:57:13 Server kernel: Killed process 23099 (smbd) total-vm:400552kB, anon-rss:10868kB, file-rss:4kB, shmem-rss:15916kB Jan 4 17:57:13 Server kernel: oom_reaper: reaped process 23099 (smbd), now anon-rss:32kB, file-rss:0kB, shmem-rss:3324kB Jan 4 18:01:01 Server kernel: notify invoked oom-killer: gfp_mask=0x24280ca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), nodemask=0, order=0, oom_score_adj=0 Jan 4 18:01:01 Server kernel: notify cpuset=/ mems_allowed=0 Jan 4 18:01:01 Server kernel: CPU: 3 PID: 26616 Comm: notify Not tainted 4.9.30-unRAID #1 Jan 4 18:01:01 Server kernel: Out of memory: Kill process 24534 (smbd) score 1 or sacrifice child Jan 4 18:01:01 Server kernel: Killed process 24534 (smbd) total-vm:423376kB, anon-rss:11248kB, file-rss:4kB, shmem-rss:15980kB Jan 4 18:01:01 Server kernel: oom_reaper: reaped process 24534 (smbd), now anon-rss:0kB, file-rss:0kB, shmem-rss:3324kB Jan 4 20:58:20 Server kernel: mdcmd (677): spindown 2 Jan 4 20:58:21 Server kernel: mdcmd (678): spindown 8 Jan 4 20:58:45 Server kernel: mdcmd (679): spindown 1 Jan 4 20:58:47 Server kernel: mdcmd (680): spindown 7 Jan 4 21:01:59 Server kernel: mdcmd (681): spindown 0 Jan 4 21:03:09 Server kernel: mdcmd (682): spindown 3 Jan 4 21:03:10 Server kernel: mdcmd (683): spindown 5 Jan 4 21:29:09 Server kernel: mdcmd (684): spindown 4 Jan 5 00:32:14 Server kernel: mdcmd (685): spindown 6 Jan 5 08:42:32 Server emhttp: Spinning up all drives... Jan 5 08:42:32 Server kernel: mdcmd (686): spinup 0 Jan 5 08:42:32 Server kernel: mdcmd (687): spinup 1 Jan 5 08:42:32 Server kernel: mdcmd (688): spinup 2 Jan 5 08:42:32 Server kernel: mdcmd (689): spinup 3 Jan 5 08:42:32 Server kernel: mdcmd (690): spinup 4 Jan 5 08:42:32 Server kernel: mdcmd (691): spinup 5 Jan 5 08:42:32 Server kernel: mdcmd (692): spinup 6 Jan 5 08:42:32 Server kernel: mdcmd (693): spinup 7 Jan 5 08:42:32 Server kernel: mdcmd (694): spinup 8 Jan 5 08:45:27 Server kernel: cpuload invoked oom-killer: gfp_mask=0x24200ca(GFP_HIGHUSER_MOVABLE), nodemask=0, order=0, oom_score_adj=0 Jan 5 08:45:27 Server kernel: cpuload cpuset=/ mems_allowed=0 Jan 5 08:45:27 Server kernel: CPU: 7 PID: 28770 Comm: cpuload Not tainted 4.9.30-unRAID #1
  9. Yes, you're right. Diagnostics attached - created the diagnostics file just after attempting (and failing) to transfer the file this morning..... server-diagnostics-20220105-0845.zip
  10. ...and I should have specified....the transfer failed again.
  11. Don't know if it's helpful/useful, but here's a snapshot of the 'stats' during the transfer....
  12. Hmmm....perhaps I understated the original issue I'm experiencing. I went back and reviewed the wording in my original post. What I DIDN'T say was the transfers are consistently timing out. I understand, from the responses given earlier, that the transfer speed will fluctuate - and that's fair enough, BUT the transfers are often FAILING....giving a message similar to this....(see attached). I followed your advice, went into the UnRaid Disk Settings and enabled 'reconstruct write'. However, even after doing that, the transfers are still failing....timing out? The transfer speed sometimes drops down to zero, and not long after that I'll get the error message. In the past, file transfers - especially of large files - has been a little slow, but they've almost never failed before....and this is happening consistently now. I'm happy to investigate installing an SSD as a cache drive, but does this current behavior point to a different issue?
  13. Thanks for the response. I didn't know that, for accessing the files, it's transparent to the user where the files currently are (on the cache drive, or on the array). That's a really nice system feature! I can now see a LOT of value in adding an SSD as a cache drive. Thanks for educating me, much appreciated!
  14. Thanks! I probably didn't use the correct terminology. When doing a transfer to the array, I need the file to be transferred to a directory I've set up on the share (which, most likely, DOES span multiple physical disks), but I don't really care which physical disk the file ends up on - I'm happy for UnRaid to manage that. Along with the Mover process moving files at the time I set, is it possible to set it up to move the file as soon as the transfer to the cache drive has completed? Or, alternatively, is it possible to over-ride the default move-time set? The reason I'm asking is - I'll often pull in TV episodes, transfer them to the array, with the intention of watching the episodes within, say, the next hour or so, so having the Mover move the files at a low-traffic time doesn't really suit my use case.
  15. I don't have a cache drive, but maybe I should look at one. Are you saying that the transfers slow down (when NOT writing to cache) when the server is running out of memory? Secondly, if I have a cache drive, if I want to copy a file to a certain location, when the file is transferred (from, say, my Windows PC) to the server, it goes to the cache drive first, and is then copied to the desired directory on the array? If this is so, when is it transferred? How long after the transfer to the cache drive is finished? If it's easier, is there somewhere this is documented on the lime website? Many thanks for your help and direction.
  16. Currently running UnRaid OS v 6.3.5. Just tried transferring a movie file across to the UnRaid server. It works file for a time - transferring at approx 113 MB/s, then just after around 10% of a 25Gb file, the transfer speed drops to 2MB/s (according to Explorer). After about a minute or so, the speed ramps back up to what it was before, and then it repeats - slows right down....almost like it's paused, before ramping up again. I've had the file transfer time-out several times. I've NEVER experienced this before. I don't have a cache drive. I also used TeraCopy to do the file transfers, but - for whatever reason - I seem to experience more 'time-outs' using that tool. Do I have an issue on my UnRaid server, is there a disk issue, or should I investigate further - if so, what should I do?
  17. So, I got stuck into looking into the problem. I found the motherboard manual and went through details of how to enter the bios. However, the manual went into a lot of detail about the parameters that could be changed in the bios, and it didn't look like there was any selection you could make that would change the speed (as you correctly point out jonathanm). Out where the UnRAID server is I have a Linksys 16 port switch with a number of spare ports, so I tried a different port - no change. I had a couple of spare cat6 cables in the office, so I opened one and switched out the cable. Initially nothing happened, but then the yellow LED lit up on the switch to indicate a gigabit connection, and the lan port on the server also glowed a different color. So, I pulled up the system stats page on UnRAID, went out to the lounge and fired up the FOTR movie again - I got past the earlier failure point without any problems, and gave up after 25 minutes - it was rock-solid stable. I also took a picture of the stats shown by UnRAID, and I think they tell an interesting picture... What can be seen now is - the network transmit graph shows peaks as high as, say, 110 Mb/s - whereas - in the earlier picture - it looked like the transmit was hitting a ceiling of about 90 Mb/s. I believe this has SOLVED the issue. I'd be seriously embarrassed, but I'm too busy being relieved. Thanks to all, but especially to ChatNoir who pointed me in the right direction. You guys are awesome!
  18. Yes, I'm currently running 6.3.5. I haven't updated as I never had a specific need to update. I'm not sure what the update would give me, but yes - I guess it makes sense to use the latest stable version.
  19. Diagnostics attached as requested. I'm embarrassed to say I had this same question when I first fired this build of the server up and noticed it - but I never followed up. I just figured if the board was capable of 1000Mbps it would have just started up that way (yes, I know that's lazy logic!). So, if the board is capable of 1000Mbps, how do I enable that? Is it a BIOS thing, or are there settings I can use in UnRAID? What are my options here? server-diagnostics-20210209-0800.zip
  20. Hi all, I've been using UnRAID a long time and have been very satisfied with the performance. I'm a home theater 'hobbyist', and have started playing with saving my 4K UHD collection on UnRAID and streaming to my current player - a Zappiti mini 4K HDR player. I'm currently using MakeMKV to rip the main movie to an mkv file and streaming from UnRAID. As I said, I've only recently been playing with this and it seems to have worked OK with my experiments so far. The other day I bought the Lord of the Rings 4K boxset and put the first half of the extended version of the Fellowship on the server. I wanted to see how the Zappiti would handle this, and so I settled in to watch for a while. It got as far as just a moment past the 'Fellowship of the Ring' title, and then it stopped playing, and I got an error message displaying 'Can't Play Video'. Our media center is at the other end of the house from the server, and I'd never seen this before so I've started trying to figure out where the issue is occurring. My main PC is in another area of the house, and I have PowerDVD 20 Ultra installed, so I brought up the UnRAID menu, set it to show system stats and started playing it from there - I know this doesn't replicate the issue I saw on the Zappiti, but I'm a little suspicious of some kind of network issue so I thought this would at least give me some information. Playing back the movie file via PowerDVD did introduce some buffering - especially at the beginning, but after the first minute or so its playback was stable. I captured an image of the UnRAID stats while the file played, and I've attached that here. I'd like to know if these stats are 'reasonable' - i.e. is this a problem, or should I look elsewhere. FWIW - here are some of the stats of my UnRAID system - M/B: Supermicro - X10SRiF CPU: Intel Xeon E5-1620 v4 @3.5GHz HVM: Enabled IOMMU: Enabled Cache: 256kB, 1024kB, 10240kB Memory: 16 GB Network: eth0: 100 Mb/x, full duplex, mtu 1500 eth1 : not connected Although I've used UnRAID a long time I'm definitely not a power-user and linux/unix commands still make me nervous. Having said all that - I'm grateful for any help or advice you could provide....
  21. Hi, Sometime last month I was looking at the Main tab of the Unraid Server in my browser and noticed in the Errors column for disk 1 there were 373 errors. I usually run a Parity Check once a month at or near the beginning of the month, so when I ran this month's parity check I was very interested to see what would happen to this figure. Well, now the errors column shows 373 errors for Disk 1, AND 336 errors on the Parity disk too! Not sure what to do about this. I've captured the Sys Log and attached it. For what it's worth, next to the 'History' button - the following appears "Last check completed on Thu 02 May 2019 06:02:48 AM NZST (three days ago), finding 0 errors." I'm not as tech-savvy as I'd like to be (so please be gentle!), but any help is much appreciated! Thanks, Ross server-diagnostics-20190505-0922.zip
  22. PLEASE HELP!!! I did something STUPID! In the Plex Media Server, using the WebUI, I went into settings/server. I've been trying to experiment to fix some issues with getting a direct connection to work. I changed the "Secure Connections" setting from 'Preferred' to 'Required', and applied changes and left the WebUI. Now I can't get back into it again! I tried restarting the docker container - no good. I tried rebooting UnRAID - no good. Is there anything I can do to restore access to the Plex WebUI? I am kicking myself..... <sigh> Never mind - I found a way to fix it by logging onto the server from Plex online. Still kicking myself.....
  23. Forgive me if this isn't the correct place to post. I'm using the Binhex Plex pass docker. I've only just installed the Plex Media Server, and got my first client up & running (a few outstanding issues but nothing too serious). I downloaded the plex app on my ipad and was successfully streaming a couple of full HD movies to it, which was great. However, I noticed the CPU utilisation for transcoding was enormous! At the moment I don't use a cache drive, but now that I'm starting to use Plex, I'm seriously considering it. I did see a thread saying you should use RAM for the transcode instead of an SSD, and now I'm confused. My system currently has 16Gb ECC RAM, my UnRAID CPU is an Intel Xeon E5-1620 v4, I only have a few dockers and no VM's. I imagine I'd only have a need for 3-4 transcoding streams simultaneously (+ a couple of direct plays). My questions are as follows: 1) Is it better to use RAM or a SSD to do transcoding for Plex? 2) If RAM is the way to go - do I have enough, and how do you set it up? 3) If SSD is the way to go - how large does the SSD have to be, and how do you set it up? If I got an SSD - at this stage Plex transcoding is the only thing I'd be using it for. Thanks for any help/advice, and please feel free to move this if it's in the wrong place.
×
×
  • Create New...