rcwills

No, but I just went in and enabled system notifications. What should I look for?

tower-diagnostics-20170601-0129.zip

I rebooted after a power outage and noticed the red X. What is the prognosis on this drive? Is it safe to rebuild or should I replace? ST8000AS0002-1NA17Z_Z8400ZWN-20170601-0129.txt

Turning on user shares fixed it. Thanks!

I can see the individual folders are still intact on each disk, but the shares are missing in the mnt/user folder. I upgraded by doing a clean install onto the flash drive then copying my config folder from the backup. Any ideas about what went wrong?

OK, ran reiserfsck and result was "Fatal corruptions were foun, Semantic pass skipped 4 found corruptions can be fixed only when running with --rebuild-tree" running again now with --rebuild tree "Objects without names 18 Files linked to /lost+found 18 Objects having used objectids : 6 Files fixed 6 Deleted unreachable items 16 Flushing..Finished Synching..Finished reiserfsck finished at..." So far, so good? I'll run a complete S.m.a.r.t. Test, then try the extended attributes fix. Then I should be good to go, right?

OK, I rotated the SATA cables, and re balanced the power rails to see if that had an effect. Here is my newest syslog. Sorry I don't know how to format it better. Also, it looks like the parity drive is sdc. Additionally, drive 1 (sdb) has been giving me other problems. It was the drive that reported a red ball earlier in the week, and it had appeared to run out of space when it reported having 20+ Gigs of free space on it, and there are also some phantom files that I can't delete in disk 1, not even if I use midnight commander to delete them. Not sure if these are related symptoms or a different problem altogether, but I thought it was worth mentioning. Thanks for all the help. I really appreciate it! syslog527.txt

OK, I'll check all the cables and maybe swap the arrangement of power cords. What about my parity drive turning blue? Should I just rebuild it, or is there a more proper step?

part 2 of logs: Thanks! smarte.txt smartf.txt smartg.txt

OK, someone told me the tower was down, so I checked the status, and disk1 had a red ball, and parity was blue and apparently unassigned/new. I freaked out, shut it down, and the next time I booted it up, disk 1 showed up green, but the parity is still missing. I assume that one or more drives is about to fail, but really I'm over my head and could use some help/advice. here is my syslog and smart reports. I'm unsure what else I can do without losing data. I'm running Unraid version 5.0.4 syslog.txt smartb.txt smartc.txt smartd.txt

can't you put a 16x card in a 1x slot and let it run on one channel? bulky and not ideal, but the bios should accept it

Here's a nice one for a small to medium amount of drives. 28A on a single 12V rail haha was coming back to this thread to mention this deal, but you beat me to it

thanks. I'll try swapping out the PSU for a 700w one

I'm running a 6 drive array with a 380w antec earthwatts green PSU. I'm hoping it was just a fluke then. I haven't used the tower for the last 10 days, but I'll turn it back on and re-enable the drive, and report back.

Hello, I'm running 5.0 beta14, and was sad to see my first red ball next to a drive. It is a seagate 2TB drive, and is still under warranty. While the SMART test seems to show a high number of Raw_Read_Error_Rate and Seek_Error_Rate, it still passed the seagate diagnostic that they make you run before you can RMA a drive. Is my drive in fact dying? Will seagate accept my RMA, or will they deny my claim? Any experience is appreciated. syslog.txt smart4.txt