tncolts

So, this is a silly, insignificant question. I recently upgraded from 6.3.5 to 6.5.1, parenthetically, the upgrade process was silky smooth; anyway, for reasons passing understanding, system info is showing “20 GB Multi-bit ECC (max. installable capacity 24 GB).” Before the upgrade, system info showed 24GB installed. I was wondering, and please forgive me for not searching the topic, has anyone else noticed system memory being incorrectly reported after upgrading past 6.3.5? 24GB is installed, like I said it’s probably a meaningless question, but I figured I’d ask anyway. I like to finish my saying: as a long time customer of unRaid, I continued to be amazed by the tremendous value this OS offers — I couldn’t possibly be happier...if I tried!!! A sincere thank you to every single person dedicated to the continued development of this product!

Good day to all of my good fellow unRaid ladies and gentlemen. As I stated in the subject I'm running unRaid 6.2.4. Last week I decided I give the Plex Media Server docker a go, I recently acquired an Apple TV 4 and I figured...what the heck, Just a brief summation of my hardware: ASUSTeK Computer INC. - P6T Intel® Core™ i7 CPU 950 @ 3.07GHz 24GB RAM 47TB Array First, I must say the Plex Media Server software is quite impressive, or at least in my opinion. I like all the bells and whistles as they say. Now, on to my question... When I play a file via Plex, my unRaid CPU temp spikes to between 90C and 95C for between one and three minutes. After which, CPU usage returns to a more normal state (10-30%). During the time at which CPU has spiked, of course, the CPU temp rises. It normally tops out at around 95C, after CPU usage returns to its normal state the CPU temp returns to around 45C. Since I've had this particular build that is a normal temp for my system (45-55C). The question (thank God, I thought we'd never get there): is this rise of CPU temp as I've described above normal for the Plex Media Server? Maybe I have something set incorrectly. You'd think more of the grunt work of transcoding could be done via the system RAM but I suppose that isn't possible. I figured this was the best place to start. If I have mistakenly placed this question in the wrong area within the forum, please move it to the appropriate place. If anyone out there has an answer to my inquiry, I'd appreciate it a great deal. Thanks to all

This issue is resolved. Thanks to all who assisted!

Will do when complete. Thanks!

Wanted to provide an update: I have followed the above recommendation, explicitly. So far, I simply removed the drive tray and re-inserted the drive using steps B and C from the above recommendation. Upon rebooting the system, re-assigning "Drive B", and re-starting the array, the rebuilding disk procedure commenced as expected. Thus far, I am 20.6% (618GB) into this re-build process. I'm cautiously optimistic that this process will complete and all disk will return to a "green ball" state. I say cautiously, because I know that 20.6% isn't that far into the process, but I'm hopeful because all previous attempts at re-building failed after about 1.5%. No S.M.A.R.T errors have been reported thus-far, no disk errors have been recorded to this point. No, I don't believe in jinxing myself either, it will either work or it will not. I'm simply trying to report my experiences so if anyone else EVER has a similar issue(s) they may know where to start. I also took the time to update all my documentation about my unRaid system, including the exact system specs -- even down to the exact drive slot position of each disk, also including a backup of the "flash" drive; I updated all relevant information and created a copy of this data in my Dropbox. In the past, this info was not stored on an external source or a cloud service. So, I feel that maybe perhaps I've improved my knowledge about my system, what it contains, and I'm confident knowing that this system information and configuration is at my disposal from virtually anywhere. I will post another update when this issue is fully resolved. I thank you all of you for the assistance that has been provided.

I certainly have more confidence that this problem will be resolved. I'm hoping a simple re-seating of the "failed" drive will do the trick. This is why people should check their hard-headed nature at the door and just post the question in the forum. When one learns, we all learn. Anyway, my thanks again!

Apparently, I'm a liar...but not really. The last machine I built was 1000 or 1100, I chose a different one for reasons that I can't remember now. So I did some digging and found the receipt. It is the CORSAIR AX series AX860. In the interest of making sure that I'm still awake and I don't forget the actual equipment I have, this is my system summary: unRAID Version: unRAID Server Pro, Version 5.0.6 Motherboard: ASUSTeK Computer INC. - P6T Processor: Intel® Core™ i7 CPU 950 @ 3.07GHz Cache: L1-Cache = 256 kB (max. 256 kB) L2-Cache = 1024 kB (max. 1024 kB) L3-Cache = 8192 kB (max. 8192 kB) Memory: 65536 MB (max. 4096 MB) 2048 MB (Single-bank Connection) = 24576 MB, 2048 MB (Single-bank Connection) 2048 MB (Single-bank Connection) = 2048 MB (Single-bank Connection), 2048 MB (Single-bank Connection) 2048 MB (Single-bank Connection) = 2048 MB (Single-bank Connection), 2048 MB (Single-bank Connection) 2048 MB (Single-bank Connection) = 2048 MB (Single-bank Connection), 2048 MB (Single-bank Connection) 24 GB = 2048 MB (Single-bank Connection), 2048 MB 1066 MHz = BANK0, 2048 MB 1066 MHz = BANK1, 2048 MB 1066 MHz = BANK2, 2048 MB 1066 MHz = BANK3, 2048 MB 1066 MHz = BANK4, 2048 MB 1066 MHz = BANK5, Network: eth0: 1000Mb/s - Full Duplex overkill.....I know, but again if she can have the shoes....I get my own data center. Thanks everyone!!

I appreciate all these suggestions and I'll post when I eventually solve this little riddle. So many great folks on this forum. It's appreciated...well at least by me. If anyone else has ideas or suggestions I'm happy to hear them. I also got do some research of power supplies. I'm not ashamed to say I'm 100% ignorant in that area. But that's ok, I can learn.

I'll be trying to get to the bottom of this as soon as these files are moved. Thank you very much for your thoughts and your time.

Screenshot and syslog attached Syslog show all sorts of write errors around 16:00 that when parity failed. Screenshot shows 384 errors; that number hasn't changed since I stopped the parity check when all these errors started popping up. I did eventuality let the parity thingy run. And well that's about it. So here are the requested files unraid_syslog_030415-2011.zip

First, thank you for responding. I could buy the lose cable thing if I had opened the case. I didn't. I just got out an unused drive tray installed the new drive and rebooted. It's weird that it's able to use that drive (the red balled one) since parity disk is new and a parity check with the new parity drive hasn't been completed yet. I'm just going to keep moving files to a the different disk after all it's been going for 8 hours now with a grand total of 0 errors. I know that probably seems stupid but it seemed like the thing to do. I understand and appreciate the logic of your response. I've had experience with loose cable/bad cable problems before. But I never even touched that drive, did not remove that tray, it's not even in the same row of drives. Is it possible that it's now loose? Yep. I'm discounting nothing at this point. The case is Norco Technologies Inc. RPC-4224 Thanks for responding.

Alright, I need some help/advice/therapy/Xanax or maybe a combination but I got an unRaid problem that's just bugging me. I've had my server for a while -- let me say, unRaid is one of the greatest things EVER for computer freaks. Here's what I had before yesterday: 1 3TB Parity Drive 7 3TB Data Drives 1 2TB Cache Drive I have space for 24 drives, I got an i7 processor, 1100w PS, 3 SAS cards...my wife says I have a problem. I tell her she can have 126 pairs of shoes, I can have a data center. Anyway, I wanted to mention specs because I believe I have everything I need to do what I want to do, because....well it's been working since I've had it. Upgraded unRaid server is: 1 4TB Parity Drive (upgrade) 9 3TB Data Drives (moved old parity to data disk) 1 2TB Cache Drive Did the research everything was going great. Then a red ball. Disk failure. It's a disk that has NEVER failed, it wasn't even touched during this process. It even has the same "Disk" identification. What I don't get is the drive works fine. I'm watching a movie off it via windows explorer. I moved a file to that disk using \\server\disk 2\. I don't get it. I have no idea what to do next. Right now, I'm literally moving all the data from disk 2 to disk 8. I'm preparing to remove the drive, I don't want to. By the way the moving of the files from \\server\disk 2 to \\server\disk 8 works fine. No errors, no problems. I tried parity check three times. Failed each time, less than a minute into the process. Anyway, I'm sorry this is long. I hate when things just stop working and then you can't figure it out. I understand stuff breaks. Maybe it's me...I'm sure I did something wrong, but I have no idea what that was. Does anyone have any ideas? Thanks to anyone that actually read all of this, I'm on like my 27th cup of joe. So yea, I'm amped right now. Just want an answer or at least a plausible explanation.

Parity Check completed without incident and extra controller cards have been removed. I may try some of the additional things that were suggested in this thread at some point, but for now.... a working system is a happy system!! Thanks to everyone in the unRAID Server Community for their input and suggestions.

I will remove the unused cards as Jonathan suggested. I have to say that right now I'm 40% on parity check and no drives have been disabled so that's an improvement at least. I'm hope that is the light I see at the end of the tunnel. Thanks to everybody for their insight on this; thankful that I had a community to ask.

OK jonathanm, I have reconfigured the RPC-4224 so that all 7 drives are running off of one of the AOC-SAS2LP-MV8 controller. I guess I just have to wait and see what happens. Did you remove the extra cards from their slots? No, I did not but there are no drives connected to those backplanes. It's been running for about 30 minutes now and so far no errors. Of course if this does fix the problem what does that mean? Does this motherboard just not handle these cards very well? I mean that was kinda the point of having three cards to support future upgrades.