chickensoup

Members
  • Posts

    527
  • Joined

  • Last visited

Everything posted by chickensoup

  1. Had the same issue, mostly Plex completely broken. Looked like permissions problems in the log. Tried to migrate from Plex-Media-Server to a fresh binhex-plex but error persisted. Appdata folders didn't look like they had been taken over by root but the whole lot was a giant mess. I'm in the process of rolling back to 6.9.2 now and will keep an eye on the progress since I don't have enough time to spend mucking around with it right now.
  2. I ran a [correcting] parity check recently and it fixed up 13 parity sync errors. I wasn't expecting this and as a result, ran another one the next night [non-correcting] which picked up another 9 parity sync errors. I'm not sure whether this is related to my recent migration of disks to XFS (see below) or if I have a disk on the way out. There aren't any SMART warnings that I'm concerned about at this stage, I did a zero-byte search against my shares and found two TV eps with zero bytes but this might be unrelated. On another share however (different disk set) I have 227 zero-byte files. Some are expected, random html and config placeholders but there is some music and old documents which wouldn't be expected. Almost all of these appear to originate on Disk 2, so I'm running a full SMART check on that disk now. The disk is pretty old and so is the data, could this be bitrot? Any suggestions on what might be causing this? If the disk checks OK, I'm wondering if a new config might be in order. Just worried about potential data loss at this stage. Background relating the filesystem changes: I recently migrated a bunch of disks from ResierFS to XFS following what guides I could find, I wasn't overly concerned about maintaining perfect metadata or even parity during the moves, just that the files moved OK. I used a Krusader docker to shuffle the data on to a blank XFS formatted disk and then changed the FS on the old, now blank Reiser disk to XFS, let unRAID format the blank disk then ran a parity check. With each move there were about 12/13 parity errors corrected which I attributed to the shuffling of ~2-3TB of data and wasn't overly concerned but now I'm wondering if I should have been. unraid-diagnostics-20190811-0100.zip
  3. What sort of symptoms? I've had SATA cables tied like this for years and never had a problem. Just want to know what I should look out for I guess.
  4. Happened again today, this might be useful.. Image location is listed as "http://10.0.0.5/%3Cbr%20/%3E%3Cb%3EWarning%3C/b%3E:%20%20filemtime():%20stat%20failed%20for%20/usr/local/emhttp/webGui/images/case-model.png%20in%20%3Cb%3E/usr/local/emhttp/plugins/dynamix/include/Helpers.php%3C/b%3E%20on%20line%20%3Cb%3E248%3C/b%3E%3Cbr%20/%3E/webGui/images/case-model.png?v=" unraid-diagnostics-20190727-1306.zip
  5. Lian-Li PC-201A, Silver version of the 201B and was discontinued a long time ago. I managed to stumble across one second hand for $50. Looks like this Internal looks like this
  6. Hey yall, Looking for advice & suggestions on 16 channel controller cards and if they'll need any special flash, etc. FYI I'm probably going to change motherboards so I can add a GPU for pass-through. My Hyper-V server is using a Gigabyte Z77X-D3H which has more PCI-E lanes. Current setup however, using all SATA ports - photo below, I'll probably need longer breakout cables than what would be included anyway. - Gigabyte H67MA-USB3 (6 SATA onboard) - 2 x Adaptec 1430SA (4-Port SATA2) The ones which look to be suitable candidates so far are: - Adaptec ASR-71605 $56.99 USD = $80.95 AUD + shipping - - Another ASR-71605 which includes breakout cables $95.98 USD = $136.33 AUD + shipping - LSI 9201-16i $128.68 USD = $182.77 AUD + shipping There are cheaper options if I stick with SATA2 - LSI MegaRAID MR SAS 84016E $55.00 USD = $78.12 AUD + shipping - HP ATTO H30F There are heaps of these without cables for < $50 AUD I'm located in Brisbane, Australia so anything domestic would be preferable. Shipping stuff over from the US is pretty expensive right now, our dollaridoo sucks. Thanks.
  7. Just wanted to add, I've noticed this as well. Just displays a broken image link. Can't really pinpoint when it happens, between reboots maybe? I'm running 6.7.2, re-selecting the image fixes it immediately. If/when it happens again I'll see if I can post a screenshot, but I'm not sure a small torn icon image is going to be much help =]
  8. Keeping this alive with my +1 as well. Also bonus points if we can add a little of our own flair, just like the banner
  9. I just checked my work inbox since it goes to both - looks like that's my mistake, I did get one with errors (33) and it must have gotten missed in the noise. For some reason I got the pending sector email twice, once at 4.46am and again at 5.07am; same disk, same count.
  10. Just to add, I had an e-mail saying one of my drives had 1 current pending sector. I wasn't really concerned since I just copied 1.97TB to the 2TB disk and the count hadn't increased. I check the UI today and notice that there are apparently 30,000 errors on the drives.. but no email notification?
  11. Hey Tom, I have more of a personal/career question to throw in. I have worked in IT my whole life and primarily fall into the technical support / system administrative category. I have limited Unix experience but I'm comfortable navigating my way around now and I have a high interest in hardware and storage at the firmware level. What advice would you give to further my knowledge and experience in these areas and have you found there is much industry demand for these types of skills? Side question, you have an interesting background and I would love to one day shake the imposter syndrome, do you ever still feel this way? I mean, you've practically built an Operating System 🙂 Thanks, B
  12. Hey LT, I just started using e-mail notifications and it seems to be working well but is a little excessive on some of the classifications. Some of the 'alerts' I get which I would argue should maybe be re-classified are as follows: Importance: Warning, Parity check started (this is a monthly scheduled check) - should be Notice Importance: normal, Parity check in progress (3%) - 6 sync errors detected. Shouldn't sync errors trigger a Warning? Importance: Warning, Docker application updates - again probably should be a notice, not a warning sent with High Priority. This was also immediately following an OS update, which is why the dockers were out of date These are just a few, I'm sure they probably all need a check over. Perhaps LT could jazz them up a bit with some of that new branding flair at the same time? Obviously the option to choose between fancy and plain text would keep most people happy, I expect. Just some thoughts. Keep up the great work guys. B
  13. I actually set this up very recently and it works, but I was about to suggest some changes to the classification of certain messages when I found your post. I have an @outlook email address, but these settings work for me.
  14. Made one last night from a inspired by a wallpaper i really like, thought I'd keep it simple. Recommend changing "Header custom text color" to FFFFFF as well.
  15. Was able to generate a new config and rebuild Parity to both P disks without any issue, all disks are up and there doesn't appear to be any issue with the data. Thanks for all your help guys Marked as Solved.
  16. Thanks! I have a quick question about re-building the array when I boot it back up. Assuming I trust the data on Disk 8, am I able to run a new config and re-build both the parity drives (at once) based on the data that is on the disks currently? Disk 8 is showing a red X (as per the second screenshot on my OP) but I don't think there is an issue with the drive at all, I've tested it outside of the array- I certainly don't trust my Parity right now but I want to re-introduce all the disks.
  17. Sorry for the long reply but I think I've finally worked out what has happened. It always felt like it was power related but the one thing I could never understand was why I was getting errors on some disks but not others- even when they were connected to the same chain off the same power supply cable. I thought at one point that maybe bending the cables in to shape to fit the case might have had some impact, since the power supplies are reasonably old (though good quality). It took a few days of thinking about the symptoms and scratching my head; the comment about poor ground also got me thinking and then while sifting through my power supplies and cabling I had a realization. I had 3 x Modular 6-Pin to SATA cables connected to my ToughPower 750W power supply. Turns out, the power supply likely only shipped with two of these and the one additional cable must be from a different PSU with a slightly different pin-out (I'm pretty sure there is no damage to the drives). My guess is the drives had 12V and Ground but that the 3.3V and 5V lines were swapped around. I feel like such an idiot. The picture below shows the two TT cables connected to the power supply (top row G, 12V, G on each) and two more modular SATA cables I had in my stash. If I had to put money on it, I would guess that the one on the right hand side in the picture was also being used which is why the symptoms were so strange. Close enough voltage to be OK for a little while, but ultimately not what the drive was looking for. Edit: All of the cable below are SATA to 6-Pin modular PSU cables, the one on the right in my hand at a distance, looks pretty much identical to the ones which shipped with the PSU.
  18. Hey Benson, Is that table of Parity speed history a plugin? I can't check mine right now sorry as it's out of action. If it's part of 6.7, would you mind sharing how to get to it? Thanks!
  19. I actually tested both the power supplies before rebuilding the server and they looked OK, even under load but it's curious that other than Parity 2 (which dropped due to a SMART 199, which could be the SATA cable) all the other power supplies with errors are on the same PSU. Disks 10, 11, Cache and Parity 1 are all on a different PSU and show no errors. I have another power supply I can use but now I'm not really sure about how to best proceed with my disks having dropped out all over the place. i.e. - Parity 2 dropped out so I unassigned it for now - After the reboot when all looked well, I ran a correcting parity check which fixed ~10 errors but when I checked the server after it had finished there were read errors showing on all the data disks. I'm not sure if I can trust my parity is valid at this stage and I'm not sure when the errors started happening, can anyone tell from the diagnostic? - Disk 8 dropped out (also not sure if this was after the parity check) but SMART looks OK, I'm running a full check on it now Not sure if I should dump the data off disk 8 and rebuild it from parity as I feel like I actually trust the data disk more than the current parity state. Is there an option to reintroduce the disk to the array and rebuild parity off the data, assuming the disk is OK? Sorry if any of the above is confusing, just never had so many errors all at once, it's been rock solid up until now (going on 10 years..) Edit: Photo of the setup attached, if anyone is curious - disk 8 is missing as i'm running a WDDiag on it at the moment.
  20. Will change the onboard SATA controller to AHCI tonight, anything else I should look at before I reboot it? It is still currently powered on. Not to over-complicate things but in full disclosure, the system is actually running off two power supplies, for no reason other than that the case supports them and I was testing power usage balancing the load between the two. Based on what you have said I suspect my TT 750 might be playing up, which is strange since it is actually powering less than it has been for the last few months. I tested both the other night after it first failed and they looked OK but I might try swapping them around to see if this fixes anything. More info here >
  21. Sorry for the late reply, been really busy with work. I've updated the OP with diagnostic after booting the server back up last night, it looked OK initially and I ran a non-correct parity check overnight, in the morning all disks were OK at about 30% with 8 errors detected so I stopped the check and changed to a correcting parity check, which I now regret- I'm hoping the data isn't corrupt. This afternoon looks just as bad as the other day only with different disks. Please note that between the two screenshots/reboots I also tidied up the cabling so the specific disks aren't necessarily on the same ports as they were the first time. Apologies if this makes things a little messier to diagnose but the logs should clear up any confusion.
  22. I'm using two Adaptec 1430SA's, the thing is that Parity 1 and Parity 2 are on the same card, one has errors and one doesn't. Drives on the second card have errors and so do ones on the motherboard, but some don't...
  23. Help please I recently transplanted my hardware over to a new case and at the same time changed the board, cpu and memory. Initially I had a problem where one of the controller cards was showing all disks on boot but not in unraid (displaying as missing). I updated the BIOS on the board from F3 to F8 and re-seated the card and cables, which seemed to work. Everything booted up ok and all disks went green. I allocated a new/spare disk as a cache drive, which formatted OK and i had green lights across the board, no errors. A few hours later after some light plex use, Parity 2 drops out first (red X). I figure maybe the cable is bad and I'm dealing with dinner/son/etc so leave it for the moment. Shortly there after when I get a chance to check it, the shares have dropped off and I have read errors across most of the disks. I'm wondering if the BIOS is setup slightly differently on the new board (legacy, ide mode, etc) so tomorrow afternoon i'll compare against the old board but I'm mostly at a loss as to what is going on. Motherboard changed from a Gigabyte GA-H57M-USB3 (rev 2.0) to a Gigabyte GA-H67MA-USB3-B3 (rev 1.0) and I ran a few passes of memtest on the new board without any issues yesterday. Edit: I unassigned Parity 2 since it was 'dropped' and after a reboot and replacing a couple of SATA cables (both parity drives) it was looking OK but then after today, errors all over the place again. Syslog is from the first time it failed, diagnostic is from after the reboot. Now disk 8 has dropped completely, I have no idea what is going on. Added an extra screenshot. unraid-syslog-20190603-1428.zip unraid-diagnostics-20190607-0945.zip
  24. Hi guys, I recently acquired a replacement case which supports dual ATX power supplies. I'm currently at 14 drives and a few months ago my original single 12V rail 550 just wasn't holding up every boot anymore. I swapped it out with a spare 750 I have and it's been OK but the new case got me thinking. I'm at a place in terms of drive count where it's hard to avoid using power adapters in one form or another. I was curious about how much difference (in terms of power draw from the wall outlet) would make, so I ran some tests before my case transplant which is currently underway, to determine if it may be worthwhile. The difference is surprisingly negligible and would give me the benefit of ditching a number of molex-sata adapters I currently have in use. I didn't think it would be worth the extra power, but I think I may actually go down this road after all. Since I'm certain someone will ask, you can power them on together using one of these The wall outlet power draw was measured using a TP-Link HS110 Smart Wi-Fi Plug I'll be posting the actual build log (case transplant + upgrades) shortly with photos of the new case but I'm still waiting on some parts and it's not finished yet... so stay tuned if you are curious Results are below!