fozzyb

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

fozzyb's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks for the reply. Definitely worth pushing the CPU up to a i5 if it will extend the longevity of the system. Would one of these HBA's work in lieu of the H310? Looks like the seller tests and flashes it to IT mode so it's more or less plug and play: https://www.ebay.com/itm/Genuine-LSI-6Gbps-SAS-HBA-LSI-9201-8i-9211-8i-P20-IT-Mode-ZFS-FreeNAS-unRAID/162958581156?hash=item25f1169da4:g:7sYAAOSwjMtcT8T8 Thanks again!
  2. Hi everyone, Hoping some of you may be able to help me out here with a new build. I haven't touched my machine in over 10 years and, needless to say it's time for an upgrade. I'm currently using the machine as a server only. No dockers, VM, etc but I'd like to add these as well as a cache drive which I haven't been able to add due to the limitations of my current system. I'm clueless to a lot of the amazing upgrades to Unraid over the years, but I want to make sure I have the hardware capable as I learn and add these upgrades. After a bit of research, would this be a viable build and, if so, what would be the best raid controllers to complement the rig? https://ca.pcpartpicker.com/user/fozzyb/saved/jmBrVn I'm currently using a very old PCI raid controller that would be more or less obsolete now. https://www.newegg.com/syba-sy-pci40010-sata-ii/p/N82E16816124028 Current drives - 2x 4TB WD Red 7x 2TB WD Green I'm sure I may have left out some important information, but it would be greatly appreciated if anyone can chime in on the above. Many thanks in advance!
  3. Hi guys! With regards to my previous post, I was able to recover all of my data from the failed drive. A couple of days went by and all was good. Two days ago the parity failed, and I followed the steps listed using the "Trust My Array" procedure found here: http://lime-technology.com/wiki/index.php?title=Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily The procedure was successful and a parity sync initiated upon starting the array. About 90% thru the check, the GUI became inaccessible, however I was still able to Telnet to the machine. Earlier today, I stopped the array and shut down the machine thru Telnet and rebooted it where the GUI then became accessible. The array was back in the state it was and asked me if I wanted to start the parity sync again. About 10 minutes later the GUI didn't work again. Not sure if this is a networking issue or an issue with the unraid box itself. Attached is a syslog and any help is greatly appreciated!! Thanks, http://dl.dropbox.com/u/11559988/syslog.txt
  4. Hi, I had a drive fail and accidentally removed it from my array and initiated a restore of the parity drive without the drive in the array. The drive is now marked as "not installed". I have data on this drive that I need to retrieve. What would the best way be to read the reiser File System to grab the data off the drive? I'm thinking use a linux Live CD to boot and read the drive. Any suggestions are much appreciated!! thanks!
  5. ohlwiler- Thank you for the suggestions! Before I got a chance to read your thread I did the following: Swapped the motherboard, ram, processor, onboard vid and USB flash with my roommates. He was previously running unRAID with no issues with the same configuration, we're in the process of combining our storage space so he had the stuff laying around. As of now the only variables that have NOT been changed on this box is the Norco back plane for the drives and the sata cables. The box is currently doing another parity rebuild. If I get failures after this I will try swapping the sata cable, and if that fails I guess the only constant would be the Norco backplane. Thanks again for the support thus far guys!
  6. Hi guys, Just an update: I purchased a new power supply which, I would say, is more than adequate for the hardware I'm running. It's a SeaSonic X Series X-850 (SS-850KM Active PFC F3) found below: http://www.newegg.com/Product/Product.aspx?Item=N82E16817151102 I did a parity check which took 24+12 hours and came home today from work to find the parity drive red again. I opened up the syslog and found a lot of write errors as well as many other miscellaneous ones that I need some help figuring out. Please find attached a new syslog for your review, if any of you can help out. Any help figuring this out once and for all is greatly appreciated. Thanks again. http://dl.dropbox.com/u/11559988/syslog.txt
  7. Hello Joe, thank you for the reply. I just did some digging around on that thread and it looks like I need to get a new PSU ASAP! However, would this be the reason that my parity drive keeps failing? I am going to go ahead and change the PSU, but I'm just wondering if you think this has contributed to the constant parity failures. Thanks!
  8. Thanks for the replies so far. The PSU is an Antec TP Trio 650: http://www.antec.com/specs/TP3_650_spe.html I'm guessing it has 3 rails which may be what's causing the problem. If it is in fact the PSU, would you guys have any good suggestions for a PSU that would be ideal for this setup? Thanks!
  9. Hi guys, Long time lurker, first time poster.. I've recently added 8 new drives to my unRAID box and since then I can't seem to run the box for more than a few hours before the parity drive goes red. I've even bought a NEW parity drive and have the same issue. I am running uTorrent on a network machine that's doing i/o to the box. Nothing too crazy. I have a 650 WATT PSU. 13 drives are WD green drives and the other 7 drives are a mix of WD BLACK/BLUE and 1 maxtor drive. Could the failure be related to lack of power? I never had this issue before I added the 8 additional drives. Those 8 drives are running off of a Supermicro AOC-SASLP-MV8 Marvell 6480 8 Channel SAS/SATA RAID PCI-E Card which was sitting idle in my machine before then. Temps on the box are low to mid 40's The syslog is here: http://dl.dropbox.com/u/11559988/syslog.txt. Really not sure how to start troubleshooting this issue. Any help is greatly appreciated.